Am Mittwoch, 26. Oktober 2016 22:46:48 UTC+2 schrieb Dan Rough: > > If I understand your question correctly, then why not just have two > playbooks? We have an infrastructure.yml playbook which provisions a server > for us. We also have another playbook which makes alterations to that > server dependent on its role. For example, in our case when we provision a > Jenkins server, I run the infrastructure.yml playbook which targets all > servers (qa-machines in your case) in its host specification (remember that > you can use ansible's limit > <http://docs.ansible.com/ansible/playbooks_best_practices.html#top-level-playbooks-are-separated-by-role> > > attribute to narrow the scope of the playbook from the command line) and > then I run jenkins.yml afterwards which targets just the jenkins server > (jenkins-slaves in your example). >
This is exactly what I am doing, except I need this to happen also when using Vagrant by assigning groups properly when I have the inventory generated by it (see above comment). I am still deliberating if I should maintain the second inventory directly, or have it generated... Thanks for your help, much appreciated! -- 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/80ba476c-22d4-4862-821c-13bf198de8af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
