Versions Compared

Old Version 1

changes.mady.by.user Nicolás Vázquez

Saved on

compared with

New Version Current

changes.mady.by.user Nitin Kumar Maharana

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Existing API methods 'registerTemplate' and 'registerIso' are both extended with a new optional boolean parameter 'directdownload'. When this new parameter is set to true, it will only allow KVM template/ISO registration, throwing an exception if hypervisor parameter is not 'KVM'. When 'directdownload' is set to as true, templates and ISOs are both registered on CloudStack without any interaction with SSVM to initiate download to secondary storage. This way, template and ISO registration using direct download will only perform two tasks:
    • URL checking on a random KVM host, retrying 3 times in case of failure, and failing registration if URL cannot be reached.
    • Create entries on CloudStack database, specifically on template_store_ref. An entry is created for each direct download registered template on template_store_ref having:
      • Template/ISO ID on template_id column
      • Null store_id
      • Download_state = 'BYPASSED'
      • State = 'Ready'
        (These entries are only persisted on 'template_store_ref' for CloudStack to list direct download registered templates on the virtual machine deployment window)
    • Template/ISO checksum can also be provided as specified on FR25 as the 'checksum' parameter. Checksums are expected as {ALGORITHM}CHECKSUM, where:
      • ALGORITHM can be: 'MD5', 'SHA-256', 'SHA-512'
      • CHECKSUM is the hash value.
        This checksum is persisted on database on registration time and it will be used after template/ISO is downloaded on primary storage to compute checksum and compare with the one provided at registration time. If checksum validation fails after retrying 3 times, VM deployment fails.
  • A new API method 'uploadTemplateDirectDownloadCertificate' is added. It accepts a certificate, a certificate name and hypervisor type as required parameters, and uploads and import provided certificate to all running KVM hosts' cloud.jks keystore, in order to be used by templates or ISOs on HTTPS. This method´s response only indicates if the operation was successful.

...