get_running_backups() on both drivers (napalm-device-types 4.34.0, RunningBackupsMixin).
PVE: the node's active vzdump tasks (/nodes/<node>/tasks?source=active&typefilter=vzdump), each with the guests it is taking now -- its own guest, or for a job the guests locked for their backup (/cluster/resources?type=vm, lock: backup) -- and a guest locked without a task on its own.
PBS: the running backup, sync, verify, gc, prune and tape tasks (/nodes/localhost/tasks?running=1); a restore or housekeeping is no backup.
tests/test_running_backups.py (11), full suite 621 passed, ruff, napalm-standard check and ratchet locally (against the device-types branch).
Depends on
NAPALM/napalm-device-types#102 (4.34.0, RunningBackupsMixin). CI installs napalm-device-types from PyPI, so the install jobs fail until 4.34.0 is tagged and published there; rerun them then.
## Summary
- `get_running_backups()` on both drivers (napalm-device-types 4.34.0, `RunningBackupsMixin`).
- PVE: the node's active vzdump tasks (`/nodes/<node>/tasks?source=active&typefilter=vzdump`), each with the guests it is taking now -- its own guest, or for a job the guests locked for their backup (`/cluster/resources?type=vm`, `lock: backup`) -- and a guest locked without a task on its own.
- PBS: the running backup, sync, verify, gc, prune and tape tasks (`/nodes/localhost/tasks?running=1`); a restore or housekeeping is no backup.
- A failed read raises.
## Related Issue
NetOrk/netork#2318
## Testing
- `tests/test_running_backups.py` (11), full suite 621 passed, ruff, `napalm-standard check` and `ratchet` locally (against the device-types branch).
## Depends on
NAPALM/napalm-device-types#102 (4.34.0, `RunningBackupsMixin`). CI installs napalm-device-types from PyPI, so the install jobs fail until 4.34.0 is tagged and published there; rerun them then.
netOrk holds a host's restart after patching while a backup runs on it, and
a guest's restart while its hypervisor is backing it up (NetOrk/netork#2318).
It asks right before the restart, so both drivers answer
get_running_backups() from napalm-device-types 4.34.0:
- PVE: the node's active vzdump tasks, each with the guests it is taking now
(its own guest, or for a job the guests locked for their backup), and a
guest locked without a task on its own, since the task list can lag and a
lock can outlive its task.
- PBS: the running backup, sync, verify, gc, prune and tape tasks; a restore
or housekeeping is no backup.
A failed read raises, so netOrk reads it as "not checked", never as "none".
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
get_running_backups()on both drivers (napalm-device-types 4.34.0,RunningBackupsMixin)./nodes/<node>/tasks?source=active&typefilter=vzdump), each with the guests it is taking now -- its own guest, or for a job the guests locked for their backup (/cluster/resources?type=vm,lock: backup) -- and a guest locked without a task on its own./nodes/localhost/tasks?running=1); a restore or housekeeping is no backup.Related Issue
NetOrk/netork#2318
Testing
tests/test_running_backups.py(11), full suite 621 passed, ruff,napalm-standard checkandratchetlocally (against the device-types branch).Depends on
NAPALM/napalm-device-types#102 (4.34.0,
RunningBackupsMixin). CI installs napalm-device-types from PyPI, so the install jobs fail until 4.34.0 is tagged and published there; rerun them then.