Configuring Velostrata Manager on GCP

To use Velostrata 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 Velostrata Manager using the steps in this topic.

Velostrata Manager orchestrates migration operations and serves the web UI. For more, see Google Cloud reference architecture.

Prerequisites

Before launching your Velostrata Manager, you will need to configure Google Cloud Platform (GCP) for Velostrata.

Deploying Velostrata Manager

To launch Velostrata Manager on GCP:

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

    Setting Acceptable values Description
    Deployment Name An alphanumeric string. The name you would like Velostrata 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 Velostrata Manager.

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

    Network 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.

    Velostrata 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 GCP API calls from the Velostrata Manager.

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

    Velostrata 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 GCP 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.

    Velostrata Manager and API password A string longer than 8 alphanumeric characters. Password you will use for authenticating in the Velostrata 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 Velostrata Manager.
    Comma separated network tags (optional) Lowercase letters, numbers, and dashes.

    Network tags will be assigned to the Velostrata Manager.

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

  4. Click Accept for the GCP 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 GCP Console.

Configuring Velostrata Manager on GCP

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

  1. Sign in to the Velostrata Manager using the User Name localsupport and the Password that you specified when configuring Velostrata Manager.

  2. After you sign in, you can Enable Automatic Stackdriver Log Collection. Enabling log collection provides the following for Velostrata:

  3. In order to use Velostrata, read and select the following:

    • End User Service Agreement
    • Data Processing Terms Agreement
    • Model Contract Clauses Agreement
  4. When the Velostrata Manager home, as page appears, click System Settings.

  5. For VMware to GCP migrations only, click Create Token and copy the token to the clipboard.

    You will use this token to configure the Velostrata Backend on vSphere, as described in Deploying the Velostrata Backend.

Changing the Velostrata Manager password

You can change the password for your Velostrata Manager on the Google Cloud Platform Console. To do so:

  1. Open your Compute Engine instances
  2. Find your Velostrata 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.
本頁內容對您是否有任何幫助?請提供意見:

傳送您對下列選項的寶貴意見...

這個網頁
Migrate for Compute Engine (formerly Velostrata)