[
https://issues.apache.org/jira/browse/CLOUDSTACK-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13734048#comment-13734048
]
Jessica Wang commented on CLOUDSTACK-4102:
------------------------------------------
Nitin,
(1)
>> However, I'm unable to change UI to hide scaleUp action for running systemVM
>> whose hypervisor is KVM/XenServer
>> because listSystemVMs API and listRouters API doesn't return hypervisor
>> property
> Will file a bug for that.
Since UI has no way to tell a SystemVM's hypervisor, UI just always shows
scaleUp action for a systemVM.
i.e. UI shows scaleUp action for a running SystemVM whose hypervisor is
KVM/XenServer.
In this case, when users click scaleUp action, will scaleSystemVm API return an
error like "KVM/XenServer doesn't support scaleUp"?
If yes, it doesn't sound that critical to me.
(2)
>> listServiceOfferings API needs to be able to take virtualmachineid of
>> SystemVM and returns service offerings upon the systemVM's state.
> Will file a bug for this.
Right now, Service Offering dropdown contains all service offerings (even it
should contain only "scale up" service offerings for a running VM).
If a user unfortunately selects a "scale down" service offering for a running
VM, will scaleSystemVm API and scaleVirtualMachine API return an error like
"scale up service offering is not supported for a running VM"?
If yes, it doesn't sound that critical to me, either.
(3)
>>> Jessica - I understand you point but still I would recommend using the
>>> change service offering label
>>> a. When vm is running we can only scale "Up" and not scale "Down", but when
>>> vm is stopped we can do both
>>> so showing only scale up label will confuse the end user.
So, "change service offering" refers to either "scale up" or "scale down".
Why don't we make the action label to be "change service offering" even when VM
is running?
i.e. the action label is "change service offering" for running VMs and stopped
VMs.
Jessica
> [UI] required ui changes for scaleup vm feature
> -------------------------------------------------
>
> Key: CLOUDSTACK-4102
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4102
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: UI
> Affects Versions: 4.2.0
> Reporter: prashant kumar mishra
> Assignee: Nitin Mehta
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: svm_changeSO.png, svm_scaleup.png, Systemvms.jpeg,
> Uservms.jpeg, usr_scaleup.png
>
>
> Current scenario
> -------------------------
> we are using "Scale UP Virtual Machine" action button to change service
> offering of a stopped vm and to scaleup SO of a running vm
> Require changes
> ================
> 1:
> Action button "Change service offering" should be removed
> WHY: because we are doing it using "scale UP virtual machine" action button
> 2:
> when vms are in stopped state we need to RENAME Scale UP Virtual Machine
> action button to Change service offering
> WHY RENAME: because underlying API calls for Change service offering button
> should be same as in Scale UP Virtual Machine
> WHY:because previous versions CS user is familiar with change SO action
> button , so its require to keep in that way to avoid confusion
> 3:
> when vms are in running state UI should not show scale UP Virtual Machine
> action button for hypervisor on which scaleup is not supported
> -->scale up is not supported on KVM
> -->not supported for system vms on xen
> 4:
> please check screenshots for more details
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
