IT/Software/Ansible: Difference between revisions
Jump to navigation
Jump to search
Access restrictions were established for this page. If you see this message, you have no access to this page.
No edit summary |
(added github repo link) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 17: | Line 17: | ||
=== In a nutshell === | === In a nutshell === | ||
* A Control Node executes tasks | * A Control Node executes tasks, defined in playbooks on Managed Nodes over SSH or API's | ||
* Control Node: This can be any linux based host (or wsl) where ansible is installed and is connected to the same network as the Managed Nodes | * Control Node: This can be any linux based host (or windows with wsl) where ansible is installed and is connected to the same network as the Managed Nodes | ||
* Managed Node: Any device that should be managed | * Managed Node: Any device that should be managed or setup | ||
* playbook.yml: A yml file that contains the involved hosts, process and tasks that should be done | * playbook.yml: A yml file that contains the involved hosts, process and tasks that should be done | ||
* inventory.yml: A yml file that contains all hosts, grouped in sections if needed (e.g. different branches, locations, device/os types) | * inventory.yml: A yml file that contains all hosts, grouped in sections if needed (e.g. different branches, locations, device/os types) | ||
| Line 40: | Line 40: | ||
* run in Terminal <code>wsl --install</code> | * run in Terminal <code>wsl --install</code> | ||
=== Execute Playbooks === | |||
* example with a playbook named playbook-example.yml and inventory.yml | * example with a playbook named playbook-example.yml and inventory.yml | ||
* <code>ansible-playbook -i inventory.yml playbook-example.yml -kK</code> | * <code>ansible-playbook -i inventory.yml playbook-example.yml -kK</code> | ||
* <code>-K</code> if become/sudo is needed | * <code>-K</code> if become/sudo is needed | ||
* <code>-k</code> for user/password based authentication | * <code>-k</code> for user/password based authentication | ||
==== Repository ==== | |||
* some easy scripts | |||
* https://github.com/stefannyffenegger/automation/tree/main/ansible | |||
Latest revision as of 18:48, 10 May 2024
Ansible
Ansible is an open source IT automation engine that automates provisioning, configuration management, application deployment, orchestration, and many other IT processes.It is free to use, and the project benefits from the experience and intelligence of its thousands of contributors.
Pros:
- reproducible environments
- easy to begin with
- fast deployment
- scalable
Cons:
- small time investment to learn it
In a nutshell
- A Control Node executes tasks, defined in playbooks on Managed Nodes over SSH or API's
- Control Node: This can be any linux based host (or windows with wsl) where ansible is installed and is connected to the same network as the Managed Nodes
- Managed Node: Any device that should be managed or setup
- playbook.yml: A yml file that contains the involved hosts, process and tasks that should be done
- inventory.yml: A yml file that contains all hosts, grouped in sections if needed (e.g. different branches, locations, device/os types)
See also IaC/IaaC https://en.wikipedia.org/wiki/Infrastructure_as_code
Install Ansible
Linux
sudo apt install ansible
Windows
- install wsl first
- https://learn.microsoft.com/en-us/windows/wsl/install
- run in Terminal
wsl --install
Execute Playbooks
- example with a playbook named playbook-example.yml and inventory.yml
ansible-playbook -i inventory.yml playbook-example.yml -kK-Kif become/sudo is needed-kfor user/password based authentication
Repository
- some easy scripts