<p>Generally, Ansible is very flexible and often there are more "correct" solutions.</p>

<p>Start for example with the question "Where do the configuration data come from?", put the default data to the roles and decide which variables should be configured in "<em>group_vars/host_vars</em>", in the roles, and which in the playbooks. Review <a href="https://docs.ansible.com/ansible/latest/user_guide/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable" rel="nofollow noreferrer">Variable precedence: Where should I put a variable?</a>. To set paths to the inventory, roles, and others see <a href="https://docs.ansible.com/ansible/latest/reference_appendices/config.html#ansible-configuration-settings" rel="nofollow noreferrer">Ansible Configuration Settings</a>.</p>

<p>To answer your questions:</p>

<blockquote>
  <p>Q1: If I run ansible-playbook -i /path to hostfile/ how do I pick the specific host I want to run against? ...where can I put the specific host that is in the hosts file?</p>
</blockquote>

<p>To pick for example "<em>router1</em>" start a play with:</p>

<pre><code>- hosts: router1
</code></pre>

<blockquote>
  <p>Q2: How do I point to the playbooks that are in the root folder without backing up directories each time like this: "ansible-playbook -i hosttarget ../../myplaybook.yml"</p>
</blockquote>

<p>Configure <a href="https://docs.ansible.com/ansible/latest/reference_appendices/config.html#default-host-list" rel="nofollow noreferrer">DEFAULT_HOST_LIST</a>. For example:</p>

<pre><code># ANSIBLE_HOSTS=$PWD/inventory/client1/hosts ansible-playbook myplaybook.yml
</code></pre>

<blockquote>
  <p>Q3: How can I load additional credentials files or group variables?</p>
</blockquote>

<p>There are a lot of options described in <a href="https://docs.ansible.com/ansible/latest/user_guide/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable" rel="nofollow noreferrer">Variable precedence: Where should I put a variable?</a>. For example "<em>include_vars</em>" might be useful to load additional credentials. For "group variables" pick from the <a href="https://docs.ansible.com/ansible/latest/user_guide/playbooks_variables.html#id17" rel="nofollow noreferrer">options</a>.</p>

CC BY-SA 4.0
2019-04-30T21:30:52.120Z
Your text describes `DEFAULT_HOST_LIST` but your example uses `ANSIBLE_HOSTS`.  That example also won't work unless the variable was already `export`ed.  You could also get rid of the semicolon and then setting the variable would just effect that one command.
chicks
CC BY-SA 4.0
2019-04-30T22:02:32.060Z
@chicks I've removed the semicolon. Thank you.  ANSIBLE_HOSTS is the name of the corresponding environment variable. See [DEFAULT_HOST_LIST](https://docs.ansible.com/ansible/latest/reference_appendices/config.html#default-host-list).
Vladimir Botka
CC BY-SA 4.0
2019-05-02T14:52:57.840Z
Thank you for your reply Mr. Botka and sorry for the delay in my response.  I have been out sick for nearly a week.  What I was looking for was some help with much more complex issues.  Currently I am limiting exactly like you show in the play but the intention is not to have to modify the play each time as it is a generic playbook used for multiple clients.  I am going to modify the original question as the comments are not long enough for me to explain correctly.
Daniel Flick
CC BY-SA 4.0
2019-05-02T15:08:56.893Z
Please follow: [How to create a Minimal, Complete, and Verifiable example](https://stackoverflow.com/help/mcve).
Vladimir Botka
CC BY-SA 4.0
2019-05-02T16:50:53.493Z
Please have a look at the Help Center:  [do not add a comment on your question or on an answer to say "Thank you".](https://stackoverflow.com/help/someone-answers).
Vladimir Botka
CC BY-SA 4.0
2019-04-26T10:10:14.037Z
2019-04-30T21:50:45.363Z
2019-04-30T21:50:45.363Z
Vladimir Botka
<p>I am very new to ansible and I think I am lacking something basic that I am not finding in the examples or on github as to the directory structure and its use.</p>

<p>I have set up my directory structure using ansible best practices document located here:</p>

<p><a href="https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html#directory-layout" rel="nofollow noreferrer">https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html#directory-layout</a></p>

<p>But the documentation is not clear on how the structure should be used in practice.  I have multiple clients in which the inventories must be kept seperate.  My directory structure is set up as follows:</p>

<pre><code>inventory/
   client1/
      group_vars/
        all
        credentials.yml &lt;encrypted&gt;
        router
        switch
        firewall 
      host_vars/
        router1
        switch1
        firewall1
      hosts
   client2/
      group_vars/
        all
        credentials.yml &lt;encrypted&gt;
        router
        switch
        firewall 
      host_vars/
        router1
        switch1
        firewall1
      hosts
roles/
  role1/
     tasks/
       main.yml
  role2/
     tasks/
       main.yml
</code></pre>

<p>The hosts files contain routers, switches and firewalls (grouped as such) like this:</p>

<pre><code>[router]
router1 ansible_host=1.2.3.4

[switch]
switch1 ansible_host=5.6.7.8

[firewall]
firewall1 ansible_host=9.10.11.12
</code></pre>

<p>The group_vars have router, switch and firewall files with the appropriate variables.  There is a credentials.yml in the ./inventory/client name/group_vars directory that is encrypted and should be loaded for every playbook. I understand precedence and I am not having any trouble there.</p>

<p>If I run ansible-playbook -i /path to hostfile/ how do I pick the specific host I want to run against?<br>
<code>ansible-playbook -i inventory/client1/hosts myplaybook.yml</code> &lt;--where can I put the specific host that is in the hosts file?  I have tried several different methods and none seem to work.  My guess is that I am running the ansible-playbook command from the wrong directory.</p>

<p>If I run ansible-playbook in the correct inventory folder (./inventory/client1/) I can pick the host, but how do I point to the playbooks that are in the root folder without backing up directories each time like this:</p>

<pre><code>ansible-playbook -i hosttarget ../../myplaybook.yml
</code></pre>

<p>It seems poor form to have to back out of the directory each time just to run a playbook.  If I just put the playbook name, it does not find it so I am thinking that it was not the intention to run ansible-playbook in this way either.</p>

<p>How can I load additional credentials files or group variables?  It would be nice if there was a way to pull this from the directory that contains the inventory but I can't figure that out.  I was thinking of possibly loading extra_vars in the playbook and setting a value for a variable called "client" in the "all" file, but it seems kludgy and prone to error.  I was hoping that there was some type of automatic pull that can be done like the loading of the group_vars and host_vars but maybe I am missing something.</p>

<pre><code>cat ./inventory/client1/all
client=client1

extra_vars=~/inventory/{{ client }}/credentials.yml
</code></pre>

<p>My thought is that since the inventory layout is shown as Ansible best practices, then maybe I am not fully understanding of how I should be running playbooks.  </p>

<p>It would seem to me that I should be able to run ansible-playbook in the root directory that contains all my plays and point it to an inventory file easily.  The playbooks should be reusable across all clients with no changes required and there should be an easy way to load variable files without having to specify them each time at the command line.  Ansible already does this very well with group_vars and host_vars so I am thinking that I am just missing something simple.</p>

<p>I have a workaround for this now using the following command line:
ansible-playbook -i inventory/atcog ecats_l2l.yml --extra-vars @inventory/atcog/group_vars/credentials.yml</p>

<p>This run a configuration playbook that runs a task that builds a VPN.  This VPN is built for a client called atcog.  I have to add this very long --extra-vars @inventory/atcog/group_vars/credentials.yml to access the credentials file for the client "atcog".  I also have to manually modify the playbook to have it only run the play on a single host by adding - hosts: atcogfirewall-1.  It seems like there should be a better way.</p>

<p>So let's say I now want to push this VPN to another client.  I now have to edit the playbook and change - hosts: krifirewall-6, then I need to send this command to make sure the right credential file is used:
ansible-playbook -i inventory/kri ecats_l2l.yml --extra-vars @inventory/kri/group_vars/credentials.yml</p>

<p>Seems like a lot of places where a typo or forgetting to update a playbook host entry can cause this to run on the wrong device or run with the wrong credentials.  </p>

<p>So if I add something like 
extra_vars=~/inventory/{{ client }}/credentials.yml
in the playbook I can likely mitigate the need to put the --extra-vars in the command line but I can't figure out a way to resolve the whole choosing the individual host issue without manually updating the playbook each time which is just asking for human error.</p>

<p>Here is a screenshot of the layout.  The playbook I am running is in the root directory but is not shown as I could not capture it all on 1 screen.
<a href="https://i.sstatic.net/ecEBC.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/ecEBC.png" alt="Screenshot of multiple client inventories and tasks"></a></p>

CC BY-SA 4.0
2019-04-24T09:19:25.170Z
Thanks Anthon.  I am not following your first comment but I think you may be referring to the layout of my inventory file.  The intention was to show the directory structure, not yaml.  I guess I could have shown it like this::

/inventory
  /client1
    /group_vars
     all
As for the location of the best practices, I was referring to the Ansible best practices located here: 
 https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html#directory-layout
Daniel Flick
<ansible><yaml><ansible-inventory>
Unable to run playbooks using Ansible best practices layout
Daniel Flick
# Unable to run playbooks using Ansible best practices layout

(Asked by: username_0 on 2019-04-24)

I am very new to ansible and I think I am lacking something basic that I am not finding in the examples or on github as to the directory structure and its use.
I have set up my directory structure using ansible best practices document located here:
https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html#directory-layout
But the documentation is not clear on how the structure should be used in practice.  I have multiple clients in which the inventories must be kept seperate.  My directory structure is set up as follows:
inventory/
   client1/
      group_vars/
        all
        credentials.yml 
        router
        switch
        firewall 
      host_vars/
        router1
        switch1
        firewall1
      hosts
   client2/
      group_vars/
        all
        credentials.yml 
        router
        switch
        firewall 
      host_vars/
        router1
        switch1
        firewall1
      hosts
roles/
  role1/
     tasks/
       main.yml
  role2/
     tasks/
       main.yml

The hosts files contain routers, switches and firewalls (grouped as such) like this:
[router]
router1 ansible_host=1.2.3.4

[switch]
switch1 ansible_host=5.6.7.8

[firewall]
firewall1 ansible_host=9.10.11.12

The group_vars have router, switch and firewall files with the appropriate variables.  There is a credentials.yml in the ./inventory/client name/group_vars directory that is encrypted and should be loaded for every playbook. I understand precedence and I am not having any trouble there.
If I run ansible-playbook -i /path to hostfile/ how do I pick the specific host I want to run against?
ansible-playbook -i inventory/client1/hosts myplaybook.yml <--where can I put the specific host that is in the hosts file?  I have tried several different methods and none seem to work.  My guess is that I am running the ansible-playbook command from the wrong directory.
If I run ansible-playbook in the correct inventory folder (./inventory/client1/) I can pick the host, but how do I point to the playbooks that are in the root folder without backing up directories each time like this:
ansible-playbook -i hosttarget ../../myplaybook.yml

It seems poor form to have to back out of the directory each time just to run a playbook.  If I just put the playbook name, it does not find it so I am thinking that it was not the intention to run ansible-playbook in this way either.
How can I load additional credentials files or group variables?  It would be nice if there was a way to pull this from the directory that contains the inventory but I can't figure that out.  I was thinking of possibly loading extra_vars in the playbook and setting a value for a variable called "client" in the "all" file, but it seems kludgy and prone to error.  I was hoping that there was some type of automatic pull that can be done like the loading of the group_vars and host_vars but maybe I am missing something.
cat ./inventory/client1/all
client=client1

extra_vars=~/inventory/{{ client }}/credentials.yml

My thought is that since the inventory layout is shown as Ansible best practices, then maybe I am not fully understanding of how I should be running playbooks.  
It would seem to me that I should be able to run ansible-playbook in the root directory that contains all my plays and point it to an inventory file easily.  The playbooks should be reusable across all clients with no changes required and there should be an easy way to load variable files without having to specify them each time at the command line.  Ansible already does this very well with group_vars and host_vars so I am thinking that I am just missing something simple.
I have a workaround for this now using the following command line:
ansible-playbook -i inventory/atcog ecats_l2l.yml --extra-vars @inventory/atcog/group_vars/credentials.yml
This run a configuration playbook that runs a task that builds a VPN.  This VPN is built for a client called atcog.  I have to add this very long --extra-vars @inventory/atcog/group_vars/credentials.yml to access the credentials file for the client "atcog".  I also have to manually modify the playbook to have it only run the play on a single host by adding - hosts: atcogfirewall-1.  It seems like there should be a better way.
So let's say I now want to push this VPN to another client.  I now have to edit the playbook and change - hosts: krifirewall-6, then I need to send this command to make sure the right credential file is used:
ansible-playbook -i inventory/kri ecats_l2l.yml --extra-vars @inventory/kri/group_vars/credentials.yml
Seems like a lot of places where a typo or forgetting to update a playbook host entry can cause this to run on the wrong device or run with the wrong credentials.  
So if I add something like 
extra_vars=~/inventory/{{ client }}/credentials.yml
in the playbook I can likely mitigate the need to put the --extra-vars in the command line but I can't figure out a way to resolve the whole choosing the individual host issue without manually updating the playbook each time which is just asking for human error.
Here is a screenshot of the layout.  The playbook I am running is in the root directory but is not shown as I could not capture it all on 1 screen.

**Tags:** ansible, yaml, ansible-inventory

> **Comments:**
> **username_0**: Thanks Anthon.  I am not following your first comment but I think you may be referring to the layout of my inventory file.  The intention was to show the directory structure, not yaml.  I guess I could have shown it like this::  /inventory   /client1     /group_vars      all As for the location of the best practices, I was referring to the Ansible best practices located here:   https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html#directory-layout  

---

## 1 answers

### Answer by username_1 on 2019-04-26. Score: 3

Generally, Ansible is very flexible and often there are more "correct" solutions.
Start for example with the question "Where do the configuration data come from?", put the default data to the roles and decide which variables should be configured in "group_vars/host_vars", in the roles, and which in the playbooks. Review Variable precedence: Where should I put a variable?. To set paths to the inventory, roles, and others see Ansible Configuration Settings.
To answer your questions:

Q1: If I run ansible-playbook -i /path to hostfile/ how do I pick the specific host I want to run against? ...where can I put the specific host that is in the hosts file?

To pick for example "router1" start a play with:
- hosts: router1


Q2: How do I point to the playbooks that are in the root folder without backing up directories each time like this: "ansible-playbook -i hosttarget ../../myplaybook.yml"

Configure DEFAULT_HOST_LIST. For example:
# ANSIBLE_HOSTS=$PWD/inventory/client1/hosts ansible-playbook myplaybook.yml


Q3: How can I load additional credentials files or group variables?

There are a lot of options described in Variable precedence: Where should I put a variable?. For example "include_vars" might be useful to load additional credentials. For "group variables" pick from the options.

> **Comments:**
> **username_2**: Your text describes `DEFAULT_HOST_LIST` but your example uses `ANSIBLE_HOSTS`.  That example also won't work unless the variable was already `export`ed.  You could also get rid of the semicolon and then setting the variable would just effect that one command.  
> **username_1**: @username_2 I've removed the semicolon. Thank you.  ANSIBLE_HOSTS is the name of the corresponding environment variable. See [DEFAULT_HOST_LIST](https://docs.ansible.com/ansible/latest/reference_appendices/config.html#default-host-list).  
> **username_0**: Thank you for your reply Mr. Botka and sorry for the delay in my response.  I have been out sick for nearly a week.  What I was looking for was some help with much more complex issues.  Currently I am limiting exactly like you show in the play but the intention is not to have to modify the play each time as it is a generic playbook used for multiple clients.  I am going to modify the original question as the comments are not long enough for me to explain correctly.  
> **username_1**: Please follow: [How to create a Minimal, Complete, and Verifiable example](https://stackoverflow.com/help/mcve).  
> **username_1**: Please have a look at the Help Center:  [do not add a comment on your question or on an answer to say "Thank you".](https://stackoverflow.com/help/someone-answers).  

---

