Skip to content

Volumes Console

Reference · Updated Sep 2026

Coming from another cloud?

▸AWS·Amazon EBS volumes

Amazon EBS volumeshigh

  • Strictly bound to a single Availability Zone where created; cannot be moved without snapshot.
  • Multiple volume types (gp3, io2, st1) with different performance/billing characteristics; Cinder uses volume_types but backend-defined.
  • Billed per provisioned GB-month regardless of usage; OpenStack typically quota-based without standard usage billing.
  • API via EC2 CreateVolume; differs from Cinder create_volume.
AWS docs ↗
▸Azure·Managed Disks

Azure Managed Diskshigh

  • Azure Managed Disks are fully managed with automatic redundancy (3 replicas, 99.999% SLA); Cinder durability depends on backend.
  • Predefined disk types (Ultra Disk, Premium SSD v2, Premium SSD, Standard SSD, Standard HDD) with fixed performance tiers; Cinder uses volume types with configurable QoS.
  • Disks billed on provisioned size regardless of use; Cinder billing typically on provisioned size too but varies by provider.
Azure docs ↗
▸DigitalOcean·Volumes

Volumeshigh

  • Uses proprietary /v2/volumes API instead of OpenStack Cinder /v3/{project_id}/volumes; actions like attach/detach/resize via undocumented POST /volumes/{id}/actions rather than /os-volume-attach etc.
  • Enforces single-instance attachment only (one Droplet at a time); OpenStack supports multi-attach volumes.
  • Volume names must be globally unique per region; OpenStack uses IDs primarily with optional display names.
  • Size specified in GiB (binary) with 1 GiB to 16 TiB range; OpenStack typically GiB but flexible.
DigitalOcean docs ↗
▸Google Cloud·Persistent Disk

Persistent Diskhigh

  • Uses Google Compute Engine REST API instead of OpenStack Cinder API.
  • Offers multiple performance tiers (pd-standard HDD, pd-balanced SSD, pd-ssd, pd-extreme) with performance scaling linearly with provisioned size, unlike Cinder's backend-dependent performance.
  • Supports regional disks replicated synchronously across 2 zones for higher availability (better than 99.9999% durability), while Cinder volumes are typically zonal unless using replication features.
  • Online resize to increase size without detaching; no manual striping/RAID needed as GCP handles distribution automatically.
Google Cloud docs ↗
▸Hetzner·Cloud Volumes

Cloud Volumeshigh

  • Provisioned via Hetzner CSI driver (csi.hetzner.cloud), ReadWriteOnce only, min 10GB, NVMe-based.
  • Billed €0.044/GB/month until deleted, no pause; attach/detach via CSI, unlike Cinder's broader access modes (RWX via Manila).
  • Snapshots supported but no volume encryption at rest by default; location-specific (e.g., fsn1).
  • Proprietary REST API at https://api.hetzner.cloud/v1/volumes using Bearer token auth, not OpenStack Cinder API (v3 JSON over Keystone). Endpoints like POST /volumes/{id}/actions/attach, POST /volumes/{id}/actions/resize (upsize only). No /v3/{project_id}/volumes/{volume_id}/action os-extend.
Hetzner docs ↗

Volumes console

Overview#

Select Storage Service > Volumes to show the volumes console.

Volumes console showing a list of volumes with columns for name, size, status (Available or In-use), type, and attached instanceClick to zoom
Volumes list showing available and in-use volumes with size, status, and attachment info

Select Create Volume to open the full-page volume wizard at /storage/volume/create. The wizard has these fields, in order:

  • Name (required).
  • Data Source Type (required): Blank Volume, Image, or Volume Snapshot.
  • Volume Type (required): currently Flash_Premium is the only option.
  • Capacity (GiB) (required): a slider and numeric input in the range 1-80 GiB, default 10.
  • Count: how many volumes to create at once.
Create Volume wizard page showing the Name, Data Source Type, Volume Type, Capacity (GiB), and Count fieldsClick to zoom
Create Volume wizard page with Data Source Type, Volume Type, and Capacity fields

Select a volume to view volume details, including the Detail, Volume Backups, and Volume Snapshots tabs.

Volume detail view showing volume name, status, size, type, attached instance, and tabs for Detail, Volume Backups, and Volume SnapshotsClick to zoom
Volume detail view with Detail, Volume Backups, and Volume Snapshots tabs

The Console displays the upstream Volume Backups tab, but Quake AI does not offer native Cinder backups. Use volume snapshots for point-in-time recovery or volume clones for independent copies.

Volume types#

Quake AI offers a single volume type:

  • Flash_Premium: NVMe SSD-backed storage for latency-sensitive workloads.

Volume types are platform-defined. The Console does not include a separate Volume Types view; the type appears in the Create Volume wizard selector. Type creation and deletion are administrator operations and are not available to tenant accounts. List the catalog from the CLI with openstack volume type list.

Actions#

You can take the following actions on volumes.

  • Edit (update the name or description)
  • Delete (permanently remove the volume)
  • Transfer ownership and accept ownership
  • Attach to or detach from instances
  • Create volume snapshots (point-in-time copy of volume data)
  • Clone an existing volume
  • Upload volume to image (captures the current state as a bootable image)
  • Make a volume bootable
  • Extend a volume's capacity

Volumes service#

Volumes service CLI reference#

Volumes service API reference#

See also#

Was this page helpful?