ansible/docsite/rst/patterns.rst

224 lines
6.1 KiB
ReStructuredText
Raw Normal View History

.. _patterns:
2012-05-13 17:00:02 +02:00
Inventory & Patterns
====================
2012-03-07 17:35:18 +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.
2012-03-09 20:39:29 +01:00
2012-08-28 21:41:10 +02:00
.. contents:: `Table of contents`
:depth: 2
:backlinks: top
2012-03-09 20:39:29 +01:00
.. _inventoryformat:
Hosts and Groups
++++++++++++++++
2012-03-08 19:53:48 +01:00
The format for /etc/ansible/hosts is an INI format and looks like this::
2012-03-08 19:36:47 +01:00
mail.example.com
[webservers]
foo.example.com
bar.example.com
[dbservers]
one.example.com
two.example.com
three.example.com
The things in brackets are group names. You don't have to have them,
but they are useful.
2012-03-08 19:36:47 +01:00
2012-04-18 01:59:15 +02:00
If you have hosts that run on non-standard SSH ports you can put the port number
2012-11-04 00:19:14 +01:00
after the hostname with a colon. Ports listed in any SSH config file won't be read,
so it is important that you set them if things are not running on the default port::
2012-04-18 01:59:15 +02:00
2012-11-04 00:19:14 +01:00
badwolf.example.com:5309
2012-04-18 01:59:15 +02:00
2012-11-04 00:19:14 +01:00
Suppose you have just static IPs and want to set up some aliases that don't live in your host file, or you are connecting through tunnels. You can do things like this::
jumper ansible_ssh_port=5555 ansible_ssh_host=192.168.1.50
In the above example, trying to ansible against the host alias "jumper" (which may not even be a real hostname) will contact 192.168.1.50 on port 5555.
2012-11-04 00:19:14 +01:00
Adding a lot of hosts? In 0.6 and later, if you have a lot of hosts following similar patterns you can do this rather than listing each hostname::
2012-08-15 04:14:47 +02:00
[webservers]
2012-10-04 02:58:27 +02:00
www[01:50].example.com
db-[a:f].example.com
2012-08-15 04:14:47 +02:00
For numeric patterns, leading zeros can be included or removed, as desired. Ranges are inclusive.
2012-08-15 04:14:47 +02:00
2012-03-08 19:53:48 +01:00
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"
Within :doc:`playbooks`, these patterns can be used for even greater purposes.
Anyway, to use Ansible, you'll first need to know how to tell Ansible which hosts in your inventory file to talk to.
This is done by designating particular host names or groups of hosts.
The following patterns target all hosts in the inventory file::
2012-03-08 19:53:48 +01:00
all
*
2012-03-08 19:36:47 +01:00
Basically 'all' is an alias for '*'. It is also possible to address a specific host or hosts::
2012-03-08 19:36:47 +01:00
one.example.com
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::
2012-03-08 19:36:47 +01:00
webservers
webservers:dbservers
2012-07-20 17:51:03 +02:00
You can exclude groups as well, for instance, all webservers not in Phoenix::
2012-07-04 23:44:39 +02:00
webservers:!phoenix
Individual host names (or IPs), but not groups, can also be referenced using
wildcards::
2012-03-08 19:36:47 +01:00
2012-03-09 20:39:29 +01:00
*.example.com
*.com
2012-03-08 19:36:47 +01:00
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
2012-03-09 20:39:29 +01:00
one*.com:dbservers
2012-03-08 19:36:47 +01:00
2012-04-18 01:54:23 +02:00
Easy enough. See :doc:`examples` and then :doc:`playbooks` for how to do things to selected hosts.
Host Variables
++++++++++++++
2012-07-04 23:44:39 +02:00
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
Group Variables
+++++++++++++++
2012-07-04 23:44:39 +02:00
Variables can also be applied to an entire group at once::
[atlanta]
host1
host2
[atlanta:vars]
ntp_server=ntp.atlanta.example.com
proxy=proxy.atlanta.example.com
2012-05-10 07:36:52 +02:00
Groups of Groups, and Group Variables
+++++++++++++++++++++++++++++++++++++
It is also possible to make groups of groups and assign
2012-05-10 07:36:52 +02:00
variables to groups. These variables can be used by /usr/bin/ansible-playbook, but not
2012-06-20 03:22:01 +02:00
/usr/bin/ansible::
[atlanta]
host1
host2
[raleigh]
host2
host3
[southeast:children]
2012-05-06 23:16:42 +02:00
atlanta
raleigh
[southeast:vars]
some_server=foo.southeast.example.com
2012-05-10 07:36:52 +02:00
halon_system_timeout=30
self_destruct_countdown=60
escape_pods=2
[usa:children]
southeast
northeast
southwest
southeast
2012-07-20 17:51:03 +02:00
If you need to store lists or hash data, or prefer to keep host and group specific variables
seperate from the inventory file, see the next section.
2012-04-18 01:54:23 +02:00
2012-07-20 17:51:03 +02:00
Splitting Out Host and Group Specific Data
++++++++++++++++++++++++++++++++++++++++++
.. versionadded:: 0.6
In addition to the storing variables directly in the INI file, host
and group variables can be stored in individual files relative to the
inventory file. These variable files are in YAML format.
2012-07-20 17:51:03 +02:00
Assuming the inventory file path is::
/etc/ansible/hosts
If the host is named 'foosball', and in groups 'raleigh' and 'webservers', variables
in YAML files at the following locations will be made available to the host::
/etc/ansible/group_vars/raleigh
/etc/ansible/group_vars/webservers
/etc/ansible/host_vars/foosball
For instance, suppose you have hosts grouped by datacenter, and each datacenter
uses some different servers. The data in the groupfile '/etc/ansible/group_vars/raleigh' for
the 'raleigh' group might look like::
2012-04-18 01:54:23 +02:00
---
2012-07-20 17:51:03 +02:00
ntp_server: acme.example.org
database_server: storage.example.org
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)
2012-07-20 17:51:03 +02:00
is an excellent way to track changes to your inventory and host variables.
2012-04-18 01:54:23 +02:00
.. versionadded:: 0.5
If you ever have two python interpreters on a system, set a
variable called 'ansible_python_interpreter' to the Python
interpreter path you would like to use.
2012-07-20 17:51:03 +02:00
YAML Inventory
++++++++++++++
.. deprecated:: 0.7
Ansible's YAML inventory format is deprecated and will be removed in
Ansible 0.7. Ansible 0.6 includes a `conversion script
<https://github.com/ansible/ansible/blob/devel/examples/scripts/yaml_to_ini.py>`_.
2012-07-20 17:51:03 +02:00
Usage::
2012-07-04 23:44:39 +02:00
2012-07-20 17:51:03 +02:00
yaml_to_ini.py /etc/ansible/hosts
.. seealso::
:doc:`examples`
Examples of basic commands
:doc:`playbooks`
Learning ansible's configuration management language
`Mailing List <http://groups.google.com/group/ansible-project>`_
Questions? Help? Ideas? Stop by the list on Google Groups
`irc.freenode.net <http://irc.freenode.net>`_
#ansible IRC chat channel