This page describes specific networking for public cloud networks that differs from general virtual datacenter networking. For an overview and for a guide to the general features of virtual datacenter networking, see Manage Networks
This feature onboards network elements that were previously created outside Abiquo in public cloud providers. Synchronize private networks is available in:
You can synchronize the following elements:
To import any networks created previously in the cloud provider, click the synchronize element button All networks that were previously created in the cloud provider will be onboarded. From Abiquo 4.0.2, this includes IP addresses that do not belong to virtual machines.above the Networks list.
When you onboard virtual datacenters, the synchronize virtual datacenters feature will automatically onboard the networks that belong to the virtual datacenters selected for synchronization.
The network name will be the cloud provider network ID.
When working in Abiquo, DO NOT DELETE networks directly in the provider because this may cause inconsistency. The synchronization process is designed to onboard public cloud elements, especially when you begin to work with a public cloud provider.
In AWS, the private network will always be a VPC Subnet (Virtual Private Connect network), with a name in the format vpc-XXXXXXXX:subnet-XXXXXXXXXX. In AWS, these networks will be virtual private connect networks that can belong to the different availability zones in the VPC. You can assign an IP address in a subnet to deploy in its availability zone. These public IPs are Elastic IPs in AWS. Abiquo will manage them as public IPs but they are floating IPs that are not attached to any Abiquo network.
Amazon may charge for Elastic 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 virtual machines.
This section describes features of private networking in the Abiquo AWS integration.
AWS Availability Zones are a high availability feature that enable users to control whether virtual machines will deploy together or separately. When you create custom private networks in the Abiquo virtual datacenter, you can choose which Availability Zone your network will be assigned to. Then you can choose to deploy in a specific Availability Zone by assigning a private IP address in the private network belonging to that Availability Zone.
When you create a VDC, Abiquo creates a VPC with a private network (VPC subnet) and AWS automatically allocates an Availability Zone.
To find out which Availability Zone a network belongs to, select the network and look in the network details box at the bottom of the Networks page.
When you create a private network, you can select an Availability Zone or select No preference and Abiquo will automatically choose an Availability Zone for you.
When you assign a load balancer to a private subnet, AWS will assign it one of the available IP addresses. If you try to assign this address to a virtual machine, an error will occur and the platform will create an event message that the IP address is in use.
Manage public IPs in public cloud
Floating public IP addresses are available in many cloud providers, including AWS and Azure.
To onboard any public IP addresses that were already created in your cloud provider, click the Synchronize public IPs button.
To remove the public IP address, first remove it from the virtual machine. Then to remove the public IP address from the VDC, click the Remove from VDC link near the IP address. The IP address will move to the panel on the right. Select the IP address in the list and click the delete button.
When you create a hybrid cloud with Abiquo you can connect the virtual machines in your Abiquo datacenters and public cloud regions in different ways.
Abiquo now creates a virtual private cloud with NAT support, so your private networks will have access an Internet gateway that will provide NAT services to the virtual machines in the public cloud region. And you can establish a VPN connection between your private and public datacenters.
Machines within the Abiquo virtual datacenter in an AWS VPC have Internet access through the NAT gateway.
Abiquo supports AWS Elastic IPs, which are floating public IP addresses. Therefore you can access virtual machines in a public cloud region through a floating public IP assigned to one of the machines in this datacenter. From there, you can access the other machines on the VPC private subnet (Private Connect Network).
For Microsoft documentation about Azure Virtual Networks, see https://azure.microsoft.com/en-us/documentation/articles/virtual-networks-overview/
Abiquo defines a virtual datacenter in Microsoft Azure ARM by a virtual network. Azure manages subnets of these virtual networks and each virtual datacenter can access multiple subnets in a single virtual network.
There is an example of a hybrid cloud networking environment described in the Microsoft Azure documentation. See https://azure.microsoft.com/en-us/documentation/articles/virtual-networks-setup-hybrid-cloud-environment-testing/
To create this test environment in Abiquo, first configure your local subnet following the Azure instructions. Also create the virtual network to extend your local network in Azure. Then using Abiquo, you can easily specify and create the Abiquo virtual datacenter with a subnet of the Azure virtual network. Then you can configure the site-to-site VPN connection following the Azure instructions. And use Abiquo to deploy the virtual machine that will be the second domain controller.
Abiquo creates virtual datacenters and virtual networks in Azure ARM.
In Azure ARM, the Abiquo virtual machine always has a public IP.