Github user serg38 commented on the issue:
https://github.com/apache/cloudstack/pull/1813
@priyankparihar Fortunately those API are already written. As per PR1767
you can get VM details including rootdiskcontroller using listVirtualMachines
API and listTemplates.
So if we are talking about resizing a root disk on existing VM we can
obtain all the details upfront for
1. vmware.root.disk.controller global setting
2. vmware.root.disk.controller if it is set on VM level
3.vmware.create.full.clone global setting
4. vmware.create.full.clone if ti s set on the storage pool where root disk
resides
After that UI can make a determination if resizing should be allowed or not
For the case of new VM deployment with variable root disk size all options
above can be obtaine except #4 since storage pool will be determine only during
volume allocation. I think for that case we just use items #1-3 to determine if
we allow variable root disk size in UI or not (for #3 we obtain
rootdiskcontroller setting if it is set on Template level)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
