Commit da458bbf by Brian Coca

added way to display inventory vars for host to faq + some minor fixes/edits

parent 323012be
...@@ -154,7 +154,15 @@ Ansible by default gathers "facts" about the machines under management, and thes ...@@ -154,7 +154,15 @@ Ansible by default gathers "facts" about the machines under management, and thes
ansible -m setup hostname ansible -m setup hostname
This will print out a dictionary of all of the facts that are available for that particular host. This will print out a dictionary of all of the facts that are available for that particular host. You might want to pipe the output to a pager.
.. _browse_inventory_vars:
How do I see all the inventory vars defined for my host?
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
You can see the resulting vars you define in inventory running the following command::
ansible -m debug -a "var=hostvars['hostname']" localhost
.. _host_loops: .. _host_loops:
...@@ -208,7 +216,7 @@ Anyway, here's the trick:: ...@@ -208,7 +216,7 @@ Anyway, here's the trick::
{{ hostvars[groups['webservers'][0]]['ansible_eth0']['ipv4']['address'] }} {{ hostvars[groups['webservers'][0]]['ansible_eth0']['ipv4']['address'] }}
Notice how we're pulling out the hostname of the first machine of the webservers group. If you are doing this in a template, you Notice how we're pulling out the hostname of the first machine of the webservers group. If you are doing this in a template, you
could use the Jinja2 '#set' directive to simplify this, or in a playbook, you could also use set_fact: could use the Jinja2 '#set' directive to simplify this, or in a playbook, you could also use set_fact::
- set_fact: headnode={{ groups[['webservers'][0]] }} - set_fact: headnode={{ groups[['webservers'][0]] }}
...@@ -310,6 +318,7 @@ The no_log attribute can also apply to an entire play:: ...@@ -310,6 +318,7 @@ The no_log attribute can also apply to an entire play::
Though this will make the play somewhat difficult to debug. It's recommended that this Though this will make the play somewhat difficult to debug. It's recommended that this
be applied to single tasks only, once a playbook is completed. be applied to single tasks only, once a playbook is completed.
I don't see my question here I don't see my question here
++++++++++++++++++++++++++++ ++++++++++++++++++++++++++++
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment