We followed the recommendation at http://docs.ansible.com/playbooks_best_practices.html#stage-vs-production and have separate inventory files for each distinct environment (in your case test1 and test2).
We then invoke ansible with "-i test1" or "-i test2" depending on what environment is being targeted. The ability to hit -all- webservers with one command is lost, but you usually don't want to do that and it's safer to update test1 before test2 (or production). So far this has worked well. -- 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/e6068281-ffe8-4bc8-94a8-f349887be3a2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
