Abiquo 5.1

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 19 Next »

This manual is a basic guide to how to Administer and Use Public Cloud in Abiquo

The following basic roles are described in this manual: cloud administrator, enterprise administrator, and user.

Cloud administrator tasks

This section describes the cloud administrator tasks in public cloud.

Configure your user account

All users should configure their user accounts before starting work with the cloud platform.

Edit your user account details

The system administrator should log in first and change the passwords and user details.

To change your user password and user details:

  1. Click on the username icon at the bottom left of the screen
  2. Select Edit user
  3. Change the Password, enter an Email, a Phone number and an SSH public key, and change other details as required.
    General information

Note that you cannot change many of the details of the main cloud administrator account, and you cannot change its role and privileges. However, you can replace the main cloud administrator account  with another equivalent cloud administrator account. You can also edit this user account and other user accounts in Users View

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 initials or user icon in the lower left corner of the screen, and from the menu, select Two-factor authentication.
  2. Select the authentication method and click Enable
  3. Copy the Backup codes from 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

Enabling two factor authentication

Two factor authentication with Google Authenticator with backup codes and QR code

Login with two-factor authentication

Edit public cloud credentials for your enterprise

To work with a public cloud region, each enterprise should have its own public cloud account for the cloud provider. All the users in the tenant will work with this same account. 

Privilege: Manage provider credentials

Before you begin:

  1. Check your provider's documentation and pricing. 
  2. Obtain credentials to access the cloud provider's API. We provide basic guides but you should always check with your provider. See Obtain public cloud credentials

To add public cloud credentials:

  1. Go to Users → select and edit enterprise → Credentials → Public
  2. Enter the Credentials as described here

    ProviderSelect public cloud provider or vCloud Director region. Some providers may require different credentials for groups of regions, for example, "Amazon (CHINA)". If a specific provider does not display, for example, a vCloud Director region, the cloud administrator may need to allow access for your enterprise.
    Access key ID

    Identity to access the cloud provider API. For example, a username, API access key ID, subscription ID and certificate, or another account identifier. For DigitalOcean v2, the platform does not use this field but you need to write something in to enable the button Add account after.

    For Azure, the format is subscription-id#app-id#tenant-id

    Secret access keyKey to access the cloud provider API. For example, an API key or other API credential.

    For DigitalOcean v2 enter the token.

    Also use for pricingUse this credential to access pricing data in the provider. For example, to get hardware profile prices from AWS. For Azure, add a separate pricing credential.
    Current credentialsProvider that have credentials already in the platform
    Create accountFor resellers with Amazon, Azure ARM, and other partner accounts, click the enterprise create account button to create a customer account in the provider and add it to an enterprise in the platform
  3. Click Add account. The platform will validate your credentials with the cloud provider and save them
  4. Finish editing the enterprise and click Save

This will add a cloud provider account for a tenant enterprise with access to a public cloud region.

Add an application for OAuth

For OAuth applications, users can add applications, display keys, inspect the privileges assigned to the application, and delete the application.

Privilege: Manage user applications

To add an OAuth application:

  1. Click on the User name or User icon in the top right-hand corner of the screen to open the Username menu 
  2. Select Manage applications
  3. Click the + button
  4. Enter the Name and Description of the application
    Popup to add application for OAuth authentication
  5. To set the privileges of the application, go to Privileges. By default, all of the user's privileges are selected for the application. We recommend that you go to Privileges and remove any unnecessary privileges
    Add privileges to OAuth applications
  6. Click Save

Abiquo will add the new application to the Applications list and display the API key and an API secret key. Copy the API key and API secret key to a secure storage area.

View keys and privileges assigned to OAuth application

Create public cloud regions


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

Control tenant resources

You can control the resources that an enterprise may consume. This will help prevent resource over allocation, enterprises using resources from other enterprises, and even DoS attacks. Allocation limits will also help system administrators to anticipate user needs and forecast resource demand. Hard and soft limits are used by the resource scheduler to decide if a user can deploy a virtual appliance or not.

  • Hard Limit: the maximum amount of resources (CPU, RAM, Hard Disk, etc.) that an enterprise may consume.
  • Soft Limit: triggers a warning for users that they nearing the hard limits for their enterprise.

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

Enterprise allocation limits are checked during configuration or deploy, or before operations as shown in the above table.

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

Allow the tenant to access regions

To set the datacenters and public cloud regions that an enterprise is allowed to access, edit the Enterprise and click the Datacenters tab.

Select one or more datacenters or public cloud regions in the left pane and drag and drop them into the "Allowed Datacenters" right pane.

Access to at least one datacenter or public cloud region is required in order to deploy VMs. The left pane contains datacenters, which are "Prohibited Datacenters" by default.

Datacenters Automatically Assigned to Current Enterprise on Creation

By default, when a datacenter or public cloud region is created it is automatically assigned as Allowed for the current user's enterprise only.

Note that Allowed datacenters are working datacenters where users can deploy. This is different to an admin user having administration Scope to administer the infrastructure of datacenter. 

Limit tenant resources in the region

You can set resource allocation limits for this enterprise in each allowed datacenter or public cloud region. To set allocation limits, select one of the Allowed Datacenters in the right pane and click the edit button. Set these limit values in the pop-up that opens.

Limit resources for an enterprise in a public cloud region

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

Validation of resource limits in a location

As for overall enterprise limits, resource limits in a datacenter or public cloud region are validated as described in the following table. 

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

Tenants obtain cloud provider credentials

If the tenant does not have cloud provider credentials, they should follow their cloud provider's instructions on how to obtain access to the provider's API.

Abiquo provides basic guides to obtaining credentials, but the tenant should always consult the cloud provider for the most up-to-date information.

Add tenant credentials for each provider

Before you enter public cloud credentials, there must be an existing public cloud region for the provider.

To add credentials for a public cloud provider

  1. Check in Infrastructure view or with your Administrator, that the public cloud region is already created
  2. Edit the enterprise and select the Credentials tab
  3. From the Provider pull down list, select the public cloud provider
  4. Enter your Access key ID, which may be a Username, a specific API access key ID or other account identifier
  5. Enter your Secret access key, which may be an API key or other API credential
  6. Click Validate account
  7. After the account has been validated, click Save

Prepare foundation template library

In the Abiquo Apps Library you can compile a selection of certified public cloud templates for your users to deploy by self-service.

Abiquo will store the details of these templates but not their disks.

In the Abiquo Apps Library you can compile a selection of certified public cloud templates for your users to quickly and easily deploy VMs. Abiquo stores the details of these templates but not their disks.

Public cloud libraries can have many thousands of VM templates (e.g. AWS has 19,000 AMIs) that are difficult to find and manage. In addition, administrators cannot control the content of public cloud templates. In the Apps library, you can define a cache of details of your approved or certified public cloud templates. And you can customize the templates' representation to make it even easier for cloud users to find the right template. 

To display VM templates:
  1. Go to Apps library → Public
  2. Select the public cloud region
  3. To change to the list view, click on the list view symbol in the top right-hand corner.

To display the details of a template, move the mouse over the template. A tooltip will display the template information.

Filter local public cloud templates

You can search and filter templates for all public clouds and other clouds that use their own registry, such as vCloud Director. 

To filter templates in the Apps library:

  1. Click the funnel filter button.
  2. Enter filter values that are not case sensitive
    1. For the ID, you can enter a template ID, for example, ami-0354b96a
    2. For the Name you can enter any text, including wildcards, to search for in the template Name and Description. 
  3. Click Search

To reset filter values to defaults, click Clear.

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

Tenant administrator tasks

This section describes tasks that will generally be performed by a tenant administrator.

Obtain credentials for public cloud

Abiquo provides basic guides to obtaining credentials, but the you should always consult the cloud provider for the most up-to-date information. 

Prepare enterprise templates

Depending on their user privileges, the tenant administrator may be able to do the following tasks

  • Search the Apps library for templates
  • Add templates to the Apps library
  • Modify templates
  • Share templates with their customers

Privilege: Access Virtual datacenters view

In the Virtual datacenters view you can manage your compute, network and storage resources. Each virtual datacenter (VDC) is a separate cloud environment in a single datacenter or public cloud region. To access Virtual datacenters view, click the cloud virtual datacenters button.

To display all the virtual datacenters in specific providers, click the funnel filter button at the top of the list and select one or more providers.

In private cloud with hypervisors, the platform saves the disks and a copy of the original template definition, unless the VM was captured from outside Abiquo, in which case it saves the configuration of the VM. The platform stores the instance under the master template in the Apps library. An instance is a copy of the selected disks of a VM made at a given time and stored as a VM template. In public cloud providers, the platform saves the instance as a new VM template with disks and the configuration of the VM. Remember to enter a name that will help you to identify the instance template

In the platform, hard disks are non-persistent and they are destroyed when deleted from the VMs or when the VMs are undeployed. In private cloud datacenters with hypervisors, the platform creates hard disks on the hypervisor datastore.

In private cloud datacenters, volumes are persistent and independent of the VMs. The platform creates volumes on external storage devices. Volumes are available in private cloud datacenters with hypervisors and they require the external storage feature. 

A persistent VM template has one or more persistent disks on external storage volumes. Persistent VM templates are available in private cloud datacenters with hypervisors and they require the external storage feature.

Persistent VM template disks are associated with a specific virtual datacenter. Hypervisors running persistent VMs will work directly from any persistent volumes. VM data stored on a persistent disk will be persisted on the external storage device. When you undeploy a VM, all changes made to the non-persistent disks will be lost. The next time you deploy the VM, the non-persistent template files will be freshly created, for example, standard template disks will be copied again from the appliance library to the target hypervisor. Note that it is not necessary for you to use a persistent disk as a system disk when you create a persistent VM.

Related pages

Onboard from public cloud

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

Onboard virtual datacenters from public cloud

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

Abiquo automatically onboards from public cloud regions

If you public cloud provider does not support virtual datacenter entities, Abiquo will automatically onboard when you select the public cloud region.

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

Restrict user access to virtual datacenters

By default, all users have access to all virtual datacenters. However, you can select a list of virtual datacenters for each user and they will only be able to access these virtual datacenters.

To restrict VDC access, open Users view and create or edit a user who is not an administrator or who does not have the No VDC restriction privilege.

On the create or edit dialog, select the Restrict access to VDC checkbox to open the list of available virtual datacenters. If none are selected, the user will have access to all VDCs. Select the VDCs where this user will be able to deploy VMs. You can only restrict the VDC access of users without the No VDC restriction privilege.

Manage Networks

This section describes how to manage networks in private datacenters and public cloud providers. 

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
  • In public cloud, to synchronize networks and IP addresses, click the round arrows synchronize button
  • In AWS, you can filter the list of private networks by Availability Zone

API Features

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

Screenshot: Private networks in private cloud

Screenshot: Private networks in public cloud (AWS)

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)

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 Private
  2. Click the + add button  and complete the dialog

Create private network

Create private network Amazon




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

IPv6Select checkbox for IPv6 network

Network Address

Private address range of the network

NetmaskFor IPv4 a network mask with an integer value of between 16 and 30


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

Availability zoneIn AWS, optionally select an Availability zone for high availability. To deploy a group of VMs separately, use a different availability zone for each VM. To assign a VM to an availability zone, assign a private IP address in the network belonging to the required availability zone

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

In supported providers, optionally select Define to create static routes. See Configure Static Routes using DHCP

Default network

Select to 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.





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

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. On the Private IPs page, click the add + button 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 From 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

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.

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 pencil edit button below 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.

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 below the networks list. 

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

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.

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!

Obtain IP addresses from public networks

In public networks you can reserve or purchase public IP addresses for your VMs. Reserved IPs may be charged while they are reserved, even if they are not used in VMs. 

Privilege: Manage public IPs, Access public networks tab, Manage public network elements

To add new public IP addresses to your virtual datacenter:

  1. Click the + Add button on the Public IPs page to display the list of available public IPs
    1. To move between pages, use pagination controls such as arrows and page numbers
    2. To filter your search, enter an IP address or Network name in the Search filter box
  2. Select IP addresses to add them to your virtual datacenter 
  3. Click Add to reserve the IPs

The platform will add the IPs to your VDC

You can also reserve public IPs directly from the Edit VM dialog.

Obtain public IP addresses in public cloud

During onboarding from public cloud, the platform will onboard existing public IP addresses in providers that support them, such as AWS and Azure. You can obtain them from the provider and assign them to your virtual datacenters and VMs.

The provider may charge for public IP addresses as soon as you reserve them for your virtual datacenter. Therefore you should reserve your IP addresses just before you deploy and check they are deleted when you undeploy your VMs. Remember that your provider may also limit the number of public IP addresses that you can use per virtual datacenter.

To add public IP addresses to your virtual datacenter, so that you can later assign them to your VMs:

Privileges: Manage virtual network elements, Manage floating IPs, Access public networks tab, Manage public network elements

  1. Go to Virtual datacenters → Select a public cloud virtual datacenter → Network → Public
  2. On the Allocated public IPs page, click the + add button
  3. To add the public IP to a virtual datacenter, click the Add to VDC link near the IP address

Now when you edit a VM in the VDC and go to Network → Public, the platform will display the public IP address and you can add it to your VM.

To obtain a public IP directly for a VM, click Purchase public IPs.

Synchronize public IP addresses with the cloud provider

To onboard any public IP addresses that were already created in your cloud provider, or update changes made directly in the provider:

Privileges: Manage virtual network elements, Manage floating IPs, Access public networks tab, Manage public network elements

  1. Go to Virtual datacenters → select a public cloud virtual datacenter → Network → Public
  2. Click the double arrow synchronize public IPs button (beside the + add button)

Release a reserved public IP address

You can release a public IP if it is not assigned to a VM.

In private cloud, to release a public IP that belongs to a public network, select the IP in the IP list and click the delete button.

In public cloud, click the link to Remove from VDC and then click the delete button.

Manage firewalls

Introduction to Firewalls

The platform provides a unified interface to firewalls in varied cloud environments. 

This section describes firewall policies, which are similar to security groups. The platform supports firewall policies in private cloud with network managers (NSX) and in public cloud (AWS, Azure). In Oracle Cloud, the platform enables users to onboard classic firewalls and assign them to VMs.

In vCloud Director, the platform also supports classic firewalls, which are Edge firewalls at level of the public cloud region (orgVDC). See Manage classic firewalls

Synchronize firewall policies with the cloud provider

The synchronization process will onboard firewalls and it will update the platform's information about firewalls that already exist in the cloud provider. The platform synchronizes automatically when you onboard virtual resources from public cloud. Depending on the provider, the platform may support synchronization at the level of the location (public cloud region) or virtual datacenter.

To synchronize firewalls do these steps:

  1. Select All virtual datacenters and the location, or a single virtual datacenter
  2. Click the double-arrow synchronize button 

To synchronize a firewall before you add new firewall rules:

  1. Select the firewall and click the double-arrow synchronize button

Create a firewall policy

The platform can create firewall policies in virtual datacenters in the provider, or in the platform only, for later use in providers, depending on provider support.

Privilege: Manage firewall

To create a new firewall, do these steps:

  1. Go to Virtual datacentersNetworkFirewalls
  2. Click the Add button
  3. Enter the firewall details




    Name of the firewall policy.

    LocationPublic cloud region or datacenter
    Virtual datacenter
    • Virtual datacenter: The platform will create your firewall in the cloud provider. It will add a provider-ID that will display on the main Firewalls page. The platform will synchronize rules with the provider
    • No virtual datacenter: If allowed by the provider. The platform will create the firewall in the platform only, for your enterprise in the public cloud region. The platform will not synchronize rules with the provider. The platform will create the firewall in the provider when you select a virtual datacenter.
    DefaultOptional. Select to make the firewall the default for the virtual datacenter


    Description of the firewall policy

  4. Click Save to create the firewall
  5. Add Firewall rules as described below

If you entered a virtual datacenter, the platform created your firewall in the provider. The platform will display a Provider-ID and a Virtual datacenter ID for the firewall. 

If you selected No virtual datacenter, the firewall will be created in the platform in the public cloud region for your enterprise. The synchronize process will not update this firewall. The platform will not create it in the provider until you select a virtual datacenter.

Set a firewall policy as the default for a virtual datacenter

You can set a default firewall policy for each virtual datacenter. 

Privilege: Manage default firewall

To set or unset a default firewall for a virtual datacenter:

  1. Select the firewall
  2. Click the star button

When the user creates a VM, the platform will assign the default firewall. The firewall rules apply to VMs, not individual NICs on the VMs. Changes to the firewall ruleset will apply to every VM in the virtual datacenter with the default firewall. If you do not set a default firewall but the provider requires one, for example, AWS, the platform will set the provider's default firewall. In AWS the default firewall is not marked. 

Edit a firewall policy

If your provider allows it, you may edit a firewall policy in the platform. 

To edit a firewall policy:

  1. Go to Virtual datacenters → select virtual datacenter or select a region → Network → Firewalls
  2. Select the firewall policy and click the pencil edit button.
  3. Make your changes and click Save




Name of the firewall policy. Some providers will not allow you to edit the name of the firewall policy

DefaultSelect this option to set the firewall as the default. The platform will assign the default firewall to new VMs.


Description of the firewall policy

Move a firewall policy to another virtual datacenter

Before you begin:
  1. Check if your provider allows you to move firewalls. For example, Azure ARM allows you to move firewalls to other VDCs in the same resource group

To move a firewall to another virtual datacenter

  1. Go to Virtual datacenters → Locations
  2. Select the public cloud region
  3. Edit the firewall policy and select the Virtual datacenter

Edit firewall rules

You can define firewall rules for inbound and outbound traffic in your firewall policy.

To add a new firewall rule:

  1. Select the virtual datacenter or location
  2. Select the firewall
  3. On the Firewall rules panel, click the pencil Edit button
  4. Select the Inbound or Outbound tab for the traffic direction you wish to control
  5. Enter the details of a rule
    1. Protocol
      • Select from Common protocols, OR
      • Select and enter a Custom protocol
    1. Port range with the Start port and End port that this rule will apply to. To enter one port, enter the same value twice, or optionally apply the rule to a number of ports at the same time
    2. Sources or Targets as a network address and netmask
  6. Click Add. The firewall rule will be added to the Firewall rules list
  7. Enter more rules as required, then click Save

Edit firewall rules in AWS

Before you edit firewall rules in AWS, synchronize the firewall to update the rules because AWS will not allow you to create a rule that already exists in the security group. Remember that it may take some time for firewall rules to propagate throughout AWS. Until the rules have propagated, the platform will not be able to detect them. See http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/query-api-troubleshooting.html#eventual-consistency

Delete firewall policy rules

To delete firewall rules, do these steps.

  1. Go to Virtual datacenters → select a virtual datacenter or select All → Network → Firewalls
  2. Edit the firewall
  3. Select the Inbound or Outbound tab
  4. On the left-hand side of each rule you wish to delete, click the trash/garbage Delete button
  5. Click Save

Display firewall policies

You can display and manage firewalls in the platforms at the level of the virtual datacenter or the location (public cloud region or datacenter).

To display firewalls that exist in a virtual datacenter in the provider:

  1. Go to Virtual datacenters → select a virtual datacenter → NetworkFirewalls

To display all firewalls in a location (public cloud region or datacenter), including those that only exist in the platform and not in the provider:

  1. Go to Cloud virtual datacenters view → Locations
  2. Select a location
  3. Go to Network → Firewalls

To filter firewalls, enter text in the Search box to search by the NameDescription, and Provider ID in the Firewalls list.

Assign a firewall policy to a VM

See Assign a firewall policy to a VM

Delete a firewall policy

To delete a firewall policy:

  1. Edit each VM that is using the firewall policy to remove the firewall policy
  2. Select the firewall policy
  3. Click the Delete button

Manage firewalls with the API

API Documentation

For the Abiquo API documentation of this feature, see Abiquo API Resources and the page for this resource FirewallPoliciesResource.

Manage load balancers

Introduction to load balancers

The load balancer feature aims to simplify the creation of load balancers across all cloud platforms, providing a unified interface. You can create a load balancer in the enterprise for the location and later assign it to a virtual datacenter, and then the platform will create it in the provider. You can also reuse load balancer configurations.

Please refer to cloud provider documentation as the definitive guide to the load balancing features.  And remember to check your cloud provider pricing before you begin.

In vCloud Director, load balancers belong to a public cloud region, not a virtual datacenter. This means that in vCloud Director, you can attach VMs from more than one virtual datacenter to the same load balancer, and these load balancers do not work with private networks, which belong to only one virtual datacenter.

See Provider support for load balancers tables

Display load balancers

You can display and manage load balancers in the platform at the level of the virtual datacenter or the location (public cloud region or datacenter).

To display load balancers in a region, including those that are not assigned to a virtual datacenter in a provider

  1. Go to Cloud virtual datacenters view
  2. Click the Locations button and select a location
  3. Go to Network → Load balancers

To display load balancers in virtual datacenters:

  1. Go to Cloud virtual datacenters view
  2. Select a virtual datacenter

  3. Go to Network → Load balancers.

Create a load balancer

Before you begin:
  • Synchronize your virtual datacenters (including VMs, networks, firewalls, firewall rules, and load balancers)
  • If required by your provider, create firewalls for your VMs to allow your load balancers to access the VMs
  • In Azure make sure that your VMs belong to availability sets

Privilege: Manage load balancers, Assign load balancers

To create a load balancer:

  1. Go to Virtual datacenters → select a virtual datacenter → NetworkLoad balancers 
    1. For vCloud, select All virtual datacentersNetworkLoad balancersRegion
  2. Click the + add button and complete the following dialogs according to your cloud provider's documentation

Load balancer general information

The following screenshots are from AWS or Azure




The name of the load balancer.

  • Amazon will only accept the following characters: A-Z, a-z, 0-9 and "-", and you cannot modify the name
  • Azure will not accept names with white space


In providers that support subnets, the subnets to which the load balancer will connect


See cloud provider documentation for more information


  • AWS: private or public IP
    Rackspace: private or public IP
    Azure ARM: private or public IP
    Neutron: private IP, or private and public IPs
    NSX: private IP, or private and public IPs
    vCloud Director: private or public IP (IPs on external networks)

  • You may be able to change the address to another one in the same VDC by editing the load balancer

Load balancer routing rules



Common protocols

Select one of the common protocols to load presets

Protocol in

The incoming protocol to the load balancer. See cloud provider documentation for accepted values.

Port in

The incoming port to the load balancer. See cloud provider documentation for accepted values.

Protocol out

The outgoing protocol from the load balancer.

Port outThe outgoing port from the load balancer
SSL CerftificateFor secure connections (e.g. HTTPS), you can add an SSL certificate.
  • The platform will never store or validate the SSL certificate 
  • The platform will pass the certificate directly to the provider
Select an existing certificate or add a new one. Cannot be used in platform-only load balancers
AddClick Add to save a routing rule for the load balancer

To delete a routing rule, click the delete button beside the name of the routing rule in the list

Load balancer SSL certificate




Name of the certificate


The certificate contents

Intermediate certificate

An intermediate certificate can be issued by a provider to support older browsers that may not have all of the trusted root certificates for that provider, so that users will not receive invalid SSL warnings. If you have an intermediate certificate, add it at the same time as the certificate to ensure that a trusted-chain certificate is configured.

Private key

The RSA private key for the certificate

Load balancer health check




Common protocols

Select one of the most common protocols to load presets


Name of the health check


The protocol with which the health check will be performed


The port to which the health check will be performed

PathThe server path to ping (for supported protocols)
Interval (sec)The interval in seconds between health checks
Timeout (sec)The timeout in seconds after which an attempted health check will be considered unsuccessful
AttemptsThe number of attempts before the health check will be considered unsuccessful
AddAdd the current health check to the load balancer

Load balancer firewalls

If your provider supports firewalls, to add a firewall to your load balancer, select your firewall from the list of Firewalls that were created in your provider. Rackspace does not display a firewall selection list.

If a firewall is not on the list, it may not have been properly synchronized. In this case, you will need to click Cancel, synchronize firewalls and start again to create a new load balancer.

Assign load balancer nodes

To assign your load balancer to VMs, drag and drop the VMs them from the Available Nodes list into the Attached Nodes list.

  • The VMs to be load balanced can be in the same or different virtual appliances in the same virtual datacenter
  • You can also attach VMs by selecting load balancers when configuring the VM. 

The platform will display the Status of the load balancer nodes on the Nodes tab, if status information is available from the provider.

You can also check the status using the Abiquo API.

Manage load balancers with the API

API Documentation

For the Abiquo API documentation of this feature, see Abiquo API Resources and the page for this resource LoadBalancersResource.

Edit load balancers

The cloud provider determines which elements of a load balancer that you can modify. Due to different provider support for load balancer features, it may be possible to make modifications in the platform that will later be rejected by the cloud provider, triggering an error. Check your cloud provider documentation for supported modifications.

Edit VMs to assign or unassign to load balancers

Privilege: Assign load balancers

To assign a virtual machine to a load balancer, select the load balancer from the list.

Onboard and synchronize load balancers from public cloud

When you onboard a VDC from a public cloud provider, the load balancers associated with the VDC and its VMs will be onboarded into the platform.

To access vCloud load balancers, and provider-only load balancers

  1. Go to Virtual datacenters → All virtual datacenters
  2. Go to NetworkLoad balancers → select region

To synchronize all load balancers in a VDC or region:

  1. Go to Virtual datacenters
  2. Select the VDC or region
  3. Click the arrow synchronize button.

Load balancers that have been deleted directly in the provider are displayed in light gray text. You can edit these load balancers to recreate them in the provider, or delete them.

Delete or release load balancers

To delete a load balancer:
  1. Select the load balancer
  2. Click the delete button.

If your enterprise does not have credentials in the provider, then the load balancer will be released (it will be deleted in the platform but it will remain in cloud provider).

Cloud user tasks

This section describes the tasks performed by the cloud user. Depending on user privileges, some of these functions may be performed by the tenant administrator.

Add public key to user account

Click on your user name in the top right-hand corner of the screen.

Edit your user account and update your details. Add a public key for SSH access to VMs deployed in public cloud.

Create virtual appliances

To create a new virtual appliance, open the Virtual datacenters view. Then select the virtual datacenter where the virtual appliance will be deployed, click the   add button, and complete the form.



Work with VMs

The basic process for working with VMs is the same throughout the whole Abiquo cloud platform, regardless of the underlying technology, which may be hypervisors, public clouds or Docker. The following screenshots show a private cloud environment, but they would be very similar for a public cloud or even a Docker environment.

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

Configure VMs

Configuring VMs in public cloud is similar to private cloud.

Edit VM general information in public cloud

Do NOT change the Abiquo tag on the Amazon Instance

Do not change the Abiquo platform's tag on an Amazon instance in Amazon or you will break the link between Abiquo and the VM. If the link is broken, you will not be able to manage the VM with Abiquo.

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

Edit Public Cloud Network Configuration

You can edit the network configuration of an AWS machine if it is:

  • Saved but not deployed
  • Deployed and powered off

Click on the Network tab to edit the network configuration.

Do Not Rename the Amazon Instance

Do not change the virtualmachine tag of an AWS instance in AWS or you will break the link between Abiquo and the VM. If the link is broken, you will not be able to manage the VM with Abiquo. 

Add an Elastic IP as a Floating Public IP
  • Your AWS account will have a limit for Elastic IPs independent of any Abiquo public IP limit for your virtual datacenter
  • Add the Elastic IP to the virtual datacenter before you add it to a VM
  • You can only add ONE Elastic IP to each VM in Abiquo
  • You cannot move the Elastic IP to another VM

To add a floating public IP to your VM:

  • First obtain the floating public IP for your virtual datacenter from the public cloud provider
  • Edit the VM configuration
  • Select the Network tab
  • Select the Public page
    • you will see the IPs that are already allocated to your enterprise in the virtual datacenter. You can select from these IPs.
  • Drag and drop the IP address into the network interfaces list
  • AWS charges for Elastic IPs that are allocated but NOT USED by running VMs, so:
    • Deploy or power on your VM as soon as possible after adding an Elastic IP
    • When you undeploy your VM, remember to remove the Elastic IP from your VM and remove it from your VDC
  • Elastic IPs are counted in your Abiquo Public IP limits

A floating public IP should be displayed as shown in the following screenshot.  The floating IP is not part of any Abiquo VLAN.



Remove a Floating IP

To remove a floating IP from your VM, power off or undeploy the VM and click the X button near the IP address.

The floating IP will still be assigned to your virtual datacenter.

Your public cloud provider may charge for a public IP that is assigned to a virtual datacenter but not in use.

When you undeploy the VM, remember to remove the floating IP after you undeploy the VM because AWS charges for floating IPs that are not in use.

To ensure that your public cloud provider does not charge you for the floating public IP, remove it from your virtual datacenter. The floating public IP will be released and you cannot add it to another machine. When you add another floating IP to your virtual datacenter and VM, there is no guarantee that it will have the same IP address.

Bootstrap Scripts

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

Assign Firewalls to VMs

If firewalls are offered in your datacenter and firewalls have been created in your virtual datacenter, then you can assign firewalls to your VMs.

Privilege: Assign firewall

To assign a firewall from the virtual datacenter to a VM, edit the VM and open the Firewalls tab. Mark the firewall with a tick in the Firewall policies checklist. You can add as many firewall policies as necessary, up the public cloud provider's limit. See http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_SecurityGroups.html#VPCSecurityGroups

Click Save.

Remove a firewall from a VM

Privilege: Assign firewall

To remove a firewall from a VM, edit the VM and open the Firewalls tab. Remove the tick beside the firewall in the Firewall policies checklist. Click Save. 

Configure Chef Recipes and Roles

Chef is an infrastructure automation product that uses configuration recipes. You can use Abiquo Chef Integration to deploy a VM that will then configure itself using Chef recipes and roles. 

The Chef tab is enabled if the enterprise is Chef-enabled and the VM template is Chef-enabled. Before the VM is deployed, you can select from the available roles and recipes. These will be added to the machine's runlist. When the machine is deployed it will download the roles and recipes, and run them in order. Click the Chef tab. By default on this tab you can select roles. Mark the "Select individual components" checkbox to select individual recipes too. The selected recipes will be added to the Virtual Appliance's runlist in order of selection.

To change the order of the runlist, click on the pencil button beside a role or recipe, then edit the order number, then click OK.

Change the Order of Roles and Recipes After Deployment

To change the runlist order after deployment click on the pencil button, then edit the order number, then click OK. The Abiquo Chef Agent will connect to the Chef Server and update the runlist.

See also Configuring and Using Abiquo Chef Integration in the Abiquo HOWTOs and Troubleshooting Abiquo Chef Integration in the Administrator's Guide.

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

Configure Monitoring and Metrics

If you have the privilege to Manage VM monitoring and it is configured in your virtual datacenter, you can enable the option to fetch metrics from the hypervisor or public cloud region.

To enable VM monitoring and metrics, work with a VM that is powered off or undeployed.

Edit the VM and go to the Monitoring tab.

Mark the fetch metrics checkbox.

Select from the available options, f or example, for AWS, you can select detailed or basic monitoring.

The functionality and list of available metrics depend on the underlying virtualization technology.

Select the individual metrics you would like to retrieve for your VM.

Display Metrics for a VM

On the VM icon, click the Monitoring symbol to display the metrics. 

The metrics panel will open.

Select the refresh button to update the display of a metric.

Select the filter button to configure the display of the metric.

Set the

  • Granularity, which is how often the metric is sampled
  • Statistic, which determines how the raw values will be processed over time
  • "Last" period, which is how long the display will look behind at the processed data.

Click Accept to save the values.

To view the exact metric values in a call-out box, mouse over the monitoring graph line.

To create a highlight point, click on the metric graph line.

To simultaneously view the data for more than one VM, use the virtual appliance monitoring view.

  • No labels