| Table of Contents |
|---|
...
Introduction to updating VM templates
There are two main ways to make sure your users have up-to-date templates in Abiquo:
Create a new template from an instance of the old template
Update existing template disks
...
Update a VM template by creating a new template
To update a VM template :
...
as a new template.
Deploy a VM from the template, shut it down gracefully, and create an Abiquo instance (as a backup)
Update the instance VM (e.g. install a new service pack or security patch), then create another instance template
Promote the template new instance to a master template, with a name that denotes it as the new version. See Promote an instance to a master template on and change the name to show users that it is a new version. See https://abiquo.atlassian.net/wiki/spaces/doc/pages/311371382/Manage+VM+templates#Promote-an-instance-to-a-master-template
Propagate Copy the new template to all the relevant datacenters' appliance libraries
Share the new template in the catalogue to all enterprises as applicable
Rename catalogue in each of your datacenters (with Duplicate VM template)
In each datacenter catalogue, share the VM template to your enterprises (with Scopes)
Rename the old VM template or change the description of the old template to show users that it is deprecated
...
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
Any user with the appropriate privileges can create an instance of a template can be created by any user/enterprise with the appropriate privilege, and the instance will be stored in the user’s enterprise
You cannot remove a master template if there is an instance has been createdin any enterprise. 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 . Or you can check this directly in the repository file system
You cannot 'un-share' a template if it is being used by any virtual appliance in the datacenter
You can remove a template disk to make the template Unavailable to users. If you later replace the template disk with the same disk, then the template will become Available again
You cannot 'un-share' a template if it is being used by any virtual appliance in the datacenterTo update the template disk, you also need to update the template definition in Abiquo. You can update a template disk file using the Abiquo UI or API, as described in the documentation. After you update the template disk, users will deploy with the new disk
...
Updating VM template disk files
...
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. Abiquo supports changes to:
file content
size
format (see Template compatibility table)
capacity
Update the disk using the UI or 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.For instructions:
for the UI method, see https://abiquo.atlassian.net/wiki/spaces/doc/pages/311378488/Modify+VM+template+disks#Replace-a-template-disk
for the API method, see Upload and replace template disks via API
...
Changing VM template files on the filesystem
...