You could just keep your individual inventories for each client but then use a directory containing symlinks to all the client inventory files.
I use this trick as I have 2 environments that run inside the same physical datacenter. Mostly I want to make changes to just one environment at a time, but for stuff like patching it makes sense to hit all the hosts in the datacenter. Only slight downside is if you use group_vars then you have to symlink to the group_vars as well. Jon On Sunday, September 3, 2017 at 11:40:30 PM UTC+1, [email protected] wrote: > > They are at the moment at least webservers each hosting a project or group > of projects relating to a particular client. It makes resource allocation > and billing easier. It affords us the facility to throw hardware resources > or scale up a client's needs. But although each server is essentially a > LAMP stack, some use different software or have different requirements and > would need a playbook of their own. > > Managing all projects, their webservers, future additional servers and DB > servers etc, plus prod/staging/testing versions in one inventory isn't > ideal either. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/c2fa8522-549e-4a2e-aa7d-28f28dc29e37%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
