for non config type stuff, we run from local notebooks, or an admin host
(triggered by our chatbot), depending on what is happening, and who is
triggering it.
Brent
On Thu, Jan 1, 2015 at 12:56 AM, Gary Malouf wrote:
> Interesting, you are deploying ansible in on each of your
Interesting, you are deploying ansible in on each of your production
servers and running it in local mode. I've done that for experimentation,
but did not consider doing it at scale.
To avoid confusion - by local I was asking if people are running playbooks
from their personal machine rather t
And by "goat", I mean host. :-)
On Dec 31, 2014 10:25 PM, "Brent Langston" wrote:
> 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 i
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 yo
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 me
