Add Proxmox snapshots: list, take, roll back, delete
A guest's drawer on the Proxmox page now has a Snapshots section. Everyone signed in sees them, operators take them, administrators roll back and delete (each behind a confirmation). Proxmox does each as a task, followed for up to 20 seconds. Audit log and change log entries for all three. An http:// Proxmox address is now allowed. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
12e9fee7af
commit
97df28c6dc
11 files changed
+733
-11
No files matched your search
+3
-2
@@ -43,9 +43,10 @@ It is for the readers written from documentation (see "Not verified" on each int
|
||||
|
||||
- **Config fields:** Proxmox URL, API token ID, API token secret, allow self-signed certificate
|
||||
- **Auth:** `PVEAPIToken=<tokenId>=<tokenSecret>` header
|
||||
- **Actions used:** list nodes/VMs/LXCs, read guest config and live status, read node host stats and storage usage, start/stop/reboot/shutdown a guest, read backup job schedules and recent `vzdump` task history
|
||||
- **Actions used:** list nodes/VMs/LXCs, read guest config and live status, read node host stats and storage usage, start/stop/reboot/shutdown a guest, **list, take, roll back to and delete a guest's snapshots**, read backup job schedules and recent `vzdump` task history
|
||||
- **Required access:** A dedicated API token (Datacenter → Permissions → API Tokens) with a role granting **VM.Audit + VM.PowerMgmt** (e.g. `PVEVMAdmin`) on the VMs/LXCs to manage, **plus Sys.Audit and Datastore.Audit** on the node(s) for the host CPU/RAM/storage cards to populate. A token scoped to VM management only will still work for the guest list and power actions — it'll just show an error on the per-node hardware card instead of failing outright. Backup job schedules and run history need that same **Sys.Audit** — no separate permission to grant if the node-stats card already works.
|
||||
- **Notes:** self-signed certificates are supported via the "Allow self-signed certificate" checkbox — common for an internal PVE host.
|
||||
- **Snapshots** (Infrastructure → Proxmox → click a guest → *Snapshots*): everyone signed in sees a guest's snapshots (oldest first, a branch indented, *with memory* marked); an **operator** can take one (a name — or one made from the time, `hlm-YYYYMMDD-HHMMSS` — a description, and for a running VM whether to keep its memory so a rollback brings it back running); **rolling back and deleting are an administrator's**, each behind a confirmation, because a rollback throws away everything the guest has done since and Proxmox removes the snapshots taken after the one chosen. Proxmox does each as a task: the page waits up to 20 s and says how it went, or that it is still going and looks again. Every one is in the audit log and the change log (*A snapshot was taken of guest 100 on pve1*). The token needs **VM.Snapshot** (take, delete) and **VM.Snapshot.Rollback** (roll back) as well as VM.Audit — the `PVEVMAdmin` role has them; a token without them lists the snapshots and gets Proxmox's own refusal when it tries the rest. Checked against Proxmox's published API description and a pretend Proxmox, not a live host.
|
||||
- **Notes:** self-signed certificates are supported via the "Allow self-signed certificate" checkbox — common for an internal PVE host. An address that says `http://` (a reverse proxy in front of Proxmox) is spoken to over plain HTTP.
|
||||
|
||||
### Synology DSM
|
||||
|
||||
|
||||
Reference in new issue
Block a user