...
- If user tries to deploy a VM from a template containing multiple disks, user will have to choose a Datadisk offering for every Datadisk template chosen to be deployed along with the VM template
- If the actual size of the disk exceeds the size of the disk offering then VM deployment will fail
- During VM create process, when CloudStack makes DB entries for the ROOT disk, Volume DB entries will be made corresponding to each of the Datadisk template
- Volume state will be updated to Uploaded state because the volume is already present in secondary storage and has been packaged into an OVA during template post processing
- During VM orchestration while the storage is being prepared, a volume will be created in primary storage for each of the additional disks
- Each of the volumes will be migrated from secondary storage to the primary storage chosen by the deployment planner
- When VM starts it will be booted with all the chosen disks
Change in the existing behavior
...
{"serverDuration": 111, "requestCorrelationId": "c9caddbd0bbd40bf"}