Google Cloud Platform

This topic explains how to get started with Google Cloud Platform (GCP) in Commander.

In this topic:

Getting started with GCP

To manage your GCP resources with Commander, the following configuration is required:

  1. Create a service account for Commander to have programmatic access to GCP.

    For more information, see Create a service account for Commander to access GCP.

  2. Ensure that the proper APIs are enabled for the project where the service account was created.

    For more information, see Enable the required APIs.

  3. Give the service account permissions for all of the resources that you want to add as a single GCP cloud account in Commander.

    For more information, see Grant permissions to the Commander service account.

  4. Optional: If Internet access is established through a web proxy server, integrate your web proxy server with Commander.

    For more information, see Connecting Public Clouds through a Web Proxy Server.

  5. Add your GCP account to Commander as a cloud account.

    For more information, see Adding GCP Cloud Accounts.

  6. Retrieve GCP billing data to ensure the accuracy of VM billing records.

    For more information, see Retrieving GCP Billing Data.

Create a service account for Commander to access GCP

In the GCP console, you must create a new service account. The service account is required to authenticate and authorize Commander to access GCP services.

To learn more about GCP service accounts, see Understanding Service Accounts in the GCP documentation.

To create a service account:

  1. In the GCP console, use the navigation menu to navigate to IAM & admin.
  2. In the header, select the project location for the new service account.

    While the project location you choose has no impact on the service account's visibility and permissions, make sure to select a project that won't be deleted.

    In the following example, Embotics Project X has been selected as the location for the new service account.

    Setting the Project Context for the Service Account in GCP Console

  3. In the left menu, select Service accounts.
  4. On the Service accounts page, click Create Service Account.
  5. On the Service account details page, do the following:
    1. Enter a distinct name, such as "Commander Service Account".
    2. Optionally, enter a description.
    3. Click Create.

    Note: The Service account ID field is automatically populated based on the name you enter.

  6. On the Grant this service account access to project (optional) page, click Continue.

    You will grant permissions in another context.

  7. On the Grant users access to this service account (optional) page, click Create Key.
  8. In the Create key (optional) section, keep the default key type, JSON, and click Create.
  9. If your browser prompts you to save the file, save it to a known location.

    The JSON file contains the service account's private key. You'll use this JSON file when adding a GCP cloud account.

    Note: This is the only time when you can download this private key.

  10. Click Done.

Enable the required APIs

In the GCP console, ensure that the following APIs are enabled for the project where you created the service account for Commander:

  • Cloud Resource Manager API — so that Commander can group resources by organization and project.
  • Cloud Billing API — so that Commander can retrieve billing data.

To learn how to enable APIs for a project, see Enabling and Disabling Services in the Google Cloud documentation.

Grant permissions to the Commander service account

You must give the service account permissions for all of the resources that you want to add as a single GCP cloud account in Commander.

To learn more about GCP service accounts, see Understanding Service Accounts in the GCP documentation.

Note: 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.

To grant permissions to the service account:

  1. In a text editor, open the downloaded JSON file that contains your key.
  2. Copy the value for "client_email".

    In our example, the value is vcommander-service-account@embotics-project-x.iam.gserviceaccount.com.

  3. In the GCP console, navigate to IAM & admin and select IAM.
  4. In the header, select a resource that you want to manage with Commander (such as an organization, folder or project).

    In this example, the organization "embotics.com" is one of the resources we want to manage with Commander.

    Setting the Context for Service Account Permissions in GCP Console

  5. On the IAM page, click Add.
  6. In the Add members pane, paste the "client_email" text you copied into the New members field.

    Adding Service Account to Appropriate Context

  7. Click the Select a role drop-down list and set the following permissions as required:
    • Assign the Project Editor permission so that Commander can carry out actions on resources within the selected object (such as powering instances on and off).
    • If you selected an organization, assign the Folder: Folder Viewer and Organization: Organization Viewer permissions so that the Commander views display GCP resources in their proper structural hierarchy, rather than in a flat list.
    • To monitor VM performance metrics, the service account must have at least the Monitoring Viewer role.
  8. Click Add Another Role and assign other permissions on this resource as necessary.

    Adding Roles to Commander Service Account in GCP Console

  9. Repeat steps 4 through 8 for each resource that you want to be part of this GCP cloud account.
  10. Click Save.

What's next? Now you're ready to add a GCP cloud account.

Costing

Commander uses hard-coded costs for all projected GCP costs, such as service catalog costs, deployed service costs and reports with a projected cost model configuration. Hard-coded costs are provided for all supported service types and instance types, by region.

Note: To make sure your price list is current, you can use the command workflow "Update Public Cloud List Prices". The workflow checks whether your price list is current, then updates the price list if necessary. You can configure this workflow to run on a recurring schedule, so that your price list is always current. By default, this workflow is disabled, but you can set how frequently it runs. For more information, see .

A cost model is automatically applied when a GCP account is added as a cloud account. The cost model enables you to add IT support costs, custom costs like backup costs and application software licensing costs to GCP billing data and to Commander's hard-coded costs. You can create additional cost models for different parts of your public cloud account.

The cost model and cost files allow users to see accurate estimated GCP costs when viewing cost details for existing resources.

For shared-core, predefined and memory-optimized instances, which are charged by the unit, the instance cost is displayed.

For custom instances, where costs are based on CPU and memory resource usage, the individual CPU and memory costs are displayed.

GCP costing differs from AWS and Azure costing in an important way. GCP charges aggregated CPU and memory usage costs, grouped by project and service type; GCP billing data doesn't include costs for individual VMs. This means that:

  • GCP doesn’t associate costs with VMs, the GCP VM Billing Report will always be empty. The GCP VM Comparative Economics Report will only show the projected cost model, not the historical or current cost models. For AWS and Azure, VM billing records and the VM Billing Report are based on retrieved billing data, so they will be populated as long as billing data retrieval is turned on.
  • Actual costs aren't displayed for GCP instances
  • Commander doesn't retrieve labels from GCP billing data
  • You may notice a few differences in the Cost Analytics Details tables when you're managing GCP. To learn more, see Troubleshooting Cost Analytics.

Commander doesn't support costs for:

  • Preemptible VMs (PVMs)
  • Sole-tenant nodes
  • Committed use discounts
  • Premium application licenses (SAP, SQL Server)
  • Disk snapshots
  • Network traffic
  • GPUs

By default, Commander doesn't apply GCP's Sustained Use Discounts to estimated costs. To change this behavior, edit the advanced system property embotics.cost.gcp.discount. After editing this system property, to trigger a cost recalculation, edit the GCP cost model and click Finish without making any changes.

GCP storage costs are per-region, but images don't have a region assignment. Commander displays image storage costs based on us-east1 region pricing.

To learn more about costing for GCP deployments, see also Costs for deployment configurations.