projects / ceph.git / blame
| Commit | Line | Data |
|---|---|---|
| 3efd9988 FG |
1 | .. _ceph-volume-simple: |
| 2 | ||
| 3 | ``simple`` | |
| 4 | ========== | |
| 5 | Implements the functionality needed to manage OSDs from the ``simple`` subcommand: | |
| 6 | ``ceph-volume simple`` | |
| 7 | ||
| 8 | **Command Line Subcommands** | |
| 9 | ||
| 10 | * :ref:`ceph-volume-simple-scan` | |
| 11 | ||
| 12 | * :ref:`ceph-volume-simple-activate` | |
| 13 | ||
| 14 | * :ref:`ceph-volume-simple-systemd` | |
| 15 | ||
| 16 | ||
| 17 | By *taking over* management, it disables all ``ceph-disk`` systemd units used | |
| 18 | to trigger devices at startup, relying on basic (customizable) JSON | |
| 19 | configuration and systemd for starting up OSDs. | |
| 28e407b8 AA |
20 | |
| 21 | This process involves two steps: | |
| 22 | ||
| 23 | #. :ref:`Scan <ceph-volume-simple-scan>` the running OSD or the data device | |
| 24 | #. :ref:`Activate <ceph-volume-simple-activate>` the scanned OSD | |
| 25 | ||
| 26 | The scanning will infer everything that ``ceph-volume`` needs to start the OSD, | |
| 27 | so that when activation is needed, the OSD can start normally without getting | |
| 28 | interference from ``ceph-disk``. | |
| 29 | ||
| 30 | As part of the activation process the systemd units for ``ceph-disk`` in charge | |
| 31 | of reacting to ``udev`` events, are linked to ``/dev/null`` so that they are | |
| 32 | fully inactive. |