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
To create a virtual datacenter:
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.
To define allocation limits for a VDC
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 a virtual appliance:
The platform will create a virtual appliance for the enterprise and users can create and deploy VMs within it.
To create new VMs, the cloud user simply clicks the Create virtual machine button and selects 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.
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.
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, and VMware with NSX. Abiquo has a consistent interface for load balancers that incorporates different provider functionality.
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.