Migrate to Virtual Machines, formerly Migrate for Compute Engine, moves virtual machines from on-premises or other cloud environments into Compute Engine. Migration from other clouds follows two stages: convert source virtual machines into Google Compute Engine instances, then containerize them when needed. section 15.4.4 section 15.4.5
A production migration typically requires:
- Configure a site-to-site VPN and firewall rules between the source environment and the VPC containing the migration manager. section 15.4.5
- Use Cloud Router with BGP over Cloud VPN or Cloud Interconnect when dynamic routing or a highly available, low-latency connection is appropriate. section 15.4.5
- Organize large migrations into waves by logical role, define runbooks and ordering, and schedule simulated testing before execution. section 15.4.5
- Account for the migration manager's separate Compute Engine VM and the policies required for actions such as starting or stopping workloads. section 15.4.5
Windows VM to a container image
Register a Compute Engine source with migctl, create and inspect a Windows migration, update its YAML plan if necessary, generate artifacts, and retrieve the resulting archive from Cloud Storage. Expand the archive with PowerShell, authenticate to Container Registry, then build and push the Docker image. section 15.4.4
migctl source create ce my-ce-src --project my-project --json-key=m4a-ce-src.json
Browse the command sequence for registering a Compute Engine migration source before creating a migration. section 15.4.4
