Ansible/Separate Playbooks by Role - Revision history

Admin: /* Useful Commands */

2018-11-13T19:12:23Z

Useful Commands

← Older revision		Revision as of 19:12, 13 November 2018
Line 65:		Line 65:
	</pre>		</pre>

	==Useful Commands==		===Useful Commands===

	Other useful commands:		Other useful commands:

Admin: /* Further Examples */

2018-11-13T19:12:17Z

Further Examples

← Older revision		Revision as of 19:12, 13 November 2018
Line 23:		Line 23:
	</pre>		</pre>

	==Further Examples==		===Further Examples of Using Separate Playbooks===

	If you further separate your tasks (things to do) and handlers (things to do that are triggered by other things being done) by role, you can start to do lots of different things.		If you further separate your tasks (things to do) and handlers (things to do that are triggered by other things being done) by role, you can start to do lots of different things.

Admin: /* Useful COmmands */

2018-11-13T19:11:43Z

Useful COmmands

← Older revision		Revision as of 19:11, 13 November 2018
Line 65:		Line 65:
	</pre>		</pre>

	==Useful ~~COmmands~~==		==Useful Commands==

	Other useful commands:		Other useful commands:

Admin: /* Using Separate Playbooks */

2018-11-13T19:09:36Z

Using Separate Playbooks

@@ Line 21: / Line 21: @@
 ansible-playbook site.yml --limit webservers
 ansible-playbook webservers.yml
 </pre>

Admin: Created page with "==Separating Playbooks by Role== For Ansible playbooks involving multiple roles, top level playbooks should be separated by role. Here is the simplest possible top-level pla..."

2018-11-13T19:06:00Z

Created page with "==Separating Playbooks by Role== For Ansible playbooks involving multiple roles, top level playbooks should be separated by role. Here is the simplest possible top-level pla..."

New page

==Separating Playbooks by Role==

For Ansible playbooks involving multiple roles, top level playbooks should be separated by role.

Here is the simplest possible top-level playbook, which includes two sub-playbooks:

<pre>
- import_playbook: webservers.yml
- import_playbook: dbservers.yml
</pre>

These files are both at the top level, and

==Using Separate Playbooks==

Now that you have multiple roles split across playbooks, you can either configure your whole infrastructure, by running site.yml with ansible-playbook, or you can configure particular pieces of infrastructure, for example by only running dbservers.yml.

To limit which playbooks are run, either run the whole site-wide playbook with the --limit flag, or run with the sub-playbook:

<pre>
ansible-playbook site.yml --limit webservers
ansible-playbook webservers.yml
</pre>

==Flags==

{{AnsibleFlag}}