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
Pricing
Hyper-V
Red Hat OpenShift
Editions & Modules
Developer
$24.95
per month
Bronze
$49.00
per month
Silver
$89.00
per month
Gold
$135.00
per month
Platinum
$199.00
per month
No answers on this topic
Offerings
Pricing Offerings
Hyper-V
Red Hat OpenShift
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Hyper-V
Red Hat OpenShift
Features
Hyper-V
Red Hat OpenShift
Server Virtualization
Comparison of Server Virtualization features of Product A and Product B
Hyper-V
8.6
Ratings
5% above category average
Red Hat OpenShift
-
Ratings
Virtual machine automated provisioning
9.00 Ratings
00 Ratings
Management console
7.00 Ratings
00 Ratings
Live virtual machine backup
9.00 Ratings
00 Ratings
Live virtual machine migration
8.50 Ratings
00 Ratings
Hypervisor-level security
9.40 Ratings
00 Ratings
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
Because Hyper-V is a Microsoft product and based on Windows OS, creating virtual Windows servers and clients are easy. When we want to test our group policies it it best to do it on hyper-v environment then implement to production clients. The same goes with operating system quality and features updates as well as operating system upgrades.
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.
Virtualization - Hyper-V does this well and I feel like it might be the best and easiest software out there to use. I am able to spin up virtual environments very quickly. Hyper-V also has a "quick" add feature where you don't even need to have the OS ISO on your computer and you can choose between Windows 10, Server or Ubuntu.
Setup and Management - Hyper-V is pretty straight forward. When I first started using this it seemed a bit confusing, but after a couple of days of playing with it you end up finding out everything is pretty straight forward and really not that complicated.
Just turn off the VM and go into the settings and you can manage the Storage, Memory, and CPU's.
Setting a VM up on a Domain is super easy and you can create a static mac address for the machine so in Windows DHCP you can use that static mac address to give that VM an IP it can use every time it boots up.
I think the best feature is the ability to create "Checkpoints" - If you are going to be doing something over and over and you need to start from the same point with each test you can setup your VM the way you need it prior to testing. Create a Checkpoint. Do your tests and then revert back to the Checkpoint so the system will be exactly how you had it setup prior to testing. Then you can go on and do your second set of tests and so on.
Another great thing is the ability to just backup the vhdx file.
As I mentioned at the beginning of this review we run most everything from Hyper-V. I make weekly backup of the vhdx files which are the Virtual Environment files.
This is an extreme example, but if the building ever caught on fire I could go out and buy like 15 PCs at Best Buy and load up Hyper-V on them and just import the vhdx files and be back up and running fairly quickly.
One thing is the way how it works with the GitHubs model on an enterprise business, how the hub and spoke topology works. Hub cluster topology works the way how there is a governance model to enforce policies. The R back models, the Red Hat OpenShift virtualization that supports the cube board and developer workspace is one big feature within. So yes, these are all some features I would call out.
I would love to see Hyper-V add a better remote control feature. As it is, it uses RDP to connect to any VM in the host. This is old technology and slowly deprecating. It would be significantly more useful to have a controlled interface for remoting to the VM's that is much more like Teamviewer, LogMeIn, etc.
So I don't know that this is a specific disadvantage for Red Hat OpenShift. It's a challenge for anything that Kubernetes face is. There's an extremely large learning curve associated with it and once you get to the point where you're comfortable with it, it's really not bad. But beating that learning curve is a challenge. I've done a couple presentations on our implementation of Red Hat OpenShift at various conferences and one of the slides I always have in there is a tweet from years ago that said, "I tried to teach somebody Kubernetes once. Now neither of us knows what it is."
Cheap and easy is the name of the game. It has great support, it doesn't require additional licenses, it works the same if it is a cluster or stand-alone, and all the servers can be centrally managed from a system center virtual machine manager server, even when located at remote sites.
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
It is very easy to configure new virtual machines and manage them. But you have to use different interfaces to perform various tasks. Especially as soon as it comes to clustering you have to use at least two different interfaces (Hyper-V Manager and Failover-Cluster Manager) to perform all necessary tasks. The newly released Windows Admin Center is a way into the right direction to get all management tasks into one single interface.
The virtualization part takes some getting used to it you are coming from a more traditional hypervisor. Customization options are not intuitive to these users. The process should be more clear. Perhaps a guide to Openshift Virtualization for users of RHV, VMware, etc. would ease this transition into the new platform
In the past 2 years our Hyper-V servers have only had a handful of instances where the VM's on them were unreachable and the physical Hyper-V server had to be restarted. One time this was due to a RAM issue with the physical box and was resolved when we stopped using dynamic memory in Hyper-V. The other times were after updates were installed and the physical box was not restarted after the updates were installed.
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.
Hyper-V itself works quickly and rarely gave performance issues but this can be more attributed to the physical server specifications that the actual Hyper-V software in my opinion as Hyper-V technically just utilizes config files such as xml, and a data drive file (VHD, VHDX, etc) to perform its' duties.
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.
Most of the time, you can find support on the thousands of websites, blogs and community sites that are out there. Very much Internet supported, and if you don't stray too far away from the standard setup of Hyper-v, you shouldn't go wrong. I've had to call a couple of times, and Microsoft was very good at resolving my problem. it seem that Microsoft has heard from people and their support system, and are doing a much better job in this
Every time we need to get support all the Red Hat team move forward looking to solve the problem. Sometimes this was not easy and requires the scalation to product team, and we always get a response. Most of the minor issues were solved with the information from access.redhat.com
We had in person training from a third party and while it was very in depth it was at a beginner's level and by the time we received the training we had advanced past this level so it was monotonous and redundant at that point. It was good training though and would have provided a solid foundation for learning the rest of Hyper-V had I had it from the beginning.
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.
The training was easy to read and find. There were good examples in the training and it is plentiful if you use third party resources also. It is not perfect as sometimes you may have a specific question and have to spend time learning or in the rare case you get an error you might have to research that error code which could have multiple causes.
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.
initial configuration of hyper-v is intuitive to anyone familiar with windows and roles for basic items like single server deployments, storage and basic networking. the majority of the problems were with implementing advanced features like high availability and more complex networking. There is a lot of documentation on how to do it but it is not seamless, even to experienced virtualization professionals.
Considering the maturity of ESXi, Hyper-V is something I would definitely consider using in future jobs or organisations. We selected Hyper-V after many years of using ESXi; several factors led us to this change, including a poor support experience with VMware, and the lower cost of Hyper-V. We looked at other options including Nutanix and Hyper Converged Infrastructure, however with such a busy team we didn't have the time to learn this completely new technology stack, whereas (whilst also new) Hyper-V had a much easier learning curve.
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.
Nothing is perfect but Hyper-V does a great job of showing the necessary data to users to ensure that there is enough resources to perform essential functions. You can also select what fields show on the management console which is helpful for a quick glance. There are notifications that can be set up and if things go unnoticed and a Hyper-V server runs out of a resource it will safely and quickly shut down the VM's it needs to in order to ensure no Hardware failure or unnecessary data loss.
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
It has allowed us to see where we need to be in the container world. I'm going to call it a net neutral impact, not negative or positive. It has given us a sense of what we are ready for and what we're not ready for. You know where you stand.
You don't know what you don't know, so it helps us know what we want to know.