Live data from Hacker News

Salt: Like Puppet, Except It Doesn’t Suck

blog.smartbear.com

71–80 of 274 posts

Re: Salt: Like Puppet, Except It Doesn’t Suck

#71
post #52

Earlier quoted context omitted.

I don't understand why ZeroMQ outside of a data center would be a deal breaker for anyone. You do realize the data on the wire is encrypted right?

Awesome. How many people have reviewed it for flaws? How many people have reviewed OpenSSH?

Maybe they should hire you to review it for security flaws?

Re: Salt: Like Puppet, Except It Doesn’t Suck

#72
post #12

IMO, ansible is even better: https://github.com/ansible/ansible/ It doesn't require any deamon and does all its work over the good old unix fashion way: SSH. And it's python too.

Browsing around ansible's website, I found the "quickstart" link. From that page[0]: > We’ve recorded a free 2-hour presentation designed to ... Wait. The quickstart presentation is 2 hours?! Looking for an easier way to get started... [0]: http://www.ansibleworks.com/quickstart/

Maybe this? http://ansibleworks.com/docs/gettingstarted.html

Re: Salt: Like Puppet, Except It Doesn’t Suck

#74
post #12

IMO, ansible is even better: https://github.com/ansible/ansible/ It doesn't require any deamon and does all its work over the good old unix fashion way: SSH. And it's python too.

>It doesn't require any deamon and does all its work over the good old unix fashion way: SSH. And it's python too

Salt is all of these things as well.

Re: Salt: Like Puppet, Except It Doesn’t Suck

#75
I use SaltStack for managing a render farm consisting of 73 Ubuntu nodes. My requirements are rather simple, really: most states just install some packages, put configuration files into place (sometimes using a template) and enable/start services. However, I can't recall a single problem when setting everything up. SaltStack is clean, simple, and just works.

Re: Salt: Like Puppet, Except It Doesn’t Suck

#76
post #17

I think salt is neato, but I also find it very frustrating to use! (Possibly through no fault of salt itself - I feel like I must be missing something.) I am generally able to SSH into a box and get things configured the way I need. However, I have huge amounts of trouble translating that into salt scripts. Consider logrotate. Here is the only documentation I can find on the topic [1]. From this, I have no idea what…

You should probably forget about the salt modules for now. Just look at the states.

>And that's just for logrotate! My uswgi + nginx configuration - translating that into salt - I don't know where to begin.

For nginx you just need a package: nginx installed state and a few states for the conf files.

uswgi will need something similar.

Re: Salt: Like Puppet, Except It Doesn’t Suck

#78
post #70

Is there a comparable tool for Windows? Powershell works great for executing commands on arbitrary servers (which sounds like the basis of Salt), but it'd be great to declaratively say "I want the server in this state" like the config management side of salt. I assume there is a tool built atop of Powershell like this somewhere?

Salt can configure Windows machines, but you need to have the master running on *nix iirc.

OK thanks for the heads up. I'll check it out, but I worry people will resist bringing in a *nix machine. It's unfamiliar and therefore must be feared!

Re: Salt: Like Puppet, Except It Doesn’t Suck

#79
post #31

I'm still looking for a configuration management system that doesn't assume that the first step towards managing servers is to add a new "master" server. From the thread, ansible looks promising. In the meantime I'll keep using chef-solo until opscode kills it.

http://docs.saltstack.com/topics/tutorials/quickstart.html
Post reply on HN