1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
community.general/html/_sources/patterns.txt

64 lines
1.3 KiB
Text
Raw Normal View History

2012-03-08 19:53:48 +01:00
The Inventory File, Patterns, and Groups
========================================
2012-03-07 17:35:18 +01:00
2012-03-08 19:36:47 +01:00
How to select hosts you wish to manage
.. seealso::
:doc:`examples`
Examples of basic commands
:doc:`playbooks`
Learning ansible's configuration management language
2012-03-08 19:53:48 +01:00
Inventory File Format
+++++++++++++++++++++
2012-03-08 19:36:47 +01:00
Ansible works against multiple systems in your infrastructure at the
same time. It does this by selecting portions of systems listed in Ansible's inventory file,
which defaults to /etc/ansible/hosts, and looks like this::
mail.example.com
[webservers]
foo.example.com
bar.example.com
[dbservers]
one.example.com
two.example.com
three.example.com
2012-03-08 19:53:48 +01:00
Selecting Targets
+++++++++++++++++
These patterns target all hosts in the inventory file::
all
*
2012-03-08 19:36:47 +01:00
2012-03-08 19:53:48 +01:00
It is also possible to address specific hosts::
2012-03-08 19:36:47 +01:00
one.example.com
one.example.com:two.example.com
2012-03-08 19:53:48 +01:00
The following patterns address one or more groups, which are denoted with the bracket
headers in the inventory file::
2012-03-08 19:36:47 +01:00
webservers
webservers:dbservers
Individual hosts, but not groups, can also be referenced using wildcards:
*.example.com
*.com
2012-03-08 19:53:48 +01:00
It's also ok to mix wildcard patterns and groups at the same time::
2012-03-08 19:36:47 +01:00
one*.com:dbservers
2012-03-08 19:53:48 +01:00
NOTE: It is not possible to target a host not in the inventory file.
2012-03-08 19:36:47 +01:00