I really like saltstack -- I'm automating our deployment and configuration of nagios using it right now.

Just stinks that I ended up doing it this way after making an attempt using other tools (using our Jenkins deployment pipeline) first. Wasted all morning. :(

@mostlycoolmark let me know how much you like it after a while. I'm planning to move off ansible.

@jdormit @mostlycoolmark the bugs are tedious, the maintainers seem to treat my bug reports as PEBCAK and ignore my patches.

We've ended up rewriting lots and lots of stuff using the command module *sigh*.

@mishari I actually have been using it for a while. My previous job used ansible extensively, and this was my first experience with something else.

I really enjoy aspects of it, the fact that it's a message bus (which changes so much about it) is amazing. You get so much more power and flexibility having an agent on the machine.

However, I miss the way ansible made playbooks. In saltstack land it's just jinja... jinja EVERYWHERE.

@mostlycoolmark how well does it work with Docker? (another sw I wish there was a good alternative to)

@mishari There are some docker modules for doing things, but we just use salt for installing docker/maintaining state on our machines and then we have a specific state file (playbook) for running deployments which will basically update the image and environment settings on our target clusters.

We wired up the deployment state file with the salt-api so that jenkins can detect a push to a dev branch, build the image, push to our registry, then call the deployment process to auto-deploy to dev.

Sign in to participate in the conversation
Mastodon for Tech Folks

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!