Google VM Migration
Use the Migrate to Virtual Machines API to programmatically migrate workloads (Google OAuth2).
OCNORA ships 11 typed Google VM Migration operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google VM Migration
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google VM Migration
Operations, grouped by what they do to your data.
Create and send 2
Update 2
Delete and cancel 2
A sample Google VM Migration workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google VM Migration trigger is needed.
- 2Fetch Inventoryvm_migration.fetch_inventoryList remote source's inventory of VMs. The remote source is the onprem vCenter (remote in the sense it's not in Compute Engine).
- 3Create Migrating Vmvm_migration.create_migrating_vmCreates a new MigratingVm in a given Source.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 11
- Create Migrating VmCreates a new MigratingVm in a given Source.vm_migration.create_migrating_vm
- Create SourceCreates a new Source in a given project and location.vm_migration.create_source
- Delete Migrating VmDeletes a single MigratingVm.vm_migration.delete_migrating_vm
- Delete SourceDeletes a single Source.vm_migration.delete_source
- Fetch InventoryList remote source's inventory of VMs. The remote source is the onprem vCenter (remote in the sense it's not in Compute Engine).vm_migration.fetch_inventory
- Get Migrating VmGets details of a single MigratingVm.vm_migration.get_migrating_vm
- Get SourceGets details of a single Source.vm_migration.get_source
- List Migrating VmsLists MigratingVms in a given Source.vm_migration.list_migrating_vms
- List SourcesLists Sources in a given project and location.vm_migration.list_sources
- Update Migrating VmUpdates the parameters of a single MigratingVm.vm_migration.update_migrating_vm
- Update SourceUpdates the parameters of a single Source.vm_migration.update_source
Google VM Migration questions
- How does OCNORA authenticate with Google VM Migration?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google VM Migration?
- 11 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google VM Migration operation I need is not listed?
- Where Google VM Migration has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google VM Migration?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google VM Migration calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google VM Migration workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.