Skip to content

[live-migration] replace event/error strings with structured MigrationNotification#2697

Open
rawahars wants to merge 1 commit intomicrosoft:mainfrom
rawahars:lm_events_proto_changes
Open

[live-migration] replace event/error strings with structured MigrationNotification#2697
rawahars wants to merge 1 commit intomicrosoft:mainfrom
rawahars:lm_events_proto_changes

Conversation

@rawahars
Copy link
Copy Markdown
Contributor

Summary

Drop the free-form event and error string fields on TransferSandboxResponse in favor of a structured MigrationNotification message that mirrors the HCS OperationSystemMigrationNotificationInfo payload.

The new MigrationNotification carries:

  • MigrationOrigin: source vs. destination side of the migration
  • MigrationEvent: lifecycle event (setup done, blackout started/exited, transfer in progress, migration done/failed, recovery done, etc)
  • MigrationResult: terminal outcome (success, cancelled, guest-initiated cancellation, source/destination failure, recovery failure)
  • AdditionalDetails: google.protobuf.Any for event-specific data

…fication

Drop the free-form `event` and `error` string fields on
TransferSandboxResponse in favor of a structured `MigrationNotification`
message that mirrors the HCS OperationSystemMigrationNotificationInfo
payload.

The new MigrationNotification carries:
  - MigrationOrigin: source vs. destination side of the migration
  - MigrationEvent: lifecycle event (setup done, blackout started/exited,
    transfer in progress, migration done/failed, recovery done, ...)
  - MigrationResult: terminal outcome (success, cancelled, guest-initiated
    cancellation, source/destination failure, recovery failure)
  - AdditionalDetails: google.protobuf.Any for event-specific data

Signed-off-by: Harsh Rawat <harshrawat@microsoft.com>
@rawahars rawahars requested a review from a team as a code owner April 21, 2026 08:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants