[
https://issues.apache.org/jira/browse/CLOUDSTACK-9912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajani Karuturi updated CLOUDSTACK-9912:
----------------------------------------
Fix Version/s: (was: 4.10.0.0)
4.10.1.0
> UI Layer checks for Root disk resize support for VMware and XenServer.
> -----------------------------------------------------------------------
>
> Key: CLOUDSTACK-9912
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9912
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Doc, UI
> Affects Versions: 4.10.0.0
> Reporter: Priyank Parihar
> Assignee: Priyank Parihar
> Priority: Minor
> Fix For: 4.10.1.0
>
>
> Some recommendations (as suggested by [~bstoyanov]) that would make user
> experience better:
> Until now we've identified in order the Resize Root Disk to work we need both
> "vmware.create.full.clone" and "vmware.root.disk.controller" to be enabled.
> 1) When adding instance as a user on the "Select a template" step, the field
> "Root disk size (GB)" is available.
> If the global settings are not available and user goes and add a custom value
> in that field, he'll get a non-meaningful message, that would require a
> CloudStack admin to look into the logs and debug.
> Two standalone checks implementation is suggested:
> * Check if vmware.create.full.clone is true
> * Check if vmware.root.disk.controller is true
> Gray-out the field ( or remove it) so the user can't add value.
> 2) Resizing a running instance
> In the same fashion we could do the same check when the vm is already running.
> 
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
