On Tue, Mar 31, 2015 at 12:27 AM, Leon Towns-von Stauber <leo...@occam.com> wrote:
> > I would use Salt when I need to build full application stacks > > including many dependent types of systems, and don't need to manage > > the state of the systems. > > This isn't the only place I've heard Salt described as more of an > imperative system (i.e. "Do this"), as opposed to a system that describes a > desired state (i.e. "Make it like this"), which CFEngine does so well. > > However, having started to look at Salt, I don't really get the criticism > (if you take it as one). Based on limited exposure so far, it seems just as > capable as CFEngine or Puppet of specifying a desired configuration and > executing on it; it doesn't seem all that different in overall philosophy. > For anyone familiar with the issue, what am I missing? Or, perhaps, is that > description of Salt based on earlier versions, the shortcomings of which > have been addressed in current releases? > Pretty much, yes; it's had the capability for a year or so, but it's still "newish". (Earlier versions supported one "state", which de facto ended up being "do these things" as opposed to "make the system look like this", as I understand it. Some of the tutorials and documentation still assume that's how you use it.) -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ Tech mailing list Tech@lists.lopsa.org https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
