Abiquo 4.7

Skip to end of metadata
Go to start of metadata

1. Configure your user account

1.1. Edit your user account details

After you log in, you may need to edit your user account to update your details:
  1. Click the User icon in top right-hand corner of the screen and select Edit user from the pull-down menu
  2. Change your Password and edit your user details. 
  3. Check you have the correct E-mail address and Phone number to receive passwords and authentication codes, and email notifications
  4. Add your Public key that the platform will use to launch VMs so that you can access them with SSH
 Click here to expand...

Edit user general information

Edit user advanced

1.2. Enable two-factor authentication

Your platform may offer or require two-factor authentication (2fa) to improve user login security with an additional authentication code. For platform configuration instructions, see Configure two factor authentication.

Before you begin:

  • To use Google Authenticator to obtain the codes, install the Google Authenticator app on your cell phone. 
  • To use email authentication to obtain the codes, check that you have a valid email address in your user account on the platform.

To enable two-factor authentication for your user account, do these steps:

  1. Click on the User name or User icon in the top right-hand corner of the screen, and select Two-factor authentication from the pull-down Username menu.
    From the username menu, select enable two-factor authentication
  2. Select the authentication method and click Enable
  3. Copy the Backup codes from the bottom left-hand corner of the configuration window to a secure place. You can use these codes to log in to the platform if the authentication cycle fails

    The platform will display backup codes ONCE only

  4. Authenticate according to your selected method
    • For Google Authenticator, use the Google Authenticator app on your cell phone to scan the QR code. Google will supply a verification code in the app. During login, the platform will request the Authentication code from the app. 
    • For email, during login, every time you enter your user name and password to log in, a code will be sent to the E-mail address registered in your user account. Enter the Authentication code in the Login dialog
 Click here to show/hide the screenshots

Screenshot: Enabling two factor authentication

Two-factor authentication popup to select authentication method

Screenshot: Two factor authentication with backup codes (left) and QR code (middle)

Example of backup codes and QR code for two-factor authentication

Screenshot: Login with two-factor authenticationLogin with two-factor authentication

2. Create and manage VMs

2.1. Create a VM

To create a virtual machine (VM) do the following steps:
  1. Open the Virtual datacenters view by clicking on its icon in the top menu
  2. If there are no virtual appliances to hold groups of VMs, click Create a virtual appliance 
    Enter a Name and select a Virtual datacenter, and enter optional values and click Save
  3. Open a virtual appliance to hold a group of VMs by clicking on its name
  4. To create a VM, drag and drop a VM template from the Templates tab into the Virtual machines pane. You can also double-click the VM template
    1. If there is more than one version of the VM template, you can select another version
    2. If your cloud provider uses hardware profiles, select one
    3. If required, select the Tier, which is the datastore service level, for your VM disk/s

       Click here to show/hide the screenshot

The platform will create your VM. The status bar on the VM icon says it is NOT_ALLOCATED, which means that the VM has not been launched into the cloud.

The next step is to Configure a VM before you deploy.

2.2. Filter templates for creating VMs

The Template tab contains compatible templates only. If you cannot see an expected template, contact your system administrator. If there are a lot of templates, you may wish to filter the templates first.

To filter templates in the left-hand Templates tab:

  • Click the filter button and select a Category from the pull-down list
    • To display only ISOs, select the checkbox
  • Enter text (including * wildcards) in the Search box and press Enter

To clear the search:

  • Click the Clear link on the Category filter popup, which will clear both category and text search box
  • Click the grey X button beside the Search box

2.3. Configure a VM before you deploy

To configure your VM before you launch it, do the following steps:
  1. On the VM icon, click on the options menu button, and from the options menu, select Edit
  2. Change the configuration options as described in this section
  3. Click Save

2.3.1. General configuration

To configure the basic general VM settings, optionally set the following:

  1. Name, which is a friendly name for the VM. Power-on is in alphanumeric name order
  2. Guest setup in private cloud
    1. You can request a Guest initial password that will be sent by SMS or email
  3. Fully qualified domain name that the platform will set at deploy time
  4. Hardware profile and/or CPU, RAM and Cores per socket
  5. Description

To enable remote access to the VM:

  1. Select the Enable remote access check-box
  2. Display and optionally change the password for the remote access connection
  3. Before you deploy: 

    1. For SSH access, check that your user account has an SSH public key. See Configure your user account. You will need the SSH private key to log in to your VM

    2. In public cloud regions, assign:

      1. a public IP to your VM. See VM Network

      2. a firewall policy to allow access to the appropriate SSH or RDP port. See VM Firewall

You can now continue with further configuration or Save and deploy your VM.

If you don't add any IP addresses, the platform will automatically add one on the default network.

To configure IP addresses on your VM, do these steps:

  1. Select the Private, External, or Public tab
  2. For private or external networks, select the network
  3. Create NICs as required:
    • To use an existing IP address, drag and drop it into the NICs list
    • To request an automatically created NIC and IP, drag and drop the Automatically generated IP tag into the NICs pane
    • For private networks, to create a new IP address and NIC, click the + button
    • For public networks, to obtain a new IP address, click the + button, select the network, and select the IP address
  4. Continue configuring your VM or click Save to finish

2.3.2. Storage

In private cloud, you can create additional hard disks that are not persistent. This means that when you undeploy the VM or remove the hard disk, the platform will delete your hard disks and destroy all data on them. To save the contents of a hard disk, create an instance template, which is a copy of the VM hard disk/s in the template library.

To add a hard disk:

  1. At the top-right of the Storage tab, click the + add button

  2. Select Assign virtual disk

  3. In the dialog the options will depend on the platform configuration

    1. You must enter the Size and the Controller type

    2. Advanced options: to force the creation of a new SCSI Controller, assign a new Bus value. The platform will return the bus value assigned by the provider
    3. Optionally select the Datastore tier with the appropriate storage service level
    4. Click Save


  • You cannot change the size of the primary disk before you deploy a VM.

2.3.3. Firewall policies

Select the Firewall policies to add. You can add as many firewall policies as necessary, up to the cloud provider's limit. If you can't see the expected policies, you may need to synchronize with your provider or wait for the platform to update provider data

2.3.4. Load balancers

Select the Load balancers to use for the VM.

2.3.5. Monitoring

To enable monitoring and metrics do these steps:

  1. Select the Fetch metrics checkbox, which will retrieve all metrics
  2. Select from the available options for your provider, for example, for AWS, you can select Basic or Advanced monitoring
  3. Select the metrics you would like to display for your VM

2.4. Deploy to launch into the cloud

To launch your VMs, click Deploy virtual appliance above the Virtual machines pane on the right-hand side of the screen.

The platform will launch the VMs and power them on. The status bar below each VM icon will be coloured green. And the Deploy virtual appliance button changes to become the Undeploy virtual appliance button, which you can click to destroy the VMs.

2.5. Display VM details

To display VM details, select a VM icon. The platform will display the control panel below the VMs with details on different tabs, such as General and NICs.

 Click here to show/hide the screenshots

Here are some examples of VM control panel tabs

  • The General tab contains the CPU and RAM and other information such as the remote access password for connecting to the VM.

General tab of VM control panel

  • The NICs tab contains the details of the IP addresses of the VM.

NICs tab of VM control panel

  • The Storage tab contains the details of the hard disks and volumes attached to the VM

Storage tab of VM control panel

2.6. Display VM metrics

To display metrics of a deployed VM with metrics enabled, click the Metrics symbol on the VM icon.

To refresh metrics data, click the circular arrows refresh button on the right-hand side of the panel. To toggle the display of metrics, click the selection list symbol on the left-hand side, and select the desired metrics.

To filter metrics, click the funnel symbol. Enter the Granularity, Statistics, Period, and/or Dimensions.

Privilege: Access virtual machine metrics

To configure the display of metrics at the virtual appliance level, do these steps.

  1. Select a Virtual appliance and go to Monitoring
  2. Optionally configure the refresh interval. To do this, select the Refresh data every checkbox and enter a number of minutes. 
  3. Choose the metrics you wish to display and filter by metric statistics.

 Click here to show/hide the screenshot

Screenshot: filtering metric statistics

2.7. VM power actions

The multicloud platform supports power actions to easily stop, start, pause, and reset VMs.

To stop a VM that is deployed and powered on:

  1. Select the VM icon
  2. Click the Power off button, which is a square button.
  3. Select from the following options:
    1. Shut down: The platform will try to gracefully shut down the VM. This option may require hypervisor and guest VM configuration

    2. Power off: The platform will perform a hard power off on the virtualization technology. Warning: Using this option may cause loss of data

      Microsoft Azure (ARM)

      • To deallocate a VM in ARM, select the Power off option
      • To power off a VM in ARM, select the Shut down option

      Screenshot: Shutdown and Power Off options

Remember that stopping a VM does not destroy it in the cloud provider and the VM is still consuming resources.

To power on a VM, click the Start button, which is an arrow in a circle.

Depending on the cloud provider, you may also be able to perform the following actions:

  • pause a VM to suspend it using the double vertical bar button
  • reset a VM to restart it using the circular arrows button.

The platform displays the appropriate buttons for the provider and the current state of the VM.

 Click here to show/hide walkthrough screenshots

The following screenshots show two VMs: the VM on the left is selected to perform an action; the VM on the right shows how the result of the action will look.

Screenshot: Power on

Screenshot: Pause

Screenshot: Reset

Screenshot: Stop

2.8. Connect to a VM

The platform enables you to connect to a console of a VM for remote access. The VM must be deployed and powered on.
  • It make take up to 15 minutes after deploy for the initial guest password to propagate to a VM, especially for Windows systems
  • To obtain the remote access password, select the VM and go to the VM control panel → General → click Show password
  • To obtain VM credentials check your email or SMS, or click the key button to display guest initial password or the default credentials button

To connect to your VM from the user interface:

  1. Select the VM and on the control panel, click the Eye icon
  2. In the Remote access dialog, enter the credentials, for example:
    1. For VNC to hypervisors: the Remote access password
    2. For SSH to Linux VMs: the Remote access password and the SSH private key (in the Decryption password box)
    3. For RDP to Windows VMs: the VM user name and the password 
  3. If necessary, log in to the VM with the appropriate credentials

The remote access connection to the VM will open and you can log in and work with the VM. 

  • Remember to change your administrator password as soon as possible.


  • You cannot change the remote access password for ESXi using hot reconfigure. You must restart the VM for the password change to take effect
  • Remember to add a firewall to allow access to the appropriate ports, for example, RDP for Windows
  • In AWS, you must add a private IP on a public subnet to use a public IP; In Azure, you must add a public IP
  • If you cannot connect due to an unsecured certificate error, open a new tab in the same browser, enter the host IP of the VM, and accept the certificate.

2.9. Add more VMs to a deployed virtual appliance

When you add another VM to a deployed virtual appliance, the platform does not launch it directly into the cloud.

You can deploy new VMs individually or click the Deploy all VMs button in the top right-hand corner of the screen.

2.10. Change the configuration of a deployed VM

After you deploy a VM, the changes you can make will depend on your cloud provider. To change the configuration of a deployed VM do these steps:
  1. Select the VM
  2. If your provider or operating system does not support using hot add and hot reconfigure, power off the VM, using the Stop button on the control panel
  3. Mouse over the VM and from the options menu, select Edit.
  4. In the Edit VM dialog, go to General, and make changes as required to:
    1. Name, which is the VM friendly name
    2. CPU and RAM (if your VM is not using hardware profiles)
    3. Remote access
      1. If you disable remote access, hypervisor configuration will remain but you cannot access it through the Eye icon
      2. If you change the password, the change will be applied when you save the VM. Remember that it can be a maximum of 8 alphanumeric characters, i.e.. a to z, A to Z, 0 to 9. If you delete the password, the screen requesting the password will not appear. On ESXi hypervisors, if you set a password and later delete it, the password will be blank, not null. The screen requesting the password will appear, and you should press <Enter> to continue. 
    4. Description of the VM
    5. Hardware profiles
  5. Make changes to Networks and Storage, Firewalls, and Load balancers as required
  6. Click Save

The changes will be applied in the cloud provider directly.

  • To change a VM's Fully qualified domain name (FQDN), make the change in the VM's operating system and the platform will detect the new value
  • For ESXi hypervisors, you cannot change the Remote access password using hot reconfigure

Do NOT change the Abiquo tag in public cloud

Do not change the Abiquo platform's tag on a VM in a public cloud provider (e.g. on an AWS instance) because you could break the link between Abiquo and the VM. If the link is broken, you will not be able to manage the VM with Abiquo.

2.11. Save VM disks to create an instance template

An Abiquo instance is a new template that you create from VM disks.

Privilege: Create instance


  • In Azure the Abiquo instance functionality has been disabled in Abiquo 4.7.0 pending further development.

To create an Abiquo instance, do these steps:

  1. Select and shut down each VM that you want to copy, then click Create instance

  2. Select a VM from the dialog
  3. Enter a Name that will enable you to identify the new template
  4. Optionally select the VM disks to save to a new template in the template library. If no disks are selected, the instance will copy all disks
  5. To create more instances, select Keep window open
  6. Click Create instance. The platform will lock the VM to create the instance
    Select disks to clone for VM instance template
  7. If you kept the dialog open, click Back to list and create more instances as required, then close the dialog

The platform will store your new templates in the Apps library.

  • In vCloud Director, when you create an instance template from a multi-disk VM, the template will be correctly created in vCloud with all of the disks. The platform will display only one disk with the sum of the sizes of all the disks. It will also display only one disk when you create a VM from the template. When you deploy the VM, the Broker will correctly detect the disks and display them on the VM details Storage panel.
  • In Amazon, when you create a VM from an instance template, the platform will display one disk only, with the total size of all disks. After you deploy the VM, the platform will update the additional disks.

2.11.1. Use a saved template in private cloud

To use an instance template in a VM, double-click or drag and drop the original template and an instance menu will open. Select the instance template.

 Click here to show/hide the screenshot

2.12. Display all VMs

To display all VMs of your enterprise, go to Virtual datacentersAll virtual datacentersVirtual machines tab.

To display all the VMs in a specific virtual datacenter, select the Virtual datacenter.

To select icon or grid view, click the icon symbol or the grid symbol in the top right hand corner.

To jump directly to the virtual appliance or virtual datacenter of the VM, go to Grid view and use the shortcut links by clicking on the Name fields.

To filter the VMs, in the Search box, enter text from the VM details with wildcards as required. See Search for VMs and filter the search

2.13. Move a VM to another virtual appliance

To move a VM to another VApp in the same virtual datacenter:

  1. Select the VM

  2. On the VM control panel, click the VM move button

  3. Select the virtual appliance or create a new one, and click Accept

If you have the privilege to restrict VMs, you may also be able to move the VM to a restricted VApp in the same virtual datacenter. 

2.14. Move a VM to a restricted virtual appliance

When you move a VM to a restricted virtual appliance, your administrator or platform provider will control the VM. Your provider may offer this as an option to Outsource a VM.

To move a VM to a restricted virtual appliance:

  1. Click the VM move button on the VM control panel

  2. Select the option to move the VM to a restricted VApp OR select a restricted VApp from the list, or create a new one

     Click here to show/hide the screenshots

2.15. Move a deployed VM to another virtual datacenter

You can move a deployed VM to a virtual datacenter within the same Abiquo datacenter. The target VDC must have the same hypervisor type. If the VM is not deployed, the Move VM button will allow you to Move the VM to another virtual appliance in the same virtual datacenter.

Privilege: Manage VM move

To move a deployed VM to another VDC:

  1. If your VM does not support hot-reconfigure, shut down the VM. This is because moving a VM will change the configuration of the VM, for example, the NICs
  2. Select the VM and click the Move VM button
  3. For a deployed VM, the platform will display a list of compatible virtual datacenters (with the same hypervisor technology and network device) and virtual appliances.
  4. After you select the virtual appliance, the platform will display the configuration dialog.
  5. You must select at least one network address. It is possible to select the same external IP address that was already attached to the VM. 
  6. Optionally select firewalls and load balancers
  7. The platform may display a pricing estimate dialog for you to accept the new VM price.

The platform will move the VM to the new virtual datacenter. If the move is not successful, the VM will be restored to the original virtual datacenter.

2.15.1. Limitations

This feature does not move VMs with the following configuration:

  • External storage volumes
  • NAT rules
  • Scaling groups
  • Anti-affinity layers. 
    • The platform will attempt to remove the VM from its layer and if it cannot do so, then the move will fail. For more details of layer constraints, see Configure VM High Availability. The platform will not add the VM to a layer in the target VDC.

2.16. Delete a VM

To delete a VM, move the mouse over the VM and from the VM options menu, select Delete.

If the virtual appliance or VM is deployed, you do not need to undeploy it. You can directly delete a VM that is deployed. 

Select Delete from virtual machine options menu

3. Manage networks

3.1. Display virtual datacenter networks

To display the networks available to a virtual datacenter:

Privileges: Manage virtual network elements, Access external networks tab, Access public networks tab

  1. Go to Virtual datacenters → select virtual datacenter → Network.
  • The default network is highlighted with a star symbol
  • A network with an internet gateway is highlighted with a globe symbol.

API Features

Virtual datacenter networks are available in the Abiquo API. For example, see VirtualDatacentersResource and PrivateNetworksResource.

Network tab in virtual datacenter highlighting default network and internet gateway

In the Networks list, to view the pool and allocation of IPs:

  • To display all the IPs in the virtual datacenter, click the All button at the top of the list
  • To display the IPs in a network, click the Network name

You can then:

  • Use the slider at the bottom of the list to move through the pages 
  • Filter the list by entering text in the Search box. The filter works with all the columns of the table including:
    • IP Address
    • MAC address
    • Network name
    • Virtual appliance using the IP
    • VM using the IP
    • Provider ID of the entity using the IP (for example, a load balancer)

3.2. Create a private network

Private networks are only available within a virtual datacenter. However, your cloud provider may configure an external gateway for your virtual datacenter.

To create a private network:

  1. Go to Virtual datacenters → select virtual datacenter → Network
  2. Click the  button  and complete the dialog

Create a private network




Name of the network (VLAN). The name can contain up to 128 characters

IPv6Select checkbox for IPv6 network
NetmaskNetwork mask with an integer value of between 16 and 30

Network Address

Private address range of the network


Gateway of the VLAN. Must be an IP within the range of the network address and mask

Primary DNS

The primary DNS

Secondary DNS

The secondary DNS

DNS suffix

The DNS suffix

Excluded from firewallSelect Excluded from firewall to define a network where VM firewalls will not apply

Static Routes

Select Define to create static routes. See Configure Static Routes

Default network

Make this network the default network, replacing the existing default network.

You can configure static routes when you create or edit a network. However, you should check with your systems administrator about when your VM will receive changes to static routes.

Configure static routes for Abiquo networks





Destination network mask

Network ID

Destination network or host

Gateway IP

Next hop (on your network)

 Click here to show/hide IPv6 networks

Strict network


Non-strict network



Name of the VLAN. The name can contain up to 128 characters

IPv6Select checkbox for IPv6 network
StrictIPv6 only. If you select Strict, Abiquo will automatically generate the network address (ULA) and also the IP addresses. If you do not select strict, you can enter the network address and IP addresses.
NetmaskNetwork mask of 48, 56 or 64.

Network Address

Private address range of the network. Only for non-strict networks

Primary DNS

The primary DNS

Secondary DNS

The secondary DNS

DNS suffix

The DNS suffix

Default network

Make this network the default network. In a datacenter, this will override the existing default network

3.3. Use private networks in public cloud

In public cloud providers that support networks:

  • When you onboard resources, the platform will onboard private networks, including details of IP addresses not used by VMs
  • You can synchronize private networks
  • You can create additional private networks in the provider
    • When you create a custom private network in AWS, you can choose the Availability Zone. Availability Zones enable users to deploy VMs separately, with high availability. 
    • To deploy in an Availability Zone, assign a private IP address in the network belonging to that Availability Zone

3.4. Create IP addresses in private networks

To create new IP addresses in a private network do these steps.

  1. Go to Virtual datacenters → optionally select a virtual datacenter
  2. Go to NetworksPrivate → select a private network
  3. Click the Add + button in the top right-hand corner of the Private IPs page and enter details

Or you can add an IP directly to a VM. To do this:

  1. Go to Virtual datacenters → edit VM → Network
  2. Click the Add + button and enter details (or drag the Auto-generated IP label into the Network pane)

Enter the Number of IPs to create and the From IP address (the first in the range). The first IP address must be a new address that does not already exist in the network. After creating the first IP address, the platform will try to create the other IPs and it will skip any existing IP addresses. 

For example, if you have IP addresses in network, which are 30, 33, and 34 and then you request 3 new IPs from The new IPs created should be as follows: 31, 32, 35. 
IP Addresses
 Click here to show/hide IPv6 details

When you add IPv6 addresses on strict networks, you don't need to set the starting address.

On non-strict IPv6 networks, Abiquo recommends that you create an automatic IP address, or you can enter a From IP address manually as shown here.

3.5. Edit a private network

To edit a private network
  1. Go to Virtual datacenters → select a virtual datacenter → Network
  2. Select the network
  3. Click the Edit button  above the Networks list:
  4. You can change the network Name, Gateway, DNS settings, and optionally make the network the new default for this virtual datacenter.
  5. Click Save

The new settings will apply to all VMs deployed after you save the network.

3.6. Delete a private network

You can delete a private network if no VMs are using its IPs and it is not the default network for the virtual datacenter.

To delete a private network:

  1. Go to Virtual datacenters → select a virtual datacenter → NetworkPrivate
  2. Select the network and click the Delete button  above the Networks list. 

3.7. Display onboarded external networks

The platform automatically onboards external networks when you onboard virtual datacenters from vCloud Director.

Privileges: Manage virtual network elements, Access external networks tab, Manage external network elements

To display onboarded external networks

  1. Go to Virtual datacentersNetwork → Select vCloud VDC → External

3.8. Delete an onboarded external network

If an onboarded network has been deleted in the provider, its name will display in light gray text. If a VM is using an IP from this network, then you cannot deploy the VM.

If there are no VMs using the IPs of an external network that was already deleted in the provider, to delete the network in the platform, select it and click the Delete button.

3.9. Set default virtual datacenter networks

The platform always requires a default network for a virtual datacenter to ensure that if you deploy a VM without assigning a NIC, the platform will be able to add one from the default network.

Privileges: Manage virtual datacenter network elements, Access public network tab, Manage public network elements, Access external network tab, Manage external network elements

To set a new or existing network as the default:

  1. When you create or edit the network, select the Default network checkbox. The new default network will apply to all VMs deployed after you set it.  

In private cloud, if you set a public network as the default, remember to obtain IP addresses for your VMs before you deploy!

4. View your resources and statistics

4.1. User dashboard

The Home view or Dashboard is the first screen you will see when you log in to Abiquo. It has Metrics, Hybrid, and Optimization tabs. 

  • You can sort tables by columns by clicking on the columns in the header rows
  • To jump directly to a VM, virtual datacenter or virtual appliance, double-click on its Name or label.

4.2. Metrics

The Metrics tab provides a general view of the resources currently being used by your virtual datacenters, as well as events.

Metrics panels: 

Enterprise resources - virtual datacenters shows statistics of the resources used by your virtual datacenters. Select the virtual datacenter name from the pull-down list

Virtual CPUs

Virtual CPUs used by VMs that are currently deployed


VM disks that are created on the hypervisor datastore. This includes non-persistent VM system disks and hard disks.
These disks will be deleted when the VM is undeployed. Gigabytes of disks created on datastores.

MemoryGigabytes of RAM used by VMs that are currently deployed
Ext. StorageVolumes of storage created on integrated/managed iSCSI or NFS, or generic iSCSI storage devices.
This includes volumes of persistent external storage and persistent VM system disks. Gigabytes of volumes created in VDCs.
VLANsPrivate VLANs defined in Abiquo. A default private VLAN is always created when you create a virtual datacenter. Number of VLANS created in VDCs
Public IPsNumber of IP addresses purchased or reserved in public VLANs
RepositoryNFS Repository space used by the enterprise in the Apps library including templates and instances but not conversions (GB). Available for enterprises only, not individual virtual datacenters
Virtual machinesNumber of VMs deployed by the enterprise

Key to the graph:

  • Green: Used resources
  • Orange: Soft limits
  • Red: Hard limits

4.3. Metrics Tables

Virtual appliancesAll the virtual appliances of the current enterprise in the platform, with totals in the table header
Virtual datacentersAll the virtual datacenters of the current enterprise in the platform, with totals in the table header
Last deployed VMsThe last VMs deployed by the tenant on the platform. It can be filtered by user, including deleted users
Last triggered alertsThe last alerts triggered for the tenant on the platform
EventsAll events that you can access; to display full details of an event, can click on the event line. 

4.4. Hybrid

The Hybrid tab provides an overview of the distribution and cost of your resources between public cloud providers and private cloud. 

Hybrid panels: 

Virtual machines countThe enterprise's VMs that are deployed in public cloud providers or private cloud. You can filter the list by public cloud provider or private cloud.
Workload of VMs by locationA graph of the enterprise's VMs deployed in public cloud providers or private cloud. The virtual machines are counted by location (public cloud region or datacenter). To view the detailed list with a count of VMs in each location, click on the graph

Hybrid billing widgets:

Widget controlDescription
Latest billsThe amount of the last bill and the change in spend from the previous bill for the selected provider
Show more billsA graph with the most recent bills registered in the system. Move the mouse over the graph line to display the bill details
Estimated billFor the current period, calculated using a linear regression of daily costs for the current period, and the change in spend from the last bill for the selected provider
Average cost per VMCalculated from the last bill and the number of VMs in the selected provider


 Click here to expand...

The hybrid billing dashboard for a cloud provider

Hybrid billing details for a cloud provider

4.5. Optimization

The Optimization tab aims to help you make best use of your cloud resources. 

For more details of a VM, click on the arrow symbol beside the VM details

 Click here to expand...

Optimization panels:

CPU usage > 80%The VMs with highest average CPU usage over the last 30 days
RAM usage > 80%

The VMs with highest average RAM usage over the last 30 days

Longest time deployedThe VMs with the highest time deployed on the platform in days and hours, and not requiring the VMs to currently be in any specific state. You can filter by user name and deleted users
CPU usage < 30%The VMs with lowest average CPU usage over the last 30 days
RAM usage < 30%The VMs with lowest average RAM usage over the last 30 days
Unused public IPsThe public, floating, or NAT IPs that have been reserved by the tenant but are not in use on a deployed VM
Unused load balancersThe load balancers that have been created by the tenant in the provider but are not in use for deployed VMs  

5. View your actions and events on the cloud platform

The Events view allows users to find out what is happening on the platform.

To open the Events view, click on the Events icon   in the main menu bar. To add new events as they arrive, select the Update automatically checkbox. Otherwise, you must refresh the list manually. 

To display the event details in the panel below the Event list, double-click on an Event. 

Depending on user privileges, you may not be allowed to view events, or you may be able to view events for your tenant.

If the events you expected to display do not appear in Events view, check with your System Administrator.

5.1. Event attributes

An event has the following attributes:




The system object that is the source of the event or error. For example, it could be a VIRTUAL_APPLIANCE for a group of virtual machines.

Entity name

The name of the system object that is the source of the event or error, for example, myVirtualAppliance.

ActionThe action that generated the event, for example, DELETE. See Events Table

Performed by

The user who performed the Action, for example, admin.

SeverityThe severity of the event. Can be INFO, WARN or ERROR


The date and time when the event was generated.


Additional information about the event. See Events Table for more details. The traces displayed in Events view are also found in the Logs, which are documented in the Troubleshooting section of the Abiquo Administrator's Guide. See Abiquo Logs, especially catalina.out 

ContextThe identifier of a group of related events. This attribute is in the event detail but not in the event list.

5.2. Event context

When you view the event detail, the platform will display the Context of the event. The context is an ID that the platform assigns to each event in a group of related events. For example, if you undeploy a virtual appliance, the platform will create events for the undeploy of each VM, the destruction of the related hard disks, and the release of the NICs. And the platform will assign the context ID to each of these events. You can filter by context to display this group of events.

5.3. Filtering events

To make it easier to find a specific event, use the filter tool. Click the filter button  at the top right of Events view. Enter your filter criteria and click Accept. To remove the filter, click Clear at the bottom of the popup.

When events are filtered, the text (events filtered)  will be displayed next to the filter button.

Event fieldDescription
EntityPull-down list of Entities
ActionPull-down list of Actions
Entity nameThe name of the entity. The Name field may contain the UUID or the friendly name of the entity
SeverityPull-down list of event severity. See Events View#Severity table
UserThe name of the user who performed the action
EnterpriseThe tenant that the event occurred in
Date fromCalendar selection for start date in format YYYY/MM/DD
Date toCalendar selection for end date in format YYYY/MM/DD
MessageThe message field will contain the details of the event, including the friendly name. See Events Table

5.3.1. Examples of events filter

To filter alarm events by name, enter the friendly name of the alarm in the Message field of the filter. Note that the Name field contains the UUID of the alarm.

To display all the events related to an event, select the Event from the list, copy the Context ID and filter by Context.

5.4. Severity table

Events on the Abiquo platform are classified into three severity categories: info, warning and error. 




General information events for the user as part of the normal use of the platform


Warning about an abnormal situation that does not block normal use of the platform


Error that blocks the normal use of the platform

5.5. Events table

The Events Table describes all the actions that can be performed on each entity and the event that they can generate on the platform. For example, for the Action plan entity, you can perform the Create, Modify and Delete actions, and events will also be generated when you run an action plan.