Velostrata Migration to GCP
Aft er you’ve confi gured the environment with the IAM roles and the inti tal
networking setup, follow this guide:
Creati ng the Velostrata Manager in GCP
VPN Tunnel in GCP
Velostrata will communicate with vSphere through a private connection; you need to create a
VPN tunnel in GCP that connects to the VMWare data center.
vSphere Confi gurati on
vCenter Plugin Installati on
Confi gure Cloud Extension
These are the VMs that Velostrata will create in GCP for the waves migration, it will always
create two, and the size of the VMs depends if the configuration is “Large” or “Small”
Generate the Runbook
Modify the CSV to include the instance type, the GCP project, and the migration group.
Create a new Wave by uploading the runbook:
Validate the runbook:
Create a new Job:
You can monitor the migration status:
And you can see the migration logs in more detail:
Troubleshooti ng
Here are a few tips you need to consider when migrations are not working smoothly:
Velostrata Manager VM hast to have access to HTTP and HTTPS.
VPN Tunnel has to have the appropriate firewall rules to allow the connection.
Make sure you have enough quota for storage in the GCP project.
Make sure the subnets can communicate with each other.
You can always confirm what’s happening using Stackdriver logs.
You can also see the activities page in GCP for any other error as in the quota when
Velostrata tries to create a new VM or something similar.
For Linux VMs, you have to install the Velostrata prep package. Otherwise, the VMs in
GCP won’t be able to initiate.
Migrating AWS EC2 instances to GCP didn’t work; when instances were initiating in
GCP, there was always an error when booting.