Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 66 Next »


Display VM templates

You can use VM templates to create VMs in your cloud environments.

To display VM templates

  1. Select Private or Public

  2. Select a Datacenter or Public cloud region from the list

    • If you do not see the expected templates, you may need to click the double round-arrow Refresh button beside the Datacenter name or contact your system administrator

  3. Optionally select a template Category

  4. Optionally select icon or list view

On the right, the platform will display all the templates available for the selected datacenter or public cloud region

Privileges: Manage VM templates from Apps library

Icon view

In Icon view, to activate the VM template operations menu, select a VM template. This menu will vary, depending on the context.

Screenshot: Options menu of VM template

Screenshot: Options menu of a VM instance template, created from VM disks

In list view, to display the VM Template operations buttons, select a VM template


Organize VM templates into categories

In the Catalogue, the VM templates can be classified into categories:

  • Local categories belong to a single enterprise and cannot be seen or used by other enterprise

  • Global categories are visible to all users and are marked with the text "(global)", and you will require the "Manage VM template global categories" privilege to manage them.

The predefined categories are "Applications servers", "Database servers", "Others", and "Web servers".  If you download a VM template from a remote repository and its category does not exist yet, the platform will create the new global category with this name.

The default global category is "Others" and you cannot delete this category. 

Administrators who can manage global categories can promote a local category to global. You cannot demote a global category to local or move local categories from one tenant to another. 

Privileges: Manage VM template categories, Manage VM template global categories

To create a VM template category:

  1. Go to Catalogue → Private or Public → select datacenter or public cloud region → Virtual machine templates

  2. Check that there is no other category with the name you wish to use

  3. Open the Categories menu

  4. At the bottom of menu, click the + add button

  5. Enter the category name

  6. Optional: to create a global category, mark the checkbox to Make the category global

  7. Click Save to continue

The new category will be added to the Categories list.

To add a VM template to a category:

  1. Edit the template

  2. Go to General

  3. Select the category.

When you delete a category, all the templates belonging to this category will be changed to the category ''Others''.


Copy a VM template

To copy a VM template, move the mouse over the VM template in the Catalogue, and from the options button menu, select Duplicate.

Enter the name for the new template.

Select the disks you wish to copy and click Save.

Abiquo will create the duplicate as a new template in the Catalogue, with no links to the original template.


Introduction to mobility

The mobility feature enables users to export or move a template to private or public cloud. The original template must always be in the private cloud.

Privileges: Manage VM templates from Apps library, Export template to public cloud, Export template to private cloud

You can export:

  • multi-disk templates to other datacenters managed by Abiquo

  • single boot disks to public cloud regions in

    • AWS

    • Azure: You cannot upload more than one file with the same name in the same account and region. The file name is the unique part of the container name which is combined with the account name and region

To export to public cloud, you must first prepare the templates according to the cloud provider instructions.
See Preparing templates for export to public cloud

Abiquo uses the BPM - V2V conversion service to perform any required conversions and to upload the template to public cloud.

During an export, the platform will queue the BPM and V2V processes for conversions, instances, and persistent templates.


Export VM templates to datacenters and public cloud

Before you begin:

To export a template to a datacenter or public cloud

  1. Go to Apps library → select the private cloud datacenter where the VM template is stored.

  2. Select the VM template and from its options menu, select Export

  3. From the dialog, select Private or Public cloud.

    1. For public cloud

      1. select the public cloud provider and region

      2. select one bootable system disk.

    2. For private cloud

      1. select the datacenter

      2. select disks from the template to export.  

  4. Click Export

For private cloud, select the datacenter

For public cloud, select the public cloud region

For public cloud, select one bootable system disk. For private cloud, select disks

Export templates with the API

Using the API you can perform the export using the VirtualMachineTemplates Resource with the same method as is used for promoting an instance template. The datacenter repository should be the destination of the export and the request payload should contain a link to the VM template to export. See https://wiki.abiquo.com/api/latest/VirtualMachineTemplatesResource.html#create-a-virtual-machine-template-in-a-datacenter-repository-by-download-promote-or-export


Delete a VM template

In a private cloud datacenter, to prevent users from working with a VM template, you can do the following

  • Replace template disk(s) with new disk(s), so future VMs use the new disk(s). To replace a disk, use the Abiquo API. See Appliance manager template API upload and download

  • Delete a template, which requires that no deployed VMs are using the template and it has no instances. Note that you can promote instances to master templates and then delete the instances

  • Make a template unavailable to users, when it is in use

To delete a shared template or make it unavailable, you must be logged in to the owner enterprise. If you make it unavailabe, it will only be marked as unavailable for all users when the template owner performs a refresh of the Apps Library.

To remove a template that is not in use, click the template edit menu button and select Delete from the menu. 

Abiquo will remove the template from the Apps Library and the NFS repository file system.

Make a template unavailable to users

If you want to prevent users from creating new VMs from a template, but it is in use (in VMs or for instances) so you cannot delete it, then you can make it unavailable. This means that the platform will remove the template disk files and you cannot recover them within the platform. A template wiill also become unavailable if one or more of its disk files is deleted from the NFS repository file system outside of the platform. 

To make a template unavailable in the UI:

  1. Select the edit menu button of a template that is in use and select Delete from the menu. A confirmation popup will open with details of the template use.

  2. Confirm that you would like to force the delete. Abiquo will delete the disk files but not the template definition. The platform will mark this template as unavailable.

In the Apps library, the platform will not display the unavailable template in the default view. To display the template again, click the filter button and mark the checkbox to display Deleted templates, which are unavailable templates with no disk files. The platform will mark the template icon with a red X symbol.

Make a template available again

If one or more template disk files are deleted from the NFS repository, the template will become unavailable. However, if you restore the disk file(s) to the filesystem, then the template will become available again. If the template was downloaded from a remote repository, you can download it again to restore it. After you restore a template, when users redeploy VMs, they will work with the new template and its conversions. 

Delete Template Example

Here is a simple example of the process of deleting a template. An enterprise downloads a VM template from remote repository. A user deploys a VM from the template and modifies the VM. Then a user creates an instance from the deployed VM and deploys a new VM from the instance.

 Click here to show/hide the example

Screenshot: Deploy an instance of the Core in a new VM. There are now two VMs - one with the core template and one with an instance of the core template VM

Screenshot: The core template has two instances: Core_Instance_1 and Core_Instance_1_Instance_1

Now the administrator would like to delete the template, but there are VMs and instances. So the administrator will make the template unavailable. The platform will delete the disk files and users cannot create new VMs from the template.

Screenshot: The administrator clicks the template edit menu and selects Delete

Screenshot: The platform displays the details of deployed VMs and instances on the "Virtual machine template in use" popup. The administrator clicks Yes to continue.

The template disk files and the disk conversions will be deleted from the Apps Library. You cannot recover them within the platform

Screenshot: To view the unavailable template, click the template filter and select the Deleted checkbox. Click on the unavailable template to view the instances and they will display in the Instances panel below the master templates.


Manage instance templates in datacenters

Unable to render {include} The included page could not be found.




Manage instance templates in public cloud

Unable to render {include} The included page could not be found.



Delete private templates in public cloud

In public cloud, to delete a private template (or custom template), such as an Abiquo instance:

  1. Move the mouse over the template and from the options menu, select delete  

  2. Optionally select the checkbox to Delete this template in the cloud provider

  3. Confirm the delete

By default, the platform will delete the template from the Catalogue only and it will remain in the cloud provider.

If you delete the template in the cloud provider:

  • In AWS, when you delete a private AMI, it will also delete all the snapshots used by the AMI. If more than one AMI is using the same snapshot, AWS will delete the snapshot when you delete the last AMI.

  • In Azure, when you delete a private image, if the image was created from an image stored as a page blob, Azure will also delete the image.

  • In vCloud Director, when you delete an Abiquo private template, it will delete the vappTemplate that contains the template.

  • In OCI, it will delete the private image only

  • In GCP, it will delete the private image only



Other Pages related to VM template management


  • No labels