Configuring Migrate for Compute Engine Manager

To use Migrate for Compute Engine Manager for managing migrations, you'll need to first deploy it on a Compute Engine VM, then configure it. You do that by deploying the Migrate for Compute Engine Manager using the steps in this topic.

Migrate for Compute Engine Manager orchestrates migration operations and serves the web UI. For more, see Google Cloud reference architecture.

Prerequisites

Before launching your Migrate for Compute Engine Manager, you will need to configure Google Cloud for Google Cloud Migrate for Compute Engine (formerly Velostrata).

Deploying Migrate for Compute Engine Manager

To launch Migrate for Compute Engine Manager on Google Cloud:

  1. Open Migrate for Compute Engine on Google Cloud Marketplace. Click Launch.
  2. Select the GCP Project that will host your Migrate for Compute Engine Manager. This is the infrastructure project you set up when Configuring Google Cloud.
  3. In the New Migrate for Compute Engine deployment page, enter values as described in the following table.

    Setting Acceptable values Description
    Deployment Name An alphanumeric string. The name you would like Migrate for Compute Engine Manager to have when it is deployed. Choose something meaningful for the migration you'll be doing, such as account-processing-velo-manager.
    Zone A zone name available from the dropdown.

    Select a zone that is accessible from your VPN. Accessible zones will be listed among the subnet's configuration values in the VPC network's configuration.

    For more about zones, see Regions and zones in the Compute Engine documentation.

    Machine type A type from the dropdowns.

    The collection of virtualized hardware resources that should be available to the deployed Migrate for Compute Engine Manager.

    For more about machine types, see Machine types in the Compute Engine documentation.

    Network interfaces A network name available from the dropdown.

    Determines network traffic the instance can access.

    For more about networks and subnetworks, see Regions and zones in the Compute Engine documentation.

    Subnetwork A subnetwork name available from the dropdown. The list is populated based on the Network you choose.

    Assigns the instance an IPv4 address from the subnetwork's range. Instances in different subnetworks can communicate with each other using their internal IPs as long as they belong to the same network.

    For more about networks and subnetworks, see Regions and zones in the Compute Engine documentation.

    Migration Manager Service Account

    A service account name, as described in Service accounts.

    If you used the provided script to create service accounts and roles, this would be the service account whose name has the form velos-manager-deployment-name@infrastructure-project.iam.gserviceaccount.com.

    Used when performing Google Cloud API calls from the Migrate for Compute Engine Manager.

    You can create this service account via Cloud Shell as described in Creating GCP roles and service accounts via Cloud Shell.

    Migrate for Compute Engine Cloud Extension Service Account

    A service account name, as described in Service accounts.

    If you used the provided script to create service accounts and roles, this would be the service account whose name has the form velos-cloud-extension-deployment-name@infrastructure-project.iam.gserviceaccount.com.

    Used when performing Google Cloud API calls from the Cloud Extension created during setup.

    You can create this service account via Cloud Shell as described in Creating GCP roles and service accounts via Cloud Shell.

    Migration Manager and API password A string longer than 8 alphanumeric characters. Password you will use for authenticating in the Migrate for Compute Engine Manager or its API with the apiuser username.
    Private key encryption password A string longer than 8 alphanumeric characters. Can contain any of the following symbols: ~!@#%^&*()_+{}[]|./<>: Used to encrypt the private key of Migrate for Compute Engine Manager.
    Comma separated network tags (optional) Lowercase letters, numbers, and dashes.

    Network tags will be assigned to the Migrate for Compute Engine Manager.

    For more information, including a suggested tag name, see Setting up networks on Google Cloud.

  4. Click Accept for the Google Cloud Marketplace Marketplace Terms of Service.

  5. Click Deploy.

The deployment progress screen appears. When complete, note the IP Address. The IP address will always be available from your Compute Engine Instances page on the Google Cloud console.

Configuring Migrate for Compute Engine Manager on Google Cloud

You can configure the Migrate for Compute Engine Manager to begin logging. You can also get the token you'll need when you deploy the Migrate for Compute Engine Backend on vSphere.

  1. Sign in to the Migrate for Compute Engine Manager using the User Name apiuser and the Password that you specified when configuring Migrate for Compute Engine Manager.

  2. After you sign in, you can Enable Automatic Google Cloud Observability Log Collection. Enabling log collection provides the following for Migrate for Compute Engine:

  3. When the Migrate for Compute Engine Manager home, as page appears, click System Settings.

  4. For VMware to Google Cloud migrations only, click Create Token and copy the token to the clipboard.

    You will use this token to configure the Migrate for Compute Engine Backend on vSphere, as described in Deploying the Migrate for Compute Engine Backend.

Changing the Migrate for Compute Engine Manager password

You can change the password for your Migrate for Compute Engine Manager on the Google Cloud console. To do so:

  1. Open your Compute Engine instances
  2. Find your Migrate for Compute Engine Manager instance (for example velostrata-1-vm) and click on its name.
  3. In the top bar, click Edit.
  4. In the Custom metadata section, edit the value for apiPassword.
  5. Scroll to the bottom of the screen and click Save.