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
Proxmox VE
Score 8.9 out of 10
N/A
Proxmox Virtual Environment is an open source server virtualization management solution based on QEMU/KVM and LXC. Users can manage virtual machines, containers, highly available clusters, storage and networks via a web interface or CLI. Proxmox VE code is licensed under the GNU Affero General Public License, version 3. The project is developed and maintained by Proxmox Server Solutions GmbH.
$7.50
per month
Pricing
Red Hat OpenShift
Proxmox VE
Editions & Modules
No answers on this topic
Community
€ 90
year & CPU socket
Basic
€ 280
year & CPU socket
Standard
€ 420
year & CPU socket
Premium
€ 840
year & CPU socket
Offerings
Pricing Offerings
Red Hat OpenShift
Proxmox VE
Free Trial
Yes
No
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Proxmox Virtual Environment's source code is published under the free software license GNU AGPL, v3 and thus is freely available for download, use and share. A Proxmox VE Subscription is an additional service program that helps IT professionals and businesses keep Proxmox VE deployments up-to-date. A subscription provides access to the stable Proxmox VE Enterprise Repository delivering software updates and security enhancements, technical help and support.
Stateful pods and DBs can be challenging to manage in OpenShifts. Depending on the configuration, lost deployments could result in data loss. The best use case for OpenShifts is any instance where agile and quick deployments are needed. Thanks to the OCP git runner, we can implement new builds across all environments quickly.
We used Proxmox to implement private cloud services, for clusters of a small number of servers, from 3 to 11 with and without high availability. Allways with ZFS file systems, and we used to install the root pool in SSDs mirrored and use other pools with RAID 10 in groups of four, for the virtual machines and containers, for the backups and snapshots, we used magnetic disks with RAID 10, in groups of four. Do not use an even number of servers because does not facilitates the implementation of High Availability, because the corosync service must have an odd number of servers to detect a failed server for the quorum system. We used a variety of servers, from clone PCs with AMD Ryzen with 6 cores and 12 threads with 64 GB of RAM no ECC, to high end servers with 64 cores and 128 threads per cpu and 2 cpus per server, with AMD EPYC Rome or Milan, 2 terabytes of RAM ECC.
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.
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."
The web UI does not work as well on mobile devices. It is useable, but a mobile optimised / responsive UI would be nice to have. There is a mobile app, so that may alleviate this issue, but I have not yet tried it.
Support in the community forums could be better. There are paid support plans, but new users trying out the software will not have access to this. Answers to questions can sometimes be terse, and I can imagine this may put some people off.
The wiki is a bit hit and miss with certain topics. I've often seen outdated or missing information, and the whole thing looks like it could do with some polish. I'd love to see it opened up for the community to add to.
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
Proxmox VE provides the most capable, yet stable virtualization platform in the market today. Licensing options are also competitive and cost-effective for support, and support is extremely fast and knowledgable of getting issues resolved as quickly and soundly as possible.
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
The interface is easy to use for most of it, but still lacks screens for some configurations. Also, a few of the screens are not as intuitive as they could be. This is specially true with disk and network configuration, where some graphic/visual representations of the configurations would be very useful
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.
Proxmox VE's ha-cluster functionality is very much improved, though does have a not-very-often occurrence of failure. In a 2-node cluster of Proxmox VE, HA can fail causing an instance that is supposed to migrate between the two nodes stop and fail until manually recovered through the command-line tools provided. Other than this, the HA clustering capability of Proxmox VE has proven to be reliable in 3 or more clustered environments with much less chance of these failures to occur.
I've not noticed any significant performance impacts with Red Hat OpenShift. I think the development team has put a lot of effort into ensuring that it is performant. And so performance typically is not a major concern for us with Red Hat OpenShift.
Proxmox VE's interfacing is always fast to load, both the Web interface and the command-line tool interfaces. Reporting is practically real time almost all the time, and you can see everything in mere seconds, easily able to identify if something is wrong or it everything is in tip-top shape as always desired
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
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.
Our developer community is using Red Hat OpenShift for years and they are familiar and comfortable with the product. Red Hat OpenShift UI makes it easier for new developers to adopt without knowing much of Kubernetes. Our platform team feels it’s easy to mange the cluster and upgrades. Other options has more operation overhead and less friendly to developers not have in-depth knowledge of Kubernetes.
Proxmox VE is cheaper than VMware, especially upscaling an HA architecture. Compared with other free or less expensive solutions, Proxmox VE is high compatible with more types of hardware solutions and more VM types. From my point of view, Proxmox VE has no competitor at the same price level, it offers the most complete and production-ready HA solution.
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
Proxmox VE provides everything you need to quickly add new storage mediums, network and local, as well as networking interfaces, such as using Linux standard bridges and now Open-vSwitch bridges which can be even more scalable than before. Proxmox VE 4.0 dropped support for OpenVZ in favor of the more well supported and native LXC and made an upgrade path to it very simple.
