Storage planning
To meet your scalability and redundancy needs, select the appropriate ephemeral, persistent, and shared storage technologies before deploying RHOSO. Proper planning ensures your network configurations and security settings support your workload requirements.
Ephemeral storage is associated with a specific Compute instance. When this instance is terminated, so is the associated ephemeral storage. Ephemeral storage is useful for runtime requirements, such as storing the operating system of an instance.
Persistent storage is independent of any running instance. Persistent storage is useful for storing reusable data, such as data volumes, disk images, and shareable file systems.
You should consider and plan the storage requirements of your RHOSO environment before installing and deploying RHOSO. You should consider the following aspects of storage requirements when creating your storage plan:
- Supported features and topologies
- Storage technologies
- Networking
- Scalability
- Accessibility
- Performances
- Costs
- Security
- Redundancy and disaster recovery
- Storage management
- Persistent storage configuration
To meet workload and scaling needs, you can configure storage services for block, image, object, and file storage. You can configure Red Hat Ceph Storage as a unified back end for all storage services or you can configure alternative back-end storage solutions for these services. - Storage technologies
To design a reliable storage solution for your deployment, you can deploy individual storage technologies or combine them to meet different workload requirements. Understanding how these technologies interact helps you optimize storage capacity and performance." - Storage networks
When you install RHOSO, two default isolated storage networks are configured that follow best practices for network connectivity between storage components and deployments. - Storage scalability
Clustered storage solutions provide greater scalability and resiliency. For example, when you use Red Hat Ceph Storage as a Block Storage (cinder) back end, you can scale storage capacity and redundancy by adding more Ceph Object Storage Daemon (OSD) nodes. - Storage access and administration
Volumes are consumed only through instances. Users can extend, create snapshots of volumes and use the snapshots to clone or restore a volume to a previous state. - Storage security
The Block Storage service (cinder) provides data security through the Key Manager service (barbican). The Block Storage service uses a one-to-one, key to volume mapping with the key managed by the Key Manager service. You define the encryption type when configuring the volume type. - Storage redundancy and disaster recovery
The Block Storage service (cinder) provides volume backup and restoration for disaster recovery when you deploy the optional backup service, and supports snapshots for cloning and restoring volumes to previous states. - Storage management
You can configure RHOSO by using the Dashboard (horizon) or the OpenStack CLI. You can perform most procedures by using either method but some advanced procedures can only be completed using the CLI. - RHOCP storage sizing
You can configure the Image service (glance) and Object Storage service (swift) to allocate space in the RHOCP backing storage. In this scenario, estimate the RHOCP storage sizing based on the expected use of these services.