mirror of https://github.com/ansible/ansible.git
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
487 lines
18 KiB
ReStructuredText
487 lines
18 KiB
ReStructuredText
11 years ago
|
.. _inventory:
|
||
13 years ago
|
|
||
7 years ago
|
Working with Inventory
|
||
|
======================
|
||
13 years ago
|
|
||
11 years ago
|
.. contents:: Topics
|
||
|
|
||
7 years ago
|
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,
|
||
|
which defaults to being saved in the location ``/etc/ansible/hosts``.
|
||
|
You can specify a different inventory file using the ``-i <path>`` option on the command line.
|
||
|
|
||
|
Not only is this inventory configurable, but you can also use multiple inventory files at the same time and
|
||
7 years ago
|
pull inventory from dynamic or cloud sources or different formats (YAML, ini, etc), as described in :doc:`intro_dynamic_inventory`.
|
||
7 years ago
|
Introduced in version 2.4, Ansible has inventory plugins to make this flexible and customizable.
|
||
13 years ago
|
|
||
|
.. _inventoryformat:
|
||
|
|
||
13 years ago
|
Hosts and Groups
|
||
|
++++++++++++++++
|
||
13 years ago
|
|
||
7 years ago
|
The inventory file can be in one of many formats, depending on the inventory plugins you have.
|
||
7 years ago
|
For this example, the format for ``/etc/ansible/hosts`` is an INI-like (one of Ansible's defaults) and looks like this:
|
||
8 years ago
|
|
||
|
.. code-block:: ini
|
||
13 years ago
|
|
||
|
mail.example.com
|
||
|
|
||
|
[webservers]
|
||
|
foo.example.com
|
||
|
bar.example.com
|
||
|
|
||
|
[dbservers]
|
||
|
one.example.com
|
||
|
two.example.com
|
||
|
three.example.com
|
||
|
|
||
8 years ago
|
The headings in brackets are group names, which are used in classifying systems
|
||
11 years ago
|
and deciding what systems you are controlling at what times and for what purpose.
|
||
13 years ago
|
|
||
7 years ago
|
A YAML version would look like:
|
||
|
|
||
|
.. code-block:: yaml
|
||
|
|
||
|
all:
|
||
|
hosts:
|
||
7 years ago
|
mail.example.com:
|
||
7 years ago
|
children:
|
||
|
webservers:
|
||
|
hosts:
|
||
|
foo.example.com:
|
||
|
bar.example.com:
|
||
|
dbservers:
|
||
|
hosts:
|
||
|
one.example.com:
|
||
|
two.example.com:
|
||
|
three.example.com:
|
||
|
|
||
|
|
||
9 years ago
|
It is ok to put systems in more than one group, for instance a server could be both a webserver and a dbserver.
|
||
8 years ago
|
If you do, note that variables will come from all of the groups they are a member of. Variable precedence is detailed in a later chapter.
|
||
11 years ago
|
|
||
7 years ago
|
If you have hosts that run on non-standard SSH ports you can put the port number after the hostname with a colon.
|
||
|
Ports listed in your SSH config file won't be used with the `paramiko` connection but will be used with the `openssh` connection.
|
||
11 years ago
|
|
||
8 years ago
|
To make things explicit, it is suggested that you set them if things are not running on the default port:
|
||
|
|
||
|
.. code-block:: ini
|
||
13 years ago
|
|
||
12 years ago
|
badwolf.example.com:5309
|
||
13 years ago
|
|
||
7 years ago
|
Suppose you have just static IPs and want to set up some aliases that live in your host file, or you are connecting through tunnels.
|
||
|
You can also describe hosts via variables:
|
||
|
|
||
|
In INI:
|
||
8 years ago
|
|
||
|
.. code-block:: ini
|
||
12 years ago
|
|
||
8 years ago
|
jumper ansible_port=5555 ansible_host=192.0.2.50
|
||
12 years ago
|
|
||
7 years ago
|
In YAML:
|
||
11 years ago
|
|
||
7 years ago
|
.. code-block:: yaml
|
||
7 years ago
|
|
||
7 years ago
|
...
|
||
|
hosts:
|
||
|
jumper:
|
||
|
ansible_port: 5555
|
||
|
ansible_host: 192.0.2.50
|
||
7 years ago
|
|
||
|
In the above example, trying to ansible against the host alias "jumper" (which may not even be a real hostname) will contact 192.0.2.50 on port 5555.
|
||
|
Note that this is using a feature of the inventory file to define some special variables.
|
||
|
Generally speaking, this is not the best way to define variables that describe your system policy, but we'll share suggestions on doing this later.
|
||
|
|
||
|
.. note:: Values passed in the INI format using the ``key=value`` syntax are not interpreted as Python literal structure
|
||
|
(strings, numbers, tuples, lists, dicts, booleans, None), but as a string. For example ``var=FALSE`` would create a string equal to 'FALSE'.
|
||
|
Do not rely on types set during definition, always make sure you specify type with a filter when needed when consuming the variable.
|
||
|
|
||
|
If you are adding a lot of hosts following similar patterns, you can do this rather than listing each hostname:
|
||
12 years ago
|
|
||
8 years ago
|
.. code-block:: ini
|
||
12 years ago
|
|
||
|
[webservers]
|
||
12 years ago
|
www[01:50].example.com
|
||
12 years ago
|
|
||
8 years ago
|
For numeric patterns, leading zeros can be included or removed, as desired. Ranges are inclusive. You can also define alphabetic ranges:
|
||
|
|
||
|
.. code-block:: ini
|
||
12 years ago
|
|
||
|
[databases]
|
||
12 years ago
|
db-[a:f].example.com
|
||
12 years ago
|
|
||
9 years ago
|
|
||
8 years ago
|
.. include:: ../rst_common/ansible_ssh_changes_note.rst
|
||
9 years ago
|
|
||
|
You can also select the connection type and user on a per host basis:
|
||
|
|
||
8 years ago
|
.. code-block:: ini
|
||
9 years ago
|
|
||
12 years ago
|
[targets]
|
||
|
|
||
|
localhost ansible_connection=local
|
||
9 years ago
|
other1.example.com ansible_connection=ssh ansible_user=mpdehaan
|
||
|
other2.example.com ansible_connection=ssh ansible_user=mdehaan
|
||
12 years ago
|
|
||
7 years ago
|
As mentioned above, setting these in the inventory file is only a shorthand, and we'll discuss how to store them in individual files in the 'host_vars' directory a bit later on.
|
||
13 years ago
|
|
||
11 years ago
|
.. _host_variables:
|
||
|
|
||
13 years ago
|
Host Variables
|
||
|
++++++++++++++
|
||
|
|
||
7 years ago
|
As described above, it is easy to assign variables to hosts that will be used later in playbooks:
|
||
8 years ago
|
|
||
|
.. code-block:: ini
|
||
12 years ago
|
|
||
13 years ago
|
[atlanta]
|
||
|
host1 http_port=80 maxRequestsPerChild=808
|
||
|
host2 http_port=303 maxRequestsPerChild=909
|
||
|
|
||
11 years ago
|
.. _group_variables:
|
||
|
|
||
13 years ago
|
Group Variables
|
||
|
+++++++++++++++
|
||
|
|
||
7 years ago
|
Variables can also be applied to an entire group at once:
|
||
|
|
||
|
The INI way:
|
||
|
|
||
|
.. code-block:: ini
|
||
13 years ago
|
|
||
|
[atlanta]
|
||
|
host1
|
||
|
host2
|
||
|
|
||
|
[atlanta:vars]
|
||
|
ntp_server=ntp.atlanta.example.com
|
||
|
proxy=proxy.atlanta.example.com
|
||
|
|
||
7 years ago
|
The YAML version:
|
||
|
|
||
|
.. code-block:: yaml
|
||
|
|
||
|
atlanta:
|
||
|
hosts:
|
||
|
host1:
|
||
|
host2:
|
||
|
vars:
|
||
|
ntp_server: ntp.atlanta.example.com
|
||
|
proxy: proxy.atlanta.example.com
|
||
|
|
||
|
Be aware that this is only a convenient way to apply variables to multiple hosts at once; even though you can target hosts by group, **variables are always flattened to the host level** before a play is executed.
|
||
7 years ago
|
|
||
11 years ago
|
.. _subgroups:
|
||
|
|
||
13 years ago
|
Groups of Groups, and Group Variables
|
||
|
+++++++++++++++++++++++++++++++++++++
|
||
13 years ago
|
|
||
7 years ago
|
It is also possible to make groups of groups using the ``:children`` suffix in INI or the ``children:`` entry in YAML.
|
||
|
You can apply variables using ``:vars`` or ``vars:``:
|
||
|
|
||
|
|
||
|
.. code-block:: ini
|
||
13 years ago
|
|
||
|
[atlanta]
|
||
|
host1
|
||
|
host2
|
||
|
|
||
|
[raleigh]
|
||
|
host2
|
||
|
host3
|
||
|
|
||
|
[southeast:children]
|
||
13 years ago
|
atlanta
|
||
|
raleigh
|
||
13 years ago
|
|
||
|
[southeast:vars]
|
||
|
some_server=foo.southeast.example.com
|
||
13 years ago
|
halon_system_timeout=30
|
||
|
self_destruct_countdown=60
|
||
|
escape_pods=2
|
||
13 years ago
|
|
||
|
[usa:children]
|
||
|
southeast
|
||
|
northeast
|
||
|
southwest
|
||
11 years ago
|
northwest
|
||
13 years ago
|
|
||
7 years ago
|
.. code-block:: yaml
|
||
|
|
||
|
all:
|
||
|
children:
|
||
|
usa:
|
||
|
children:
|
||
|
southeast:
|
||
|
children:
|
||
|
atlanta:
|
||
|
hosts:
|
||
|
host1:
|
||
|
host2:
|
||
|
raleigh:
|
||
|
hosts:
|
||
|
host2:
|
||
|
host3:
|
||
|
vars:
|
||
|
some_server: foo.southeast.example.com
|
||
|
halon_system_timeout: 30
|
||
|
self_destruct_countdown: 60
|
||
|
escape_pods: 2
|
||
7 years ago
|
northeast:
|
||
|
northwest:
|
||
|
southwest:
|
||
7 years ago
|
|
||
7 years ago
|
If you need to store lists or hash data, or prefer to keep host and group specific variables separate from the inventory file, see the next section.
|
||
|
Child groups have a couple of properties to note:
|
||
|
|
||
7 years ago
|
- Any host that is member of a child group is automatically a member of the parent group.
|
||
|
- A child group's variables will have higher precedence (override) a parent group's variables.
|
||
|
- Groups can have multiple parents and children, but not circular relationships.
|
||
|
- Hosts can also be in multiple groups, but there will only be **one** instance of a host, merging the data from the multiple groups.
|
||
13 years ago
|
|
||
8 years ago
|
.. _default_groups:
|
||
|
|
||
|
Default groups
|
||
|
++++++++++++++
|
||
|
|
||
|
There are two default groups: ``all`` and ``ungrouped``. ``all`` contains every host.
|
||
8 years ago
|
``ungrouped`` contains all hosts that don't have another group aside from ``all``.
|
||
7 years ago
|
Every host will always belong to at least 2 groups.
|
||
|
Though ``all`` and ``ungrouped`` are always present, they can be implicit and not appear in group listings like ``group_names``.
|
||
8 years ago
|
|
||
11 years ago
|
.. _splitting_out_vars:
|
||
|
|
||
12 years ago
|
Splitting Out Host and Group Specific Data
|
||
|
++++++++++++++++++++++++++++++++++++++++++
|
||
|
|
||
7 years ago
|
The preferred practice in Ansible is to not store variables in the main inventory file.
|
||
12 years ago
|
|
||
7 years ago
|
In addition to storing variables directly in the inventory file, host and group variables can be stored in individual files relative to the inventory file (not directory, it is always the file).
|
||
11 years ago
|
|
||
7 years ago
|
These variable files are in YAML format. Valid file extensions include '.yml', '.yaml', '.json', or no file extension.
|
||
|
See :doc:`YAMLSyntax` if you are new to YAML.
|
||
12 years ago
|
|
||
|
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::
|
||
|
|
||
9 years ago
|
/etc/ansible/group_vars/raleigh # can optionally end in '.yml', '.yaml', or '.json'
|
||
12 years ago
|
/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::
|
||
13 years ago
|
|
||
|
---
|
||
12 years ago
|
ntp_server: acme.example.org
|
||
|
database_server: storage.example.org
|
||
|
|
||
7 years ago
|
It is okay if these files do not exist, as this is an optional feature.
|
||
12 years ago
|
|
||
7 years ago
|
As an advanced use case, you can create *directories* named after your groups or hosts, and
|
||
7 years ago
|
Ansible will read all the files in these directories in lexicographical order. An example with the 'raleigh' group::
|
||
10 years ago
|
|
||
|
/etc/ansible/group_vars/raleigh/db_settings
|
||
|
/etc/ansible/group_vars/raleigh/cluster_settings
|
||
|
|
||
|
All hosts that are in the 'raleigh' group will have the variables defined in these files
|
||
|
available to them. This can be very useful to keep your variables organized when a single
|
||
|
file starts to be too big, or when you want to use :doc:`Ansible Vault<playbooks_vault>` on a part of a group's
|
||
7 years ago
|
variables.
|
||
10 years ago
|
|
||
7 years ago
|
Tip: The ``group_vars/`` and ``host_vars/`` directories can exist in
|
||
11 years ago
|
the playbook directory OR the inventory directory. If both paths exist, variables in the playbook
|
||
10 years ago
|
directory will override variables set in the inventory directory.
|
||
11 years ago
|
|
||
12 years ago
|
Tip: Keeping your inventory file and variables in a git repo (or other version control)
|
||
12 years ago
|
is an excellent way to track changes to your inventory and host variables.
|
||
13 years ago
|
|
||
7 years ago
|
.. _how_we_merge:
|
||
|
|
||
|
How Variables Are Merged
|
||
|
++++++++++++++++++++++++
|
||
|
|
||
|
By default variables are merged/flattened to the specific host before a play is run. This keeps Ansible focused on the Host and Task, so groups don't really surive outside of inventory and host matching. By default, Ansible overwrites variables including the ones defined for a group and/or host (see the `hash_merge` setting to change this) . The order/precedence is (from lowest to highest):
|
||
|
|
||
7 years ago
|
- all group (because it is the 'parent' of all other groups)
|
||
7 years ago
|
- parent group
|
||
|
- child group
|
||
|
- host
|
||
|
|
||
|
When groups of the same parent/child level are merged, it is done alphabetically, and the last group loaded overwrites the previous groups. For example, an a_group will be merged with b_group and b_group vars that match will overwrite the ones in a_group.
|
||
|
|
||
|
.. versionadded:: 2.4
|
||
|
|
||
|
Starting in Ansible version 2.4, users can use the group variable ``ansible_group_priority`` to change the merge order for groups of the same level (after the parent/child order is resolved). The larger the number, the later it will be merged, giving it higher priority. This variable defaults to ``1`` if not set. For example:
|
||
|
|
||
|
.. code-block:: yaml
|
||
|
|
||
|
a_group:
|
||
|
testvar: a
|
||
|
ansible_group_priority: 10
|
||
|
b_group
|
||
|
testvar: b
|
||
|
|
||
|
In this example, if both groups have the same priority, the result would normally have been ``testvar == b``, but since we are giving the ``a_group`` a higher priority the result will be ``testvar == a``.
|
||
|
|
||
11 years ago
|
.. _behavioral_parameters:
|
||
|
|
||
11 years ago
|
List of Behavioral Inventory Parameters
|
||
|
+++++++++++++++++++++++++++++++++++++++
|
||
|
|
||
7 years ago
|
As described above, setting the following variables control how Ansible interacts with remote hosts.
|
||
9 years ago
|
|
||
9 years ago
|
Host connection:
|
||
9 years ago
|
|
||
9 years ago
|
ansible_connection
|
||
8 years ago
|
Connection type to the host. This can be the name of any of ansible's connection plugins. SSH protocol types are ``smart``, ``ssh`` or ``paramiko``. The default is smart. Non-SSH based types are described in the next section.
|
||
9 years ago
|
|
||
9 years ago
|
|
||
8 years ago
|
.. include:: ../rst_common/ansible_ssh_changes_note.rst
|
||
9 years ago
|
|
||
7 years ago
|
General for all connections:
|
||
9 years ago
|
|
||
|
ansible_host
|
||
|
The name of the host to connect to, if different from the alias you wish to give to it.
|
||
|
ansible_port
|
||
|
The ssh port number, if not 22
|
||
|
ansible_user
|
||
|
The default ssh user name to use.
|
||
7 years ago
|
|
||
|
|
||
|
Specific to the SSH connection:
|
||
|
|
||
9 years ago
|
ansible_ssh_pass
|
||
8 years ago
|
The ssh password to use (never store this variable in plain text; always use a vault. See :ref:`best_practices_for_variables_and_vaults`)
|
||
9 years ago
|
ansible_ssh_private_key_file
|
||
|
Private key file used by ssh. Useful if using multiple keys and you don't want to use SSH agent.
|
||
|
ansible_ssh_common_args
|
||
|
This setting is always appended to the default command line for :command:`sftp`, :command:`scp`,
|
||
|
and :command:`ssh`. Useful to configure a ``ProxyCommand`` for a certain host (or
|
||
|
group).
|
||
|
ansible_sftp_extra_args
|
||
|
This setting is always appended to the default :command:`sftp` command line.
|
||
|
ansible_scp_extra_args
|
||
|
This setting is always appended to the default :command:`scp` command line.
|
||
|
ansible_ssh_extra_args
|
||
|
This setting is always appended to the default :command:`ssh` command line.
|
||
|
ansible_ssh_pipelining
|
||
|
Determines whether or not to use SSH pipelining. This can override the ``pipelining`` setting in :file:`ansible.cfg`.
|
||
7 years ago
|
ansible_ssh_executable (added in version 2.2)
|
||
8 years ago
|
This setting overrides the default behavior to use the system :command:`ssh`. This can override the ``ssh_executable`` setting in :file:`ansible.cfg`.
|
||
|
|
||
9 years ago
|
|
||
|
Privilege escalation (see :doc:`Ansible Privilege Escalation<become>` for further details):
|
||
|
|
||
|
ansible_become
|
||
|
Equivalent to ``ansible_sudo`` or ``ansible_su``, allows to force privilege escalation
|
||
|
ansible_become_method
|
||
|
Allows to set privilege escalation method
|
||
|
ansible_become_user
|
||
|
Equivalent to ``ansible_sudo_user`` or ``ansible_su_user``, allows to set the user you become through privilege escalation
|
||
|
ansible_become_pass
|
||
8 years ago
|
Equivalent to ``ansible_sudo_pass`` or ``ansible_su_pass``, allows you to set the privilege escalation password (never store this variable in plain text; always use a vault. See :ref:`best_practices_for_variables_and_vaults`)
|
||
7 years ago
|
ansible_become_exe
|
||
|
Equivalent to ``ansible_sudo_exe`` or ``ansible_su_exe``, allows you to set the executable for the escalation method selected
|
||
|
ansible_become_flags
|
||
|
Equivalent to ``ansible_sudo_flags`` or ``ansible_su_flags``, allows you to set the flags passed to the selected escalation method. This can be also set globally in :file:`ansible.cfg` in the ``sudo_flags`` option
|
||
9 years ago
|
|
||
|
Remote host environment parameters:
|
||
|
|
||
|
ansible_shell_type
|
||
|
The shell type of the target system. You should not use this setting unless you have set the ``ansible_shell_executable`` to a non-Bourne (sh) compatible shell.
|
||
|
By default commands are formatted using ``sh``-style syntax.
|
||
|
Setting this to ``csh`` or ``fish`` will cause commands executed on target systems to follow those shell's syntax instead.
|
||
|
ansible_python_interpreter
|
||
|
The target host python path. This is useful for systems with more
|
||
|
than one Python or not located at :command:`/usr/bin/python` such as \*BSD, or where :command:`/usr/bin/python`
|
||
|
is not a 2.X series Python. We do not use the :command:`/usr/bin/env` mechanism as that requires the remote user's
|
||
|
path to be set right and also assumes the :program:`python` executable is named python, where the executable might
|
||
|
be named something like :program:`python2.6`.
|
||
|
ansible_*_interpreter
|
||
|
Works for anything such as ruby or perl and works just like ``ansible_python_interpreter``.
|
||
|
This replaces shebang of modules which will run on that host.
|
||
11 years ago
|
|
||
9 years ago
|
.. versionadded:: 2.1
|
||
|
|
||
9 years ago
|
ansible_shell_executable
|
||
|
This sets the shell the ansible controller will use on the target machine,
|
||
|
overrides ``executable`` in :file:`ansible.cfg` which defaults to
|
||
|
:command:`/bin/sh`. You should really only change it if is not possible
|
||
|
to use :command:`/bin/sh` (i.e. :command:`/bin/sh` is not installed on the target
|
||
9 years ago
|
machine or cannot be run from sudo.).
|
||
9 years ago
|
|
||
7 years ago
|
Examples from an Ansible-INI host file::
|
||
11 years ago
|
|
||
9 years ago
|
some_host ansible_port=2222 ansible_user=manager
|
||
11 years ago
|
aws_host ansible_ssh_private_key_file=/home/example/.ssh/aws.pem
|
||
|
freebsd_host ansible_python_interpreter=/usr/local/bin/python
|
||
|
ruby_module_host ansible_ruby_interpreter=/usr/bin/ruby.1.9.3
|
||
|
|
||
9 years ago
|
Non-SSH connection types
|
||
|
++++++++++++++++++++++++
|
||
|
|
||
8 years ago
|
As stated in the previous section, Ansible executes playbooks over SSH but it is not limited to this connection type.
|
||
|
With the host specific parameter ``ansible_connection=<connector>``, the connection type can be changed.
|
||
|
The following non-SSH based connectors are available:
|
||
9 years ago
|
|
||
|
**local**
|
||
|
|
||
|
This connector can be used to deploy the playbook to the control machine itself.
|
||
|
|
||
|
**docker**
|
||
|
|
||
8 years ago
|
This connector deploys the playbook directly into Docker containers using the local Docker client. The following parameters are processed by this connector:
|
||
9 years ago
|
|
||
|
ansible_host
|
||
|
The name of the Docker container to connect to.
|
||
|
ansible_user
|
||
|
The user name to operate within the container. The user must exist inside the container.
|
||
|
ansible_become
|
||
|
If set to ``true`` the ``become_user`` will be used to operate within the container.
|
||
|
ansible_docker_extra_args
|
||
|
Could be a string with any additional arguments understood by Docker, which are not command specific. This parameter is mainly used to configure a remote Docker daemon to use.
|
||
|
|
||
8 years ago
|
Here is an example of how to instantly deploy to created containers::
|
||
9 years ago
|
|
||
|
- name: create jenkins container
|
||
8 years ago
|
docker_container:
|
||
|
docker_host: myserver.net:4243
|
||
9 years ago
|
name: my_jenkins
|
||
|
image: jenkins
|
||
|
|
||
|
- name: add container to inventory
|
||
|
add_host:
|
||
|
name: my_jenkins
|
||
|
ansible_connection: docker
|
||
|
ansible_docker_extra_args: "--tlsverify --tlscacert=/path/to/ca.pem --tlscert=/path/to/client-cert.pem --tlskey=/path/to/client-key.pem -H=tcp://myserver.net:4243"
|
||
|
ansible_user: jenkins
|
||
|
changed_when: false
|
||
|
|
||
|
- name: create directory for ssh keys
|
||
|
delegate_to: my_jenkins
|
||
|
file:
|
||
|
path: "/var/jenkins_home/.ssh/jupiter"
|
||
|
state: directory
|
||
12 years ago
|
|
||
7 years ago
|
.. note:: If you're reading the docs from the beginning, this may be the first example you've seen of an Ansible playbook. This is not an inventory file.
|
||
|
Playbooks will be covered in great detail later in the docs.
|
||
|
|
||
13 years ago
|
.. seealso::
|
||
|
|
||
11 years ago
|
:doc:`intro_dynamic_inventory`
|
||
11 years ago
|
Pulling inventory from dynamic sources, such as cloud providers
|
||
11 years ago
|
:doc:`intro_adhoc`
|
||
13 years ago
|
Examples of basic commands
|
||
|
:doc:`playbooks`
|
||
7 years ago
|
Learning Ansible's configuration, deployment, and orchestration language.
|
||
13 years ago
|
`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
|
||
7 years ago
|
|