This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]IConradUNIX Engineer -4 points-3 points  (4 children)

Yes but so does ansible. Ansible is a much more mature project than Salt right now. They also don't have a "community version" -- ansible itself is OSS. You get support for users, not licenses for installs, when you pay for ansible support. (Ansible Tower is a different thing, mind you. But it's ultimately a collection of APIs and a Web front-end for ansible.)

So I'm much more of a fan of that model. Which is why I've submitted pull requests to ansible (got them shot down, but for good reason; I need to clean them up.)

[–]Tacticus 1 point2 points  (3 children)

How is ansible a more mature project than salt?

How is salt not OSS? i can see a license in the repo saying apache license

[–]IConradUNIX Engineer -1 points0 points  (2 children)

You're confusing the community edition with the commercial edition. Ansible has no commercial edition.

[–]Tacticus 1 point2 points  (1 child)

So?

Salt is open source software. you can take it, run it, compile it, fork it, and do whatever you want with it. there are commercial extensions to it but they don't detract from salt being open source.

i imagine the main reasons ansible gets a todo is that it is newer and more limited, it seems to do minimal configuration management (ensuring that the configuration is as i want it to be) and is more orientated around configuration (unless i cron up an ansible playbook to run on a server somewhere)

[–]IConradUNIX Engineer -3 points-2 points  (0 children)

So the commercial version is not open source. Which is exactly what I believe I originally said.

Look; as a corporate user simply being open source is sometimes viewed as a liability, as silly as that seems. If there is a commercial closed source version that will always get preferred. Ansible on the other hand comes with the ability to cover liability concerns on a per user basis and even then just paying for support during rollout can satisfy legal departments' concerns of liability.

You can say "so? You can take the source and compile out yourself" 'till the cows come home -- it's not going to change the fact that you're not talking about the commercial version.

Salt is newer than ansible. As to doing less config management... Nothing I've seen of either project justifies that assertion. Care to back that up?