We, at hioscar.com, run ansible local from the local goat for all config runs from cron, every 10 minutes.
Pros: It's fast It's automatic, so devs don't need direct access to our systems. Con: It isn't aware of the whole inventory, mainly due to our setup. This ends up complicating things when you build logic around inventory knowledge of other systems. An example is setting quorum size based on number of nodes in the inventory. Overall it's been a cool setup. If the con is a show stopper, then check out ansible tower. On Dec 31, 2014 10:04 PM, "Gary Malouf" <[email protected]> wrote: > In the past, we ran Ansible on our bastion aka jump host. I've seen many > postings online that people actually install Ansible locally and manage it > completely from there. What are the pros and cons of going with that setup > over having Ansible installed on an instance? > > -- > 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/6e854963-cd83-4d0f-9c47-36a24921b847%40googlegroups.com > <https://groups.google.com/d/msgid/ansible-project/6e854963-cd83-4d0f-9c47-36a24921b847%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CABta7G2Lw7mGZ_iw_30VXme0Jh_Z5qMy8gihJaB0GwUF44GO0g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
