Block Storage volumes

Quake AI concept: Snapshots

• Linode Block Storage is modeled as independent Volumes that you attach and mount to a Linode, rather than an OpenStack Cinder volume/snapshot workflow exposed as a dedicated snapshot resource on the same page. The canonical Block Storage doc emphasizes that volumes are separate from Linodes and can persist after a Linode is deleted. (Akamai TechDocs)
• A volume can only be attached to one Linode at a time, and both the volume and Linode must be in the same data center. The doc also says migration to a different data center is not directly available, which is stricter than OpenStack deployments that often support attaching volumes across the same cloud-wide control plane depending on backend policy. (Akamai TechDocs)
• The service is explicitly priced as storage capacity at $0.10/GB per month or $0.00015/GB per hour, with pricing that may vary by data center. That is a provider-specific billing model for capacity, not an OpenStack API behavior like Nova or Cinder snapshot semantics. (Akamai TechDocs)
• The Block Storage page states that the Backups Service does not cover Block Storage volumes and that customers must manage their own backups if they want protection for volume data. In OpenStack, snapshot capability is typically part of the storage service itself, so Linode's docs separate backup service from block storage management. (Akamai TechDocs)