liveBook · Manning

Migctl

As explained in Google Anthos in Action

migctl is the command-line utility for configuring, executing, and monitoring Migrate to Containers migrations.

migctl is the unified command-line utility for configuring, executing, and monitoring Migrate to Containers migrations. It connects a migration source to a processing cluster, creates migration plans, generates artifacts, and reports progress. section 15.4.2 section 15.4.4

A typical migration workflow uses migctl to:

  • Install Migrate to Containers on a Kubernetes processing cluster with an installation service-account key, then verify deployment with `migctl doctor`. section 15.4.2
  • Register a Compute Engine source with a service-account key and the required Compute Viewer and Compute Storage Admin bindings. section 15.4.2
  • Create a migration from a VM identifier, retrieve or update its plan, execute it, and monitor progress with status commands. section 15.4.2 section 15.4.4
  • Generate and download artifacts for deployment, including Windows artifacts retrieved from Cloud Storage. section 15.4.2 section 15.4.4

Compute Engine source and migration

Register a source with `migctl source create ce`, create a migration with `migctl migration create ... --intent Image`, inspect it with `migctl migration get`, monitor it with `migctl migration status`, and retrieve generated files with `migctl migration get-artifacts`. section 15.4.2

Windows IIS migration

Create a Windows migration with `--workload-type=WindowsIIS`, update the generated plan when necessary, generate artifacts, copy `artifacts.zip` from Cloud Storage, expand it with PowerShell, and build and push the resulting Docker image. section 15.4.4

migctl source create ce my-ce-src --project my-project --json-key=m4a-ce-src.json

Shows the concrete command for registering a Compute Engine migration source with migctl. section 15.4.4

How Google Anthos in Action covers it

How deep it goes
Provides an operational command sequence from cluster installation through artifact retrieval, while leaving application deployment and image construction to adjacent tools.
Examples
Uses Linux Apache and Windows IIS VM migrations, migration YAML plans, generated deployment specifications, and Docker images.
What it assumes
Assumes a Kubernetes processing cluster, Compute Engine source, service-account JSON keys, IAM bindings, and relevant VM identifiers.
What you can do after
Operate migrations via named commands, customize plans, inspect progress, and obtain artifacts for Kubernetes or Docker deployment.
How it connects
Connects Kubernetes, Compute Engine, service accounts, IAM, migration plans, Cloud Storage, Docker images, and GKE.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Google Anthos in Action. The section links point to the parts of the book it draws on.