Live data from Hacker News

Salt stack, the simpler puppet

saltstack.com

31–34 of 34 posts

Re: Salt stack, the simpler puppet

#31
post #25
post #9

At Ayatii we use Salt both for initial configuration and scaling. It's very easy to get setup, and the concepts of States, Pillars and Reactors are easy enough to grasp and start hacking useful utilities for your deployment. For instance, with a couple lines of Python, I was able to 'react' to any new DigitalOcean instance that was created and able to update DNS records or Nginx config (if it was a certain type of in…

njpatel I would love to get my hands on your python code on the reactor stuff. Still haven't found a real world example for updating loadbalancers or dns.

I was going to do a blog post but never got around to it! I copy-and-pasted the DNS one we use into a gist (removing specific bits of our setup). We use DO, but this should get you to a point where all the bits are working and then you can do as you wish.

Excuse the Python code...I'm very much not a Python guy! https://gist.github.com/njpatel/8603816

Re: Salt stack, the simpler puppet

#32
post #24

Earlier quoted context omitted.

Salt additionally is not opencore, but truly opensource.

Ansible is open source. We do have a GUI/REST-API company product that sits on top of Ansible that adds things like role based access control, centralized logging, and so on. This is not an enterprise version of Ansible, but an additional offering. By making this commercial we can produce a really high quality product by hiring some top notch developers, and can move forward at a faster pace. There are no proprietary…

Thanks for the great tool! I think the GUI and REST API a pay-for service was a smart decision and will hopefully allow you guys to keep building out the project while also making a living.

Not sure where the confusion about Ansible being not fully opensource comes from. And it's not as though Salt doesn't have enterprise support and tool integration that you can pay for too.

As I noted earlier, conf management has so many facets and reasons for being implemented that no one tool will ever win a battle. Honestly I'm happy to have such a wide open space right now with so many great and open source projects in it. When I started developing web apps 10 years ago, there was nothing that begins to approach the robustness of all four big players in this arena right now.

Thank you to all the hardworking contributors, paid and unpaid, to Puppet, Chef, Salt and Ansible. Thank you!

Re: Salt stack, the simpler puppet

#33

Earlier quoted context omitted.

Disclaimer -- Ansible author here. This isn't exactly an even comparison -- Ansible has been working on it's SSH implementation for about two years, so it's pretty evolved, and you won't find that elsewhere. By comparison, Salt's implementation is currently a rough sketch, and one they discourage using. Ansible has a pretty robust implementation that allows sudo and su operations, and is pretty finely tuned for using…

Disclaimer: Salt developer here. Please don't conflate acknowledging that the ssh implementation is a newly-implemented feature with "discouraging" the use of it. You're better than that.

I agree that there's no reason to assume that Salt discourages the use of a feature that clearly required time to implement. But in the docs and videos I've seen of the new interface the words "way slower" come up over and over again.

There's a vibe that salt-ssh is an answer to folks who would use Ansible, and less a feature that Salt has long had on it's list of things that need to be implemented.

Not saying there's any truth to that statement, but that's the vibe I got from the folks I know who use Salt and knew that I preferred Ansible at the time. So while the word "discouraging" is a bit heavy, there's an absence of leadership as to why salt-ssh was developed and when it's appropriate vs. 0mq.

Re: Salt stack, the simpler puppet

#34
post #31
post #25

Earlier quoted context omitted.

njpatel I would love to get my hands on your python code on the reactor stuff. Still haven't found a real world example for updating loadbalancers or dns.

I was going to do a blog post but never got around to it! I copy-and-pasted the DNS one we use into a gist (removing specific bits of our setup). We use DO, but this should get you to a point where all the bits are working and then you can do as you wish. Excuse the Python code...I'm very much not a Python guy! https://gist.github.com/njpatel/8603816

Thanks
Post reply on HN