I rate the tool's initial deployment a five out of ten. I rate adding a new server to an existing system a nine out of ten. It has pretty decent documentation for installation. 

We have deployed SaltStack on a hybrid cloud. It is difficult to set up and requires one executive to operate the deployment. I rate the process a six out of ten.

The solution's configuration process needs improvement. They should provide better documentation for easier understanding.

There are multiple ways to do the initial setup. The documentation is clear, but could be better organized.

Initial setup should have been straightforward; however, documentation issues and bugs in general caused this to take a very long time.

The setup was smooth. We were already acquainted with this kind of tool.

Initial setup seemed so easy, but there is an art to designing pillars, writing state files, and other customizable structures.

Initial (basic) setup is easy when you follow the docs.

The setup was pretty straightforward. It took some time getting familiar with all the configuration options and playing around with pillars and grains. On the whole, it was relatively easy to get going.

The setup was complex. The salt-master topography was master-minion, but then expanded to syndic, then back to master-minion. We did have to juggle, but that may be the shifting overall cloud architecture. It looked more like a chicken-egg problem, but we did have to revise the Salt architecture frequently.

Initial setup was more complicated than Puppet, but the solution was also more comprehensive. Setup was worth the trouble.

Learning SaltStack did seem a bit daunting at the moment I was learning it. The concept of creating a top.sls with references to various states and their targets, then creating corresponding files in YML, took a day or two; beyond that, it was real easy.

The initial ramp-up period to understand the concepts took time. Post that, it’s a very easy-to-use solution, especially after the Salt Formulas have matured.

The hardest parts of initial setup for me were learning some of the intricacies of YAML and Jinja, and figuring out the moving parts on the master so I could get the system to reliably create the minions I wanted. Later, learning to configure Salt-cloud was a bit tough because of the configuration files required to work with resources on Amazon Web Services. None of these issues were "showstoppers", though, as the amount of online documentation and configuration examples for other users is excellent.

I was not a part of the setup, but from what I have read, it is pretty simple.

Initial setup was straightforward; worked out of the box .

The initial setup was simple enough to get started and see the benefits that the solution brings. There are many tutorials available to get someone started.

The initial setup was neither straightforward nor complex; it required some effort.

The installation was straightforward, especially the master and minion configuration. This configuration was time saving and led to a faster, automated application deployment.

Salt's initial setup took about two days to go from knowing nothing to having a configured Apache Tomcat server serving our content. That's simple in my book. The complexity comes in when you want to add security policies or routing that aren't ordinary for a horizontally scaling web application; that takes some creativity.

The installation is straightforward and is pretty much a simple setup.

The setup was pretty straightforward, especially compared to "legacy" solutions.

The initial setup was complex because we did not think it would be as simple as it was. I can build a new SaltStack infrastructure in a matter of minutes now, but initially it took me longer than I would like to admit. Again, it is hard to make your way through the documentation. I was using YouTube videos for instruction.

Initial setup was simple.

Salt has a very straightforward installation.

Initial setup was very easy.

SaltStack is a very straightforward system with very good documentation. There are different solutions for deployments. Many scenarios and best practices are available publicly on the SaltStack site.

Initial setup is straightforward.