Am Freitag, 21. April 2017 01:32:24 UTC+8 schrieb Brian Coca: to 'not connect' to a host, just don't include it in the target (via > hosts:/--limit or inventory). >
>From this I read that there is no way to simulate a playbook against a given inventory without connecting to the inventory's hosts. Let me explain why this would make sense for me. Although this is may be a rather exotic case, there may be others who have the same problem? The point is that through group and host variables some installation steps are configured to be executed on some hosts while not on others. On a software system with lots of different services that are distributed over the target system's host associating services (i.e. programs to be installed and configured) to groups. Hence there are a large number of groups, and each host is in a number of them - roughly speaking as many as it will be running services in the end. Because there are quite a few permutations of groups-per-host searching for bugs in the inventory, var files, playbooks, roles etc. can be difficult and confusing, and since the productive system with its about 100 hosts is by far the most complicated it would be good to dry-run that environment at home without physical access to the machines. Running an installation with a different inventory will not really help here. -- 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/91da492f-06bb-4982-ba8e-6a1afd2df017%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
