Decommission Cloud Number Registry

Preview

This product is subject to the "Pre-GA Offerings Terms" in the General Service Terms section of the Service Specific Terms. Pre-GA products are available "as is" and might have limited support. For more information, see the launch stage descriptions.

This page explains how to decommission Cloud Number Registry in your organization.

Before you begin

1. Select the project in your organization that has been configured to provide Cloud Number Registry access.
2. Verify that you have the permissions required to complete this guide.

Required roles

To get the permissions that you need to decommission Cloud Number Registry, ask your administrator to grant you the Cloud Number Registry IPAM Admin (roles/cloudnumberregistry.ipamAdmin) IAM role on your project. For more information about granting roles, see Manage access to projects, folders, and organizations.

You might also be able to get the required permissions through custom roles or other predefined roles.

View the status of the IPAM admin scope

As you go through the decommission process, the IPAM admin scope has different statuses. Check the status to determine which step needs to be taken.

• READY_TO_USE: Cloud Number Registry is active and in use.

  From this state, you can disable the IPAM admin scope.

• DISABLED: the IPAM admin scope is disabled.

  From this state, you can clean up the IPAM admin scope.

• CLEANUP_IN_PROGRESS: a clean up operation is in progress.

  You must wait for cleanup to complete before you can proceed.

• READY_FOR_DELETION: the clean up operation is completed.

  From this state, you can delete the IPAM admin scope.

gcloud

View details about the IPAM admin scope by using the gcloud alpha number-registry ipam-admin-scopes describe command.

gcloud alpha number-registry ipam-admin-scopes describe SCOPE_NAME \
    --location=global

Replace SCOPE_NAME with the IPAM admin scope name.

Disable the IPAM admin scope

Disabling the IPAM admin scope stops Cloud Number Registry from making updates to the discovered resources, and prevents you from creating any user-managed resources.

Check that the status of the IPAM admin scope is in the READY_TO_USE state before you disable it.

Caution: Disabling the IPAM admin scope can't be undone. If you change your mind after you disable Cloud Number Registry, you must complete the decommission steps described on this page, and then set up Cloud Number Registry again.

gcloud

Disable the IPAM admin scope by using the gcloud alpha number-registry ipam-admin-scopes disable command.

gcloud alpha number-registry ipam-admin-scopes disable SCOPE_NAME \
    --location=global

Replace SCOPE_NAME with the IPAM admin scope name.

Clean up the IPAM admin scope

Clean up the IPAM admin scope to remove all Cloud Number Registry resources except for the IPAM admin scope and the default registry book. All realms and discovered ranges in the registry book are deleted.

Check that the status of the IPAM admin scope is DISABLED before you clean up the IPAM admin scope.

Caution: Cleaning up the IPAM admin scope can't be undone.

gcloud

Clean up the IPAM admin scope by using the gcloud alpha number-registry ipam-admin-scopes cleanup command.

gcloud alpha number-registry ipam-admin-scopes cleanup SCOPE_NAME \
    --location=global

Replace SCOPE_NAME with the IPAM admin scope name.

Delete the IPAM admin scope

Deleting the IPAM admin scope removes all Cloud Number Registry information.

Check that the status of the IPAM admin scope is READY_FOR_DELETION before you delete the IPAM admin scope. If the status is CLEANUP_IN_PROGRESS, check back in a few minutes.

Caution: Deleting the IPAM admin scope can't be undone.

gcloud

Delete the IPAM admin scope by using the gcloud alpha number-registry ipam-admin-scopes delete command.

gcloud alpha number-registry ipam-admin-scopes delete SCOPE_NAME \
    --location=global

Replace SCOPE_NAME with the IPAM admin scope name.