Abiquo Documentation Cookies Policy

Our Documentation website uses cookies to improve your experience. Please visit our Cookie Policy page for more information about cookies and how we use them.


Documentation

Skip to end of metadata
Go to start of metadata

Abiquo 3.4 supports virtual machine templates with multiple disks. This will enable customers to create templates that fulfill sophisticated drive requirements for specific applications, particularly in Microsoft Windows environments.
In particular, this feature enables administrators to store and modify multi-disk templates in the Apps library, so users can deploy these templates. In this initial version, all disks will be deployed to the same datastore.

Definitions

This section defines some of the terms used when referring to templates with multiple disks. 

Template disks

Template disks can include:

  1. Standard disks in the Apps library
  2. Persistent disks on external volumes
    • Persistent disks can only be used in the same virtual datacenter as the external volume
  3. Empty disks that are a logical representation of a disk that will be created on the hypervisor. These disks will be created in the same way as extra hard disks on the hypervisor datastore

Templates

Templates can include:

  1. Standard templates
    • Any template that does not have persistent disks is a standard template
    • Templates from previous versions of Abiquo will be converted to standard templates with a single disk which is the primary disk
  2. Persistent templates
    • Any template with a persistent disk is a persistent template
    • Persistent templates from previous versions will become persistent templates with a persistent primary disk

 

Template states

Template disk states

Template disks can be:

  • In progress
  • Done
  • Failed
  • Unavailable

The unavailable state means that the template definition is in the appliance library but the disk is not present in the NFS repository.


Template states

In Abiquo 3.4, the possible template states are the same as the template disk states. The template states are determined from the states of the disks in the template. If any of the disks is in an error state (failed or unavailable), the template will also be in an error state. You can delete individual disks that are in an error state, but a template must always have one disk, even if it is in an error state. The priority of the disk state in determining the template state is as follows:

  • In progress
  • Failed
  • Unavailable
  • Done

For example, if a template has any failed disks, the template is also in the failed state, even if any of its other disks are unavailable or done.

 

  • No labels