cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daan Hoogland (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-7921) Add Template Refresh Option
Date Wed, 08 Feb 2017 09:23:56 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-7921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daan Hoogland closed CLOUDSTACK-7921.
-------------------------------------
    Resolution: Won't Fix

> Add Template Refresh Option
> ---------------------------
>
>                 Key: CLOUDSTACK-7921
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7921
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.4.0
>            Reporter: Michael Phillips
>
> I. Proposal
> I would like to propose a new function in which we have the ability to refresh a template.
OS templates need to be refreshed every so often to update things like OS patches and software.

> II. Current Method
> Currently the only way to refresh a template is to delete the old template, then upload
the new template.
> III. The issue
> There are 3rd party apps out there, such as hostbill, that use cloudstack for vm provisioning.
When a template is created it seems the template gets assigned a unique GUID in the database.
When you refresh the template by deleting and re-uploading, the new template has a new GUID
which breaks any connections to the old template.
> IV. How to possibly solve
> Have a new function to refresh a template. Refreshing the template would reuse all the
info from the old template, but would just replace the templates disk file with the new one.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message