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.
$0.08
per hour
vCenter Operations Manager (vCOPS), discontinued
Score 7.0 out of 10
N/A
VMware vCenter Operations Manager (vCOPS) is an automated operations management solution that provides integrated performance, capacity, and configuration management for highly virtualized and cloud infrastructure. The product is currently discontinued.
N/A
VMware vCenter
Score 8.2 out of 10
N/A
VMware vCenter is an advanced server management software that provides a centralized platform for controlling vSphere environments for visibility across hybrid clouds. VMware vCenter is no longer sold as a standalone product and is now available as a part of VMware Cloud Foundation.
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.
The VMware vCenter server is very useful in maintaining the CPU/RAM/datastore resources are balanced when there are multiple ESX/ESXi host servers. It is clear what resources are being used, and it is easy to migrate VMs to different ESX/ESXi hosts. Being able to remotely connect to the VM servers in vCenter when you cannot have other remote connections helps in maintenance and troubleshooting.
We had a few microservices that dealt with notifications and alerts. We used OpenShift to deploy these microservices, which handle and deliver notifications using publish-subscribe models.
We had to expose an API to consumers via MTLS, which was implemented using Server secret integration in OpenShift. We were then able to deploy the APIs on OpenShift with API security.
We integrated Splunk with OpenShift to view the logs of our applications and gain real-time insights into usage, as well as provide high availability.
Resources allocation estimates are amazing, this feature allowed us to increase density on our hosts by reclaiming RAM and CPU from over allocated VMs letting us increase the amount of VMs per host. The report was very clear and easy to understand.
The planing feature enabled us to gather all the info we needed to plan hardware purchases as it showed us, with our current rate of deployment, when we would reach capacity in or environment.
The heat maps provided excellent drill down capabilities allowing for proactively resolving potential issues.
I wouldn't necessarily say there is look everyday technology transform. I can see a trend wherein Red Hat OpenShift is adopting all the new technology trends and helping their customers align with their priorities and the emerging technology trends. I wouldn't call out various scope for development every day. There is scope for development. It is all how the organizations adopt it and how they deliver it to their customers. I don't want to call out there is scope for development. It's happening. It is a never ending process.
At the moment, I don't have anything to call out. We are experiencing Red Hat OpenShift and we can see every day they're coming up with new features as and when they come up with new features, we want to experience it more and more. We are looking for opportunities wherein this can be leveraged to help our users and partners.
It would be nice to be able to make configuration changes either directly in vCenter Operations Manager or have it link back to the correct locations in vCenter.
Currently, the HTML 5-based vSphere Client lets you manage the essential functions of vSphere from any browser, however, it would be nice if they would port all management functions over to the HTML 5-based Client.
Performing updates and upgrades to the infrastructure is a bit challenging for someone that may not be as intimate with vSphere. I think the updates/upgrades should be more integrated into the UI and provide the ability to push to the hosts, etc...
It would also be nice to have a more robust snapshot management tool to prevent snapshot overgrowth. It would be nice to be able to set a lifespan for the snapshot(s)
This is the current strategy for the company, most of the products in the organisation are aligning to Openshift and various use cases it support. Also lot of applications are being developed for AI use case, openshift.AI provides opportunity to host and leverage the AI capabilities for these applications
We are very dependent on this software, it has become a much needed tool to perform the daily tasks that are required to maintain the virtual server environment. VMware has become very pricey over the years, so we are looking for alternatives for cost savings strategy, but nothing has been found to be on par to what we are currently using
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
I work with vCenter for 10+ years and i love it. I can find my way around and can help building and expanding the platform. It is easy to use and there are a lot good communities for the extra support when needed. Even the Homelab community is of great value.
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.
VMware support has always been fantastic and they have been invaluable in solving tougher issues that have been run into. Most of the time, any oddities encountered are fixed by available updates. This can be deduced by support quickly with logs within vCenter. We have not run into something yet that support was unable to help with. They either have a solution already, or they are able to find one quickly.
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.
Since moving away from the Windows Server hosting the vCenter application and instead using a virtual appliance, it has become much easier to implement and deploy the new versions. We can easily create a snapshot or clone of the vCenter vApp to ensure any problems encountered during the upgrade can be mitigated with a fall back to the old version to prevent unscheduled downtime.
The Tanzu Platform seemed overly complicated, and the frequent changes to the portfolio as well as the messaging made us uneasy. We also decided it would not be wise to tie our application platform to a specific infrastructure provider, as Tanzu cannot be deployed on anything other than vSphere. SUSE Rancher seemed good overall, but ultimately felt closer to a DIY approach versus the comprehensive package that Red Hat OpenShift provides.
It's easy to understand what are being billed and what's included in each type of subscription. Same with the support (Std or Premium) you know exactly what to expect when you need to use it. The "core" unit approach on the subscription made really simple to scale and carry the workloads from one site to another.
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
That is a complicated question and one that's not easy for me to answer. There's a lot of factors that go into all of the stuff that we just don't have an easy way of measuring. And we realize that while we're implementing Red Hat OpenShift, we've tried to start measuring some of that stuff, but we don't have a baseline to go on. So it's hard to say. What I can tell you is general experience with the platform has been extremely positive from the development aspect. Teams have been very, very happy with the speed at which they're able to do stuff. They've been happy with that. The way it works in one environment is exactly the way it works in the next environment because we don't have configuration drift, that type of thing, and has had very positive impacts. But we didn't have a baseline to start with. So I can't talk about getting there faster or anything like that.
