ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

Update intro_inventory.rst (#18696)

Browse source 
Proposing some small grammatical changes for readability.
This commit is contained in:
Luc Russell 2016-12-01 03:32:51 -05:00 committed by scottb
parent c0695ffa41
commit 8ba5a41a33
1 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
docsite/rst/intro_inventory.rst
View file

@ -33,15 +33,15 @@ The format for ``/etc/ansible/hosts`` is an INI-like format and looks like this:
two.example.com two.example.com
three.example.com three.example.com
The things in brackets are group names, which are used in classifying systems 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. and deciding what systems you are controlling at what times and for what purpose.
It is ok to put systems in more than one group, for instance a server could be both a webserver and a dbserver. It is ok to put systems in more than one group, for instance a server could be both a webserver and a dbserver.
If you do, note that variables will come from all of the groups they are a member of, and variable precedence is detailed in a later chapter. 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.
If you have hosts that run on non-standard SSH ports you can put the port number 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 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. connection but will be used with the `openssh` connection.
To make things explicit, it is suggested that you set them if things are not running on the default port:: To make things explicit, it is suggested that you set them if things are not running on the default port::
@ -284,9 +284,9 @@ Examples from a host file::
Non-SSH connection types Non-SSH connection types
++++++++++++++++++++++++ ++++++++++++++++++++++++
As stated in the previous section, Ansible is executing playbooks over SSH but is not limited to. 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. With the host specific parameter ``ansible_connection=<connector>``, the connection type can be changed.
Following non SSH based connectors are available: The following non-SSH based connectors are available:
**local** **local**
@ -294,7 +294,7 @@ This connector can be used to deploy the playbook to the control machine itself.
**docker** **docker**
This connector deploys the playbook directly into Docker containers using the local Docker client. Following parameters are processed by this connector: This connector deploys the playbook directly into Docker containers using the local Docker client. The following parameters are processed by this connector:
ansible_host ansible_host
The name of the Docker container to connect to. The name of the Docker container to connect to.