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

Fix document structure (#44935)

Browse source
This commit is contained in:
Dag Wieers 2018-08-31 00:16:36 +02:00 committed by GitHub
parent 2a4e92aab7
commit 32fc6746d8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/docsite/rst/scenario_guides/guide_aci.rst
View file

@ -101,14 +101,14 @@ After registering the return values of the :ref:`aci_tenant <aci_tenant_module>`
Running on the controller locally
---------------------------------
.................................
As originally designed, Ansible modules are shipped to and run on the remote target(s), however the ACI modules (like most network-related modules) do not run on the network devices or controller (in this case the APIC), but they talk directly to the APIC's REST interface.
For this very reason, the modules need to run on the local Ansible controller (or are delegated to another system that *can* connect to the APIC).
Delegating to localhost
.......................
```````````````````````
So let us assume we have our target configured in the inventory using the FQDN name as the ``ansible_host`` value, as shown below.
.. code-block:: yaml
@ -137,7 +137,7 @@ If one would forget to add this directive, Ansible will attempt to connect to th
Using the local connection method
.................................
`````````````````````````````````
Another option frequently used, is to tie the ``local`` connection method to this target so that every subsequent task for this target will use the local connection method (hence run it locally, rather than use SSH).
In this case the inventory may look like this: