Loading runbooks into a wave
To create a wave, first create and configure a runbook inventory.
To load a runbook into a wave:
- Sign in to Migrate for Compute Engine Manager, and then click the Migration Waves icon.
- Click New Wave from the top bar of the Migrate for Compute Engine Runbook Automation Page, and then name the Wave.
- To choose the CSV for this wave's runbook, click Choose File, and then click Save.
Migrate for Compute Engine checks the runbook for structural problems, such as missing columns.
Validating a wave
Before taking any action on a wave by creating jobs, the wave must be validated. Validation finds semantic errors such as invalid or nonexistent:
- VM IDs
- Connectivity from Google Cloud to the vSphere environment or AWS
- Cloud Extension IDs
- Google Cloud instance types
- Google Cloud cloud details
- Google Cloud subnets
- Google Cloud projects
Google Cloud service accounts
Migrate for Compute Engine supports custom service accounts only. Validation fails with built-in Google Cloud service accounts.
For sole-tenant and Windows Bring Your Own License (BYOL) VMs, Migrate for Compute Engine performs the following additional validations:
- Whether the keys and values for node affinity exist.
- Whether the selected instance type has more than two cores.
- Whether the Host Maintenance Policy agrees with the type of license selected.
Validation must complete without errors in order to add jobs.
To perform a validation:
- Click Action > Validate.
To validate the runbook, click Yes.
The validation may take several minutes to complete. When it completes, a validation status column appears in the table. If a validation fails, click Failed within the row to see the failure messages.
If validation fails, fix your runbook and reload it, or change your environment settings, for example, Cloud Details in Migrate for Compute Engine Manager. Then re-run the validation until it succeeds.