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.


Abiquo 4.6

Skip to end of metadata
Go to start of metadata

Previous page: Infrastructure

Next page: Apps Library


Abiquo users will consume their cloud resources and provision new virtual environments in the virtual datacenters (VDCs) that belong to their tenant. Each VDC is a separate cloud environment in a datacenter or public cloud region.  

VDCs provide an abstraction layer so the cloud user is removed as far as possible from the physical infrastructure. So the cloud user does not need to be concerned about the underlying technology and can simply receive the service that is defined in their Service Level Agreement.

For each tenant, you can create multiple VDCs, but each VDC uses only one hypervisor or provider, to ensure consistency in the VDC.
 
To create different tiers of service or different SLAs for private cloud users, you can create VDCs with different physical infrastructure and hypervisors. For example, a development environment might be suitable for running on cheap commodity hardware with a free hypervisor such as KVM, whereas a production application may need to run on VMware if it requires other more advanced features offered by these hypervisors.

In public cloud, Abiquo works with "VDC-like" entities such as Amazon VPCs, Azure virtual networks, and vCloud Director vApps,  For example, see AWS Integration#HowAbiquoCreatesaVirtualPrivateCloud

 Click here to show/hide the task: Create a virtual datacenter

To create a virtual datacenter:

  1. Login as the Cloud Admin.
  2. Open "Virtual datacenters" view
  3. Click on the + icon in the "Virtual Datacenters" pane
  4. Fill in necessary info, select Datacenter, and Hypervisor type. Specify the virtual datacenter's name, select the physical datacenter where its applications will be deployed and if there is more than one hypervisor type, select the hypervisor you want to use. Please note that the hypervisor depends on the physical datacenter configuration, so select the physical datacenter first.
  5. Click "Save". A virtual datacenter for the enterprise will be available for virtual appliances to be created and deployed within.

Note: To create a virtual datacenter for another cloud tenant, you will need to switch to that tenant first in Home view or Users view.

Admins can define allocation limits to restrict resources available to cloud users in the VDC. These allocation limits complement the limits set by cloud operators for the tenant. When users reach the soft limit, the platform can display a warning message. When users reach the hard limit, the platform will block their action.

 Click here to show/hide the task: Set allocation limits for the virtual datacenter

To define allocation limits for a VDC

  1. Select the virtual datacenter and edit. 
  2. Select the Allocation Rules tab
  3. To allow your users unlimited resources, set the limits to 0.
    Note that you cannot have a hard limit only, and that soft limits must always be less than or equal to hard limits.

Within the VDC, cloud users can take advantage of self service. With the appropriate privileges, for example, they can create their own networking configuration and storage. Users create their applications within Virtual Appliances (VApps). VApps are like folders where cloud users can create groups of VMs using the templates from the Apps Library.

To create new VMs, the cloud user simply double-clicks or drags and drops the required templates. 


The cloud user then configures that VM to meet their needs. For example, configuring CPU and memory, and adding additional network interfaces or storage. If the tenant has a Chef server configured, the user can also select Chef recipes to automatically configure the VMs at deployment time.
 
When the configuration is complete, the cloud user deploys, which launches the VMs to the hypervisor. The platform copies the VM disks and configuration from the Apps Library (NFS storage within the datacenter) to a hypervisor datastore.
 
Once deployed, the cloud user is able to Start/Stop/Reset individual VMs through the Abiquo UI. They can also launch a console onto the VM and perform any other configuration or administration tasks that may be required for their application.

In public cloud, you can onboard virtual datacenters and their virtual resources.

 Click here to show/hide the task: Onboard from public cloud
  1. Go to Virtual datacenters view. Click the plus button and select synchronize from public cloud from the dropdown menu.
  2. Select the public cloud region.
    Select a public cloud region to synchronize
  3. Select the virtual datacenter to synchronize from the list.
    Select a virtual datacenter entity to synchronize from the cloud provider
  4. Abiquo will import this virtual infrastructure from the provider. Note that Abiquo will detect network configuration but it will not enforce a standard configuration.

Imported virtual infrastructure is now managed by Abiquo and is available to virtual datacenter users. Changes made directly in the provider can be updated in Abiquo by clicking the synchronize button beside the virtual datacenter name in the VDC list.

Abiquo users can create firewalls (security groups) or classic firewalls in public cloud providers that support them, such as AWS, Azure, and vCloud Director, as well as in private cloud with VMware and NSX or Neutron and KVM or OpenStack.

 Click here to show/hide the task: Create firewall policies in AWS


  1. Go to Virtual datacenters → Select virtual datacenter → Network → Load balancers
  2. Select the location or the virtual datacenter and click the double-arrow synchronize button in the top right-hand corner of the page
  3. Click the + button and enter firewall general information
    Create a firewall policy
  4. Click the synchronize button to synchronize firewall rules. You will probably see a default rule to allow all outbound traffic.
  5. Click the pencil edit button to edit firewall rules. Enter firewall rules, for example, to allow SSH

Firewall policies are created for the virtual datacenter. As always, check your provider documentation for specific information about security group functionality. See Manage Firewalls.

Note: cloud users will require appropriate privileges to use firewalls

Abiquo users can create load balancers in public cloud providers that support them, such as AWS, ARM, vCloud, Rackspace, VMware with NSX, or OpenStack with Abiquo OpenStack Neutron integration. Abiquo has a consistent interface for load balancers that incorporates different provider functionality. 

 Click here to show/hide the task: Create a load balancer
  1. Select the location or the virtual datacenter and synchronize (or synchronize the individual elements: firewalls (where applicable) and load balancers).
  2. Click the + button and enter load balancer general information
    Create a load balancer entering general information
  3. Create routing rules
    Create a load balancer entering a routing rule
  4. Enter a health check if required - AWS will automatically create one if you do not enter one
  5. Assign a firewall if required - Rackspace will automatically allow traffic to the appropriate load balancer ports
    Create a load balancer entering a health check
  6. Assign nodes
    Create a load balancer assigning nodes
  7. Click Save

A load balancer is created. As always, check you provider documentation for pricing and functionality. For more information about load balancers in Abiquo, see Manage Load Balancers.

Note: cloud users will require appropriate privileges to use load balancers.

 

A virtual datacenter provides an abstraction of the same resources as a physical datacenter (such as compute, network infrastructure, storage, backup, security, etc) with the added advantages of cloud computing:

  • Virtualization
  • Pay-as-you-go billing
  • Quick scalability
  • Technology and hardware abstraction.

A VDC offers the classical data center infrastructure as a service, so users can run their applications more economically and with greater flexibility.