docs/doc/source/planning/openstack/storage-resources.rst
Ron Stone 4868e1c226 Spelling and typo fixes
Based on sphinx spellchecker testing/refinement.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Ibfe9b6d7bc8bf044a7fff0ac7e362e4067b17989
2022-08-16 16:19:27 -04:00

6.6 KiB
Executable File

Storage Resources

uses storage resources on the controller-labelled master hosts, the compute-labeled worker hosts, and on storage hosts if they are present.

The storage configuration for is very flexible. The specific configuration depends on the type of system installed, and the requirements of the system.

Storage Services and Backends

The figure below shows the storage options and backends for .

Storage Options and Backends

Each service can use different storage backends.

Ceph

This provides storage managed by the internal Ceph cluster. Depending on the deployment configuration, the internal Ceph cluster is provided through on OpenStack master / controller hosts or storage hosts.

Table 1. Available Backends for Storage Services
Service Description Available Backends
Cinder
  • persistent block storage
  • used for VM boot disk volumes
  • used as additional disk volumes for VMs booted from images
  • snapshots and persistent backups for volumes
  • Internal Ceph on master/controller hosts or storage hosts
Glance
  • image file storage
  • used for VM boot disk images
  • Internal Ceph on master/controller hosts or storage hosts
Nova
  • ephemeral object storage
  • used for VM ephemeral disks
  • CoW-Image on Compute Nodes
  • Internal Ceph on master/controller hosts or storage hosts

Uses of Disk Storage

Containerized OpenStack System

The system containers use a combination of local container ephemeral disk, backed by Ceph and a containerized HA mariadb deployment for configuration and database files.

VM Ephemeral Boot Disk Volumes (that is, when booting from an image)

Virtual machines use local ephemeral disk storage on computes for Nova ephemeral local boot disk volumes built from images. These virtual disk volumes are created when the instances are launched. These virtual volumes are destroyed when the instances are terminated.

VM Persistent Boot Disk Volumes (that is, when booting from Cinder Volumes)

Virtual machines can optionally use the Ceph-backed storage cluster for backing Cinder boot disk volumes. This provides permanent storage for the root disks, facilitating faster machine startup, but requiring more storage resources. For booted from images it provides additional Cinder disk volumes for persistent storage.

VM Additional Disks

Virtual machines can optionally use local ephemeral disk storage on computes for additional virtual disks, such as swap disks. These disks are ephemeral; they are created when a instance is launched, and destroyed when the instance is terminated.

VM Block Storage backups

Cinder volumes can be backed up for long term storage in a separate Ceph pool.

Storage Locations

In additional to the storage used by system containers, the following storage locations may be used.

Controller Hosts

In the Standard with Controller Storage deployment option, one or more disks can be used on controller hosts to provide a small Ceph-based cluster for providing the storage backend for Cinder volumes, Cinder backups, Glance images, and remote Nova ephemeral volumes.

Compute Hosts

One or more disks can be used on compute hosts to provide local Nova ephemeral storage for virtual machines.

Combined Controller-Compute Hosts

One or more disks can be used on combined hosts in Simplex or Duplex systems to provide local Nova Ephemeral Storage for virtual machines and a small Ceph-backed storage cluster for backing Cinder, Glance, and Remote Nova Ephemeral storage.

Storage Hosts

One or more disks are used on storage hosts to provide a large scale Ceph-backed storage cluster for backing Cinder, Glance, and Remote Nova Ephemeral storage. Storage hosts are used only on with Dedicated Storage systems.