Let's say that we have defined two machines in our inventory file:
[db-server-preprod]
172.16.0.1
172.16.0.2
If I run a playbook against this group will run in the same time on both machines if serial is 0 or sequentially if is 1 and the order seems to be the one in which the IPs are defined in the group.
But the question is if can I control the order of the playbook execution on the defined machines?
The same role behaves slightly different for one of the machines (the master) as opposed to all the others but is important that the machine that I want to be the master will be the first one on which the playbook executes.
My ideas so far:
db-server-preprod*
variant + all the other environments. A playbook runs in order from top to bottom. Within each play, tasks also run in order from top to bottom.
Using the --limit parameter of the ansible-playbook command is the easiest option to limit the execution of the code to only one host. The advantage is that you don't need to edit the Ansible Playbook code before executing to only one host.
shuffle: Hosts are randomly ordered each run.
Ansible playbooks are written in YAML format, and they contain multiple tasks executed in sequential order.
You may place your master host into separate group, then apply common role to all servers at once, then apply master-roles only to master server, and slave-roles to all servers except master using excluding pattern.
Inventory:
[all-servers]
host1
host2
host3
host4
[master-server]
host2
Playbook:
---
- hosts: all-servers
gather_facts: no
tasks:
- debug: msg=role-common
- hosts: master-server
gather_facts: no
tasks:
- debug: msg=role-master
- hosts: all-servers:!master-server
gather_facts: no
tasks:
- debug: msg=role-slave
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With