Google Cloud Platform plug-in configuration notes

The Google Cloud Platform plug-in lets you create, delete, and restore disk and host-based snapshots in all zones where Google Cloud is present.

Google Cloud Platform plug-in configuration prerequisites

Before you configure the Google Cloud Platform plug-in, enable the following APIs under APIs & Services from Google Cloud console:

Google Cloud Platform plug-in configuration parameters

The following parameters are required for configuring the Google Cloud Platform plug-in:

Table: Google Cloud Platform plug-in configuration parameters

CloudPoint configuration parameter	Google equivalent term and description
Project ID	The ID of the project from which the resources are managed. Listed as project_id in the JSON file.
Client Email	The email address of the Client ID. Listed as client_email in the JSON file.
Private Key	The private key. Listed as private_key in the JSON file. Note: You must enter this key without quotes (neither single quotes nor double quotes). Do not enter any spaces or return characters at the beginning or end of the key.
Zones	A list of zones in which the plug-in operates.

CloudPoint supports the following GCP zones:

Table: GCP zones supported by CloudPoint

GCP zones
asia-east1-a, asia-east1-b, asia-east1-c asia-east2-a, asia-east2-b, asia-east2-c asia-northeast1-a, asia-northeast1-b, asia-northeast1-c asia-northeast2-a, asia-northeast2-b, asia-northeast2-c asia-south1-a, asia-south1-b, asia-south1-c asia-southeast1-a, asia-southeast1-b, asia-southeast1-c
australia-southeast1-a, australia-southeast1-b, australia-southeast1-c
europe-north1-a, europe-north1-b, europe-north1-c europe-west1-b, europe-west1-c, europe-west1-d europe-west2-a, europe-west2-b, europe-west2-c europe-west3-a, europe-west3-b, europe-west3-c europe-west4-a, europe-west4-b, europe-west4-c europe-west6-a, europe-west6-b, europe-west6-c
northamerica-northeast1-a, northamerica-northeast1-b, northamerica-northeast1-c southamerica-east1-a, southamerica-east1-b, southamerica-east1-c
us-central1-a, us-central1-b, us-central1-c, us-central1-f us-east1-b, us-east1-c, us-east1-d us-east4-a, us-east4-b, us-east4-c us-west1-a, us-west1-b, us-west1-c us-west2-a, us-west2-b, us-west2-c us-west3-a Utah, us-west3-b Utah, us-west3-c Utah us-west4-a Nevada, us-west4-b Nevada, us-west4-c Nevada

Configuring multiple accounts or subscriptions or projects

If you are creating multiple configurations for the same plug-in, ensure that they manage assets from different Tenant IDs. Two or more plug-in configurations should not manage the same set of cloud assets simultaneously.
When multiple accounts are all managed with a single CloudPoint server, the number of assets being managed by a single CloudPoint instance might get too large and it would be better to space them out.
To achieve application consistent snapshots, we would require agent/agentless network connections between the remote VM instance and CloudPoint server. This would require setting up cross account/subscription/project networking.

GCP plug-in considerations and limitations

Consider the following before you configure this plug-in:

If a zone is removed from the GCP plug-in configuration, then all the discovered assets from that zone are also removed from the CloudPoint assets database. If there are any active snapshots that are associated with the assets that get removed, then you may not be able perform any operations on those snapshots.
Once you add that zone back into the plug-in configuration, CloudPoint discovers all the assets again and you can resume operations on the associated snapshots. However, you cannot perform any restore operations on the associated snapshots.

More Information