Support automatic VM lock freeing #48

Closed
opened 2019-08-07 10:17:16 -04:00 by JoshuaBoniface · 2 comments
JoshuaBoniface commented 2019-08-07 10:17:16 -04:00 (Migrated from git.bonifacelabs.ca)

If a VM failed in some obscure way, PVC should provide a mechanism for freeing the RBD locks at a VM level (i.e. unlock all disk images belonging to VM X). Frontend both in CLI, API, and useful during some automated events (maybe clear on start if safe?).

If a VM failed in some obscure way, PVC should provide a mechanism for freeing the RBD locks at a VM level (i.e. unlock all disk images belonging to VM `X`). Frontend both in CLI, API, and useful during some automated events (maybe clear on start if safe?).
JoshuaBoniface commented 2019-08-07 17:51:25 -04:00 (Migrated from git.bonifacelabs.ca)

Added this as a CLI/API command (pvc vm flush-locks or POST /api/v1/vm/<vm>/locks), plus the already-existent on-fence lock freeing. This should be robust enough and without getting into the potential headaches of automated lock freeing.

Added this as a CLI/API command (`pvc vm flush-locks` or `POST /api/v1/vm/<vm>/locks`), plus the already-existent on-fence lock freeing. This should be robust enough and without getting into the potential headaches of automated lock freeing.
JoshuaBoniface commented 2019-08-07 17:51:25 -04:00 (Migrated from git.bonifacelabs.ca)

closed

closed
Sign in to join this conversation.
No Milestone
No project
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: parallelvirtualcluster/pvc#48
No description provided.