Hi guys, Starting here too with Ansible, this is what we are using for now. Do you see any problems when using the following topology?
.ansible |-- roles | |-- ansible | |-- tasks | |-- main.yml | |-- git | |-- tasks | |-- main.yml | |-- linux-server | |-- tasks | |-- main.yml | |-- timezone.yml |-- scope | |-- client1 | |-- inventory | |-- db.yml | |-- linux-server.yml | |-- playbooks | |-- db.yml | |-- web.yml | |-- vars | |-- aws.yml | |-- azu.yml | |-- client2 | |-- inventory | |-- windows-servers.yml | |-- web.yml | |-- playbooks | |-- windows-servers.yml | |-- web.yml | |-- vars | |-- aws.yml | |-- azu.yml On Monday, November 24, 2014 at 12:30:13 PM UTC-5, Rick Kasten wrote: > > I checked through the documentation for ansible.cfg > <http://docs.ansible.com/intro_configuration.html>, and the only setting > I found was roles_path. I know everything else can be set via command > switches, but that's another issue. > > There will be very little difference in the playbooks themselves across > customer, so we decided to go with something like this: > > ansible/ > |-- group_vars/ > |-- inventories/ > | |-- customer1/ > | | |-- host_vars/ > | | `-- customer1 > | `-- customer2/ > | |-- host_vars/ > | `-- customer2 > |-- library/ > |-- playbooks/ > |-- roles/ > |-- database/ > `-- webserver/ > > That way ansible/ should remain completely empty. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/b59d0656-90fd-46cb-9cc2-b600eb6b21ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
