Node maintenance mode UI

A lot of people seems to miss the maintenance mode ... can you explain what you use it for? I've never used it in VMware, i never saw the point in doing so in a cluster. As VMs are already taken care of with HA or manual migration, what should it do? How often are people that are not aware of maintenance playing around in your PVEs?
 
A lot of people seems to miss the maintenance mode ... can you explain what you use it for? I've never used it in VMware, i never saw the point in doing so in a cluster. As VMs are already taken care of with HA or manual migration, what should it do? How often are people that are not aware of maintenance playing around in your PVEs?
If maintenance mode is activated, resources are moved to other hosts. After deactivating maintenance mode, the previously moved resources are automatically migrated back to the previous host.
But slightly different with Ceph OSDs: You do not want the OSDs to be replaced on other nodes just because of maintenance. ;)
 
If maintenance mode is activated, resources are moved to other hosts. After deactivating maintenance mode, the previously moved resources are automatically migrated back to the previous host.
Thank you, so what would you do in a maintenance mode situtation with the hypervisor?

As I wrote, the VMs are already taken care of with HA, the migration part is already implemented and works as it should on reboot / shutdown including failback as you can see here:

1728140163616.png

This is a CEPH test cluster with three nodes and two VMs. Both VMs were on pve-ceph-02 and it got rebootet. The VMs were automatically migrated, one on each other node and as the rebooted node got up again, the VMs are both migrated back.
 
Thank you, so what would you do in a maintenance mode situtation with the hypervisor?

As I wrote, the VMs are already taken care of with HA, the migration part is already implemented and works as it should on reboot / shutdown including failback as you can see here:

View attachment 75827

This is a CEPH test cluster with three nodes and two VMs. Both VMs were on pve-ceph-02 and it got rebootet. The VMs were automatically migrated, one on each other node and as the rebooted node got up again, the VMs are both migrated back.

What if you want to test a different kernel or change other settings with some reboots? Maintenance is an easy way to prevent HA from migrating the VMs back.
 
Last edited:
What if you want to test a different kernel or change other settings with some reboots? Maintenance is an easy way to prevent HA from migrating the VMs back.
That is a good point. Thank you for clarification. Until we have a UI button for this, the CLI option may be sufficient.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!