[GitHub] [cloudstack] DaanHoogland commented on issue #3610: [WIP DO NOT MERGE] KVM: Rolling maintenance
DaanHoogland commented on issue #3610: [WIP DO NOT MERGE] KVM: Rolling maintenance URL: https://github.com/apache/cloudstack/pull/3610#issuecomment-574248688 > > This requires VM-per-VM tracking/migration effort and is way outside of the scope of this work/PR. It is however an interesting idea for some future improvements. > > Yes of course this is not good to implement within cloudstack itself. That's why we have a separate application to do that where we are using the above algorithm I like the notion that not everything should be implemented in cloudstack. What do you mean "not good to implement in cloudstack"? Cloudstack is about orchestration and provisioning, so this should be a perfect task for cloudstack. If you mean "hard to implement" yes it would. we do not have a workflow engine in the system, which would be ideal for this. 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: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack] DaanHoogland commented on issue #3610: [WIP DO NOT MERGE] KVM: Rolling maintenance
DaanHoogland commented on issue #3610: [WIP DO NOT MERGE] KVM: Rolling maintenance URL: https://github.com/apache/cloudstack/pull/3610#issuecomment-574146153 > 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 ? 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: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [cloudstack] DaanHoogland commented on issue #3610: [WIP DO NOT MERGE] KVM: Rolling maintenance
DaanHoogland commented on issue #3610: [WIP DO NOT MERGE] KVM: Rolling maintenance URL: https://github.com/apache/cloudstack/pull/3610#issuecomment-573745853 ... > > We have a similar application to perform all these tasks and also a centralized dashboard to control upgrading hypervisors on all platforms in a different locations. @ravening do you have this in public domain somewhere? > > Update: > Nvm, I went through the code and understood what its doing. It enables maintenance mode on each individual hypervisor. This can be really bad in most cases because in the worst case a VM can be migrated multiple times @ravening I cna safely say that at least all the VMs from the first host to be handled will be migrated multiple times. How is this bad? And how could this be avoided? 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: us...@infra.apache.org With regards, Apache Git Services
