AP> You run Ansible manually, I haven't talked to anybody who runs Ansible
AP> on an automatic schedule like Puppet and Chef are typically used.
My sense is that the Ansible people think that would be a somewhat odd way
to use it. If you didn't make a change, why would you want to run it? If
you did make a change, then why not run it by hand?
For me, with a long history of thinking that systems should be constantly
ensuring that they're in the right state, that was a weird idea to me. But
I think there's not any reason why you couldn't use Ansible that way. We
don't at my current employer, because we didn't set it up (and design our
workflow with it) with that mind, but we've seen the advantages of it, and
are moving sort of in that direction. (In particular, we now run it on an
automatic schedule in *check* mode, so that it will tell us when it thinks
it should do something, but not automatically do it.)
It's definitely friendly to the mindset that you might want to push out
some changes to some places before you push them out everywhere, which is
sometimes hard to do with an automatic always-be-in-the-right-state
system. There are certainly ways to do that with Puppet and Chef, but you
have to try. With Ansible it's native and easy. Whether that's a good or a
bad thing may vary. :^)
-Josh (iril...@infersys.com)
_______________________________________________
Tech mailing list
Tech@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
