AP> Because configuration management is about a lot more than "running ssh in a AP> 'for' loop."
PS> Maybe I'm misunderstanding, but you seem to be implying that Salt is PS> not helping you do anything more than run commands. If so, it's PS> important to note that it can both run commands and manage config ala PS> puppet style. I couldn't tell for sure from Corey's post about this. In particular, does it have built-in primitives to do things like "ensure that this service is (or isn't) running", or "ensure that this service is (or isn't) configured to start at boot time", or "ensure that this user exists (or doesn't)", or "ensure that this package is (or isn't) installed", and so on? But ok, it looks like it can: http://docs.saltstack.com/topics/tutorials/states_pt2.html for exmaple has apache: pkg: - installed service: - running as an example. And later on that page, an example of how to say "install this web page, which requires Apache". And some other good stuff, so, ok. Different question: What are some things you can do with Puppet that you *can't* do with Salt? (With only its built-in stuff -- "but you can write Python code to do that" is good, but not the same as "works out of the box".) Separately: What's the crypto situation? Is the traffic between master and minions itself encrypted, or are keys just used for authentication and authorization? Searching within the page for "crypt" on http://docs.saltstack.com/ didn't turn up anything. Ah: http://docs.saltstack.com/topics/ says "Salt uses public keys for authentication with the master daemon, then uses faster AES encryption for payload communication; authentication and encryption are integral to Salt." Phil had some concerns about this; have those been addressed in the most recent versions? -Josh (iril...@infersys.com) _______________________________________________ Discuss mailing list Discuss@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
