Proxmox VE vs. SUSE Rancher

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.

Incentivized

SUSE Rancher as a management tool becomes useful on a larger scale. Small deployments not so much. If someone also requires Kubernetes capacity or storage, Rancher is an excellent choice. Also, without Kubernetes' skills, it is unlikely that Rancher deployment is going to be a success. Then again if someone else is managing your Kubernetes capacity, setting up the software's capacity will yield greater control. Rancher is not a very integrated solution similar to others in the market.

Incentivized

• BackUp System, provides extensive propiertes and verifications. An exclusive server for BackUp Administration (PBS)
• Hardware Customization. You can select several properties to adapt the hardware to your needs
• Easy administration. You will be able to manage the server with easily accessible tools such as the web console and usage statistics.
• Certificates Administration.

• Public and private cloud infrastructure providers based on K8s CAPI
• REST API that can be used to integrate company services with Rancher
• GUI that is easy to learn and use in daily operations
• Builtin GitOps automation solution based on Fleet project
• It is fully open source

• Can't manage ZFS replication or snapshots as easily as I'd like
• Encrypted disks aren't easily deployed in VMs
• Moving disks between VMs is not automated

Incentivized

• No possibility to snapshot Projects. You can snapshot and restore the whole Kubernetes cluster, but not a Project or Namespace. For this, you have to use external tools.
• You cannot detach the Rancher-created Kubernetes clusters from Rancher management.

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.

Incentivized

Out of every product I have used for this, Proxmox VE is the most concise, clear, and functional I have ever seen. I continue to use Proxmox VE even after occasionally comparing alternatives available because of it's usability, design concept, and great support of features. It's very unlikely I will find a product that can even compete with Proxmox VE in every angle of what Proxmox VE provides.

Incentivized

The usability and user experience are good in general, although sometimes some errors can cause confusion, especially for those users who are not experts.

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.

Incentivized

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

Incentivized

They are fast, understanding, very intelligent, know their product very well, fast, responsive, and concise. Need I say more?

Incentivized

Use cases can be complex hence support as well. Problems have been solvable, but not always easily. It's great that there is support!

Incentivized

It worked, was easy and super fast to deploy, and provided everything we needed in a matter of minutes

Incentivized

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.

Incentivized

As we use only AWS EKS Clusters originally we were using the AWS Console and CLI but that is too limited in scope. Also, we were using AWS IAM roles to provide access to users but that was lots of extra work to have them integrated into SSO while on Rancher we have just connected our GitHub login with the Alfresco organization and that uses, in turn, Okta for SSO so provisioning for access is automatic for any developer who has been assigned to GitHub.

Incentivized

The investment for small environments is quite significant. There has to be a compelling case to enhance the areas where SUSE Rancher brings in value to make such a financial leap. There is also a free version to test the value propositions, which will help support the user's buying decisions. More clusters, more volume, more tasks and more complexity in the environment equals more value that Rancher can provide.

Incentivized

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.

Incentivized

• Proxmox has allowed to us to do more with less. We can invest in a single (or multiple if clustering) host with a decent specification, and run most of our infrastructure on it.
• Open source technologies allowed us to re-use previous skills and knowledge. There was very little onboarding required because we already knew Debian, KVM, ZFS, etc.
• Virtualisation has vastly reduced the amount of time required to maintain all our systems. Everything is so much more organised and lends itself to automation (with Ansible, in our case).

Incentivized

• Shortens "Time-to-Market" factor for new business applications or implementing new functionalities. From 1 to 50 microservices-based business applications in 6 years.
• 24/7 availability, generates more money. There are many infrastructure components that are regularly powered-off for maintenance or upgrade, bur we rarely are turning off our downstream Kubernetes clusters where our business applications lives.
• Single Point of Contact with platform maintenance and development Team, eases implementation of new business applications