Table of Contents |
---|
Prepare to onboard from public cloud
Before onboarding virtual resources, administrators must do these steps:
Create the public cloud region to import from
Allow the tenant access to the public cloud region (Enterprise → Datacenters → Allow public cloud region)
Register the tenant's credentials for the public cloud provider (Enterprise → Credentials)
...
Introduction to onboard from public cloud
You can onboard virtual resources from public cloud into the platform. If the cloud provider supports virtual datacentersdatacenter (VDC) entities, such as AWS VPCs or Azure virtual networks, you can onboard them . After you onboard the virtual datacenters, you can synchronize them and the virtual resources. If as VDCs and synchronize them. If the cloud provider does not support virtual datacentersVDCs, then you can onboard the resources from the public cloud regions, such as RackSpace and OpenStack Google Cloud Platform regions.
Panel |
---|
PrivilegePrivileges: Manage virtual datacenters |
Before onboarding virtual resources, administrators must do the following steps:
- Create the public cloud region to import from
- Allow the tenant access to the public cloud region (Enterprise → Datacenters → Allow datacenter)
- Register the tenant's credentials for the public cloud provider (Enterprise → Credentials)
...
...
Onboard virtual datacenters from public cloud
Excerpt | ||
---|---|---|
| ||
To onboard resources from public cloud:
|
Onboard virtual datacenters from public cloud
To onboard a virtual datacenter:
...
For more details see Set a virtual datacenter role to limit user access. The platform will onboard the selected resources for you to manage.
|
...
title | Click here to show/hide the screenshot |
---|
...
|
...
|
...
|
...
|
...
title | Click here to show/hide the screenshot |
---|
...
|
...
View classic VMs
To view display classic VMs , for example in AWS these are EC2 classic VMs, click the "See classic" link.
Expand | ||
---|---|---|
| ||
in public cloud:
Go to Virtual datacenters
Click the + Add button and select Synchronize public cloud
Select the public cloud region
Click the See classic link
...
Synchronize VDCs and resources
During VDC synchronization, the platform will ensure that the resources in the platform and the provider are the same.
- It will delete entities in the platform that were deleted already in the provider
- However, it will maintain resources attached to undeployed VMs in the platform
- For example, if a user has an undeployed VM with IPs and a load balancer, then after the synchronization, these resources are attached to the VM in the platform only
- Warning: These resources are "free" in the provider. Users working directly in the provider could assign these resources to other VMs. This will cause a conflict and error at deploy time
Excerpt | ||
---|---|---|
| ||
To update a virtual datacenter and onboard any changes made in the provider, synchronize the virtual datacenter:
|
...
|
...
To synchronize specific resources such as networks, public IPs, |
...
and so on:
For more information, see the resource documentation. |
...
Expand | ||
---|---|---|
title | Click here to show/hide the screenshotsScreenshot: Synchronize firewallsnetworks Screenshot: Synchronize private networks in public cloud | |
Info | ||
| ||
Note to System Administrators: For information about tuning public cloud synchronization, see Abiquo Configuration Properties. |
...
Manage resources that were deleted directly in the cloud provider
Excerpt | ||
---|---|---|
| ||
When administrators delete resources in the provider, the platform will display the resource name in light gray to indicate that the user cannot work with the resource. The resource types include:
To delete these resources (if they are not in use), select the resource and click the delete button. |
...
title | Click here to show/hide the screenshot |
---|
...
Delete or release virtual resources in public cloud
Excerpt | ||
---|---|---|
| ||
The virtual resources that you onboarded or created in public cloud will be grouped with their associated virtual datacenters. Before you begin:
|
...
To delete onboarded resources in public cloud:
|
...
|
...
Onboard from public cloud using the API
Tip | |
---|---|
title | Abiquo API Feature This feature is available in the Abiquo API. See VirtualDatacentersResource for synchronization and AllowedLocationsResource for retrieval of virtual datacenters and VMs. |
...
Onboard from public cloud regions without
...
If your public cloud provider does not support virtual datacenter entities, Abiquo will automatically onboard when you select the public cloud region.
...
virtual datacenters
The platform onboards and synchronizes virtual resources in public cloud regions for providers that do not use virtual datacenters or similar entities, for example, OpenStack clouds and RackspaceGoogle Cloud Platform. 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 virtual datacenter. Abiquo will check if any new entities in the provider are related to the existing ones in Abiquo and place them in the existing virtual datacenter.Abiquo your public cloud provider does not support virtual datacenter entities, to onboard virtual resources do the following steps:
Go to Virtual datacenters
At the bottom of the V. Datacenters list, click the + add button
Select Synchronize public cloud
Select a public cloud region
The platform will place all VMs and network resources that are not related to existing Abiquo virtual resources into a generic virtual datacenter. Abiquo The platform names this virtual datacenter with the same name as the public cloud region, but the user can rename it. Abiquo The platform will use this virtual datacenter for future synchronizations, adding or removing resources to match the cloud provider.
If the Abiquo there are already virtual resources in the platform for this provider, then these entities will already be part of a virtual datacenter. The platform will check if any new entities in the provider are related to the existing ones in the platform and place them in the existing virtual datacenter.
If the integration with the provider supports entities that are not assigned to any in a virtual datacenter, such as firewalls, load balancers, or floating IPs, these may be loaded into Abiquo as unassigned the platform may load these as separate entities.
If conflicts occur during synchronization, Abiquo the platform will cancel the synchronization. This would could 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 virtual datacenters but are related by a VM.
...
Control onboard of VMs to VApps
Excerpt | ||
---|---|---|
| ||
When you onboard virtual resources from providers without virtual datacenters, by default, the platform will onboard each VM into its own VApp. To onboard all VMs into a single virtual appliance, set the singlevapp enterprise property to true. If you wish to configure the name, set the singlevapp name enterprise property:
For instructions on how to set an enterprise property, see Manage enterprise credentials and properties |