Salt Project vs. VMware Cloud Director

SaltStack is a very well architected toolset and framework for reliably managing distributed systems' complexity at varied scale. If the diversity of kind or number of assets is low, or the dependencies are bounded and simple, it might be overkill. Realization that you need SaltStack might come in the form of other tools, scripts, or jobs whose code has become difficult, unreliable, or unmaintainable. Rather than a native from-scratch SaltStack design, be aware that SaltStack can be added on to tools like Docker or Chef and optionally factor those tools out or other tools into the mix.

Incentivized

If you have a lot of customers that all need to have a separate place to work in, without the possibility of getting in each other way, and you want to safe yourself a lot of work. Than I strongly recommend you Cloud director. Ofcourse, only if you have a VMware environment as your working environment. If you just have a small group of customers and you can easily handle the work that's coming from it, then it is overkill to add cloud director to your environment. In a later station, you can always introduce cloud director (so tis never to late if you still want to use it)

Incentivized

• Targeting is easy and yet extremely granular - I can target machines by name, role, operating system, init system, distro, regex, or any combination of the above.
• Abstraction of OS, package manager and package details is far advanced beyond any other CRM I have seen. The ability to set one configuration for a package across multiple distros, and have it apply correctly no matter the distrospecific naming convention or package installation procedure, is amazing.
• Abstraction of environments is similarly valuable - I can set a firewall rule to allow ssh from "management", and have that be defined as a specific IP range per dev, test, and prod.

Incentivized

• Building virtual racks
• Managing the customers' network and security
• Simplicity but the completeness of IaaS solution
• Integration with major software providers

Incentivized

• Managing network hardware should be more native and easy
• SaltStack should buffer jobs and, when a client returns, make sure it is executed proberly
• SaltStack should provide basic pillar and states structures to help get newbies started

Incentivized

• The add-on/extension required on the internet browser sometimes are difficult to get working at first. We've experience instances where the add-on/extension latest versions will not work and have to downgrade to an older version.
• The server console lacks features and tools. For example it would be useful to have a copy and paste tool or a file upload tool.
• The vCloud Director management site uses Adobe Flash, which makes it impossible to use on a mobile device.

Incentivized

We haven't had to spend a lot of time talking to support, and we've only had one issue, which, when dealing with other vendors is actually not that bad of an experience.

We moved to SaltStack from Puppet about 3 years ago. Puppet just has too much of a learning curve and we inherited it from an old IT regime. We wanted something we could start fresh with. Our team has never looked back. SaltStack is so much easier for us to use and maintain.

Incentivized

vCloud Director is definitely my favorite as far as cloud managers. The only thing that compares is Cisco UCS Director, but it has slightly different functionality and purpose. I understand why a lot of clients still go with vCloud Director even though VMware intends to sunset it

Incentivized

• We manage two complex highly available self-healing (all infrastructure and systems) environments using SaltStack. Only one person is needed to run SaltStack. That is a HUGE return on investment.
• Building tooling on top of SaltStack has allowed us to share administrative abilities by role - e.g. employee X can deploy software Y. No need to call a sysadmin and etc.
• Recovery from problems, or time to stand-up new systems is now counted in minutes (usually under eight) rather than hours. This is a strategic advantage for rolling out new services.

Incentivized

• Saves a lot of time, and time is money
• Stable, so little to non downtime
• With P1 , good support

Incentivized