Difference between revisions of "Ansible playbooks"
From Notes_Wiki
m |
m |
||
| Line 15: | Line 15: | ||
*[[Installing_rsyslog_from_yum_repository#Automated_rsyslog_server_and_client_configuration | Automated_rsyslog_server_and_client_configuration]] | *[[Installing_rsyslog_from_yum_repository#Automated_rsyslog_server_and_client_configuration | Automated_rsyslog_server_and_client_configuration]] | ||
*[[Automated configuration of 389-DS using ansible]] | *[[Automated configuration of 389-DS using ansible]] | ||
*[[Automated installation of OpenVZ on CentOS using ansible]] | |||
Revision as of 10:59, 11 April 2015
<yambe:breadcrumb>Ansible|Ansible</yambe:breadcrumb>
Ansible-playbooks
To run ansible-playbooks use:
ansible-playbook -i <hosts-file> <playbook.yaml>
It is also possible to supply values of various variables using -e "var=value" option. Here host names in playbook will get dereferenced from provided hosts file. Trust based ssh should be present between current host and root@<remote-machine> for script to work properly.
Example playbooks:
- Installing_GLPI#Automated_installation
- Basic_redmine_installation#Automated_installation
- Automated OSSEC installation using ansible
- Automated bind configuration using ansible
- Automated_rsyslog_server_and_client_configuration
- Automated configuration of 389-DS using ansible
- Automated installation of OpenVZ on CentOS using ansible
