...
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 AWS integration#HowAbiquoCreatesaVirtualPrivateCloud
...
Expand | ||
---|---|---|
| ||
To create a virtual datacenter:
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. |
...
Expand | ||
---|---|---|
| ||
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.
Expand | ||
---|---|---|
| ||
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.
...
Expand | ||
---|---|---|
| ||
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.
Expand | ||
---|---|---|
| ||
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 |
...
Expand | ||
---|---|---|
| ||
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. |
Panel |
---|
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:
A VDC offers the classical data center infrastructure as a service, so users can run their applications more economically and with greater flexibility. |
...