Onboard 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.  Google Cloud Platform (GCP) does not use virtual datacenter entities, so the platform onboards and synchronizes regions and all their resources.
       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.

• If metrics are enabled on the platform, the platform will enable the fetch of metrics for the VM. The user can then edit the VM to select the metrics to display in the UI.

• The platform will store the timestamps of when the VM was created and when it was captured into the platform. It will display these time stamps on the VM details panel.

• 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. 

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

1. Go to Virtual datacenters → V. 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

The virtual resources that you onboarded or created in public cloud will be grouped with their associated virtual datacenters.

Before you begin:

1. If you recently created virtual resources, such as load balancers, synchronize the virtual datacenter to ensure that the platform can find all the dependencies of the virtual datacenter.

To delete onboarded resources in public cloud:

1. Delete each virtual datacenter

   • You can choose to delete each virtual datacenter in the platform only, or in the platform and the provider. 

   • If you delete in the platform only, the platform will automatically remove VMs, virtual appliances, load balancers, public IPs, and firewalls from the virtual datacenter. It will not delete the firewalls

   • When you delete a virtual datacenter, public IPs that are not attached to VMs will remain in the provider and the synchronization process will delete them

   • Remember to check which is the default VDC in your provider, e.g. AWS default VPC, because it may be inconvenient to delete this VPC

Onboard from public cloud using the API

Onboard from public cloud regions without 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, Google 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 your public cloud provider does not support virtual datacenter entities, to onboard virtual resources do the following steps:

1. Go to Virtual datacenters

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

3. Select Synchronize public cloud

4. Select a public cloud region

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

If 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 in a virtual datacenter, such as firewalls, load balancers, or floating IPs, the platform may load these as separate entities.

If conflicts occur during synchronization, the platform will cancel the synchronization. This 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

"sync.singlevapp":"true",
"sync.singlevapp.name":"sync vapp name"