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

See Microsoft Azure Integration for full details of the integration.

Changes to the Azure Integration in Abiquo 3.6.1

New feature

Abiquo 3.6.1 introduces support for Azure Virtual Networks (see https://azure.microsoft.com/en-us/documentation/articles/virtual-networks-overview/ ). Private cloud service networks created with Abiquo 3.6 will be migrated to virtual network subnets during the upgrade.

In Microsoft Azure many different cloud services (virtual datacenters) can have IPs in the same virtual network. Azure manages subnets of these virtual networks and each cloud service can access multiple subnets in a single virtual network. Azure virtual networks are represented in Abiquo as a new network type called a global network. To start with, global networks are only supported in Azure. Abiquo creates a DNS in the Azure account with the global network DNS configuration defined in Abiquo and assigns it to the virtual network. Abiquo removes the DNS configuration when the Azure virtual network is deleted.

Creating a Virtual Datacenter in Azure

When the user is creating a virtual datacenter, and they select an Azure location, the Custom private network button changes to Custom external network.

Create a custom external network

Abiquo external networks can have private address spaces and be shared across one tenant's virtual datacenters. When the user creates a custom external network in Abiquo, they can select an existing global network, which Abiquo will extend if necessary to include the subnet.


If the user does not specify a subnet, Abiquo will create a new global network, based on the address space entered by the user or the default address space.

When Abiquo deploys a machine that does not have an IP assigned, it assigns a private IP in the automatically created default network. In Microsoft Azure, the default network will be an Abiquo external network that is part of a global virtual network.

Create or Edit an Azure External Network

To create new external networks there is a form similar one used when creating a custom network for a new virtual datacenter. As with other virtual datacenter networks, the user can edit a network to change the name and set it as the default network.


Changes to the Azure Integration in Abiquo 3.6

Azure Instances

Abiquo 3.6 introduces the Abiquo instance feature for Azure, which performs Azure snapshots. You can create an Abiquo instance of a virtual machine deployed in Azure and this copy of the machine’s system disk will be stored on Azure storage and made available with the other virtual machine templates in the Abiquo Apps library. As in AWS, the Azure snapshots are not linked to the original virtual machine template.

When creating an instance, the Azure plugin will:

  1. Create a snapshot of the VM primary VHD disk

  2. Create a new blob from the snapshot in user's Azure storage account

  3. Create a new template with this blob

  • Abiquo instance templates will be named in this format: INSTANCE_NAME_IN_ABIQUO + '_abqinstance_' + AZURE_TEMPLATE_ORIGINAL_NAME

    • For example:  1b7e3d60-68cb-486c-af9b-1e1e783a6397-snapshot-2b171e93f07c4903bcad35bda10acf22-abqinstance-CoreOS-Stable-494.3.0

The limitations of the Azure instance feature are:

  • Abiquo only uses storage accounts with a "locally redundant" configuration (Azure plugin currently existing limitation)

  • Azure plugin is not multidisk enabled so snapshot will only manage one disk (Azure plugin currently existing limitation)

Existing Azure Templates

Existing Azure templates in user's subscription (in the old portal under "My Images") are now returned by the image search and available for deploy (previously only public templates were available).

New Azure Regions

The newest Azure regions are now supported including:

  • Japan East

  • Brazil South

  • Australia East

  • Australia Southeast

Azure VM responsiveness

Abiquo 3.6 has optimized performance when accessing virtual machines in Azure for on, off, refresh and reconfigure operations. These operations are now registered much more rapidly by the virtual system monitor.

Onboard Virtual Datacenters

The onboard feature is the public cloud counterpart to the Abiquo capture feature in private datacenters. It enables users to bring the building blocks of an existing public cloud environment under Abiquo management and to update the Abiquo platform with any changes that may have occurred outside the platform. Initially, this feature works at the virtual datacenter level and it supports AWS virtual private clouds and Azure cloud services.

Azure networking prior to version 3.6.1 

 

Azure networking in 3.6.1 and above