[
https://issues.apache.org/jira/browse/CLOUDSTACK-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733817#comment-13733817
]
Jessica Wang commented on CLOUDSTACK-4102:
------------------------------------------
Nitin,
> 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.
This makes sense.
However, for SystemVM, Service Offering dropdown contains the same service
offerings no matter systemVM state is running or stopped.
Shouldn't Service Offering dropdown contain different service offerings for
running state and stopped state?
i.e. If a systemVM is running, Service Offering dropdown contains only system
offerings that is bigger(upper).
If a systemVM is stopped, service offering dropdown contains all system
offerings.
If the answer is yes, API needs to be able to support it.
i.e. listServiceOfferings API needs to be able to take virtualmachineid of
SystemVM and returns service offerings upon the systemVM's state.
Currently, listServiceOfferings API is only able to take in virtualmachineid of
UserVM, but unable to take in virtualmachineid of SystemVM.
Right now, UI calls
"listServiceOfferings&issystem=true&systemvmtype=secondarystoragevm" API for
scaleUp action in a systemVM.
Adding "&virtualmachineid=[systemVmId]" to the API call will return an error:
{
"listserviceofferingsresponse": {
"uuidList": [
{
"uuid": "1",
"description": "vmId"
}
],
"errorcode": 431,
"cserrorcode": 4350,
"errortext": "unable to find a virtual machine with specified id"
}
}
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: Jessica Wang
> 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
