Deploy Ceph RADOS Block Device storage on an Arm AGI CPU host
Introduction
Understand the staged Ceph topology
Create three virtual machines
Prepare and validate the virtual machines
Bootstrap Ceph on one node
Create and use an RBD volume
Expand Ceph to three nodes
Test Ceph RBD during an OSD outage and recovery
Next Steps
Deploy Ceph RADOS Block Device storage on an Arm AGI CPU host
Who is this for?
This Learning Path is for infrastructure developers who want a hands-on introduction to Ceph block storage on an Arm server.
What will you learn?
After completing this Learning Path, you'll be able to perform the following tasks:
- Create three networked Ubuntu 26.04 Arm64 virtual machines (VMs) on one Arm AGI CPU host.
- Bootstrap a single-node Ceph cluster and use an RADOS Block Device (RBD) block volume.
- Extend the cluster to three Ceph nodes with one object storage daemon (OSD) per node.
- Verify replicated storage during a controlled OSD failure and recovery.
Prerequisites
Before starting, you'll need the following prerequisites:
- An Arm AGI CPU host running Ubuntu 24.04 with kernel-based VM (KVM) hardware virtualization support
- At least 12 available CPU cores, 12 GB of available memory, and 90 GB of available storage on the AGI CPU host
- Root or
sudoaccess on the AGI CPU host - Familiarity with Linux block devices and VMs
- Outbound internet access from the AGI CPU host and the VMs
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
You’ll build and test replicated Ceph RBD storage on an Arm AGI CPU host. First, you’ll create three Ubuntu 26.04 Arm64 VMs, prepare them, and bootstrap a single-node cluster. You’ll map an RBD image, mount it, and verify file persistence on the single node. After authorizing cluster SSH access to the other nodes, you’ll add their OSDs and increase replication. Finally, you’ll stop and restart an OSD to check continued access and recovery.