On Tuesday, May 27, 2014 5:33:38 PM UTC-5, Adam Morris wrote:
>
>
> I'm curious why you would do this (not because there is anything 
> inherently wrong with it, but I'm wondering what your thinking is here).
>

In short -- I am trying to avoid running 88 non-changing tasks to execute 2 
changing ones. For instance; when I'm applying sites to a server, I don't 
want to also apply apache, and whatever else apache depends on, and so 
forth -- just to apply the sites.  Here's an example playbook;

https://github.com/iceburg-net/ansible-pcd/blob/master/iceburg-sites.yml

Apache was setup in a playbook I previously executed (as a dependency of 
the php role);

https://github.com/iceburg-net/ansible-pcd/blob/master/webservers.yml


... so, for instance, when I'm applying sites via the apache-site role, 
it's really useful to know where to put SSL certificates. I define where to 
put ssl certificates in an upstream role (httpd) as `httpd_ssl_dir`.   
`httpd_ssl_dir` best belongs in the httpd role and not the apache_sites 
roles because OTHER ROLES may want to use it; and it's the natural spot to 
look for it. 

I know my organizational process differs from Michael and it's made it very 
inefficient to me to work with ansible; but none-the-less it's my favorite 
infrastructure automation tool && I believe my struggles have always been 
failure to clearly communicate my ideas. I think I'm closer now && I hope 
that I've created something respectable. 

I believe elegance and simplicity are one in the same, and, in fact, 
dependent upon eachother.

~ Brice
 

-- 
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/3658e1c3-c30e-4451-baa8-afb1d255b0b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to