Block storage services
A screen for checking the per-host/backend operational status of core Cinder (block storage) services and viewing storage backend capacity. When a volume create/attach/backup failure occurs, you can quickly identify which Cinder component is the problem. It is organized into two tabs: Block storage / Storage backends.
- Path: Cloud Builder › System Info › Block Storage Services
- Search: Attribute-based text search (default filter key: Name)
- No checkboxes · CSV export supported
For Service State/Status definitions, see Compute nodes — Status definitions.
Sidebar (SNB)
From the left sidebar, move to each screen.
| No. | Feature | Item | Description |
|---|---|---|---|
| 1-1 | Servers | Servers | · Bare-metal server inventory (register, allocate, delete). |
| 1-2 | Host aggregates | Host aggregates | · Logical groups of hosts. |
| 1-3 | Availability zones | Availability zones | · Availability zones (AZ). |
| 1-4 | Compute services | Compute services | · Service endpoint status. |
| 1-5 | Compute nodes | Compute nodes | · Nodes, hypervisors, and resource providers. |
| 1-6 | Network agents | Network agents | · Neutron agent status. |
| 1-7 | Block storage services | Block storage services | · Cinder services and backends. |
| 1-8 | Orchestration services | Orchestration services | · Heat engine status. |
Tabs
2 tabs. View service status and backend capacity separately.
| No. | Feature | Item | Description |
|---|---|---|---|
| 2-1 | Block storage | Block storage | · Cinder service status + Enable/Disable. |
| 2-2 | Storage backends | Storage backends | · Per-backend protocol and capacity (read-only). |
Block storage table
Cinder service status (per Host@Backend).
| No. | Feature | Item | Description |
|---|---|---|---|
| 3-1 | Columns | Service state | 🟢 Up / 🔴 Down. |
| Name / Host | cinder-volume, etc. / Host@Backend. | ||
| Service status | Enabled / Disabled. | ||
| Action | Enable / Disable. |
Storage backends table
Per-backend protocol and capacity (read-only).
| No. | Feature | Item | Description |
|---|---|---|---|
| 4-1 | Columns | Name / Protocol | Host@Backend path / protocol such as ceph. |
| Backend name | Backend name. | ||
| Storage capacity (GiB) | Used / total. |
Host@Backend notation rules
Since a single Cinder host can have multiple backends, services are shown in Host@Backend format.
| Case | Notation |
|---|---|
| Default | Host@Backend |
| Host only | Shows Host only |
| Backend only (exception) | If there is no Host, - |
| Multiple entangled backends | Split into rows (one row = one backend) |
Enable / Disable
From the row action menu on the Block storage tab, change the service's policy status. A Reason is required when disabling. For modal details and follow-up, see Compute nodes — Enable/Disable.
Disable entry (row action)
Choose Disable from the row menu (when Enabled).
Disable confirmation modal
Excludes it from scheduling (policy status Disabled). A Reason is required.
| No. | Feature | Item | Description |
|---|---|---|---|
| 2-1 | Cancel | Cancel | · Close. |
| 2-2 | Disable | Disable | · Apply after entering a Reason. The status changes to Disabled. |