This blueprint creates a Migrate for Compute Engine (v5) environment deployed on an host project with multiple target projects.
The blueprint is designed to implement a M4CE (v5) environment on-top of complex migration landing environments where VMs have to be migrated to multiple target projects. It also includes the IAM wiring needed to make such scenarios work.
This is the high level diagram:
This sample creates\updates several distinct groups of resources:
- projects
- Deploy M4CE host project with required services on a new or existing project.
- M4CE target project prerequisites deployed on existing projects.
- IAM
- Create a service account used at runtime by the M4CE connector for data replication
- Grant migration admin roles to provided user accounts
- Grant migration viewer role to provided user accounts
| name | description | type | required | default |
|---|---|---|---|---|
| migration_admin_users | List of users authorized to create a new M4CE sources and perform all other migration operations, in IAM format | list(string) |
✓ | |
| migration_target_projects | List of target projects for m4ce workload migrations | list(string) |
✓ | |
| migration_viewer_users | List of users authorized to retrive information about M4CE in the Google Cloud Console, in IAM format | list(string) |
[] |
|
| project_create | Parameters for the creation of the new project to host the M4CE backend | object({…}) |
null |
|
| project_name | Name of an existing project or of the new project assigned as M4CE host project | string |
"m4ce-host-project-000" |
| name | description | sensitive |
|---|---|---|
| m4ce_gmanaged_service_account | Google managed service account created automatically during the migrate connector registration.. It is used by M4CE to perform activities on target projects |