cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "prashant kumar mishra (JIRA)" <>
Subject [jira] [Updated] (CLOUDSTACK-4102) [UI] required ui changes for scalup vm feature
Date Tue, 06 Aug 2013 08:54:47 GMT


prashant kumar mishra updated CLOUDSTACK-4102:

    Attachment: usr_scaleup.png
> [UI]  required ui changes for scalup vm feature 
> ------------------------------------------------
>                 Key: CLOUDSTACK-4102
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: prashant kumar mishra
>            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:

View raw message