Ansible Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
-i <path> | -i <path> | ||
</pre> | </pre> | ||
==Inventory File Structure== | |||
<pre> | |||
host1.example.com | |||
[webservers] | |||
web1.example.com | |||
web2.example.com | |||
[dbservers] | |||
db1.example.com | |||
db2.example.com | |||
</pre> | |||
The headings in brackets are group names, which are used in classifying systems and deciding what systems you are controlling at what times and for what purpose. | |||
=Playbook= | =Playbook= | ||
Revision as of 00:56, 16 May 2017
Internal
Inventory File
Ansible works against multiple systems at the same time. It does this by selecting portions of systems listed in Ansible’s inventory file. The default location of the inventory file is /etc/ansible/hosts.
A different location of the inventory file can be specified on the command line with:
-i <path>
Inventory File Structure
host1.example.com [webservers] web1.example.com web2.example.com [dbservers] db1.example.com db2.example.com
The headings in brackets are group names, which are used in classifying systems and deciding what systems you are controlling at what times and for what purpose.