Proposal: Foundational Repository for VM Migration as Code

[hassannmoussaa]

Hi everyone,
I’d like to open a discussion around creating a foundational repository to help automate and simplify VM migrations using an “as code” approach.

The idea is to design a repo (or possibly multiple repos if separation makes sense) that would:

Provide infrastructure-as-code templates to configure and drive the VM Migration API

• Automate key lifecycle steps such as:
• Installing the migration agent
• Managing replication policies
• Running test clones
• Executing cutover workflows

**Allow migrations to be fully declarative, enabling repeatable and auditable processes.

Be extensible for different environments (VMware, Hyper-V, Bare Metal, etc.).**

The main goal is to create a baseline framework that accelerates adoption of migration-as-code patterns while leaving room for customization.

I’d love to get your thoughts on:

Feasibility: How realistic is this approach with the current APIs and tools?

Scope: Should the foundational repo cover end-to-end migration workflows, or should agent install / replication / cutover logic live in separate repos?

Collaboration: Is anyone interested in contributing to design or early prototypes with me from the current contributors.

Looking forward to your feedback and ideas on how we can move this forward!

Thanks,
Hassan Moussa

[ludoo]

This is a good idea. There's already two repos doing something similar for secops and genai, with tight integration with this repo.

Check this as an example https://github.com/GoogleCloudPlatform/genai-factory

[hassannmoussaa]

I wanted to ask for your thoughts on whether it would be appropriate to move forward by drafting a high-level proposal on this topic. Do you think it could potentially be incorporated into the github foundation's scope?

Additionally, would you be open to collaborating with me in a supervisory or advisory capacity as I work through this? I may just need some guidance along the way, and your expertise would be invaluable.

[hassannmoussaa]

It may require some addition to magic-modules also but i think i can tackle such work and it could be beneficial if it include blueprints for the following

• VMs (Windows/Linux from VMware, Hyper-V, AWS, Azure, Bare Metal). etc
• Databases (MySQL, PostgreSQL, SQL Server, Oracle → Cloud SQL, AlloyDB, Spanner). etc
• Data lakes (HDFS, S3, Azure Blob → GCS/BigQuery). etc
• Containers (Kubernetes clusters → GKE Autopilot/Standard). etc