| Table of Contents |
|---|
Introduction to updating VM templates
...
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
| Note |
|---|
Do not change VM template files on the filesystem |
If you change the disks of a VM template on the NFS filesystem |
, |
you |
also need to correctly update all the relevant Abiquo database fields, such as |
, as well as the OVF information, which Abiquo may require to maintain platform coherence. |
...
Considerations when updating VM templates
...
You can rename and change descriptions of any VM template (or instance) in the catalogue, even if the template is used by a virtual appliance in the datacenter (deployed or undeployed)
Any user with the appropriate privileges can create an instance of a template, and the instance will be stored in the user’s enterprise
You cannot remove a master template if there is an instance in any enterprise. As a cloud admin user, you will need to switch to each enterprise and check the repository for instances. Or you can check in the repository file system
You cannot remove scopes to “unshare” a template if it is being used by any virtual appliance in an enterprise in the datacenter
You can remove a template disk from the filesystem to make the template Unavailable to users. If you later replace the template disk with the exact same disk, then the template will become Available again
You can update a template disk , but you also need to using the UI or API, and as part of this process, you will update the template definition in Abiquo. To do this, follow Follow the instructions for the Abiquo UI or API. After you update a template disk, users will deploy VMs with the new disks
...