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
Windows Server Failover Clustering
Score 9.1 out of 10
N/A
Windows Server Failover Clustering (WSFC) is a group of independent servers that work together to increase application and service availability.
N/A
XenServer
Score 8.2 out of 10
N/A
XenServer (formerly Citrix Hypervisor) is a virtualization management platform optimized for application, desktop and server virtualization infrastructures.
If you run Windows VMs, you will need licenses. With Windows Server DataCenter, you have unlimited number of VMs, and you don't need additional licenses for the Windows VMs. Running Hyper-V (Windows Server DataCenter) with Failover Cluster will be way cheaper than anything else.
In the scheme of the real world, Citrix Hypervisor is used much less than the other two main competing products; MS Hyper-V and VMWare vSphere. So, choosing Citrix Hypervisor for your organization comes down to whether you are comfortable going with a lesser-used product. All …
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.
Windows ServerFailover Clustering works very well for applications that can sustain a short disconnect when failing over. It works, and works well, in providing single-node applications HA, meaning an active/passive setup. It is not a load balancing solution. Use NLB for that. Another area that it works well is when used in combination with Hyper-V. We set our Hyper-V hosts up as clusters, and those clusters also host clusters for SQL Server and other enterprise class applications like BMC's Control-M/Enterprise and Control-M/Server.
It can be really helpful & useful if we are using Citrix Hypervisor with other provisioning tools. Here are some specific scenarios where Citrix Hypervisor (formerly Citrix XenServer) is well-suited: Server Consolidation, Virtual Desktops, Disaster Recovery, Development & Testing Environments. On the other hand, there are some scenarios where Citrix Hypervisor may be less appropriate: Small-scale Deployments, Highly Heterogeneous Environments, and Limited Virtualization Requirements.
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.
Live Migration of VMs between hosts. If you have sufficient network bandwidth, it is fast and I never had a failed live migration break the VM or kill it. Worst case is the live migration will fail (not enough RAM for example) but the VM always stayed up.
Windows Server Failover Clustering enables Scaleout Storage, which is probably the coolest feature Microsoft has to offer at this moment. It gives you Active-Active SMB file shares which can now be used by most Microsoft Services like MS SQL, Hyper-V, etc. and clients if Windows 8+
Cluster Validation is really complete and easy to understand. The validation gives you comprehensive error messages that help to diagnose and fix rapidly to get your Failover Cluster running in no time.
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.
The setup of the Windows Server Failover Clustering is complex, requiring different networks and multiple network cards.
Better integration between the Windows Failover clustering and Hyper-V. Unlike VMWare you have to make changes to two places instead of just one panel.
I wish there was a web portal to manage the cluster. Instead you have to remote desktop into the VIP address and go to the Cluster manager.
Adding or presenting additional storage to the host can often be a task that is far more involved than competitive products.
The product can require reboots more frequently than competitors due to the DOM kernel getting "hung up".
Sometimes when a virtual machine is deleted it still leaves behind orphaned vdisks.
Recovering from the loss of a host can sometimes cause virtual machines to require lengthy command prompt scripting to fix so they can be powered back on from another host.
OpenShift is really easy of use through its management console. OpenShift gives a very large flexibility through many inbuilt functionalities, all gathered in the same place (it's a very convenient tool to learn DevOps technics hands on) OpenShift is an ideal integrated development / deployment platform for containers
It has proven its value to us both for maintaining SLAs and providing the ability to perform much needed and regular systems maintenance without taking applications offline for more than a few seconds.
With the knowledge and usage of solutions from VMware and Microsoft offering more compelling cloud integrated options it makes it more compelling in many environments which I consult. XenServer is a good product and fits the bill in many smaller environments but as clients look to the cloud or a hybrid cloud it can in some cases make it a bit more difficult.
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
Usability of Failover Clustering on Windows Server is generally good. Failover Clustering console is not hard to understand if the complexity of the product is taken into account. Most of the task on the Cluster can be done via PowerShell, so automation is possible and not hard (PowerShell is very intuitive). Configuring storage is the hardest and most confusing task during cluster configuration, so storage configuration should be planned in advance. Cluster Validation Wizard is verbose but most of the errors are easy to understand.
XenServer is a good product in its use and probably free if you have the right Citrix licenses already. However, it does require specific knowledge to manage, which makes it harder to manage if you don't have that knowledge in house.
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.
It's been a little problematic in the past at larger VDI deployments requiring a bit more care and feeding than other vendors. But the latest releases (6.5.x) have brought about huge improvements in the stability and availability.
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.
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
Online documentation is excellent. Everything I needed to know, I learned from the online documentation. I haven't used phone support as I haven't needed to but would presume it is similar to Microsoft Support for other products that I've used. Phone support from Microsoft is hit and miss. It depends on who you get. That said, my rating is based on the online documentation.
The staff I've worked with are very knowledgeable or able to get a very well articulated and capable support team member on the phone or helping them if necessary and they always want to ensure the best experience possible for you on the platform. The ability for the support team to reach out to hardware vendors for assistance is a nice plus too.
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.
Part of a training for certification to become a trainer for Citrix included an in-person training with a Master CCI. The XenServer training at this time was pretty simplified due to the product primarily being installed however you did have to work with it and mildly configure the system.
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.
Haven't given it a real go with any online training however there are some options out there. I have taught a course following Citrix material for XenDesktop which leverages XenServer and it is pre-built so not the best for XenServer specifically for installation but configuration is mildly touched on
Ensure you review the HCL (hardware compatibility list) and reach out to the hardware vendors to ensure they support the platform and in case they have documentation that can be followed for the implementation. Also ensure the prerequisites are completed prior to implementation so that as few unexpected delays occur as you can control.
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.
Both VMware and Microsoft Failover do the job and they both do it extremely well. For many bussiness and environments though, they will have the existing investment in a Microsoft environment and Microsoft infrastructure. The introduction of VMware will or may achieve the end result however it introduces new dimensions like support, licensing, documentation and ensuring the support team are trained.
Feature for feature they are neck and neck. I have used Hyper-V 2012 and 2016, VMware ESXi and XenServer evenly. XenServer is a fast install, good documentation, with enterprise features out the box that compare or exceed what VMWare offered with a higher cost of entry.
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
The servers latest versions have made massive improvements to scalability. But from past experience there have been issues when running workloads for extended periods of time without reboot on the hosts. I would need to run similar workloads on the 6.5 release which has changed much of the bottlenecks or issues so I'd imagine its far more capable now, Perhaps able to stand near the best in the market.
All of the above. Red Hat OpenShift going into a developer-type setting can be stood up very quickly. There's a very short period to have developers onboard to it and they're able to become productive much faster than a grow your own type solution.
Failover Cluster gives us the power to do updates or hardware upgrade / change without having to create an outage. Which permit us not to work night shifts.
By creating one cluster with all Hyper-V servers, it enabled us to move VMs via live migration between host to balance RAM usage which was time consuming and took a lot of time over network before.
It created some problems that caused us to have to investigate quite some time before finding the cause. We encountered dll locking that caused the Failover Cluster to force-restart a host. Logs are really not the strong point of Failover Cluster Manager, and even Microsoft Support wasn't able to help much. We had to find the problem ourself.
Xenserver is easy to learn. We paid for support only for installation and deployment in the first three years, and now our team has the knowledge to solve most problems.
Low CAPEX if you have a team that uses open source software day by day.
But paid support is necessary to solve critical problems. The open source community is not enough. Actually, we have difficulty solving some bugs without paying for support.
Medium OPEX if you have a team that uses open source software day by day.
