[
https://issues.apache.org/jira/browse/CLOUDSTACK-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733449#comment-13733449
]
Nitin Mehta commented on CLOUDSTACK-4102:
-----------------------------------------
For the 2nd point.
> 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
I think we should keep using the same label (i.e. "Scale Up VM") for the same
action(the same underlying API calls).
I'll be confused if I see two different actions firing the exactly underlying
API calls.
We just need to document that ChangeSerice action has been renamed to ScaleUp
action.
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.
b. Existing customers understand the label of change service offering when vm
is stopped and this shouldnt be removed. Underneath its calling the new api and
that is fine. The UI user shouldnt be confused with the API because he is a UI
user. I would be taken for a shock if the existing functionality is removed and
renamed. The user will be confused all the more.
> [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: Jessica Wang
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: svm_changeSO.png, svm_scaleup.png, 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
