| Table of Contents |
|---|
VM template update procedure
To update a VM template:
Shut down the deployed template gracefully and create an instance
Update the instance (e.g. install new service pack or security patch)
Promote the template to a master template, with a name that denotes it as the new version. See Manage instance templates in
datacentersPropagate the new template to all the relevant datacenters' appliance libraries
Share the new template in the catalogue to all enterprises as applicable
Rename or change the description of the old template to show users that it is deprecated
Considerations
When you want to update a template, remember:
You can rename and change descriptions of any template (or instance) in the catalogue, even if the template is being used by a virtual appliance in the datacenter (deployed or undeployed).
An instance of a template can be created by any user/enterprise with the appropriate privilege
You cannot remove a master template if an instance has been created. As a cloud admin user, you will need to impersonate each enterprise and check the repository for instances
Abiquo will not allow you to overwrite a template, so you cannot download a template from a remote repository to the same datacenter's catalogue more than once
You cannot delete a template to download a new version if it is being used by any virtual appliance in the datacenter
You cannot 'un-share' a template if it is being used by any virtual appliance in the datacenter
Updating VM template disk files using the appliance manager API
You can update VM template disk files. The use case is as follows.
Upload or download a template
Use it to create a VM
Update the template.
AbiquoAbiquo supports changes to:
file content
size
format
capacity
Update the disk using the Appliance manager API
When the user next deploys the VM, the platform will copy the updated disk
Please contact Abiquo Support for further information.
Changing VM template files on the filesystem
...