Move VM migration into pvcworkerd #178

New Issue

joshuaboniface · 2024-01-29T11:44:29-05:00

joshuaboniface commented

2024-01-29 11:44:29 -05:00

Currently, VM migrations are special actions that occur within the VMInstance objects based on state triggers, and happening within the node daemon.

While this has worked fairly well, it seems like a good candidate to move to pvcworkerd. This will allow it to happen truly asynchronously, without timeout queue jumping, and while reporting stats about the migration.

This would also allow the removal of the receive-side logic that currently exists and which can get out-of-sync.

The only main complication would be the transition to the new version, which would have to be considered.

Currently, VM migrations are special actions that occur within the VMInstance objects based on state triggers, and happening within the node daemon. While this has worked fairly well, it seems like a good candidate to move to pvcworkerd. This will allow it to happen truly asynchronously, without timeout queue jumping, and while reporting stats about the migration. This would also allow the removal of the receive-side logic that currently exists and which can get out-of-sync. The only main complication would be the transition to the new version, which would have to be considered.

joshuaboniface added this to the 1.0 milestone 2024-01-29 11:44:29 -05:00

joshuaboniface added the

Daemon

label 2024-01-29 11:44:29 -05:00

joshuaboniface self-assigned this 2024-01-29 11:44:29 -05:00

Sign in to join this conversation.