ansible-collections/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2025-10-22 03:53:59 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Merge pull request #1747 from njharman/alpharange

Browse source 
Alphabetic inventory hostname patterns.
This commit is contained in:
Michael DeHaan 2012-12-17 16:52:11 -08:00
commit 04195e202d
5 changed files with 54 additions and 37 deletions
Download patch file Download diff file Expand all files Collapse all files

13
docsite/rst/patterns.rst
View file

@ -48,8 +48,9 @@ Adding a lot of hosts? In 0.6 and later, if you have a lot of hosts following s
[webservers]
www[01:50].example.com
db-[a:f].example.com
Leading zeros can be included or removed, as desired, and the ranges are inclusive.
For numeric patterns, leading zeros can be included or removed, as desired. Ranges are inclusive.
Selecting Targets
+++++++++++++++++
@ -57,7 +58,7 @@ Selecting Targets
We'll go over how to use the command line in :doc:`examples` section, however, basically it looks like this::
ansible <pattern_goes_here> -m <module_name> -a <arguments>
Such as::
ansible webservers -m service -a "name=httpd state=restarted"
@ -70,7 +71,7 @@ This is done by designating particular host names or groups of hosts.
The following patterns target all hosts in the inventory file::
all
*
*
Basically 'all' is an alias for '*'. It is also possible to address a specific host or hosts::
@ -78,7 +79,7 @@ Basically 'all' is an alias for '*'. It is also possible to address a specific
one.example.com:two.example.com
192.168.1.50
192.168.1.*
The following patterns address one or more groups, which are denoted
with the aforementioned bracket headers in the inventory file::
@ -105,7 +106,7 @@ Host Variables
++++++++++++++
It is easy to assign variables to hosts that will be used later in playbooks::
[atlanta]
host1 http_port=80 maxRequestsPerChild=808
host2 http_port=303 maxRequestsPerChild=909
@ -188,7 +189,7 @@ the 'raleigh' group might look like::
It is ok if these files do not exist, this is an optional feature.
Tip: Keeping your inventory file and variables in a git repo (or other version control)
Tip: Keeping your inventory file and variables in a git repo (or other version control)
is an excellent way to track changes to your inventory and host variables.
.. versionadded:: 0.5