doc: add detailed scenarios examples

wip

Signed-off-by: Guillaume Abrioux <gabrioux@redhat.com>
update-doc
Guillaume Abrioux 2021-03-24 13:51:36 +01:00
parent 2768aea832
commit 8086e50484
3 changed files with 77 additions and 0 deletions

View File

@ -247,6 +247,17 @@ When deploying RGW instance(s) you are required to set the ``radosgw_interface``
``radosgw_address`` must be set the same way than ``monitor_address``.
Detailed scenarios examples
---------------------------
You can find more detailed scenarios in link below.
.. toctree::
:maxdepth: 1
scenarios/index
``ceph.conf`` Configuration File
---------------------------------

View File

@ -0,0 +1,57 @@
*************************
Deploying a basic cluster
*************************
Topology
========
Here we are going to describe how to deploy 3 monitors, 3 managers and 2 osds.
Writing your inventory
----------------------
.. code-block:: ini
[mons]
mon0
mon1
mon2
[mgrs]
mgr0
mgr1
mgr2
[osds]
osd0
osd1
.. note::
If you don't define a ``[mgrs]`` section, ceph-ansible will automatically collocate 1 ceph manager daemon on each monitor node.
Configuring your cluster
------------------------
Configuring your cluster can be done in many ways. There are a lot of variables that are either mandatory or optional according what you want to achieve.
By the way, these variables can be set at different places: inventory, host_vars, group_vars, etc.
We will try to identify the most common cases and cover them through this documentation.
- **ceph_origin**:
- valid value:
- ``repository``: Ceph will be get through a dedicated repository
- ``distro``: Ceph will be get through the main repository already present on your distro.
- ``local``: Ceph binaries will be copied over from the local machine
- **ceph_repository**:
- Must be set when ``ceph_origin: repository``
- valid value:
- ``community``:
- ``rhcs``
- ``dev``
- ``custom``
- ``uca``

View File

@ -0,0 +1,9 @@
Examples of detailed scenarios
------------------------------
.. toctree::
:maxdepth: 1
basic_cluster