Ansible playbooks are written in YAML text files and define actions to execute against host/devices, check official Ansible playbook introduction: https://docs.ansible.com/ansible/devel/user_guide/playbooks_intro.html
Task definitions or Playbooks
Task definitions are defined in text files, called playbooks in Ansible terminology, in YAML format. Execution of task definitions or playbooks are make using
ansible-playbook command followed by your desired playbook to execute. Playbooks can also use Jinja templates to enable dynamic expressions and access to variables.
Ansible Playbook execution:
ansible-playbook my_new_created_playbook.yml -f 10-f 10 parallelize 10 executions
Create "Executable" Playbooks
Add the following line
#!/usr/bin/env ansible-playbook at the beginning of your playbooks and make it executable
chmod +x /path/to/your/playbook.yml to execute without calling ansible-playbook binary.
Create a new file touch /tmp/test_file.txt, REMOTE_SERVER should be already present in your Ansible inventory:
Playbook using module
#!/usr/bin/env ansible-playbook - hosts: REMOTE_SERVER_HOSTNAME tasks: - name: Ansible create a new file called test_fle.txt in /tmp directory file: path: "/tmp/test_file.txt" state: touch
Important Note: dash symbol (-) and indentation has to be properly formatted.
You can use variables in your playbooks, check official documentation for further information: https://docs.ansible.com/ansible/devel/user_guide/playbooks_variables.html
- Read Ansible introduction to playbooks: https://docs.ansible.com/ansible/devel/user_guide/playbooks_intro.html
- Review different options for running playbooks, including:
- Review Ansible playbooks examples
- Ansible: modules, plugins, Playbooks (examples)
ansible-config, Ansible Tower, Ansible Galaxy (Roles) (
Ansible Molecule, Ansible collections,
ansible HOSTNAME -m ping,
ansible -m ping,
ansible --help, Tags, Ansible variables