If you have 250 hosts with the same roles applied to them, then yes I'd go with that.
You can make the inventories less huge depending on your naming convention by using regexes , e.g. [webservers] www[01:250].example.com Or if you'd rather you can have multiple static inventory files in a single inventory folder, that works too. Ansible loads them all to get the list of hosts, so that might fit better with what you're trying to do. On 6 July 2017 at 08:24, <[email protected]> wrote: > We have that but it does not answer my question. We still would have one > inventory file with all hosts for 1000 projects per qa, dev and prod, right? > (we have less than 1000 ... is just a forced example) > > Is it possible to organize ... that OPS can "walk" all hosts also the > repository has - if possible - splittet all details per team (or per > component) - for > better readability without being forced to run the playbook several times? > > On Thursday, July 6, 2017 at 8:50:27 AM UTC+2, Dick Davies wrote: >> >> Try setting up one inventory for QA, another for DEV, and a third for >> production. >> You can use the same playbooks with different inventories so it'll keep >> the >> environments isolated but you'll get better consistency between each env. >> >> On 6 July 2017 at 07:36, <[email protected]> wrote: >> > Hi, >> > >> > assume we would have 1000 projects in a big company and an OPS guys >> > tells us to copy every detail for provisioning for qa, dev and prod in >> > one >> > repository. Some told arguments: >> > >> > just to clone one repository >> > all Unix machines require a basic setup and therefore the concrete >> > inventory >> > file has to have all hosts and roles >> > (the intention is to maintain the host names at multiple locations) >> > >> > a) Is this the way to go or is there a better solution? >> > b) when a) could you please provide examples (url's) where to read? >> > >> > Kind Regards, >> > Thomas >> > >> > -- >> > 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/54c81f68-5bd5-451e-9194-e68c7ed9cac9%40googlegroups.com. >> > For more options, visit https://groups.google.com/d/optout. > > -- > 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/17c6a4f9-53ed-42ae-a7f9-f66f81ff59a8%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. -- 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/CAK5eLPRgJUmn6N-%2BvFo%2B_se6krpHFZoD-b%2BBWq3SsR3Y1ZpXLg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
