Skip to main content

Connecting to Google Cloud Platform

Deploy OneIQ Pulse in GCP to collect inventory and performance data

Support Kappa avatar
Written by Support Kappa
Updated this week

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.

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. In OneIQ, create or select an IT Environment, then deploy the GCP connector using the service account key and project details.

  3. Deployment of OneIQ Pulse VM in GCP

Step 1: Create a OneIQ Pulse service account in GCP

  1. Create a service account in GCP that the OneIQ Pulse VM will use. Ensure you've selected the right GCP Project.

  2. Enter service account details. e.g.

    1. Service account name: OneIQ Pulse Service Account

    2. Service account ID: oneiq-pulse

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

      Click Create and continue

  3. Enter service account details. e.g. Under Permissions, select Viewer. (OneIQ Pulse only needs read-only permission.)

    Select Continue

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

5. Select JSON and click Create. 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

The Google Cloud Resource Manager API manages and organizes resources within Google Cloud Platform (GCP) projects. It provides a set of functionalities and tools to help users create, manage, and organize cloud resources in a structured and controlled manner. GCP collection requires Cloud Resource Manager API to be enabled:

  1. https://console.developers.google.com/apis/api/cloudresourcemanager.googleapis.com/overview

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

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

  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: The name of the virtual machine that will be deployed in GCP that will run the OneIQ Pulse connector. e.g. my-gcp-connector

    2. Service account: The email address configured in GCP that represents the service account

    3. Projects: The Project(s) in GCP that the Pulse Connector should connect to and gather data from.

Step 4: Deployment of OneIQ Pulse VM in GCP

This step uses gcloud to apply the OneIQ template to your GCP project. Google Cloud then creates the deployment and starts the Compute Engine VM that runs OneIQ Pulse.

What happens

  1. Choose a deployment name - used to find and delete the deployment later.

  2. Select the OneIQ template file - tells Google Cloud what to create, including the Pulse VM.

  3. Run the deploy command - creates the deployment and starts the Pulse VM.

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

# Define the name of your deployment: 
deploymentName=oneiq-pulse-gcp

# Define the template containing the manifest for your deployment
template=oneiq-pulse-gcp.jinja

# Deploy your manifest
gcloud deployment-manager deployments create $deploymentName --template $template

To remove your deployment, run the following command:
​gcloud deployment-manager deployments delete $deploymentName -q

Tip: To confirm the VM was created, open Deployment Manager, open the deployment, and check the Resources list.

Did this answer your question?