c87da91757
In the past we had used an openstack-manuals tool to manually generate config option tables that would then be included into driver config documentation. With the move of documentation in-tree and the deprecation and removal of that tool, we have ended up with options that are no longer being updated when drivers change, or maintainers are left manually updating the existing tables. This addes a sphinx extension to use a new config-table directive to automatically pull in config options from the source so we no longer need to perform any manual action to pick up changes. Change-Id: I625fb96229001c326ed2400155e2d067279a400e
3.1 KiB
Ceph RADOS Block Device (RBD)
If you use KVM or QEMU as your hypervisor, you can configure the Compute service to use Ceph RADOS block devices (RBD) for volumes.
Ceph is a massively scalable, open source, distributed storage system. It is comprised of an object store, block store, and a POSIX-compliant distributed file system. The platform can auto-scale to the exabyte level and beyond. It runs on commodity hardware, is self-healing and self-managing, and has no single point of failure. Due to its open-source nature, you can install and use this portable storage platform in public or private clouds.
RADOS
Ceph is based on Reliable Autonomic Distributed Object Store (RADOS). RADOS distributes objects across the storage cluster and replicates objects for fault tolerance. RADOS contains the following major components:
- Object Storage Device (OSD) Daemon
-
The storage daemon for the RADOS service, which interacts with the OSD (physical or logical storage unit for your data). You must run this daemon on each server in your cluster. For each OSD, you can have an associated hard drive disk. For performance purposes, pool your hard drive disk with raid arrays, or logical volume management (LVM). By default, the following pools are created: data, metadata, and RBD.
- Meta-Data Server (MDS)
-
Stores metadata. MDSs build a POSIX file system on top of objects for Ceph clients. However, if you do not use the Ceph file system, you do not need a metadata server.
- Monitor (MON)
-
A lightweight daemon that handles all communications with external applications and clients. It also provides a consensus for distributed decision making in a Ceph/RADOS cluster. For instance, when you mount a Ceph shared on a client, you point to the address of a MON server. It checks the state and the consistency of the data. In an ideal setup, you must run at least three
ceph-mondaemons on separate servers.
Ways to store, use, and expose data
To store and access your data, you can use the following storage systems:
- RADOS
-
Use as an object, default storage mechanism.
- RBD
-
Use as a block device. The Linux kernel RBD (RADOS block device) driver allows striping a Linux block device over multiple distributed object store data objects. It is compatible with the KVM RBD image.
- CephFS
-
Use as a file, POSIX-compliant file system.
Ceph exposes RADOS; you can access it through the following interfaces:
- RADOS Gateway
-
OpenStack Object Storage and Amazon-S3 compatible RESTful interface (see RADOS_Gateway).
- librados
-
and its related C/C++ bindings
- RBD and QEMU-RBD
-
Linux kernel and QEMU block devices that stripe data across multiple objects.
Driver options
The following table contains the configuration options supported by the Ceph RADOS Block Device driver.
cinder.volume.drivers.rbd