Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »

Prepare to onboard from public cloud

Unable to render {include} The included page could not be found.

Introduction to onboard from public cloud

Unable to render {include} The included page could not be found.

Onboard virtual datacenters from public cloud

To onboard resources from public cloud:

  1. Go to myCloud → Virtual datacenters

  2. At the bottom of the V. Datacenters list, click the + add button

  3. Select Synchronize public cloud

  4. On the General information tab, select the region and the other entities to onboard

    1. The virtual datacenter entities are: AWS VPCs, Azure Virtual Private Networks, OCI Virtual Cloud Networks, vCloud vApps

    2. (warning) Google Cloud Platform (GCP) does not use virtual datacenter entities, so the platform onboards and synchronizes regions and all their resources.
      (warning) In GCP You cannot onboard or synchronize individual resources, for example, a public IP. 

      • When you first onboard from GCP, the platform will onboard virtual datacenter resources into a generic virtual datacenter for the region. 

      • The platform will add regional or global resources separately, such as global networks and public IP addresses. 

      • If you created virtual datacenters and resources before onboarding, the platform will add related resources into your virtual datacenters

      If conflicts occur during onboarding, the platform may stop and roll back the onboarding.

    3. Optionally, to restrict user permissions in the virtual datacenter, go to Roles and select a custom user role.
      Optionally, set exceptions to the virtual datacenter role 

For more details see Set a virtual datacenter role to limit user access

The platform will onboard the selected resources for you to manage.

  • The platform will mark the Public subnet (identified by a custom route table and NAT gateway) with a globe symbol and set the Internet gateway flag for this subnet. 

  • Users with bespoke network configurations should check the results of the synchronization.

  • The platform will synchronize private and public IP addresses even if they are not in use by VMs, and mark the IP addresses in use by provider entities with provider identifiers.

  • The platform will import VM templates. If the platform cannot find the VM template, the VM will have no template in the platform. To save a copy of your VM disk to create a template, so you can recreate the VM, make an Abiquo instance of the VM. 

If you delete an onboarded VDC, the platform will delete it in the provider. If your enterprise does not have valid credentials for the public cloud provider, when you delete public cloud entities in the platform, they will still exist in the public cloud provider.



View classic VMs

Unable to render {include} The included page could not be found.

Synchronize VDCs and resources

To update a virtual datacenter and onboard any changes made in the provider, synchronize the virtual datacenter:

  1. Go to Virtual datacentersV. Datacenters list

  2. Beside the virtual datacenter Name, click the round arrow Synchronize button

To synchronize specific resources such as networks, public IPs, and so on:

  1. Go to Virtual datacenters → select the resource tab

  2. Click the round arrow Synchronize button for the resource. 

For more information, see the resource documentation.

Screenshot: Synchronize networks



Manage resources that were deleted directly in the cloud provider

Unable to render {include} The included page could not be found.



Delete or release virtual resources in public cloud

Unable to render {include} The included page could not be found.


Onboard from public cloud using the API


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 virtual datacenters

Unable to render {include} The included page could not be found.
  • No labels