Overview
Multi-tier storage routes different workload classes to appropriate device media through volume types in the block storage service and pool configurations in nxtStore. Tier configuration is managed through nxtDeploy’s Storage Tiers panel, which auto-generates the required pool, CRUSH rule, and block storage backend configuration.Prerequisites
- Administrator credentials with the
adminrole - Device class CRUSH rules created for each tier (see CRUSH Maps)
- Access to nxtDeploy (
https://connect.<your-domain>)
Tier Overview
Configuring Tiers via nxtDeploy
Open Storage Tiers panel
Navigate to nxtDeploy → Configuration → Storage Tiers.The panel displays detected device classes in the cluster and lets you define
which tiers to expose as volume types.
Apply configuration
Click Apply. nxtDeploy automatically:
- Creates the pool with the correct CRUSH rule for the device class
- Registers the Cinder backend pointing to the new pool
- Creates the volume type with appropriate extra specs
- Updates the
_50_ceph_tiers.ymlconfiguration file
New volume type appears in
openstack volume type list and is available to tenants.Manual Tier Configuration
For environments where nxtDeploy is not managing tier configuration, configure tiers manually.- Create Pool and Rule
- Register Cinder Backend
Create CRUSH rule for NVMe
Create NVMe-backed pool
Verifying Tier Configuration
- Check Volume Types
- Test Volume Creation
List all volume types
Show volume type extra specs
volume_backend_name extra spec should match the Cinder backend name.Next Steps
CRUSH Maps
Configure device class rules that route each tier to the correct physical media
Pool Management
Manage the pools backing each storage tier
Capacity Planning
Monitor per-tier utilization and plan expansion
Block Storage — Volume Types
Advanced Cinder volume type configuration for QoS and backend selection