-
Notifications
You must be signed in to change notification settings - Fork 36
Use scaleVirtualMachine API instead of changeServiceForVirtualMachine #818
Conversation
|
@blueorangutan package |
|
@Pearl1594 a Jenkins job has been kicked to build primate packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔️centos ✔️debian ✔️archive. |
|
For reference, here follows some CloudStack issues raised due to changeServiceForVIrtualMachine API command problems: |
|
Thanks @GabrielBrascher There were a few other reasons we went with changeServiceForVirtualMachine when the VM is stopped which I can't recall atm |
|
@davidjumani @Pearl1594 @shwstppr can you share reasons for the change - thanks. I see legacy UI uses the scale API, is that it? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Consistent with legacy UI. As per apache/cloudstack#4125 changeServiceForVirtualMachine seems to be having issues and scaleVirtualMachine handles both running and stopped VMs.
@davidjumani if there is any corner case failing we can handle in backend
|
@rhtyd
|
GabrielBrascher
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code LGTM.
CloudStack UI currently also does not use the changeServiceForVIrtualMachine. Additionally, there are a couple of open issues regarding changeServiceForVIrtualMachine API command problems:
…apache#818) Co-authored-by: Pearl Dsilva <pearl.dsilva@shapeblue.com>
…#818) Co-authored-by: Pearl Dsilva <pearl.dsilva@shapeblue.com>
Align with Legacy UI and call scaleVirtualMachine API when attempting scaling