[
https://issues.apache.org/jira/browse/CLOUDSTACK-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733850#comment-13733850
]
Nitin Mehta commented on CLOUDSTACK-4102:
-----------------------------------------
>>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.
>> In your attachment "Systemvms.jpeg", "System Vms" includes Virtual Router,
>> right?
"System Vms" are referring to "Virtual Router + Secondary Storage VM + Concole
Proxy VM" ?
Yes it should
>>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.
Will file a bug for this.
For 1st and 3rd do u think they are critical bugs?
> [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
