Convert existing Cloud Volumes ONTAP deployments to Infrastructure Manager
Beginning on February 9, 2026, new Cloud Volumes ONTAP deployments in Google Cloud can use Google Cloud Infrastructure Manager. Google is deprecating Google Cloud Deployment Manager in favor of Infrastructure Manager. To convert your existing Cloud Volumes ONTAP deployments from Deployment Manager to Infrastructure Manager, manually run the conversion tool. This one-time process automatically switches your systems to Infrastructure Manager.
The conversion tool is available on the NetApp Support Site and creates the following artifacts:
-
Terraform artifacts, saved in
conversion_output/deployment_name. -
Summary of the conversion, saved in
conversion_output/batch_summary_<deployment_name>_<timestamp>.json. -
Debug logs, saved in the
<gcp project number>-<region>-blueprint-config/<cvo name>directory. You need these logs for troubleshooting. The<gcp project number>-<region>-blueprint-configbucket stores the Terraform logs. -
The Cloud Volumes ONTAP project is the Google Cloud project in which you create Cloud Volumes ONTAP resources. The Console agent and Cloud Volumes ONTAP system can be in the same or different Google Cloud projects (cross-project configuration). In a cross-project configuration, you can deploy the Console agent in one project, such as project A, and deploy Cloud Volumes ONTAP systems in another project, such as project B, if the service account for the Console agent has the required permissions.
|
|
Cloud Volumes ONTAP systems using Infrastructure Manager store data and records in Google Cloud Storage buckets. You might incur extra costs for these buckets, but do not edit or delete the buckets or their content:
|
-
Verify that your Cloud Volumes ONTAP system is 9.16.1 or later.
-
Verify that none of the Cloud Volumes ONTAP resources or their properties have been manually edited from the Google Cloud Console.
-
Verify that the Google Cloud APIs are enabled, including the Google Cloud Quotas API. Refer to Enable Google Cloud APIs.
-
Verify that the service account for the NetApp Console agent has all required permissions. Refer to Google Cloud permissions for the Console agent.
-
If the Console agent and Cloud Volumes ONTAP are in different projects, verify that the service account for the Console agent has all required permissions in the Cloud Volumes ONTAP project. Learn about granting permissions to the service account for the Console agent to access other projects in Create a Google Cloud service account to use with the agent.
-
Before you begin the conversion, we recommend that you take a snapshot of the root and boot disks of the Cloud Volumes ONTAP system.
For private-mode or protected-mode deployments, ensure these additional prerequisites:
-
Ensure that you have the latest Console agent version. Download the product installer from the NetApp Support Site and then manually install the agent on your host so that the agent can use Infrastructure Manager APIs.
-
If you are running the tool in private mode, ensure that you have enabled the Cloud Build API in addition to the other APIs. Refer to Enable Google Cloud APIs.
-
Ensure that you have completed the network configurations and created the worker pool for private-mode or protected-environment deployments. Refer to Infrastructure Manager configuration in private mode or protected environments.
-
-
The conversion tool uses the following domains. Enable them on port 443 in your network:
Domain Port Protocol Direction Purpose cloudresourcemanager.googleapis.com
443
TCP
EGRESS
Project validation
deploymentmanager.googleapis.com
443
TCP
EGRESS
Deployment discovery
config.googleapis.com
443
TCP
EGRESS
Infrastructure Manager API
storage.googleapis.com
443
TCP
EGRESS
GCS bucket operations
iam.googleapis.com
443
TCP
EGRESS
Service account validation
compute.googleapis.com
443
TCP
EGRESS
Compute API calls used by Google Cloud and Terraform Import and Plan
cloudbuild.googleapis.com
443
TCP
EGRESS
Build operations only required for private mode
openidconnect.googleapis.com
443
TCP
EGRESS
Authentication
oauth2.googleapis.com
443
TCP
EGRESS
OAuth2 token exchange
registry.terraform.io
443
TCP
EGRESS
Terraform provider registry
releases.hashicorp.com
443
TCP
EGRESS
Terraform binary downloads
apt.releases.hashicorp.com
443
TCP
EGRESS
HashiCorp APT repository
us-central1-docker.pkg.dev
443
TCP
EGRESS
GCP Artifact Registry
metadata.google.internal
80
HTTP
Internal
VM metadata & auth tokens
pypi.org
443
TCP
EGRESS
Python package index
files.pythonhosted.org
443
TCP
EGRESS
Python package downloads
checkpoint-api.hashicorp.com
443
TCP
EGRESS
Terraform version check
download.docker.com
443
TCP
EGRESS
Docker APT repository
security.ubuntu.com
80/443
TCP
EGRESS
Ubuntu security updates
*.gce.archive.ubuntu.com
80
TCP
EGRESS
Ubuntu package mirror
Prepare the environment for running the tool
Run these steps before running the tool.
-
Create a role and attach it to a service account:
-
Create a YAML file with the following permissions.
title: NetApp Dm TO IM Convert Solution description: Permissions for the service account associated with the VM where the tool will run. stage: GA includedPermissions: - compute.addresses.get - compute.disks.get - compute.forwardingRules.get - compute.healthChecks.get - compute.instanceGroups.get - compute.instances.get - compute.regionBackendServices.get - config.deployments.create - config.deployments.get - config.deployments.getLock - config.deployments.lock - config.deployments.unlock - config.deployments.update - config.deployments.delete - config.deployments.updateState - config.operations.get - deploymentmanager.deployments.get - deploymentmanager.deployments.list - deploymentmanager.manifests.get - iam.serviceAccounts.get - storage.buckets.create - storage.buckets.get - storage.objects.create - storage.objects.delete - storage.objects.get - storage.objects.listInclude additional permission for private-mode or protected deployments
If you are running the tool in private mode or in a protected environment, also add the
cloudbuild.workerpools.getpermission to the YAML file.Include additional permissions for cross-project deployments (Console agent in one project, Cloud Volumes ONTAP in another)
In a cross-project deployment, you create the previous YAML file for the project of the Console agent. You need to create a second YAML file with the following permissions for the project where the Cloud Volumes ONTAP resources reside:
title: NetApp Dm TO IM Convert Solution for Cross Project description: Permissions for the service account associated with the VM where the tool will run for the project where CVO resources resides. stage: GA includedPermissions: - compute.addresses.get - compute.disks.get - compute.forwardingRules.get - compute.healthChecks.get - compute.instanceGroups.get - compute.instances.get - compute.regionBackendServices.get - deploymentmanager.deployments.get - deploymentmanager.deployments.list - deploymentmanager.manifests.get - resourcemanager.projects.get -
Create a custom role in Google Cloud with the permissions defined in the YAML file in the project of the Console agent. In a cross-project setup, you also create this role in the project where the Cloud Volumes ONTAP resources reside.
gcloud iam roles create dmtoim_convert_tool_role --project=PROJECT_ID \
--file=YAML_FILE_PATH
For more information, refer to Creating and managing custom roles. -
Attach the custom role to the service account that you'll use to create the VM.
-
Add the
roles/iam.serviceAccountUserrole to this service account. Refer to Service accounts overview. -
Enable the IAM Service Account Credentials API in the project:
gcloud services enable iamcredentials.googleapis.com --project=PROJECT_ID -
Allow the service account that you created to impersonate the Console agent service account. To do so, grant the
Service Account Token Creatorrole to the service account that you created.gcloud iam service-accounts add-iam-policy-binding \ CONSOLE_AGENT_SA@PROJECT_ID.iam.gserviceaccount.com \ -- member="serviceAccount:CONVERT_VM_SA@PROJECT_ID.iam.gserviceaccount.com" \ -- role="roles/iam.serviceAccountTokenCreator" \ -- project=PROJECT_ID
-
-
Create a VM with the following configurations. You run the tool on this VM.
-
Machine Type: Google Compute Engine machine type e2-medium
-
OS: Based on your requirement, select either of these images:
-
Ubuntu 26.04 LTS Minimal (ubuntu-2604-resolute-amd64)
-
SUSE Linux Enterprise Server 15 SP7 x86_64
-
-
Networking: Firewall allowing HTTP and HTTPS
-
Disk Size: 20GB
-
Security: Service accounts: the service account you created
-
Security: Access Scope - access set for each API:
-
Cloud Platform: Enabled
-
Compute Engine: Read only
-
Storage: Read only (default)
-
Google Cloud Logging (previously Stackdriver Logging) API: Write only (default)
-
Stackdriver Monitoring (now part of Google Cloud Operations) API: Write only (default)
-
Service Management: Read only (default)
-
Service Control: Enabled (default)
-
Google Cloud Trace (previously Stackdriver Trace): Write only (default)
-
-
-
Connect to the newly created VM using SSH:
gcloud compute ssh dmtoim-convert-executor-vm --zone <region where VM is deployed> -
Download the conversion tool from the NetApp Support Site by using your NSS credentials:
wget <download link from NetApp Support site> -
Extract the downloaded file:
unzip <downloaded file name>
-
Download and install these prerequisite packages:
-
Docker: 28.2.2 build 28.2.2-0ubuntu1 or later
-
Terraform: 1.14.1 or later
-
Python: 3.13.7, python3-pip, python3 venv
sudo apt-get update sudo apt-get install python3-pip python3-venv -y wget -O - https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com noble main" | sudo tee /etc/apt/sources.list.d/hashicorp.list sudo apt update && sudo apt install terraform sudo apt-get install -y docker.io sudo systemctl start dockerGoogle Cloud CLI
gcloudis preinstalled on the VM.
-
-
Set up Python:
sudo update-alternatives --install /usr/bin/python3 python3 /usr/bin/python3.11 2 -
Install pip3 for installing the package:
python3.11 -m ensurepip --upgrade -
Install Terraform:
wget https://releases.hashicorp.com/terraform/1.7.4/terraform_1.7.4_linux_amd64.zip unzip terraform_1.7.4_linux_amd64.zip sudo mv terraform /usr/local/bin/ rm terraform_1.7.4_linux_amd64.zip -
Install Google Cloud SDK (gcloud)
curl https://sdk.cloud.google.com | bash exec -l $SHELL
Run the conversion tool
Use these steps to run the conversion tool on both Ubuntu and SUSE Linux Enterprise Server.
-
Add the current user to the Docker group, so that the tool can use Docker without
sudoprivileges.sudo usermod -aG docker $USER newgrp docker -
Install the conversion tool:
cd <folder where you extracted the tool> ./install.shThis installs the tool in an isolated environment,
dmconvert-venv, and verifies that all required software packages are installed. -
Enter the environment where the tool is installed:
source dmconvert-venv/bin/activate -
Run the conversion tool as a
non-sudouser. Ensure that you use the same service account that the Console agent uses, and that the service account has all the necessary permissions for Google Cloud Infrastructure Manager.dmconvert \ --cvo-project-id=<the Google Cloud project ID for the Cloud Volumes ONTAP deployment> \ --cvo-name=<Cloud Volumes ONTAP system name> \ --service-account=<the service account attached to the Console agent>Run the tool in cross-project deployments (Console agent in one project, Cloud Volumes ONTAP in another)
Specify the
--console-agent-project-idparameter if your Cloud Volumes ONTAP system is in a project other than the project where the Console agent resides.dmconvert \ --cvo-project-id=<the Google Cloud project ID for the Cloud Volumes ONTAP deployment> \ --console-agent-project-id=<the Google Cloud project ID for the Console agent> \ --cvo-name=<Cloud Volumes ONTAP system name> \ --service-account=<the service account attached to the Console agent> \Run the tool in private-mode or protected-mode deployments
Specify the
--worker-poolparameter to run the tool in private-mode or protected-mode deployments. For worker pool configuration, refer to Infrastructure Manager configuration in private mode or protected environments.dmconvert \ --cvo-project-id=<the Google Cloud project ID for the Cloud Volumes ONTAP deployment> \ --cvo-name=<Cloud Volumes ONTAP system name> \ --service-account=<the service account attached to the Console agent> \ --worker-pool=<worker pool name>
The tool displays a list of all Cloud Volumes ONTAP systems and SVM details. When it finishes running, you can see the statuses of all the converted systems. Each converted system appears in the Google Cloud Console under Infrastructure Manager in a <system-name-imdeploy> format. This format indicates that the NetApp Console now uses Infrastructure Manager APIs to manage that Cloud Volumes ONTAP system.
|
|
After conversion, do not delete the deployment object for Deployment Manager in the Google Cloud Console. This deployment object contains information that you might need to roll back the converted system. |
If you need to roll back the conversion, you must use the same VM. If you have converted all systems and do not need to roll back to Deployment Manager, you can delete the VM.
Roll back the conversion
If you don't want to continue with the conversion, you can roll back to Deployment Manager by following these steps:
-
On the same VM that you created for running the tool, run this command:
dmconvert \ --cvo-project-id=<the Google Cloud project ID for the Cloud Volumes ONTAP deployment> \ --cvo-name=<Cloud Volumes ONTAP system name> \ --service-account=<the service account attached to the Console agent> \ --rollbackIf you have a cross-project deployment, specify the
--console-agent-project-idparameter:dmconvert \ --cvo-project-id=<the Google Cloud project ID for the Cloud Volumes ONTAP deployment> \ --console-agent-project-id=<the Google Cloud project ID for the Console agent> \ --cvo-name=<Cloud Volumes ONTAP system name> \ --service-account=<the service account attached to the Console agent> \ --rollback -
Wait until the rollback is complete.