summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorsirkubax <muszynski@so1.net>2017-09-27 16:47:10 +0200
committersirkubax <muszynski@so1.net>2017-09-27 16:47:10 +0200
commit27c3e82f12f40c75bdd08e97aead14048a080505 (patch)
treefb7c04206690d9a35f1be3e2f4f852150351d6f1
parent656516a2b9c0951779b2450de24f46e8effad81c (diff)
test markdown
-rw-r--r--ansible.html.markdown12
1 files changed, 6 insertions, 6 deletions
diff --git a/ansible.html.markdown b/ansible.html.markdown
index 27a467cc..14565057 100644
--- a/ansible.html.markdown
+++ b/ansible.html.markdown
@@ -79,9 +79,9 @@ $ ansible -m command -a 'echo $HOME'
* Module: `raw` - executes a low-down and dirty SSH command, not going through the module subsystem (usefull to install python2.7)
-### Ansible - naming and quick intro
+## Ansible - naming and quick intro
-#### Inventory
+### Inventory
Inventory is a set of an objects or hosts, against which we are executing our playbooks or single tasks via shell commands
For this few minutes, lets asume that we are using default ansible inventory (which in Debian based system is placed in /etc/ansible/hosts)
@@ -95,15 +95,15 @@ hostB.localdomain
```
* [Additional Reading.](http://docs.ansible.com/ansible/latest/intro_inventory.html)
-#### Task
+### Task
Execution of a single Ansible **module** is called a **task**
The simplest module is called `ping` as you could see above
- Another example of the module that allow you to execute command remotly on multiple resources is called shell. It is the same as you would execute command remotely over ssh.
+ Another example of the module that allow you to execute command remotly on multiple resources is called `shell`. See above how you were using them already.
-##### Playbook
+### Playbook
Execution plan written in a form of script file(s) is called `playbook`.
Playbook consist of multiple elements
* a list (or group) of hosts that 'the play' is executed against
@@ -114,7 +114,7 @@ Playbook script language is YAML
You can think that playbook is very advanced CLI script that you are executing.
-##### Example of the playbook:
+#### Example of the playbook:
This playbook would execute (on all hosts defined in the inventory) two tasks
*`ping` that would return message *pong*
* `shell` that execute three commands and return the output to our terminal