blob: 818c7fbe37981276edf761417476f7f1566e8e98 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
|
.. _getting_started_index:
############################
Getting started with Ansible
############################
Ansible automates the management of remote systems and controls their desired state.
A basic Ansible environment has three main components:
Control node
A system on which Ansible is installed.
You run Ansible commands such as ``ansible`` or ``ansible-inventory`` on a control node.
Managed node
A remote system, or host, that Ansible controls.
Inventory
A list of managed nodes that are logically organized.
You create an inventory on the control node to describe host deployments to Ansible.
.. image:: ../images/ansible_basic.svg
:width: 400px
:align: center
:height: 200px
:alt: Basic components of an Ansible environment include a control node, an inventory of managed nodes, and a module copied to each managed node.
Ready to start using Ansible?
Complete the following steps to get up and running:
#. Install Ansible. Visit the :ref:`installation guide<installation_guide>` for complete details.
.. code-block:: bash
python3 -m pip install --user ansible
#. Create an inventory by adding the IP address or fully qualified domain name (FQDN) of one or more remote systems to ``/etc/ansible/hosts``.
The following example adds the IP addresses of three virtual machines in KVM:
.. code-block:: ini
[myvirtualmachines]
192.0.2.50
192.0.2.51
192.0.2.52
#. Verify the hosts in your inventory.
.. code-block:: bash
ansible all --list-hosts
.. code-block:: ansible-output
hosts (1):
192.0.2.50
192.0.2.51
192.0.2.52
#. Set up SSH connections so Ansible can connect to the managed nodes.
a. Add your public SSH key to the ``authorized_keys`` file on each remote system.
b. Test the SSH connections, for example:
.. code-block:: bash
ssh username@192.0.2.50
If the username on the control node is different on the host, you need to pass the ``-u`` option with the ``ansible`` command.
#. Ping the managed nodes.
.. code-block:: bash
ansible all -m ping
.. literalinclude:: ansible_output/ping_output.txt
:language: text
Congratulations! You are now using Ansible.
Continue by :ref:`learning how to build an inventory<get_started_inventory>`.
.. seealso::
`Ansible Demos <https://github.com/ansible/product-demos>`_
Demonstrations of different Ansible usecases
`Ansible Labs <https://www.ansible.com/products/ansible-training>`_
Labs to provide further knowledge on different topics
`Mailing List <https://groups.google.com/group/ansible-project>`_
Questions? Help? Ideas? Stop by the list on Google Groups
:ref:`communication_irc`
How to join Ansible chat channels
.. toctree::
:maxdepth: 1
get_started_inventory
get_started_playbook
basic_concepts
|
