A couple of days ago, Proxmox released the first beta release of the upcoming Proxmox VE 5.0 Release.
I am really excited for some of the new features, so I thought I’ll give you a short overview. Furthermore, I will take a closer look at my personal favorite features and go into detail why they are important for me!
Roadmap for Proxmox VE 5.0
- 5.0 based on Debian Stretch
- pve-zsync GUI
- live migration with local storage (qemu)
- support for external fencing devices
- qdevice (additional external vote, e.g. for 2-node clusters)
- Ceph improvements
I am mostly exited for the three features marked in bold letters:
Finally, it will be possible to move your VMs without setting up a shared storage! Sure, in larger deployments shared storage is the way to go, but in a homelab scenario, this might not be optimal. For example in my case, I run Proxmox off of local Samsung 850 Pro SSDs, to get the optimal performance for my containers and VMs.
The second feature I have been looking forward to for a long time, is the qdevice. Why is that important? Again, this won’t affect larger deployments, but if you want to run a cluster with only two physical machines, so far you were out of luck. A cluster always requires a positive quorum, that means the majority of votes. With only two server, this is impossible, because if one machine goes down, you’ll always only get one (of the two votes) which will not give you a positive vote and therefore won’t let you make changes.
Now with the new qdevice, there can be an additional external vote, like from a user, to get a positive quorum and therefore allow the change!
Lastly Cloudinit, which is basically the industry standard for bootstrapping and initializing a virtual machine. As an example, once you create a new VM or container, cloudinit will install your SSH Keys, update the system and install some necessary packages like OpenSSH or SaltStack. This will be a huge timesaver, when you have to install a large amount of VMs. I will use it, to install the Salt-Minion and set it up to connect to the Master Node. From there, all further configuration will be done by the SaltStack
- Released 22.03.2017
- Based on Debian Stretch
- Kernel 4.10
- Many small improvements and bug fixes
I will post more information, as new features are implemented. If you want to get more information right away, here some links: