Abiquo 5.1

Skip to end of metadata
Go to start of metadata

Abiquo synchronizes virtual resources in public cloud regions that do use virtual datacenters (VDCs) or similar entities, for example, Generic OpenStack and Rackspace. You can only synchronize these providers at the public cloud region level. You cannot synchronize a VDC or an individual resource, for example, a load balancer. 

If Abiquo already has virtual resources on the platform for the provider, then these entities will already be part of a VDC. Abiquo will check if any new entities in the provider are related to the existing ones in Abiquo and place them in the existing VDCs.

Abiquo will place all VMs and network resources that are not related to existing Abiquo virtual resources into a generic VDC. Abiquo names this VDC with the same name as the public cloud region, but the user can rename it. Abiquo will use this VDC for future synchronizations, adding or removing resources to match the resources in the cloud provider.

If the Abiquo integration with the provider supports entities that are not assigned to any VDC, such as firewalls, load balancers or floating IPs, these may be loaded into Abiquo as unassigned entities.

If conflicts occur during synchronization, Abiquo will cancel the synchronization. This would occur if two VMs already exist in different VDCs but are related by a firewall or load balancer. Or if two firewall policies or load balancers exist in different VDCs but are related by a VM.

To onboard public cloud regions, use the same process as the one to onboard VDCs. See Manage Virtual Datacenters

  • No labels