I guess I'm trying to figure out how to setup a complete infrastructure
tree for many systems and playbooks.
Suggestion -- Create one and invite comments. This is how all the BP guides get created originally.
Hi all,
Same with you, I'm also looking into 'howto' structure playbooks and
inputs.
Here's my sample also:
dev-server.yml (include nginx and mysql playbooks inside it)
nginx-ubuntu.yml
- nginx/
- templates/
- nginx.j2
- vars/
- tasks/
- files/
mysql-ubuntu.yml
- mysql/
- templates/
- vars/
- tasks/
- files/
> > We could also do stuff more similar to Puppet land:
>
> > openssh/tasks
> > openssh/files
>
> > Which makes sharing easier
On Wednesday, May 9, 2012 at 11:30 AM, Matt Coddington wrote:
I like this modular setup a lot. One feature I've seen previouslydiscussed on the list is the ability of playbooks to include otherplaybooks... is this something that's on the roadmap? Using theexample below, I can imagine wanting to:
I think the templates/vars/tasks/files/handlers directories are a bit overkill for the run-of-the-mill task. I suspect the average task will only use 2 or 3 of these directories and only contain 1 or 2 files. The same visual separation can be achieved with file extensions that follow a convention (i.e. tasks get .yml, vars get .vars, etc.). I'm sure the organization freaks will disagree, but I'm trying to advocate for Ansible's mantra of simplicity. =)
On Wednesday, May 9, 2012 at 1:46 PM, Suraj Gupta wrote:
I don't follow your point about "two ways to do things...", and expansion is equivalent in both models (you either expand the convention or your expand the directories)We can agree to disagree - it seems that Ansible doesn't impose a structure, which is great. =)
How about shared files? For example, handlers or templates are re-used across nginx/other/other2/... Something to consider for the best practices doc?