Page History

...

• No change in user experience during template registration
• Once template is downloaded and installed in the secondary storage it will be post processed
  • All data disks will be identified and for each of the Datadisk
    • An OVF descriptor will be created 
    • Datadisk template will be created by packaging the disk and OVF into an OVA
  • Template post processing will return information about each of the additional data disks present (if any).
  • Information about the data disks will include size of the data disk , and path where the template has been installed and the device id
  • For each of the additional disks a Datadisk template will be created
    • Entries will be made in vm_templates and vm_template_store_ref table
    • Template will be referenced to the corresponding VM template by populating vm_template_details for VM template with key value pair - child_template_id,  <datadisk_template_id>

...

• 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

...