I’ve been a pretty stalwart Puppet user since I first discovered it in 2009. At that time, my choices were, as I saw them, between the brand-new cfengine3, the I’ve-seen-how-the-sausage-is-made bcfg2, and Puppet. Of those choices, Puppet seemed like the best choice.
In particular, I liked Puppet’s “defined state” style of configuration management, and how simple it was to describe dependencies between the various packages, files, and services to be configured.
Like I said, I’ve been using Puppet happily for the past 4 years; but now, I think I’ve been swayed by Salt Stack.
I know I looked at salt stack before; but, at the time, I think I dismissed it as just “remote execution.” Salt does, after all, start from a very different place than Puppet. At its most simple, it is a mechanism for shipping Python functions to remote nodes and executing them. It seemed the very opposite of the idempotent state management that I was looking for.
But now that I’ve taken the time to look deeper into the documentation (or, perhaps, now that the project has grown further) I’ve found Salt Stack States: the state enforcement configuration management system I was looking for; and with a trivial-to-setup remote execution layer underneath it.
Salt is based on 0MQ. I don’t know much about message queues; but I do know that I could never get ActiveMQ working for use with Puppet’s MCollective. After only 30 minutes of hacking, I had Salt, with 0MQ, running on two OS X machines and two Debian machines, all taking to the same master, each from behind its own form of inconveniently private network.
$ sudo salt '*' test.ping ln1.civilfritz.net: True Jonathons-MacBook-Pro.local: True numfar.civilfritz.net: True dabade.civilfritz.net: True
Some other things that I like about Salt:
States are defined in YAML, so there’s no proprietary (cough poorly defined cough) language to maintain.
The remote execution layer and state module layer help keep executable code separate from state definitions.
Key management is a bit less foolish. (It shows you what you’re about to sign before you sign it.)
Of course, no new technology arrives without the pain of a legacy
conversion. I have a lot of time and effort invested into the Puppet
manifests that drive
ln1.civilfritz.net; but converting them to Salt
Stack States is serving as a pretty good exercise for evaluating whether
I really prefer Salt to Puppet.
I’ve already discovered a few things I don’t like, of course:
The abstraction of the underlying Python implementation is a bit thin. This is sometimes a good thing, as it’s easier to see how a state definition maps to individual function calls; but it also means that error messages sometimes require an understanding of Python. Sometimes you even get full tracebacks.
Defined states don’t seem to understand the correlation between uid and uidNumber. In Puppet I started specifying group ownership as
0when I discovered that AIX uses the
root. In Salt, this appears to try to reassign the group ownership every time.
All hosts in a Salt config have access to all of the files in the master.
YAML formatting can be a bit wonky. (Why are arguments lists of dictionaries? Why is the function being called in the same list as its arguments?)
No good firewall (
iptables) configuration support. The
iptablesmodule isn’t even present in the version of Salt I have; but the documentation warns that even it is likely to be deprecated in the future.
That said, I can’t ignore the fact that, since Salt happens to be
written in Python, I might actually be able to contribute to this
project. I’ve already done some grepping around in the source code, and
it seems immediately approachable. Enhancing the
for example, to provide node-restricted access to files, shouldn’t be
too bad. I might even be able to port Puppet Lab’s
from Ruby to Python for use as a set of Salt modules.
Time will tell, I suppose. For now, the migration continues.