Abiquo 5.4

Skip to end of metadata
Go to start of metadata

Abiquo 5.4 gives users more control over disk sizes and storage service levels which are Abiquo datastore tiers. These changes especially apply to public cloud because you can now edit VM template disks and select service levels, and you can also do this on instances in public cloud before or after you launch them

Modify disks of VM templates

In public cloud, users can now edit the storage tier and size of VM template disks.

 if the user does not specify a tier, the platform will select a default tier as follows.

  • AWS: General purpose SSD (gp2)
  • Azure: Standard HDD
  • GCP: Balanced Persistent Disk
  • OCI: Balanced

If the provider supports it, you can also change the tier of a template disk. Currently Azure and AWS support this functionality.

Note: The minimum boot disk sizes to deploy in OCI using Abiquo are 50 GB for Linux and 256 GB for Windows

Screenshot: Edit a VM template in the Abiquo Catalog

Screenshot: Edit VM template disks

Screenshot: Edit a VM template disk

Remember that in private cloud, you must configure the template with the correct deployed capacity of the disk or your deploy may fail. See Determine the size of a VM disk file.

Modify VM hard disks in public cloud

In public cloud, you can change the size of hard disks before and after you launch the instance in the cloud provider. In general, the boot volume in public cloud is an Abiquo hard disk, whereas auxiliary disks are Abiquo volumes. 

If the VM is not deployed, you can change the size of a hard disk, and you can also change the tier in Azure, AWS, and GCP.

Screenshot: Modify a hard disk in public cloud before you launch an instance in AWS.

If the VM is deployed, you can change the size of a hard disk to make it larger. You can also edit the tier in Azure and AWS. To make changes to deployed VMs in Azure, the VM must be in the "deallocated" state. 

Screenshot: Deallocate a VM in Azure

Screenshot: Edit a VM in Azure

Screenshot: Edit VM hard disk in Azure

Modify VM hard disks in private cloud

In private cloud, you cannot change the size of the boot disk before you deploy the VM. 

Screenshot: Modify a boot disk in private cloud

Modify VM volumes in public cloud

If the VM is not deployed, you cannot edit the size or the tier, when you edit the VM. To edit these volumes, go to the Volumes section of the virtual datacenter or location.

Screenshot: Modify a volume in a virtual datacenter in Azure

If the VM is deployed, you can edit the size of a volume in Azure, AWS, and GCP, and the tier in Azure and AWS. To make changes to volumes in Azure, the VM must be in the "deallocated" state. 

Screenshot: Edit a VM and modify a volume attached to a VM in Azure

Screenshot: Edit a volume attached to a VM in Azure

This improvement does not make any changes to how users create or edit external storage volumes in private cloud.



  • No labels