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
  • OVA template custom property "cloud.ova.bootdisk" will be used to determine the ROOT disk. If it is not set the first disk will be identified as the ROOT disk
  • For each of the data disks
    • An OVF descriptor will be created 
    • Datadisk template will be created by packaging the disk and OVF into an OVA
    • Datadisk, OVF and OVA will be present in a separate folder inside the parent template folder. e.g. -
      • Say VM template id is 206, then the 1st data disk of a template will be present in folder  - template/tmpl/2/226/1 
      • Sample contents of the Datadisk template folder will be
        • MultipleVolumes.ova MultipleVolumes.ovf MultipleVolumes-disk1.vmdk
  • Template post processing will return information about each of the additional data disks present (if any).
  • Information about the data disks will include physical and virtual size of the data disk and path where the template has been installed
  • 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>

...