Fix list formatting in Getting Started (#68153)
This commit is contained in:
parent
6452a82452
commit
913ee9119a
1 changed files with 9 additions and 7 deletions
|
@ -5,9 +5,10 @@ Getting Started
|
||||||
***************
|
***************
|
||||||
|
|
||||||
Now that you have read the :ref:`installation guide<installation_guide>` and installed Ansible on a control node, you are ready to learn how Ansible works. A basic Ansible command or playbook:
|
Now that you have read the :ref:`installation guide<installation_guide>` and installed Ansible on a control node, you are ready to learn how Ansible works. A basic Ansible command or playbook:
|
||||||
* selects machines to execute against from inventory
|
|
||||||
* connects to those machines (or network devices, or other managed nodes), usually over SSH
|
* selects machines to execute against from inventory
|
||||||
* copies one or more modules to the remote machines and starts execution there
|
* connects to those machines (or network devices, or other managed nodes), usually over SSH
|
||||||
|
* copies one or more modules to the remote machines and starts execution there
|
||||||
|
|
||||||
Ansible can do much more, but you should understand the most common use case before exploring all the powerful configuration, deployment, and orchestration features of Ansible. This page illustrates the basic process with a simple inventory and an ad-hoc command. Once you understand how Ansible works, you can read more details about :ref:`ad-hoc commands<intro_adhoc>`, organize your infrastructure with :ref:`inventory<intro_inventory>`, and harness the full power of Ansible with :ref:`playbooks<playbooks_intro>`.
|
Ansible can do much more, but you should understand the most common use case before exploring all the powerful configuration, deployment, and orchestration features of Ansible. This page illustrates the basic process with a simple inventory and an ad-hoc command. Once you understand how Ansible works, you can read more details about :ref:`ad-hoc commands<intro_adhoc>`, organize your infrastructure with :ref:`inventory<intro_inventory>`, and harness the full power of Ansible with :ref:`playbooks<playbooks_intro>`.
|
||||||
|
|
||||||
|
@ -47,10 +48,11 @@ Confirm that you can connect using SSH to all the nodes in your inventory using
|
||||||
Beyond the basics
|
Beyond the basics
|
||||||
-----------------
|
-----------------
|
||||||
You can override the default remote user name in several ways, including:
|
You can override the default remote user name in several ways, including:
|
||||||
* passing the ``-u`` parameter at the command line
|
|
||||||
* setting user information in your inventory file
|
* passing the ``-u`` parameter at the command line
|
||||||
* setting user information in your configuration file
|
* setting user information in your inventory file
|
||||||
* setting environment variables
|
* setting user information in your configuration file
|
||||||
|
* setting environment variables
|
||||||
|
|
||||||
See :ref:`general_precedence_rules` for details on the (sometimes unintuitive) precedence of each method of passing user information. You can read more about connections in :ref:`connections`.
|
See :ref:`general_precedence_rules` for details on the (sometimes unintuitive) precedence of each method of passing user information. You can read more about connections in :ref:`connections`.
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue