Perforce Puppet vs. Red Hat CodeReady Workspaces

Most of the major issues that people had with the language have been addressed in Puppet 4 which primarily pertain to the limitations of the language and its ability to scale. It would be nice to allow for full ruby support as an unsupported option though so developers are able to reference their own data sources dynamically.

Incentivized

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

• Provides a reliable mechanism for deploying infrastructure-as-code, especially when integrated with source control (such as Git).
• Manages system configuration drift to provide greater stability and system up-time; the same configuration-as-code can be pushed out over and over.
• A strong asset when moving teams towards DevOps by providing development a way to take control of their own assets.

Incentivized

• Steep learning curve for first time users.
• The complexity can get a little overwhelming in a more collaborative deployment methodology across multiple platforms and data centers.
• Some external changes to Puppet like the new Puppet 4 architecture can cause considerable time consuming migration efforts especially if you have a lot of legacy classes and configuration that do not conform readily to the new design.

Incentivized

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

Incentivized

Puppet has top class support. You can simply mail them with their query and they will respond to your query in a timely manner. We do have enterprise license for puppet. Also there is a vibrant community for puppet out there. So even if you dont purchase a premium support option you can simply google your queries and get answers

Incentivized

Puppet was selected before I joined the team, had it been my choice I would have much rather went with Chef as it has the ability to do things that Puppet has not yet added to their system such a the ability to quickly query what host currently are allowing puppet to maintain their files or the ability to run remote commands without having to include it in a manifest like Chef does with the knife command. Salt allows you to do similar things to the knife command that is included with Chef, and also allows you to transfer files quickly to multiple host at once with a short simple command.

Incentivized

• With all the DevOps and automation that we have going on, we save a ton of time on the configuration of the server. It's safe to say that configuring servers via console or via UI is a thing of the past.
• We try to get all the things done by using a centralized repo (GitHub). Puppet is one tool that actually gets the actual work done.
• The small amount that we spent on purchasing premium Puppet is completely justified because of the time and effort that this tool actually helps us save.

Incentivized

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

Incentivized