Difference between revisions of "Ansible playbooks"
From Notes_Wiki
m |
m |
||
| Line 7: | Line 7: | ||
</pre> | </pre> | ||
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. | 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. | ||
'''CentOS 7.x playbooks are located at [[CentOS 7.x ansible playbooks]]''' | |||
Example playbooks: | Example playbooks: | ||
Revision as of 03:00, 15 October 2017
<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.
CentOS 7.x playbooks are located at CentOS 7.x ansible playbooks
Example playbooks:
- Installing_GLPI#Automated_installation
- Basic_redmine_installation#Automated_installation
- 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
- Automated configuration of git over SSH using ansible
- Automated configuration of php based LDAP password change page
- HTTP based ansible-pull configuration without-git
- Configure machines as LDAP client for graphical LDAP user login
