OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.
N/A
Perforce Puppet
Score 8.5 out of 10
N/A
Puppet Enteprise is an IT automation and configuration management solution that enables users to manage and automate infrastructure and complex workflows. The vendor states Puppet Enterprise combines both model‑based and task-based capabilities in a way that enables organizations to scale their multi-cloud infrastructure as their automation footprint grows, with more flexibility from both agent-based and agentless capabilities.
Red Hat maintains a consistent user interface across their products, and their feature sets facilitate easy and rapid adoption. Configuration as code is the optimal approach for all of them, and they all provide a level of command-line access that ensures teams can work in the …
OCP and OpenShift Virtualization are better for a code based infrastructure our organization is attempting to move towards shortly. VMware has also been acquired which has added instability with their future. We are planning to move all VMware workloads to OpenShift …
I don't have as much experience with the other two, I have heard of them and know they are container management systems. I have the most experience with Red Hat OpenShift.
Red Hat Enterprise Linux (RHEL), Red Hat Data Grid, Red Hat Integration, Red Hat JBoss Enterprise Application Platform and Red Hat Ansible Automation Platform
As a specialized partner in container platform Red Hat OpenShift is our preffered solution. It provides a supported kubernetes platform which contains all the required tools to make the life of customers easier and offer them the same experience accross all hyperscalers, …
I find OpenShift opinionated but also requiring less configuration to be functional than the other platforms that I've mentioned, and Tanzu requires Faustian contracts to be signed.
As I mentioned before Ansible is a great tool. There is no question about it. It has very simple syntax (YAML), is very easy to learn, and is scalable as well. But the only thing that ansible lacked at that time was the actual agent that have to go into each server. Ansible …
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 …
I have not used any other Configuration Management System since cfengine back in about 2007 so I have little current input on alternatives to Puppet having never used them, though Chef seems to have gained some traction as has Ansible.
We have used SaltStack by proxy of utilizing Ceph since it uses SaltStack to automate configuration changes to it's cluster. I found it easy to use however extremely limiting when it comes to scale as its not a proper language with a central data store like Hiera. We plan to …
HPSA is a licensed product and incurs significant upfront investment costs due to COTS licensing. Puppet Data Center Automation has a significantly lower upfront investment and product documentation is more readily available. Chef is a very similar offering, however, at the …
Puppet has a very wide user base with many organizations tht support it as well as conferences and events. Puppet DSL is based in Ruby while the server is now in Clojure providing ease of configuration with the power of scale. Puppet is a great entry point into the world of …
Red Hat OpenShift, despite its complexity and overhead, remains the most complete and enterprise-ready Kubernetes platform available. It excels in research projects like ours, where we need robust CI/CD, GPU scheduling, and tight integration with tools like Jupyter, OpenDataHub, and Quiskit. Its security, scalability, and operator ecosystem make it ideal for experimental and production-grade AI workloads. However, for simpler general hosting tasks—such as serving static websites or lightweight backend services—we find traditional VMs, Docker, or LXD more practical and resource-efficient. Red Hat OpenShift shines in complex, container-native workflows, but can be overkill for basic infrastructure needs.
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.
One of the big advantages of Red Hat OpenShift is, especially over Kubernetes itself, is that it provides a lot of built-in operators for doing a lot of different things right out of the box that you don't have to worry about trying to configure. So one of the big ones is, I mean, right in your face is that user interface and being able to work with it inside of a browser. And I think that works very, very well.
I would say that's the logging part because Red Hat OpenShift write tons of locks and if most time in the finance industry, we cannot use the built in logging infrastructure for compliance reasons. And we have to forward the logs out of the system and this is, it's too much, which we forward from one cluster. Most time we'll build up multi clusters, so we speak about 10 or more clusters. And if you send log files from 10 or more clusters, the logging systems are not prepared to take that much load. And then really often you have license problems with the logging system, so that's not really, really fun. So logging could be improved.
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.
Going to stay with this platform for the unforeseeable future. It matches our Target Architecture 2030 strategy internally to adopt more modularized platforms with Open Source on the back-end so that if needed containerized workloads can move to a different platform. With open-source based application telemetry collection being utilized on the back-end, integrating our already existing oTeL observability based platform makes it easier for our apps to be monitored
As I said before, the obserability is one of the weakest point of OpenShift and that has a lot to do with usability. The Kibana console is not fully integrated with OpenShift console and you have to switch from tab to tab to use it. Same with Prometheus, Jaeger and Grafan, it's a "simple" integration but if you want to do complex queries or dashboards you have to go to the specific console
Redhat openshift is generally reliable and available platform, it ensures high availability for most the situations. in fact the product where we put openshift in a box, we ensure that the availability is also happening at node and network level and also at storage level, so some of the factors that are outside of Openshift realm are also working in HA manner.
Overall, this platform is beneficial. The only downsides we have encountered have been with pods that occasionally hang. This results in resources being dedicated to dead or zombie pods. Over time, these wasted resources occasionally cause us issues, and we have had difficulty monitoring these pods. However, this issue does not overshadow the benefits we get from Openshift.
Their customer support team is good and quick to respond. On a couple of occassions, they have helped us in solving some issues which we were finding a tad difficult to comprehend. On a rare occasion, the response was a bit slow but maybe it was because of the festival season. Overall a good experience on this front.
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
I was not involved in the in person training, so i can not answer this question, but the team in my org worked directly with Openshift and able to get the in person training done easily, i did not hear problem or complain in this space, so i hope things happen seamlessly without any issue.
We went thru the training material on RH webesite, i think its very descriptive and the handson lab sesssions are very useful. It would be good to create more short duration videos covering one single aspect of openshift, this wll keep the interest and also it breaks down the complexity to reasonable chunks.
We utilized the Thycotic Secret Service to manage all our application secrets, resulting in seamless integration with our applications. We developed all the applications using Red Hat Fuse (currently migrated to Quarkus). We used the built-in Kali Linux support of OpenShift to manage and configure the services and API. Additionally, the Red Hat Developer Studio facilitates faster development.
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.
This is a great platform to deployment container applications designed for multiple use cases. Its reasonably scalable platform, that can host multiple instances of applications, which can seamlessly handle the node and pod failure, if they are configured properly. There should be some scalability best practices guide would be very useful
When you talk about ROIs, I don't have any negative impacts I wanted to call out here. There is no negative impacts. In fact, it's all positive impacts what we set as our milestones towards achieving our goals, towards achieving our greater vision. Red Hat OpenShift has got a big role in it and it is certainly helping us.
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.
