Red Hat CodeReady Workspaces vs. Salt Project

We have a team of 500 people so it's most reliable and scalable if any new joinees. That way user's can directly create their own workspace and start working and share the work stack throughout development teams securely, to update and modify any upcoming events. The best thing about Red Hat Workspace is it's simple, with all Runtime libraries pre-installed, so no need to request a platform from Azure or any other platform provider just log in and start creating a workspace. It has version control so can easily import GIT projects can start work without worrying we don't have Java, Python or any other platform not installed just select the platform needed and start working.

Incentivized

Managing heterogeneous environments of large numbers of nodes, especially nodes which may need sudden changes (security updates, for instance), or frequent replacement, is a strength for Saltstack. Simplicity is not a strength for Saltstack. In a homogenous environment (all CentOS 7, for example, with no Debian or Windows) I might recommend using Ansible instead - it is less flexible and granular, but simpler to configure.

Incentivized

• A superb remote execution framework! SaltStack allows us to easily program numerous functions on top of it. For example, we developed a fast parallel asynchronous deployment tool that handles all software deployment, including interdependent service management.
• Configuration management is now easy. We take advantage of this to automate (in tandem with AWS tools) the stand-up of all servers and services. It is also relatively easy to create new configuration management states for software not yet supported by the community (e.g. Grafana).
• Flexibility. Numerous small utilities have been built which simply wrap around SaltStack to allow tedious tasks to become easy.

Incentivized

• Can improve UI like Visual studio so that VS user's can switch without any difficulty.

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

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.

I've used shell scripts over ssh, custom in-house deployment tools, Chef, and SaltStack. I've evaluated Ansible, but I was never happy with performance over SSH. Chef's loose configuration data model and lack of philosophy and conventions around use makes it difficult for a team to share responsibility for configuration code. Needing to use additional tools to do orchestration for cross-host/agent dependency relationships made me look for more. SaltStack, while not as mature when I first tried it, impressed me with its speed and elegant design

Incentivized

• No need to request for any platform again and again.

Incentivized

• SaltStack has reduced the time it takes to deploy new machines for us 10-fold.
• It is much easier for us to maintain compliance with industry standards with SaltStack.
• No negative impacts!

Incentivized