3 ms·
Interesting, I went the other direction recently, from systemd to Nomad. I was motivated by a move away from config management in favor of commands wrapping No
by dmwilcox 6y ago
Interesting, I went the other direction recently, from systemd to Nomad.
I was motivated by a move away from config management in favor of commands wrapping Nomad API calls. For a "devs on-call" model this was preferable to being gatekeepers of PRs against config management.
To glue the whole thing together I got Consul Connect going in the Nomad jobs, so service config complexity was comparable to docker-compose.
Saying this out loud makes me realize it was the organizational model I was pursuing that led me here (so called "production ownership"). And I'm not a big config management fan ;). I take it you have dedicated Ops teams or Devs willing to learn Ansible well?
- aprdm 6y agoOur devs to their own ops using our blessed ansible galaxy roles + creating their own when necessary. It is all pretty standardized, is rare that someone needs to create a new galaxy role for example. We expect our teams to know their way around Ansible ( which hasn’t been a problem ), we have internal docs and training