跳转到内容

Volumes, storage and backups

此内容尚不支持你的语言。

Persistent storage: volumes, their replicas and snapshots, the storage quota, and backups.

Every address below is served under the control plane’s base URL. Permission is the guard the route is registered with; who holds it is read from the control plane’s own grant, so it cannot drift from what the server does. A dash means the route carries no permission guard of its own — the access tier below the table is then the whole of what stands in front of it.

Generated from Route. Hand edits to this table are overwritten on the next build — change the Go doc comment, or the generator.

Route Permission Who holds it Body
GET /api/v1/backups backups:read developer, operator, readonly, support
POST /api/v1/backups backups:create operator
GET /api/v1/backups/stats backups:read developer, operator, readonly, support
DELETE /api/v1/backups/{id} backups:delete operator
GET /api/v1/backups/{id} backups:read developer, operator, readonly, support
POST /api/v1/backups/{id}/restore backups:restore operator
GET /api/v1/backups/{id}/verify backups:read developer, operator, readonly, support
GET /api/v1/dvm/infrastructure/health volumes:read developer, operator, readonly, support
GET /api/v1/dvm/infrastructure/minio volumes:read developer, operator, readonly, support
GET /api/v1/dvm/infrastructure/seaweedfs volumes:read developer, operator, readonly, support
GET /api/v1/dvm/infrastructure/wireguard volumes:read developer, operator, readonly, support
GET /api/v1/dvm/recommendations volumes:read developer, operator, readonly, support
GET /api/v1/dvm/stats volumes:read developer, operator, readonly, support
GET /api/v1/dvm/volumes volumes:read developer, operator, readonly, support
POST /api/v1/dvm/volumes volumes:manage operator
DELETE /api/v1/dvm/volumes/{id} volumes:manage operator
GET /api/v1/dvm/volumes/{id} volumes:read developer, operator, readonly, support
POST /api/v1/dvm/volumes/{id}/failover volumes:manage operator
DELETE /api/v1/dvm/volumes/{id}/migration volumes:manage operator
GET /api/v1/dvm/volumes/{id}/migration volumes:read developer, operator, readonly, support
POST /api/v1/dvm/volumes/{id}/migration volumes:manage operator
GET /api/v1/dvm/volumes/{id}/replicas volumes:read developer, operator, readonly, support
GET /api/v1/dvm/volumes/{id}/snapshots volumes:read developer, operator, readonly, support
POST /api/v1/dvm/volumes/{id}/snapshots volumes:manage operator
GET /api/v1/tenants/{tenant}/storage/quota
PUT /api/v1/tenants/{tenant}/storage/quota
GET /api/v1/tenants/{tenant}/storage/usage
GET /api/v1/tenants/{tenant}/volumes
POST /api/v1/tenants/{tenant}/volumes
DELETE /api/v1/tenants/{tenant}/volumes/{id}
GET /api/v1/tenants/{tenant}/volumes/{id}
PUT /api/v1/tenants/{tenant}/volumes/{id}
POST /api/v1/tenants/{tenant}/volumes/{id}/attach
POST /api/v1/tenants/{tenant}/volumes/{id}/detach
GET /api/v1/tenants/{tenant}/volumes/{id}/replicas
POST /api/v1/tenants/{tenant}/volumes/{id}/replicas
DELETE /api/v1/tenants/{tenant}/volumes/{id}/replicas/{node}
GET /api/v1/tenants/{tenant}/volumes/{id}/snapshots
POST /api/v1/tenants/{tenant}/volumes/{id}/snapshots
DELETE /api/v1/tenants/{tenant}/volumes/{id}/snapshots/{snap}
GET /api/v1/tenants/{tenant}/volumes/{id}/snapshots/{snap}
GET /api/v1/volumes volumes:read developer, operator, readonly, support
POST /api/v1/volumes volumes:manage operator
POST /api/v1/volumes/prune volumes:manage operator
DELETE /api/v1/volumes/{name} volumes:manage operator
GET /api/v1/volumes/{name} volumes:read developer, operator, readonly, support
GET /api/v1/volumes/{name}/inspect volumes:read developer, operator, readonly, support

authenticated — Behind authentication, cross-site-request-forgery validation and tenant extraction. Every call acts inside exactly one tenant.

Declared in the source and served by nothing

Section titled “Declared in the source and served by nothing”

The addresses below are written into the control plane’s source and are registered on no router: the type that would register them is constructed nowhere, so a walk of the live router does not see them and a caller gets a 404. They are listed so that reading the source does not suggest a surface that is not there.

  • GET /api/v1/tenants/{tenant}/volumes/{id}/backups — declared at pkg/api/minio_handlers.go:68, mounted nowhere
  • GET /api/v1/tenants/{tenant}/volumes/{id}/migrate/status — declared at pkg/api/seaweedfs_handlers.go:62, mounted nowhere
  • POST /api/v1/tenants/{tenant}/volumes/{id}/backup — declared at pkg/api/minio_handlers.go:67, mounted nowhere
  • POST /api/v1/tenants/{tenant}/volumes/{id}/migrate — declared at pkg/api/seaweedfs_handlers.go:61, mounted nowhere
  • POST /api/v1/tenants/{tenant}/volumes/{id}/migrate/cancel — declared at pkg/api/seaweedfs_handlers.go:63, mounted nowhere