ravening commented on issue #3610: [WIP DO NOT MERGE] KVM: Rolling maintenance URL: https://github.com/apache/cloudstack/pull/3610#issuecomment-574160585 > > This is any day better than rolling upgrade wherein worst case a VM can be migrated n-1 number of times. > > that would mean there is either space for all vms on all hypervisors, or that only one vm is present in the whole environment, so that is an unlikely case, but I do see your point. > Any algorithmic changes to suggest, @ravening ? One thing I suggest to avoid running enableMaintenancemode api on all hypervisors to upgrade it. Instead run enableMaintenanceMode on first hypervisor which will migrate away the VM's. Upgrade it. Now from second hypervisors onwards, run findHostForMigration for each vm and see if the list contains the upgraded hypervisor. If so then migrate the vm to the upgraded hypervisor. This way you can prevent multiple vm migrations
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
