Page Comparison

Each virtual datacenter (VDC) is a separate cloud environment in a datacenter or public cloud region. Abiquo users will consume their cloud resources and provision new virtual environments in the VDCs that belong to their tenant. 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 manage 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 create different tiers of service or different SLAs for private cloud users, you can create VDCs with different hypervisors and cloud providers. For example, you may run a development environment on less expensive hardware with a free hypervisor such as KVM, whereas you may run a production application on VMwareIn private cloud, each VDC is on one Abiquo rack only, because a VDC private network requires a network tag from one rack.

In public cloud, Abiquo works with "VDC-like" entities such as Amazon VPCs, Azure Virtual Networks, and vCloud Director vApps. In clouds that do not have a "VDC-like" entity, such as Google Cloud, Abiquo creates logical VDCs. For example, see https://abiquo.atlassian.net/wiki/spaces/doc/pages/311371413/AWS+integration#How-Abiquo-creates-a-virtual-private-cloud

...

Within the VDC, cloud users can take advantage of self service. For example, they can create their own private networks and storage. Users create their applications within virtual appliances(VApps), which are like folders where cloud users can create groups of VMs using the templates from the catalogue. Administrators can also save virtual appliances to create blueprints (specs), so users can select a blueprint to create a complete configuration.

To create new VMs, the cloud user simply clicks the Create virtual machine button and selects the required templates. 

...