mirror of
https://github.com/ceph/ceph
synced 2024-12-23 03:44:23 +00:00
812989bf35
doc/architecture.rst - removed broken reference. doc/config-cluster - cleanup and added chef doc/install - Made generic to add Chef, OpenStack and libvert installs doc/init - Created light start | stop and health section doc/source - Removed $ from code examples. Trimmed paras to 80 char doc/images - Added preliminary diagram for Chef. doc/rec - Added reference to hardware. Added filesystem info. Signed-off-by: John Wilkins <john.wilkins@dreamhost.com>
31 lines
1.1 KiB
ReStructuredText
31 lines
1.1 KiB
ReStructuredText
===============================
|
|
Configuring a Storage Cluster
|
|
===============================
|
|
Ceph can run with a cluster containing thousands of Object Storage Devices
|
|
(OSDs). A minimal system will have at least two OSDs for data replication. To
|
|
configure OSD clusters, you must provide settings in the configuration file.
|
|
Ceph provides default values for many settings, which you can override in the
|
|
configuration file. Additionally, you can make runtime modification to the
|
|
configuration using command-line utilities.
|
|
|
|
When Ceph starts, it activates three daemons:
|
|
|
|
- ``ceph-osd`` (mandatory)
|
|
- ``ceph-mon`` (mandatory)
|
|
- ``ceph-mds`` (mandatory for cephfs only)
|
|
|
|
Each process, daemon or utility loads the host's configuration file. A process
|
|
may have information about more than one daemon instance (*i.e.,* multiple
|
|
contexts). A daemon or utility only has information about a single daemon
|
|
instance (a single context).
|
|
|
|
.. note:: Ceph can run on a single host for evaluation purposes.
|
|
|
|
.. toctree::
|
|
|
|
file-system-recommendations
|
|
Configuration <ceph-conf>
|
|
Deploy Config <deploying-ceph-conf>
|
|
deploying-ceph-with-mkcephfs
|
|
Deploy with Chef <chef>
|