Supported GCP Resources
You can manage the following GCP resources in Commander.
|Infrastructure / Resource Type||Details|
GCP instances can be managed from Commander's Infrastructure view or the Applications view.
GCP instances can have either a predefined instance type (such as f1-micro, n1-standard-1 or n1-highmem-2) or custom configuration of CPU and memory resources. Commander displays the instance type details for deployed instances.
Commander currently supports reconfiguring CPU and memory resources for a GCP instance manually, and through change requests. In addition to predefined GCP instance types, Commander supports custom values for memory and CPU, as well as extended memory.
If you add a GCP instance type that isn’t supported in the Commander release you currently have on your system, it will be displayed properly, but resource information, cost information, and quotas won't be calculated until you upgrade to the latest major version. Because GCP is constantly adding instance types, each major Commander release includes the most recent new instance types.
For more information on custom instance types, see Creating a VM Instance with a Custom Machine Type in the GCP documentation.
For more information on extended memory, see Adding extended memory to a machine type in the GCP documentation.
Deployments can be managed from Commander's Applications view. All deployment resources (whether directly managed by Commander or not) are displayed on the deployment's Resources tab. To provision a deployment, you must first add a deployment configuration to the service catalog.
GCP deployments are not included in resource quota calculations. Resource quota-based service request approval workflows don't work for requested GCP deployments. However, because VMs are included in quota calculations, once a deployment is provisioned, any VMs in the deployment may cause quota to be exceeded.
Both regional and zonal storage resources are organized into Commander datastores, which are logical groups for aggregating persistent VM disks. When you look at a datastore, you can see which VMs have persistent disks, as well as the total storage usage in that zone or region. Commander shows both regional and zonal storage resources.
Because GCP storage is elastic, Commander properties and variables related to capacity (for example, provisioning level) don't apply to GCP. Likewise, reports based on these properties don't include data for GCP (for example, the Over-provisioned Disk Summary Report).
During regular synchronization with GCP, Commander collects the storage used by persistent disks.
Images are equivalent to VM templates and are displayed as VM templates in Commander. GCP provides a set of public images. Any images you create in GCP are private images. Commander displays GCP images in the Applications view.
Each GCP project has a default virtual network, but may contain additional networks. Virtual networks are shown in Commander's Applications View, along with their subnets and the VMs within them. Commander also displays the number of NICs for each instance, and the IPv4 Addresses property (available in the Details section) provides a comma-separated list of all available IP addresses.
If you use shared VPC networks, the Commander service account must have visibility of the host project. For more information, see Shared VPC overview in the GCP documentation.
Each GCP virtual network contains one or more subnets (although "legacy" networks don't). Subnets are shown in Commander's Applications View. You can assign network zones to subnets.
Organizations are the root node in the Cloud Platform Resource hierarchy. Commander's Applications View shows organizations, as well as the VMs, folders, virtual networks and subnets within them.
Folders are nodes in the Cloud Platform Resource Hierarchy. A folder can contain projects, other folders, or a combination of both. Commander's Applications View shows folders, as well as the organizations, VMs, virtual networks and subnets within them.
GCP projects form the basis for creating, enabling and using all GCP services including managing APIs, enabling billing, adding and removing collaborators, and managing permissions for GCP resources. Commander's Applications View shows projects, as well as the VMs, virtual networks and subnets within them.
A region is a specific geographical location where you can run your resources. Commander displays regions in the Infrastructure view or the Applications view and Storage views.
See Select Regions for Public Clouds to learn which regions Commander displays by default, and how to change this.
Each region is divided into multiple zones. Zones are somewhat equivalent to on-premise datacenters. Resources that are located in a zone, such as instances or persistent disks, are referred to as zonal resources. Other resources, like static external IP addresses, are regional. Regional resources can be used by any resources in that region, regardless of zone, while zonal resources can only be used by other resources in the same zone. Commander's Infrastructure view or the Applications view shows zones, as well as the VMs within them.