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

In Abiquo, a virtual datacenter is a collection of virtual resources, including compute, network and storage resources. By default, the tenant administrator can manage virtual datacenters and their resources for the tenant's users on a self-service basis. This means that, for example, the tenant administrator can create private networks, obtain public IP addresses for users to attach VMs to public networks, and in private cloud, the tenant administrator can create storage volumes. 

If you have the privilege to manage virtual datacenters, at the top of virtual datacenters list on the left-hand side near the top of the screen, you will see the following buttons.

Button Action
Create a new virtual datacenter
Remove an existing virtual datacenter
Edit the selected virtual datacenter

Create a virtual datacenter

API Documentation

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

To create a new virtual datacenter, click the  button and select Create a new virtual datacenter from the pull-down menu.

General information

Complete the form:

Field

Description

Name

The name of the virtual datacenter

Location

The datacenter or public cloud region where virtual appliances will be deployed

Hypervisor

The type of the hypervisor for the virtual datacenter. This option will not display if there is only one choice.

Network

  • Default: Create a VLAN (default private or external) in the pre-configured range
  • Custom Private: Create a custom private VLAN (see form below)

Virtual datacenter networks

Abiquo offers several types of virtual datacenter networks that are described in the following table. Networks that are available in a location type are marked with a green checkmark  (tick) .

Network typeDescriptionControlDatacentersPublic cloud regions
PublicInternet addressable public IP addressesInfrastructure(tick)(tick) floating public IPs
ExternalAssigned to an enterprise and can be accessed by more than one virtual datacenterInfrastructure(tick) 
UnmanagedReceive their IP addresses outside of AbiquoInfrastructure(tick) 
PrivateHave private IP addresses and are restricted to a single virtual datacenterVirtual datacenter(tick)(tick)
VDC networks in datacenters

When you create a virtual datacenter, a private network is always created and counted as part of your VLAN allocation limits. This private network can be the automatically-created private VLAN, named "default_network", or a custom private network.

If an external or unmanaged network is set as the default network for your enterprise in a datacenter, then this network will be set as the default network for your virtual datacenter, instead of the private network.

After you create a virtual datacenter, you can change the default network by editing the network and selecting the Default network option; see Manage Networks. You can set any type of network as the new default network, including a public network, if you have IP addresses reserved for the virtual datacenter.

VDC networks in public cloud regions

In a public cloud region, the default network is always a private network. When you create a virtual datacenter, you can choose the default private network or a custom private network configuration. This network is a Virtual Private Connect network in AWS EC2, named vpc-XXXXXXXX:subnet-XXXXXXXXXX.

For a virtual datacenter in a public cloud region, the enterprise default external or unmanaged network will not be used.

You can add floating public IPs to your virtual machines and Abiquo will manage these IPs although they will not belong to any Abiquo network. Floating public IPs will be counted as part of your public IP allocation limits.

Create a virtual datacenter with a custom private network

Select the Custom option in Private Network configuration and complete the network section of this form.

Field

Description

DCPCR

Network name

The name of the VLAN to create

(tick)(tick)
NetmaskThe network mask(tick)(tick)

Network address

The network address

(tick)(tick)

Gateway

The IP of the gateway of the VLAN

(tick)(tick)
Availability zoneThe availability zone where VMs attached to this network will deploy(error)(tick)

Primary DNS

The primary DNS of the network

(tick)(tick)

Secondary DNS

The secondary DNS of the VLAN

(tick)(tick)

DNS suffix

The DNS suffix for the VLAN

(tick)(tick)
Static routesMark the checkbox to define static routes(tick)(tick)

You can manage the VLANs of your virtual datacenter in the Network tab; See Manage Networks.

Manage resource allocation limits for a virtual datacenter

The allocation limits tab allows the administrator to limit the amount of physical and virtual resources a virtual datacenter may consume. This is very useful in preventing common problems on cloud platforms, including resource over allocation, virtual datacenters allocating resources from other virtual datacenters, and DoS attacks. Allocation limits also help system administrators to anticipate user needs and to forecast resource demands.

  The cloud administrator can set the allocation limits for enterprises and then the enterprise administrator can set allocation limits for virtual datacenters.

Hard and soft limits
  • Hard Limit: The maximum amount of virtual resources (RAM, virtual CPU, local hard disk, external storage, VLANs and public IPs) that a virtual datacenter will be allowed to consume.
  • Soft Limit: The main purpose of the soft limit is to alert users and administrators that the virtual datacenter is running out of resources. When a virtual datacenter reaches the soft limit, Abiquo will display a warning that they are reaching the resource allocation limits for their virtual datacenter.

To manage the virtual datacenter allocation limits, click the Allocation Limits tab when creating your virtual datacenter and you will see the allocation limits panel.

Enter the allocation limits according to the rules in the following table.
Limit CaseValiditySoft LimitsHard LimitsNotes
No limits(tick)00If soft limit and hard limit are both zero, there will be no limits at this level
Soft limit only(tick)> 00If soft limit is greater than zero and hard limit is equal to zero, there will a soft limit but no hard limit
Hard and soft limit(tick)> 0> soft limitIf soft limit is greater than zero, hard limit must be greater than or equal to soft limit
Hard limit only(error)0> 0You cannot have a hard limit only. If soft limit is zero, hard limit must also be zero (no limits)
Soft limit greater than hard limit(error)> 0 and > hard limit> 0You cannot have a soft limit that is greater than the hard limit. Hard limit must be greater than or equal to soft limit (or no limits)
Limits greater than resources already allocated(tick)< hard limit OR no limits> allocated
resources OR no limits
Hard limit must be greater than resources that are already allocated (or no limits)

Allocation limits apply as soon as they are set.

Set virtual datacenter defaults

Field

Description

Default datastore tier

Select the default disk service level for your non-persistent virtual machine disks on the hypervisor. This is the default datastore tier for the virtual datacenter.

  • To use your cloud provider's default tier, select "Configured by location"
  • Or select a default tier, according to the available service levels

To clear the current tier, click the black x symbol beside the tier name

Enter allocation limits and save the virtual datacenter.

Abiquo will create the virtual datacenter and the default private VLAN and display it in the Virtual Datacenters View

Resource limit messages

This section describes the messages that users will receive when they reach the soft or hard limits in their virtual datacenter. The following screenshot shows some soft and hard limits for a very small virtual datacenter. As you can see, the soft limit is just one virtual CPU and the hard limit is 4 virtual CPUs.

 

Hard and Soft Limits

  • Remember that soft limits must always be less than or equal to hard limits.
  • Limits equal to 0 means that there is no limit to resource usage at this level.

 

Soft limit messages

If you try to deploy a virtual appliance with more than one CPU in the example virtual datacenter, the soft limits will be exceeded. You will see a pop-up that will allow you to to acknowledge the message and continue with the operation.

There are two types of soft limit messages, depending on the soft limit details message option on the General page of Configuration View

If the soft limit details message option is selected on the General page of Configuration View, you will see this type of message.

If the soft limit details option is not selected, you will see a general message.

It is also possible to receive this message when enterprise soft limits have been reached or exceeded but virtual datacenter soft limits have not.

Hard limit messages

If you try to deploy a virtual appliance with more than four CPUs in this virtual datacenter, then the hard limits will be exceeded. You will see a pop-up that will allow you to to acknowledge the message and terminate the operation.

There are two types of hard limit messages, depending on the hard limit details message option on the General page of Configuration View

If the hard limit details message option is selected on the General page of Configuration View, you will see this type of message.

If the soft limit details option is not selected, you will see a general message.

It is also possible to receive this message when enterprise hard limits have been exceeded but virtual datacenter hard limits have not been exceeded.

Onboard virtual datacenters from public cloud

The privilege required for onboarding a VDC is the same one as for managing virtual datacenters. 

The only requirements for onboarding a VDC are that:

  • the public cloud region that the user will be importing from has been created
  • the enterprise has registered credentials for the public cloud provider

Synchronization limitations

  • AWS
    • Virtual machines in EC2 Classic can be viewed but not onboarded
  • Azure
    • Abiquo CANNOT deploy a VM with an IP in a region. You MUST use IPs in a subnet (as configured in Abiquo v3.6 with the Cloud Service network subnet and in Abiquo v3.6.1 with an Abiquo external network which is an Azure Virtual Network subnet)
    • Abiquo will NOT synchronize VMs with IPs in a region. Abiquo can view them but cannot manage them, because an IP in a region cannot be onboarded.
    • Known issue in Azure during synchronization to be fixed in Abiquo 3.6.2
      Abiquo does not retrieve IPs assigned to virtual machines that were created in Azure and are powered OFF. The workaround for this issue is to power ON the virtual machine in Abiquo, so Abiquo will retrieve the NIC, then power OFF the VM. After this power ON/OFF, the NIC will be correctly registered in Abiquo and Azure.

Abiquo API Feature

This feature is available in the Abiquo API. See VirtualDatacenterResource for synchronization and LocationsResource for retrieval of virtual datacenters and virtual machines.

To onboard a virtual datacenter from the public cloud, click the  button and select Synchronize public cloud from the pull-down menu. 

A dialog opens with a list of public cloud regions. Select one of these regions. The user's enterprise must be allowed to use the region, and they must have entered valid credentials for public cloud provider in Abiquo.

 

Abiquo will display a drop-down list of entities in the public cloud region. These can be either AWS virtual private clouds or Azure cloud services.

Select an entity and click the Synchronize button and Abiquo will load all of the elements into a virtual datacenter. 

If you delete a synchronized VPC, Abiquo will delete it in the provider

For example, from AWS, Abiquo will import elements such as the VPC, subnet, firewalls and load balancers. All of these new elements will also be named with their provider identifiers. You can later return to this dialog and onboard more virtual datacenters using the same process.

In view classic VMS, for example in AWS these are EC2 classic VMs, click the "See classic" link. These virtual machines cannot be managed by Abiquo.

After you click Synchronize, Abiquo displays a progress screen.

When the onboarding process is complete, virtual machines within the virtual datacenter will now be managed by Abiquo. Their templates will be imported too.

In Abiquo 3.8.1+, if the virtual machine template cannot be found, a warning message will display. The virtual machine will be created in Abiquo with no template. If you click the undeploy button, a warning message will display. To save a copy of your virtual machine disk as a template, create an Abiquo instance of the virtual machine.

Network elements will also be loaded, for example, private IP addresses.

Synchronize an Onboarded VDC

To update an onboarded virtual datacenter and synchronize any changes made outside of the Abiquo platform, the user can go to the V. Datacenters list and click the Refresh button beside a virtual datacenter name.

 

Synchronize VDC Elements

Currently when working with public cloud networking, it is important to maintain each Abiquo element synchronized with the public cloud. For example, in AWS, before creating a firewall, users must load any existing AWS firewalls using the Synchronize firewalls button. 

Existing synchronize functionality has been maintained for public IPs, firewalls and load balancers.

A new synchronize functionality has been added for private networks. See Manage Networks

 

Multiple concurrent synchronizations

Contact Abiquo Support for more information about tuning public cloud region synchronization properties that were added in Abiquo 3.6.1.

  1. abiquo.pcrsync.retrydelayms
  2. abiquo.pcrsyncpool