projects / ceph.git / blame
| Commit | Line | Data |
|---|---|---|
| 7c673cae FG |
1 | ==================== |
| 2 | Cluster Operations | |
| 3 | ==================== | |
| 4 | ||
| 5 | .. raw:: html | |
| 6 | ||
| 7 | <table><colgroup><col width="50%"><col width="50%"></colgroup><tbody valign="top"><tr><td><h3>High-level Operations</h3> | |
| 8 | ||
| 9 | High-level cluster operations consist primarily of starting, stopping, and | |
| 10 | restarting a cluster with the ``ceph`` service; checking the cluster's health; | |
| 11 | and, monitoring an operating cluster. | |
| 12 | ||
| 13 | .. toctree:: | |
| 14 | :maxdepth: 1 | |
| 15 | ||
| 16 | operating | |
| c07f9fc5 | 17 | health-checks |
| 7c673cae FG |
18 | monitoring |
| 19 | monitoring-osd-pg | |
| 20 | user-management | |
| 21 | ||
| 22 | .. raw:: html | |
| 23 | ||
| 24 | </td><td><h3>Data Placement</h3> | |
| 25 | ||
| 26 | Once you have your cluster up and running, you may begin working with data | |
| 27 | placement. Ceph supports petabyte-scale data storage clusters, with storage | |
| 28 | pools and placement groups that distribute data across the cluster using Ceph's | |
| 29 | CRUSH algorithm. | |
| 30 | ||
| 31 | .. toctree:: | |
| 32 | :maxdepth: 1 | |
| 33 | ||
| 34 | data-placement | |
| 35 | pools | |
| 36 | erasure-code | |
| 37 | cache-tiering | |
| 38 | placement-groups | |
| c07f9fc5 | 39 | upmap |
| 7c673cae | 40 | crush-map |
| c07f9fc5 | 41 | crush-map-edits |
| 7c673cae FG |
42 | |
| 43 | ||
| 44 | ||
| 45 | .. raw:: html | |
| 46 | ||
| 47 | </td></tr><tr><td><h3>Low-level Operations</h3> | |
| 48 | ||
| 49 | Low-level cluster operations consist of starting, stopping, and restarting a | |
| 50 | particular daemon within a cluster; changing the settings of a particular | |
| 51 | daemon or subsystem; and, adding a daemon to the cluster or removing a daemon | |
| 52 | from the cluster. The most common use cases for low-level operations include | |
| 53 | growing or shrinking the Ceph cluster and replacing legacy or failed hardware | |
| 54 | with new hardware. | |
| 55 | ||
| 56 | .. toctree:: | |
| 57 | :maxdepth: 1 | |
| 58 | ||
| 59 | add-or-rm-osds | |
| 60 | add-or-rm-mons | |
| 94b18763 | 61 | bluestore-migration |
| 7c673cae FG |
62 | Command Reference <control> |
| 63 | ||
| 64 | ||
| 65 | ||
| 66 | .. raw:: html | |
| 67 | ||
| 68 | </td><td><h3>Troubleshooting</h3> | |
| 69 | ||
| 70 | Ceph is still on the leading edge, so you may encounter situations that require | |
| 71 | you to evaluate your Ceph configuration and modify your logging and debugging | |
| 72 | settings to identify and remedy issues you are encountering with your cluster. | |
| 73 | ||
| 74 | .. toctree:: | |
| 75 | :maxdepth: 1 | |
| 76 | ||
| 77 | ../troubleshooting/community | |
| 78 | ../troubleshooting/troubleshooting-mon | |
| 79 | ../troubleshooting/troubleshooting-osd | |
| 80 | ../troubleshooting/troubleshooting-pg | |
| 81 | ../troubleshooting/log-and-debug | |
| 82 | ../troubleshooting/cpu-profiling | |
| 83 | ../troubleshooting/memory-profiling | |
| 84 | ||
| 85 | ||
| 86 | ||
| 87 | ||
| 88 | .. raw:: html | |
| 89 | ||
| 90 | </td></tr></tbody></table> | |
| 91 |