Skip to content

Block storage

Overview

Coming from another cloud?

▸AWS·EBS

This Quake AI feature maps to AWS’s EBS.

▸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·Volumes

This Quake AI feature maps to Hetzner’s Volumes.

Block storage

Block storage volumes are persistent NVMe-backed disks that you create, attach to compute instances, and format with any filesystem. A volume's lifecycle is independent of the instance that uses it: detach a volume and reattach it to a different VM, snapshot it for point-in-time recovery, or clone it to spin up an independent replica.

OpenStack Cinder backs block storage. For details on how Quake AI implements OpenStack, see How Quake AI uses OpenStack.

Get started#

To create your first volume, follow How to create a block storage volume. For background on volume lifecycle, snapshots, and clones, see Volumes.

How-to guides#

  • How to Clone a Block Storage Volume: Create an independent copy of an existing volume. The clone is a new, fully writable volume. Changes to the clone do not affect the source, and vice versa. You can clone a source volume whether it is...
  • How to Create a Block Storage Volume: Create a persistent block storage volume that you can attach to virtual machine instances. Volumes persist independently of instances; you can detach, reattach, and snapshot them at any time.
  • How to Create a Volume Snapshot: Create a point-in-time snapshot of a block storage volume. Snapshots are space-efficient: they store only the difference from the volume's base state, and you can use them to create new volumes or...
  • How to Extend a Block Storage Volume: Increase the capacity of an existing block storage volume. Volume extensions are irreversible: capacity can only grow. Quake AI's Cinder supports online extend on an attached, in-use volume when you...
  • How to Schedule Volume Snapshots and Restore Data: Schedule recurring Cinder volume snapshots with cron on a control instance or a CI workflow. Set a retention period, remove expired snapshots, and test restores on a recovery volume.
  • How to Transfer Volume Ownership Between Projects: Move a block storage volume from one Quake AI project to another. The source project creates a transfer record. The target project accepts the record with the transfer ID and authorization key.

Concepts#

Concepts

  • Volumes: Applications need storage that survives reboots, instance deletions, and infrastructure changes. Volumes provide that: persistent block storage devices that attach to instances, behave like physical...

Reference#

Console guides#

Block volumes attach to Compute instances as persistent disks. For S3-compatible bucket storage, see Object storage.

Quick answers

Was this page helpful?