iskm/learnxinyminutes-docs
1
0
Fork 0
mirror of https://github.com/adambard/learnxinyminutes-docs.git synced 2024-12-23 17:41:41 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

test markdown

Browse Source
This commit is contained in:
sirkubax 2017-09-27 18:11:20 +02:00
parent 04a88249c9
commit da0ca8fcbd
1 changed files with 46 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

64
ansible.html.markdown
View File

@ -1,4 +1,4 @@
--- o--
category: tool category: tool
tool: ansible tool: ansible
contributors: contributors:
@ -143,10 +143,9 @@ $ ansible-playbook path/name_of_the_playbook.yml
#### ansible-roles (a 'template-playbooks' with right structure) #### ansible-roles (a 'template-playbooks' with right structure)
You already know the tasks (modules) that can be run via CLI. You already know the tasks (modules) that can be run via CLI. You also know the playbooks - the execution plans of multiple tasks (with variables and logic).
The execution plans of multiple tasks (with variables and logic) are called playbooks.
A concept called `role` was introduced for parts of the code that should be reusable. A concept called `role` was introduced for parts of the code (playbooks) that should be reusable.
**Role** is a structured way to manage your set of tasks, variables, handlers, default settings, and way more (meta, files, templates). **Role** is a structured way to manage your set of tasks, variables, handlers, default settings, and way more (meta, files, templates).
Role allows to reuse the same parts of code in multiple plybooks (you can parametrize the role 'further' during it's execution). Role allows to reuse the same parts of code in multiple plybooks (you can parametrize the role 'further' during it's execution).
@ -173,7 +172,7 @@ pre_tasks:
shell: echo 'this task is the last, but would be executed before roles, and before tasks' shell: echo 'this task is the last, but would be executed before roles, and before tasks'
``` ```
Example-role Example->role
We would clone the ready-to-use examples from additional repository We would clone the ready-to-use examples from additional repository
```bash ```bash
@ -183,30 +182,59 @@ $ source environment
$(venv) ansible-playbook playbooks/role_example.yml $(venv) ansible-playbook playbooks/role_example.yml
``` ```
Role directory structure: #### Role directory structure:
``` ```
roles/ roles/
some_role/ some_role/
defaults/ defaults/ # contains default variables
files/ files/ # for static files
templates/ templates/ # for jinja templates
tasks/ tasks/ # tasks
handlers/ handlers/ # handlers
vars/ vars/ # more variables (higher priority)
meta/ meta/ # meta - package (role) info
``` ```
#### Role Handlers #### Role Handlers
Handlers are a task that can be triggered (notified) during execution of a playbook, but they itself execute at the very end of a playbook. Handlers are a tasks that can be triggered (notified) during execution of a playbook, but they itself execute at the very end of a playbook.
It is a best way to restart a service, check if application port is open, etc. It is a best way to restart a service, check if application port is active (successfull deployment criteria), etc.
### ansible - variables ### ansible - variables
lookup's
Ansible is flexible - it has 21 levels of variable precedence
[read more]
For now you might like to know, that CLI variables has the top priority.
You should also know, that a nice way to pool some data is a **lookup**
##### Lookups
* pipe
* file
* stream
* etcd
You can use them in CLI too
```yaml ```yaml
ansible -m shell -a 'echo {{ my_variable }}` -e '{{ lookup('pipe'; 'date' }}"
``` ```
#### templates #### Templates
JINJA2
Template is a powerfull way to deliver some (partially) dynamic content. Ansible uses **Jinja2** langueage to describe the template.
```jinja2
Some static content
{{ a_variable }}
{% for item in loop_items %}
this line item is {{ item }}
{% endfor %}
```
### ansible-vault ### ansible-vault