The Abiquo Amazon EC2 integration is a hybrid cloud feature that enables our customers to add Amazon public cloud regions to the Abiquo platform as part of our agnostic public cloud management. With the Abiquo hybrid cloud platform you will be able to offer a service that is a federation of Abiquo private clouds and the public cloud. Cloud tenants can deploy virtual resources in public cloud regions or in Abiquo datacenters through the same award-winning user interface. You can control the use of public cloud resources in the same way as in the Abiquo Datacenter (quotas, limits, etc).
Amazon Regions are added as Abiquo public cloud regions. Abiquo manages public cloud regions using a set of the Abiquo Remote Services. The remote services used in a public cloud region can be shared with other datacenters or public cloud regions. No NFS repository is required to use with a public cloud region.
Each Abiquo public cloud region corresponds to a single Region in Amazon EC2. Each Abiquo enterprise using the Amazon public cloud region should have its own Amazon account. Abiquo will validate your Amazon credentials (Access Key ID and Secret Access Key) with AWS. Each enterprise may register ONE set of credentials for the enterprise's AWS account.
When users create a virtual datacenter in the public cloud region, Abiquo works with Amazon EC2. Abiquo creates a Virtual Private Cloud (VPC) for each Abiquo virtual datacenter. By default, for each Amazon VPC, Abiquo creates a public subnet and a private subnet, which is a private connect network. The private subnet has an Internet gateway and access to the VPC from outside the cloud is through NAT or Elastic IPs via the public subnet. Elastic IPs are registered in Abiquo as floating IPs. Floating IPs are managed like public IPs but they do not belong to any Abiquo network. Within your virtual datacenter, you can create more Abiquo private networks (subnets in your VPC), which will enable you to deploy to different Availability Zones. The private subnets in the same availability zone as the public subnet will have internet access through the public subnet.
VMs deployed in the VPC virtual datacenter are Amazon Instances. Add your public key to your Abiquo user before you deploy a VM. Your Amazon instance will be created using your RSA public key to enable remote access. You will need the corresponding RSA private key to access the instance.
Manage Amazon Instances with Abiquo
Do not rename an Amazon 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 again. Do not delete the tags created by Abiquo.If you need to manage your Abiquo Elastic IPs in Amazon, synchronize them to update changes in Abiquo or you may see unexpected results.
In the AWS integration, Abiquo creates VPCs with NAT support with a public subnet, and allows VMs on different subnets to be connected to the same load balancer. Abiquo supports the AWS gateway address as the first address in the network.
Abiquo configures VPC networking Scenario 2 as described in the AWS documentation http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Scenario2.html.
Under this configuration, users must attach Elastic IPs to VMs with a connection to the public subnet. And by default, VMs in private networks will have internet access through the public subnet. This is helpful for automation because a VM can now connect to the internet to download its configuration, for example, using Chef, without an Elastic IP.
When you create an Abiquo virtual datacenter in an AWS public datacenter, Abiquo creates a VPC of size /16 and a subnet of size /24 (or as defined by the user). The default CIDR for the VPC and the subnet is 192.168.0.0, which is the default private network in Abiquo. You can set a custom private network in Abiquo and this network will be used to create the VPC and subnet in Abiquo. You can create multiple Abiquo private networks in different availability zones in the same VPC.
AWS reserves five IP addresses in your private networks. It reserves the first four IP addresses and the last IP address of the VPC private connect network. These IP addresses are not displayed or used by Abiquo. Therefore the first available IP address in a network that is defined to start with address 0, will be address 5, and the gateway address will be address 1.
For example, in the default_private_network with network address 192.168.0.0, the following addresses would be reserved or used as the gateway.
|192.168.0.1||Reserved by AWS, default gateway address|
|192.168.0.2||Reserved by AWS|
|192.168.0.3||Reserved by AWS|
|192.168.0.4||Reserved by AWS|
|192.168.0.254||Reserved by AWS|
Abiquo creates a route table that is equivalent to the AWS route table with the values of the Abiquo private network. You can use the AWS NAT instance for Internet access from the Abiquo virtual datacenter private network. You can acquire floating public IPs for your virtual datacenter and in AWS, these will be created as Elastic IPs with public network addresses. Note that AWS may charge for Elastic IPs when they are NOT in use, i.e. when they are not assigned to a VM or when the VM is not deployed in AWS. You must assign the Elastic IPs to VMs with connections to the Public subnet. When creating a NAT gateway, Abiquo will reuse floating IPs that are not assigned to a VDC.
By default Abiquo assigns instances to the default VPC security group. This means that by default, all outbound traffic from instances is allowed. Enterprise administrators should configure an Abiquo firewall. Abiquo will create an AWS Security group in the VPC when this firewall is assigned to a virtual datacenter. Users can synchronize their firewalls with AWS, which will import existing security groups. The most basic configuration is to allow SSH inbound traffic, for example, port 22, which will allow SSH connections to the machine through a public IP, NAT, or from a private IP within the virtual datacenter. See AWS Security Groups as Abiquo Firewalls.
Abiquo supports multiple IP addresses in the AWS integration. You can synchronize existing VMs with multiple IP addresses and create multiple IP addresses through Abiquo, including multiple Elastic IPs.
Abiquo supports the number of IP addresses supported by the AWS hardware profile (instance type). See http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html#AvailableIpPerENI
If the user adds multiple IPs in the same subnet, Abiquo adds them to the same elastic network interface. And if the IPs are in a different subnet, Abiquo adds them to a different elastic network interface. For information about Elastic Network Interfaces, see http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html
Amazon may require separate credentials for groups of regions. For example, for regions in China the user will need separate credentials and they should select the appropriate provider, such as "Amazon (CHINA)".
Configure and remove VMs
When you deploy, you’ll select the hardware profile
Power on VM
Power off VM
Pause and resume VM
Take a VM snapshot
The VM must be powered off in Abiquo, although the actual VM is not powered off.
Using your SSH key registered in Abiquo
Create and delete networks
|Create and delete VPNs||From private cloud (NSX) to AWS|
Create and delete VPCs
Create and manage firewall policies
Enterprise Chef or your own server
Use Chef attributes
VM bootstrap scripts
|VM variables||The variables are stored on the virtual machine filesystem in ~/vm-variables.rc|
Abiquo supports Classic Load Balancers
Import and synchronize
|VM monitoring and metrics||With Abiquo monitoring and metrics server|
|Deploy AMI from AWS marketplace||-||Abiquo cannot deploy an AMI from the AWS marketplace because Abiquo cannot display the EULA to the end user. However, you can deploy in the Amazon cloud native interface and onboard in the platform.|
|Import VM template |
from private cloud datacenter
|Use compatible templates prepared according to provider instructions. See VM Template Mobility|
|Dashboard billing widgets||The Hybrid tab of the Home dashboard view can display public cloud billing information, including the latest bills and estimated bill. See Hybrid and for configuration instructions see Display cloud provider billing data.|
To onboard virtual resources from public cloud:
To onboard a virtual datacenter:
The platform will detect a public subnet by the presence of a custom route table and NAT gateway, and the platform will mark the public subnet with a globe symbol and set the Internet gateway flag for this subnet. Users with bespoke network configurations should check the results of the synchronization. The platform will synchronize private and public IP addresses even if they are not in use by VMs, and mark the IP addresses in use by provider entities with provider identifiers.
The platform will import VM templates. If the VM template cannot be found, the VM will be created in the platform with no registered template. In this case, to save a copy of your VM disk as a template, so you can recreate the VM, make an Abiquo instance of the VM.
If you delete a synchronized VDC, the platform will delete it in the provider. Always check which is the default VDC in your provider, e.g. AWS default VPC, because it may be inconvenient to delete this VPC
If your enterprise does not have valid credentials for the public cloud provider, when you delete public cloud entities in the platform, they will still exist in the public cloud provider
To view classic VMs, for example in AWS these are EC2 classic VMs, click the "See classic" link.
During VDC synchronization, the platform will ensure that the resources in the platform and the provider are the same.
To update a virtual datacenter and onboard any changes made in the provider, synchronize the virtual datacenter:
You can also synchronize resources such as networks, public IPs, firewalls, and load balancers. To do this, go to the resource tab and click the straight double arrow Synchronize button. For more information, see the resource documentation.
Screenshot: Synchronize firewalls
Screenshot: Synchronize private networks in public cloud
Public cloud synchronization parameters
Note to System Administrators: For information about tuning public cloud synchronization, see Abiquo Configuration Properties.
When administrators delete resources in the provider, the platform will display the resource name in light gray to indicate that the user cannot work with the resource. The resource types include:
To delete these resources (if they are not in use), select the resource and click the delete button.
The virtual resources that you onboarded or created in public cloud will be grouped with their associated virtual datacenters.
Before you begin:
To delete onboarded resources in public cloud:
If the enterprise does not have valid credentials for the public cloud provider, when you delete public cloud entities in the platform, they will continue to exist in the public cloud provider
Abiquo API Feature
To configure the load balancer integration:
In AWS, the platform supports load balancers as described in the following table.
Abiquo supports AWS Classic load balancers.
AWS will assign a previously unhealthy machine a healthy status after a number of successful health checks. Check the value configured for the platform with your system administrator.
You cannot change the following attributes in AWS:
|Load balancer Name|
|Abiquo-only load balancers|
|Multiple incoming connections||Use one load balancer with multiple incoming connections to different ports|
|Routing rule protocol in||AWS accepts HTTP, HTTPS, TCP|
|Routing rule port in||AWS accepts 80, 443 and 1024-65535 inclusive|
|SSL certificate||Can be a new certificate or an existing one registered in AWS with an ARN.|
In Amazon, you can work with volumes that are EBS disks.
General information about EBS disks
Delete on termination disks
Instance templates with multiple disks
When you create a VM from an instance template, the platform will display one disk only, with the total size of all disks. After you deploy the VM, the platform will update the additional disks.
Encrypted EBS disks