Add VM snapshot export/import functionality #185

New Issue

joshuaboniface · 2024-08-16T10:51:36-04:00

joshuaboniface commented

2024-08-16 10:51:36 -04:00

As an extension to #184, implement VM snapshot export and import. Mostly, this will involve porting the current VM backup/restore functionality to act with the snapshots, rather than this functionality implicitly creating said snapshots. Eventual goal is to work this functionality towards #169 to permit direct cross-cluster export/import.

joshuaboniface added the

labels 2024-08-16 10:51:36 -04:00

joshuaboniface commented

2024-08-20 23:22:10 -04:00

This functionality has now been implemented, due for release in 0.9.99. 5 commands are now present:

pvc vm snapshot create will create a snapshot, either an automatic datestring or a name.
pvc vm snapshot remove will remove a snapshot.
pvc vm snapshot rollback will roll back a (stopped) VM to the given snapshot.
pvc vm snapshot exportwill export a snapshot to a given path (on the primary coordinator).
pvc vm snapshot import will import a snapshot from a given path (on the primary coordinator).

All 5 are implemented as pvcworkerd commands due to their runtime and to provide progress feedback in the CLI client.

This functionality has now been implemented, due for release in 0.9.99. 5 commands are now present: 1. `pvc vm snapshot create` will create a snapshot, either an automatic datestring or a name. 2. `pvc vm snapshot remove` will remove a snapshot. 3. `pvc vm snapshot rollback` will roll back a (stopped) VM to the given snapshot. 4. `pvc vm snapshot export`will export a snapshot to a given path (on the primary coordinator). 5. `pvc vm snapshot import` will import a snapshot from a given path (on the primary coordinator). All 5 are implemented as `pvcworkerd` commands due to their runtime and to provide progress feedback in the CLI client.

joshuaboniface closed this issue

2024-08-20 23:22:10 -04:00

joshuaboniface referenced this issue

2024-08-20 23:30:30 -04:00

Add cluster peering for DR/replication #169

Sign in to join this conversation.