cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "prashant kumar mishra (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (CLOUDSTACK-4102) [UI] required ui changes for scaleup vm feature
Date Tue, 20 Aug 2013 10:41:51 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

prashant kumar mishra reopened CLOUDSTACK-4102:
-----------------------------------------------


Hi Jessica , 
No need to popup message
"For VMware-based Linux VMs, please read the dynamic scaling section in the admin guide before
scaling" 
when vm is in stopped state ,because it is simple change service offering (no script require
when vms are in stopped state). attaching screenshot .
                
> [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, vmstop_msg_vmware.jpg
>
>
> 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

Mime
View raw message