Re: [ansible-project] Scaling the Ansible Hierarchy?

2016-11-22 Thread Kai Stian Olstad
On 22. nov. 2016 20:25, burns...@umn.edu wrote: > Ok so I ended up rolling back to playbooks in the top level directory. > > I got myself turned around a bit here. The {{roles_path}} as part of the > include actually wasn't working; which, I should have known since you can't > use ansible.cfg

Re: [ansible-project] Scaling the Ansible Hierarchy?

2016-11-22 Thread Kai Stian Olstad
On 22. nov. 2016 19:53, burns...@umn.edu wrote: > However, it seems that my plays can no longer find my group_vars and other > such objects. Basic structure is below: > ansible.cfg > .ansible/inventory > playbooks/ >pb.yml > roles/ > # roles... > host_vars/ > # host_vars... > group_vars/

Re: [ansible-project] Scaling the Ansible Hierarchy?

2016-11-22 Thread 'Jeffrey Wen' via Ansible Project
When you run the ansible-playbook, what about prefixing the command with ANSIBLE_ROLES_PATH. For example: ANSIBLE_ROLES_PATH=your_path ansible-playbook site.yml On Tuesday, November 22, 2016 at 2:25:08 PM UTC-5, burn...@umn.edu wrote: > > Ok so I ended up rolling back to playbooks in the top

Re: [ansible-project] Scaling the Ansible Hierarchy?

2016-11-22 Thread burns498
Ok so I ended up rolling back to playbooks in the top level directory. I got myself turned around a bit here. The {{roles_path}} as part of the include actually wasn't working; which, I should have known since you can't use ansible.cfg parameters in tasks like that. I think my main problem is

Re: [ansible-project] Scaling the Ansible Hierarchy?

2016-11-22 Thread burns498
Thanks for the info! I tried this in my own environment, since I actually had a similar question before. Moved playbooks to a playbooks dir. Set role_path=./roles. This broke my include statements, which I now modified to '- include: "{{ roles_path }} /role_handlers_ant/handlers/main.yml"'.

Re: [ansible-project] Scaling the Ansible Hierarchy?

2016-11-22 Thread 'Jeffrey Wen' via Ansible Project
Thank you, Kai! That works for me! On Tuesday, November 22, 2016 at 12:38:00 PM UTC-5, Kai Stian Olstad wrote: > > On 21. nov. 2016 16:38, 'Jeffrey Wen' via Ansible Project wrote: > > *Question*: What is the solution to not overfilling my top-level > directory > > with yml files? (Or is this

Re: [ansible-project] Scaling the Ansible Hierarchy?

2016-11-22 Thread Kai Stian Olstad
On 21. nov. 2016 16:38, 'Jeffrey Wen' via Ansible Project wrote: > *Question*: What is the solution to not overfilling my top-level directory > with yml files? (Or is this normal?) At you top level, create a directory called playbooks (or choose you favorite name). Then you can run

[ansible-project] Scaling the Ansible Hierarchy?

2016-11-22 Thread 'Jeffrey Wen' via Ansible Project
Hello, I am currently following the directory layout provided by Ansible. I understand that if I keep all of my roles/* in a directory, I can easily call each role from the top level directory like so: site.yml