Glossary #

The node from which you run the ceph-deploy utility to deploy Ceph on OSD nodes.

A point that aggregates other nodes into a hierarchy of physical locations.

Important: Do Not Mix with S3 Buckets

S3 buckets or containers represent different terms meaning folders for storing objects.

Controlled Replication Under Scalable Hashing: An algorithm that determines how to store and retrieve data by computing data storage locations. CRUSH requires a map of the cluster to pseudo-randomly store and retrieve data in OSDs with a uniform distribution of data across the cluster.

A cluster node that maintains maps of cluster state, including the monitor map, or the OSD map.

Any single machine or server in a Ceph cluster.

Depending on context, Object Storage Device or Object Storage Daemon. The ceph-osd daemon is the component of Ceph that is responsible for storing objects on a local file system and providing access to them over the network.

A cluster node that stores data, handles data replication, recovery, backfilling, rebalancing, and provides some monitoring information to Ceph monitors by checking other Ceph OSD daemons.

Placement Group: a sub-division of a pool, used for performance tuning.

Logical partitions for storing objects such as disk images.

A term given to any diagram that shows the various routes a receiver can run.

Rules to determine data placement for a pool.

A single binary which handles alerts sent by the Prometheus server and notifies end user.

The core set of storage software which stores the user’s data. Such a set consists of Ceph monitors and OSDs.

AKA “Ceph Object Store”.

Database analytics and monitoring solution.

Systems monitoring and alerting toolkit.

Module that enables creating an Object Gateway zone for keeping the history of S3 object versions.

The S3/Swift gateway component for Ceph Object Store.