Ansible deploys are much nicer when you tag the needs-to-be-done-once stuff versus the every-deploy-stuff. Cut our deploy time ~80%.
-
-
That’s what your tweets about Ansible do to me.
-
What do I read or do to hurt myself (and you) less?
- 1 more reply
New conversation -
-
-
the longer you work with ansible the less you do the "ansible" way. To the point that you switch back to bash.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
we're pretty invested in docker + kuber as a deploy strategy here. Docker builds are fast if you set them up right.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It's a pity the declaration language is such a dog's breakfast.
-
I've come to the conclusion that Ansible is a good backend transport for a frontend systems declaration language...
End of conversation
New conversation -
-
-
I usually have separate playbooks for setup and deploy.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It's still way faster than chef or similar. Ansible runs in 10 minutes for me, chef took 30 from start to finish with no changes.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Agreed. Just in case you haven’t, check pipelining setting, ControlPersist support on ctrl machine, “UseDNS no“ on target
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
reasonable conclusion - xtra cmd flags feel non-standard, hard to memorize. I tend to use --tags every time, put common in a .sh
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.