Using LKS? Your Cluster creates, attaches and moves Latitude Block Storage volumes for your Workloads. See Persistent storage.
Prerequisites
- A verified team and a project in a location where high performance storage is available. The create flow only lists those locations.
- A bare metal server in the same project and location as the volume that supports network bonding. Before you can assign the volume, the server must be bonded onto a public network. Bonding joins the server’s two NICs into the redundant
bond0link that the storage network runs on. - One of the supported operating systems if you want the server to be configured automatically.
Storage traffic doesn’t travel over the public network. Latitude.sh delivers the storage network as a separate private VLAN on top of
bond0, and the server reaches the volume from a private storage IP in its own routing domain. The public network is required only because a bond needs one.Creating a volume
1
Open the create flow
In the dashboard, go to Storage > Block storage and click Create volume.
2
Choose a location and size
Pick the location and set the capacity, from 32 GB to 100 TB. The volume must be in the same location as the server you plan to map it to.
3
Create
Click Create volume. The volume opens on its detail page, ready to be mapped.
Mapping a volume to a server
Mapping connects the volume to one server. The server must be in the volume’s project and location.1
Pick a server
On the volume page, open the server picker under Assigned servers. Only servers that support network bonding are listed. Servers marked No public network can be selected, and the volume page offers to reinstall them on a public network. Assign the volume once the reinstall finishes.
2
Assign
Click Assign. The status shows Mapping while the volume is being attached, then Mapped. If the mapping fails, pick a server and try again.
If the volume’s location has no public network in your project yet, the volume page offers to create one before you can pick a server.
Activating storage networking on the server
Once the volume is mapped, the server needs a storage VLAN on top of its bond and an NVMe/TCP connection to the volume. You can let Latitude.sh configure this, or do it yourself. After you map the volume to a server, the server appears as a row under Assigned servers on the volume page. Click the row to expand it and see both options.Option 1: Reinstall
Click Reinstall in the server’s row. Reinstalling with a supported operating system configures the storage VLAN, the routes and the NVMe/TCP connection automatically, and connects the volume on boot.Option 2: Configure manually
If you don’t want to reinstall, click View guide in the server’s row. The guide lists the commands for your server and fills in the values the platform already knows, such as the storage VLAN id. Anything still shown as a placeholder, such as the storage IP or gateway, comes from Latitude support; replace it before applying. In short:1
Add the storage VLAN on top of the bond
Create a netplan file that defines a VLAN on
bond0 with the storage IP and the routes to the storage networks, then apply it with sudo netplan generate and sudo netplan apply.2
Run the storage setup script
Download and run
lsh-block-setup.sh. It installs the NVMe/TCP tooling, sets the server’s NVMe host name, and seeds the discovery target. Review the script before running it; it lists its changes and only acts with your approval.3
Connect the volume
Run
sudo nvme connect-all. The volume appears as an NVMe device on the server.Using the volume
After connecting, the volume shows up as a new NVMe device. Device numbers such asnvme1n1 change between servers and can point at a local disk, so identify the volume before touching it:
/dev/disk/by-id/, and keep that path for /etc/fstab so a device renumbering after reboot can’t mount the wrong disk:
VOLUME to the entry under /dev/disk/by-id/ that matches the serial you found. The ls line confirms it points at the device you expect.
Performance
Measured withfio and direct I/O on the unformatted volume, from a server with a 2×10 Gbps bond:
Results depend on the server’s network capacity, the filesystem and the workload.
Traffic to the volume uses both links of the bond with no tuning. At these rates, sequential throughput and random reads are limited by the server’s network.
These results use many parallel requests. The random read result needs about 1,000 requests in flight, for example 16 threads at a queue depth of 64. A single 4 KiB request takes about 0.4 ms to read and 0.9 ms to write, similar to file storage.
Expanding a volume
Volumes can grow but not shrink. Use Expand in the volume’s actions menu and pick a new size, up to 100 TB. Volumes can be expanded while mapped, and the server keeps running. Billing is prorated to the new size from the day you expand. If Expand doesn’t appear for a volume, that volume can’t be resized; contact support. After the resize, setVOLUME to the volume’s path under /dev/disk/by-id/, as in Using the volume, and confirm the server sees the new size:
+- names one of the volume’s controllers, such as nvme10. Rescan any of them, replacing <controller> with its name:
sudo xfs_growfs /mnt/volume instead.
Unmapping and deleting
To move a volume to another server, release it on the server first: stop anything using the mount, unmount it, and remove its/etc/fstab entry so the next boot doesn’t wait for a device that is no longer there.
DELETE-ALL-VOLUMES to confirm, or DELETE-VOLUME if you selected one, then click Delete. Volumes that can’t be deleted are listed with their error. Fix the problem, type the confirmation word again and click Retry to delete the rest.
Managing volumes with Terraform
To manage volumes as code, use the Latitude.sh Terraform provider v4.7.0 or later. Thelatitudesh_block_storage resource creates a volume, and latitudesh_block_storage_attachment maps it to a server. The requirements match the dashboard: the server must be in the volume’s project and location, and it must be eligible for storage. An eligible server supports bonding and is cabled to two switches. Deploying the server with public_network_id guarantees an eligible server, because that deploy only picks servers that pass the same check.
This example creates a public network, a server on it, and a volume, then maps the volume to the server in one apply:
storage_network attribute. It holds the storage VLAN id (vid), the storage IP (host_cidr), the routes and their gateway, and the NVMe/TCP target (block_gateway and block_port).
To expand a volume, increase size_in_gb. Terraform resizes it in place, even while it’s mapped, and you then grow the filesystem on the server. Decreasing size_in_gb or changing the volume’s name, location or project replaces the volume and deletes its data, so check the plan before you apply. Changing server_id unmaps the volume from the old server and maps it to the new one. Destroying the attachment unmaps the volume and keeps its data.
See the latitudesh_block_storage and latitudesh_block_storage_attachment reference for every attribute, data sources and import.
Supported operating systems
Automatic configuration on reinstall is available for these images:- Debian 13
- Ubuntu 24.04 and 26.04
- AlmaLinux 9 and 10
- Rocky Linux 9 and 10
Current limits
- Map one block volume per server for now.
- A volume can be up to 100 TB.
- Volumes can be expanded but not shrunk. Create a new volume if you need a smaller one.
- A volume can only be mapped to a server in the same project and location.
- Automatic configuration requires a reinstall with a supported operating system. On other images or without a reinstall, follow the manual guide.