Alexandre can code playbooks and modules faster than me! I'm hoping
it's just the miracle of television.
Check it out here:
http://www.youtube.com/watch?v=up3ofvQNm8c&feature=youtu.be&a
--Michael
Alexandre can code playbooks and modules faster than me! I'm hoping
it's just the miracle of television.
Check it out here:
http://www.youtube.com/watch?v=up3ofvQNm8c&feature=youtu.be&a
--Michael
lol thanks.
To understand the joke at the beginning, you have to watch Rory’s presentation, who tried to laugh at me in his presentation
http://www.youtube.com/watch?v=nsLOzpwYII8&list=PLQIcnBElABat8qE-zSHYr4udWnFyLouJC&index=1
Alexandre
Cool presentation, going really deep into ansible. One tip Alexandre gives at the beginning that I have started to implement myself, is to name files after what they are, so xxxx.playbook.yaml, yyyy.tasks.yaml.
I have tried to organise my directories in playbook, tasks, etc... it works well for general tasks, but I now create one directory per project, and put tasks, vars and playbook files in the same dir. Adding what they are to their name helps a lot.
I use directories for this.
I am overdue for rewriting the 'best practices' section to show a
really good "full ecosystem" tree and also some better style hints.
In queue for this weekend
That will be Great!! , Also is there or can there be a set of examples following the best practices which we can go through.
Another question is there a directory list, I can browse playbooks/modules done by others, So i can just reuse them if needed.
Regards,–
Kavin Kankeshwar
There are some links under "Selected Playbooks", I suspect this to grow a lot