On Jan 18, Jan Kowalsky wrote:
For example: we have some ltsp environments - every of them quite
similar configured: a host with very few vms: one for desktop another
for public cloud and maybe some other for sql and special applications.
If we find some issues in one installation it's pretty probable that we
want to fix this in all installations. E.g. we need newer packages, a
custom patch or maybe we want to change all admin ssh keys. In this case
it's much easier if they're all in one project and depend e.g. on one
group_all with admin-users defined or one group with all ltsp-servers
inside.
So if you have a good idea how to organize this, we would appreciate
this a lot. Maybe we could think about symlinking some parts of the
inventory to the particular projects ...
Essentially yes, multiple project directories with parts of the inventory
symlinked between them would be a solution to this.
If you want to use inventory groups, you should consider defining the
'ansible_group_priority' variables to define the parent/child group
precedence. You can then define a set of high-level groups that define
variables, and low-level groups that group the hosts together.
https://docs.ansible.com/ansible/latest/user_guide/intro_inventory.html#h...
Good luck. :-)
Maciej Delmanowski