Abiquo 5.0

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

Introduction

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

 

Synchronize networks

 This feature onboards network elements that were previously created outside Abiquo in public cloud providers. Synchronize networks is available in:

  • AWS: private networks
  • Azure: external networks

Synchronization is available for:

  • Virtual datacenters
    • automatic synchronization of all network elements
  • Private or External networks
  • Public IPs

To import any networks created previously in the cloud provider, click the synchronize element button above the Networks list. All networks that were previously created in the cloud provider will be onboarded.

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.

 

Hybrid cloud networking

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

Azure networks

New feature

For Microsoft documentation about Azure Virtual Networks, see https://azure.microsoft.com/en-us/documentation/articles/virtual-networks-overview/

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.

This section describes networking in the Abiquo Azure integration.

 


Create a virtual datacenter with an external network in Azure

When you create a virtual datacenter in an Azure location, you can create a default external network or a custom external network. The Custom private network button changes to a Custom external network button.

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 select an existing global network, Abiquo will create a new global network. The global network will be of the maximum size, using the subnet address space entered by the user or the default subnet 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.

AWS networks

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.

 

Private networks in AWS

This section describes 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.

The following diagram shows a Virtual Private Cloud with the VPC default subnet and the Abiquo default private network.

When you create the VPC, Abiquo creates a private network (VPC subnet) and AWS automatically allocates an Availability Zone.

 

Network Availability Zones

To find out which Availability Zone a network belongs to, look at the network details box at the bottom of the Networks page. In the screenshot below, the default_private_network is in the "eu-central-1b" Availability Zone. 

Choose an Availability Zone when creating a network

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.

Here we have chosen the "-1a" Availability Zone. This is different to the one that the default_private_network is in. And we have named the network to show that it is in Availability Zone "b". In addition, we have selected the Default network checkbox. This means that for virtual machines with no IP addresses allocated by the user, Abiquo will assign IP addresses on this network.

When you click Save, Abiquo will create the network in your AWS VPC. 

Manage public IPs in public cloud

Add floating public IP addresses to your virtual datacenter

Floating public IP addresses are available in many cloud providers, including AWS and Azure.

  1. Select a virtual datacenter in your public cloud region
  2. Click the add button  in the top right corner of the PUBLIC IPs page
  3. Click an IP address to allocate it to your public cloud region
    • Abiquo will check your location (enterprise-public cloud region) limits for public IPs
  4. To add the public IP to a VDC, click the Add to VDC link near the IP addres
    • Abiquo will check your virtual datacenter limits for public IPs
Synchronize public IP addresses with the cloud provider

To onboard any public IP addresses that were already created in your cloud provider, click the Synchronize public IPs button.

Release a floating public IP address

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.

 

 

  • No labels