Skip to main content

Connecting to Google Cloud Platform

Deploy OneIQ Pulse in GCP to collect inventory and performance data

Written by Omega Team

Overview

This procedure describes how to deploy and configure a OneIQ Pulse connector VM in your Google Cloud project to collect GCP inventory and performance data.

Network Requirements

The deployment template creates the Pulse VM on the project's default network with an external IP address, along with a firewall rule (oneiq-pulse-vm-xxxxx-deny-ingress) that blocks all inbound traffic to the Pulse VM. The rule applies to the Pulse VM only, so other VMs on the network are not affected. The SSH service is disabled on the VM, and the external IP address is used for outbound connectivity only. OneIQ Pulse only requires outbound HTTPS (port 443) access to OneIQ and Google Cloud; no inbound connections to the VM are required.

Steps Involved

  1. Create a dedicated OneIQ Pulse service account, grant it the Viewer role on the target project or projects, and download the JSON key.

  2. Enable the Cloud Resource Manager API & Cloud Runtime Configuration API

  3. In OneIQ, create or select an IT Environment, then deploy the GCP connector using the service account key and project details.

  4. Deployment of OneIQ Pulse VM in GCP

Step 1: Create a OneIQ Pulse service account in GCP

  1. Select the project in GCP, then under IAM and admin / Service Accounts Create a service account that the OneIQ Pulse VM will use.

    1. Service account name: e.g. "OneIQ Pulse Service Account"

    2. Service account ID: e.g. "oneiq-pulse"

    3. Service Account description: e.g. Used by the OneIQ Pulse Connector

    Click Create and continue

  2. Under Permissions (optional), select Viewer as the role. (OneIQ Pulse only needs read-only permission.)

Select Done

4. Go to the service account you just created, select Keys, and under Add Key select Create new key, select JSON.

A private key is saved to your computer.

6. If you need to collect data from multiple GCP Projects, go to each project, select IAM, Grant access, add the OneIQ Pulse service account principal email, and set the Viewer role.

Step 2: Enable Cloud Resource Manager API

  1. Navigate to APIs & Services > Library, find "Cloud Resource Manager API"

  2. Click Enable. (Ensure the correct project is selected)

Step 3: Configure the Pulse Connector in the OneIQ portal.

The OneIQ Pulse connector uses a Google Cloud Deployment Manager template (a Jinja file) to create the connector VM and related resources.

  1. Log in to the OneIQ Portal

  2. If GCP is the first platform you're connecting to, then select IT Environment in the left navigation menu, and select Connect IT Environment.

    If an IT Environment already exists, then skip to Step 4

  3. Give the IT Environment a name and select Confirm.

  4. Select the IT Environment and click on Deploy connector.

  5. Select Google Cloud Platform

  6. Select the Google Cloud Platform and fill in the details:

    1. Connector name: A name that identifies the connector in the OneIQ Portal, for example my-gcp-connector.

    2. Authorization type: Leave as Existing service account. Pulse runs as the service account you created in Step 1.

    3. Service account: The email address of the service account created in Step 1, in the format service-account-id@project-id.iam.gserviceaccount.com (for example, oneiq-pulse@my-project.iam.gserviceaccount.com). You can copy it from the Email column under IAM & Admin > Service Accounts in the GCP console.

    4. Zone: The GCP zone where the Pulse VM will be created. Defaults to us-central1-a.

    5. Virtual machine type: The machine type for the Pulse VM. Defaults to n1-standard-1. Not every machine type is available in every zone.

    6. Projects: The ID of each GCP project Pulse should collect data from. Use the project ID, not the project name.

Click Download to download the .jinja deployment file. The manifest expires after 24 hours, so deploy it in Step 4 within that time.

Step 4: Deploy the Connector using Google Cloud Shell

  1. Open the GCP Console: Go to the Google Cloud Console and ensure you have the correct project selected.

  2. Launch Cloud Shell: Click the Activate Cloud Shell button (a small terminal icon “>_”) in the top-right toolbar of the console.

  3. Upload the Template to Cloud Shell: Next, you need the .jinja file you downloaded in Step 3 in your Cloud Shell environment. The file is named after your connector and IT environment (for example, my-gcp-connector MyITE.jinja).

    • Click the ⋮ (three-dot menu) in the top-right corner of the Cloud Shell window and select “Upload file”. Choose the .jinja file you downloaded earlier. This will upload the file into your Cloud Shell home directory (typically at ~/cloudshell_open/).

  4. Run these commands in Cloud Shell in the GCP console, or on a computer with gcloud installed and signed in.


    projectId="your-project-id" # Replace with the ID of the GCP project to deploy OneIQ Pulse into

    deploymentName=oneiq-pulse-gcp

    template="my-gcp-connector MyITE.jinja" # Replace with the name of your .jinja file

    gcloud deployment-manager deployments create "$deploymentName" --template "$template" --project "$projectId"

    You can find your project ID in the project selector at the top of the GCP console.

    If prompted to authorize, then agree to that request.

NB: To remove your deployment, follow these steps:

  1. Confirm the deployment name that exists:

    gcloud deployment-manager deployments list

  2. Delete the existing deployment (use the exact name shown, example below):

gcloud deployment-manager deployments delete oneiq-pulse-gcp -q
Did this answer your question?