Editing Ansible playbooks
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 4: | Line 4: | ||
Task definitions are defined in text files, called playbooks in Ansible terminology, in [[DevOps/YAML|YAML]] format. Execution of task definitions or playbooks are make using <code>ansible-playbook</code> command followed by your desired playbook to execute. Playbooks can also use [[Jinja]] templates to enable dynamic expressions and access to variables<ref>https://docs.ansible.com/ansible/latest/user_guide/playbooks_templating.html</ref>. | Task definitions are defined in text files, called playbooks in Ansible terminology, in [[DevOps/YAML|YAML]] format. Execution of task definitions or playbooks are make using <code>ansible-playbook</code> command followed by your desired playbook to execute. Playbooks can also use [[Jinja]] templates to enable dynamic expressions and access to variables<ref>https://docs.ansible.com/ansible/latest/user_guide/playbooks_templating.html</ref>. | ||
| − | Ansible Playbook execution: | + | [[Ansible Playbooks|Ansible Playbook]] execution: |
* <code>ansible-playbook my_new_created_playbook.yml</code> | * <code>ansible-playbook my_new_created_playbook.yml</code> | ||
* <code>ansible-playbook my_new_created_playbook.yml -f 10</code> -f 10 parallelize 10 executions | * <code>ansible-playbook my_new_created_playbook.yml -f 10</code> -f 10 parallelize 10 executions | ||
| Line 12: | Line 12: | ||
Add the following line <code>#!/usr/bin/env ansible-playbook</code> at the beginning of your playbooks and make it executable <code>chmod +x /path/to/your/playbook.yml</code> to execute without calling ansible-playbook binary. | Add the following line <code>#!/usr/bin/env ansible-playbook</code> at the beginning of your playbooks and make it executable <code>chmod +x /path/to/your/playbook.yml</code> to execute without calling ansible-playbook binary. | ||
| − | === | + | === Ansible Playbooks Examples=== |
Create a new file ''touch /tmp/test_file.txt'', REMOTE_SERVER should be already present in your [[Ansible inventory]]:<code>/etc/ansible/host</code> | Create a new file ''touch /tmp/test_file.txt'', REMOTE_SERVER should be already present in your [[Ansible inventory]]:<code>/etc/ansible/host</code> | ||
Playbook using module <code>file</code><ref>https://docs.ansible.com/ansible/latest/modules/file_module.html#file-module</ref>: | Playbook using module <code>file</code><ref>https://docs.ansible.com/ansible/latest/modules/file_module.html#file-module</ref>: | ||
| − | + | <pre> | |
| − | + | - 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 | |
| − | + | </pre> | |
| − | + | Important Note: dash symbol (-) and indentation has to be properly formatted. | |
| − | |||
| − | Important Note: dash symbol (-) and | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
=== Variables === | === Variables === | ||
| Line 42: | Line 33: | ||
# Read Ansible introduction to playbooks: https://docs.ansible.com/ansible/devel/user_guide/playbooks_intro.html | # Read Ansible introduction to playbooks: https://docs.ansible.com/ansible/devel/user_guide/playbooks_intro.html | ||
# Review different options for running playbooks, including: <code>--limit</code> | # Review different options for running playbooks, including: <code>--limit</code> | ||
| − | |||
| − | |||
== See also == | == See also == | ||
Advertising:
