[
https://issues.apache.org/jira/browse/CLOUDSTACK-10146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16317855#comment-16317855
]
ASF subversion and git services commented on CLOUDSTACK-10146:
--------------------------------------------------------------
Commit e86bb41e0e3facb250cdcb984a8f8f91bf052b2b in cloudstack's branch
refs/heads/master from [~nicolas.vazquez]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=e86bb41 ]
CLOUDSTACK-10146: Bypass Secondary Storage for KVM templates (#2379)
This feature allows using templates and ISOs avoiding secondary storage as
intermediate cache on KVM. The virtual machine deployment process is enhanced
to supported bypassed registered templates and ISOs, delegating the work of
downloading them to primary storage to the KVM agent instead of the SSVM agent.
Template and ISO registration:
- When hypervisor is KVM, a checkbox is displayed with 'Direct Download' label.
- API methods registerTemplate and registerISO are both extended with this new
parameter directdownload.
- On template or ISO registration, no download job is sent to SSVM agent,
CloudStack would only persist an entry on template_store_ref indicating that
template or ISO has been marked as 'Direct Download' (bypassing Secondary
Storage). These entries are persisted as:
template_id = Template or ISO id on vm_template table
store_id NULL
download_state = BYPASSED
state = Ready
(Note: these entries allow users to deploy virtual machine from registered
templates or ISOs)
- An URL validation command is sent to a random KVM host to check if
template/ISO location can be reached. Metalink are also supported by this
feature. In case of a metalink, it is fetched and URL check is performed on
each of its URLs.
- Checksum should be provided as indicated on #2246: {ALGORITHM}CHKSUMHASH
- After template or ISO is registered, it would be displayed in the UI
Virtual machine deployment:
When a 'Direct Download' template is selected for deployment, CloudStack would
delegate template downloading to destination storage pool via destination host
by a new pluggable download manager.
Download manager would handle template downloading depending on URL protocol.
In case of HTTP, request headers can be set by the user via
vm_template_details. Those details should be persisted as:
Key: HTTP_HEADER
Value: HEADERNAME:HEADERVALUE
In case of HTTPS, a new API method is added
uploadTemplateDirectDownloadCertificate to allow user importing a client
certificate into all KVM hosts' keystore before deployment.
After template or ISO is downloaded to primary storage, usual entry would be
persisted on template_spool_ref indicating the mapping between template/ISO and
storage pool.
> Bypass Secondary Storage for KVM templates
> ------------------------------------------
>
> Key: CLOUDSTACK-10146
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10146
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.11.0.0
> Reporter: Nicolas Vazquez
> Assignee: Nicolas Vazquez
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
