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

      Open

      

   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 
      
      

      Open

      

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. 

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

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:

• External networks

• Firewalls 

• Classic firewalls 

• Load balancers 

• NAT network

• NAT IPs

To delete these resources (if they are not in use), select the resource and click the delete button.

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

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 enterprises#Entertenantdetailsandmetadata