Apache Mesos vs. Proxmox VE

There's really no reason to ever use Mesos. We switched over to Kubernetes and it's been a breath of fresh air - better CD support, easy CLI for browsing logs, no mysterious dangling redeploys. If you're looking for a tool to manage a fleet of Docker containers on VMs, Kubernetes beats Mesos by a wide margin.

Incentivized

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

• Mesos may have many frameworks. If you have Mesos installed on your servers, you may use it for many kinds of tasks. Today we're running only web applications but the idea is to install a different framework for big data soon.
• There is a good community growing around it.

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.

• Unreliable deployments that would fail for no good reason. Sometimes our Docker container would be "restarting" forever because Mesos thought it didn't have enough resources to start the container.
• Impossibly slow UI. Built in React under the hood with a lot of bloatware backed in, so loading the Mesos UI on a slow internet connection was painful.
• No real logging solution - it would stream "console.log()" output to the UI, but searching for logs wasn't really possible without downloading a huge file.
• No built-in support for redeploying containers from a CI. We had to create a service whose whole job was to expose an HTTP endpoint that restarted a container, and then made Circle CI ping the endpoint whenever we wanted to redeploy.

Incentivized

• 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.

Incentivized

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

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

Incentivized

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

No real support channel, the Mesos GitHub issues list was the only one we found and it wasn't particularly helpful.

Incentivized

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

Incentivized

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

Incentivized

Kubernetes is really great and their community is growing really fast (Google influence). We evaluated it in the beginning and it would fit for our web applications workload. We decided to proceed with Mesos because it has more potential. You may use a different framework for different kinds of tasks on Mesos. There is a Kubernetes framework for Mesos, by the way.

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

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

• It's optimizing our resources.
• It's improving our process. This argument is not just for Mesos, but we needed a tool like this to start changing and it works like a charm.
• It's open source.

Incentivized

• Due to the open source nature of Proxmox, we have no licensing costs while training our employees
• We've migrated 100% of our clients to Proxmox and have found improved uptime, and flexibility.
• In the 10 years of using Proxmox, we've yet to lose any data or not be notified of backup issues.

Incentivized