Skip to content
Snippets Groups Projects
Commit 68ab0c3f authored by Vincent Mazenod's avatar Vincent Mazenod
Browse files

anible

parent 47d3ad8c
No related branches found
No related tags found
No related merge requests found
Pipeline #3250 passed
......@@ -41,15 +41,15 @@
## terminologie
* **mgmt node** - Ansible management node is the machine where the Ansible is installed & which is responsible for configuration of all server machines.
Inventory:- Inventory is a file which consists of IP Address of all servers on which configuration is to be done.
Playbook: Playbook is used to manage configuration which can be deployed on the remote machines. Playbook is designed in simple human-readable format, so that it becomes easy to understand the code.
Task:- Task is the file where a user defines the steps that he needs to perform on the Playbook.
Module:- Ansible has in-built modules that can be executed directly on remote hosts or through Playbooks. Users can also write their own modules. These modules can control system resources, like services, packages, or files or handle execution of system commands.
Role: Role is used for organizing Playbooks and other files in order to facilitate sharing and reusing portions of a provisioning.
Play: A provisioning executed from start to finish is called a Play.
Facts:Used to get the system information while running the playbook, like network interfaces or operating system.
Handlers: Handlers which are similar to a task, can be used to restart or to stop a service.
* **mgmt node** (machine pilote) machine surlaquelle ansible est installé et responsable de la configuration de toutes les machines gérées.
* **Inventory** (inventaire) fichier contenant les ip de tous les serveurs à configurer
* **Playbook** gère la configuration à déployer sur chaque serveur
* **Task** fichier où sont définies les actions réalisées par le playbook
* **Module** actions plus ou moins complexe utilisables à partir des **tasks**. ansible possède de [nombreux modules natifs](https://docs.ansible.com/ansible/latest/modules/modules_by_category.html). Il est possible d'écrire ses propres modules.
* **Role** permet d'organiser les playbooks en parties claires et réutilisables
* **Play** est l'exécution d'un playbook sur un serveur
* **Facts** information collectée par ansible sur le système du serveur à configurer
* **Handlers** similaire aux **tasks** mais appelable à partir d'une **task** (redémarrage de service par exemple)
ansible all --inventory-file=inventory.ini --module-name ping -u root
......@@ -84,6 +84,7 @@ ansible all --inventory-file=inventory.ini --module-name ping -u root
* pexpect
* remote roles
* skeleton https://github.com/mrjk/ansible-skel
### Récupérer les roles nécessaires
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment