Skip to main content

Overview

A is the fundamental storage unit in Xloud Block Storage. Volumes are created independently of compute instances, persist across reboots and instance deletions, and can be attached, detached, and reattached freely. Create volumes before launching instances that require persistent data storage, or create bootable volumes pre-populated with an operating system image.
Prerequisites
  • An active Xloud account with appropriate permissions
  • Access to the Xloud Dashboard (https://connect.<your-domain>) or CLI configured with credentials
  • API credentials sourced (source admin-openrc.sh)
Additional requirements
  • An active project with sufficient storage quota (check with openstack quota show)
  • A volume type defined by your administrator — run openstack volume type list to view available options
  • The target availability zone — must match the zone of the instance you plan to attach to

Volume Source Options

SourceDescriptionUse Case
No source (blank)Empty block device — no filesystemDatabases, raw storage, custom partitioning
ImagePre-populated from an OS imageBootable root disk, application appliances
SnapshotRestored from a volume snapshotCloning existing data, test environments
VolumeCloned from another volumeDuplicating data disks

Create a Volume

Navigate to Volumes

Log in to the Xloud Dashboard (https://connect.<your-domain>) and navigate to Project → Volumes → Volumes.

Open the Create dialog

Click Create Volume in the top-right corner of the page.

Configure volume properties

Fill in the volume details:
FieldDescription
Volume NameUnique display name for the volume
DescriptionOptional free-text label
Volume SourceNo source, Image, Snapshot, or another Volume
Volume TypeStorage profile — determines performance tier and backend
Size (GiB)Capacity in gibibytes — minimum 1 GiB
Availability ZoneMust match the zone of the instance you plan to attach to
Select No source to create a blank volume. Select Image to pre-populate the volume with an OS image — useful for creating bootable disks outside of the instance launch workflow.

Create and verify

Click Create Volume. The volume list refreshes and the new volume displays with status Available.
Volume created successfully — status shows Available.

Volume Naming Conventions

Use a consistent naming scheme across your project to simplify management at scale. Recommended format: <project>-<purpose>-<index> — e.g., web-data-01, db-primary-01, backup-archive-01.

Next Steps

Attach a Volume

Connect a volume to a compute instance and prepare the filesystem for use

Volume Types

Understand the storage tiers and performance profiles available in your environment

Volume Snapshots

Create point-in-time snapshots of your volumes for fast recovery

Extend a Volume

Increase the capacity of an existing volume without downtime