blob: 96b7c2dda78a4476bed832fcc73664c89e65e5f9 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
|
===========
MDS Service
===========
.. _orchestrator-cli-cephfs:
Deploy CephFS
=============
One or more MDS daemons is required to use the :term:`CephFS` file system.
These are created automatically if the newer ``ceph fs volume``
interface is used to create a new file system. For more information,
see :ref:`fs-volumes-and-subvolumes`.
For example:
.. prompt:: bash #
ceph fs volume create <fs_name> --placement="<placement spec>"
where ``fs_name`` is the name of the CephFS and ``placement`` is a
:ref:`orchestrator-cli-placement-spec`. For example, to place
MDS daemons for the new ``foo`` volume on hosts labeled with ``mds``:
.. prompt:: bash #
ceph fs volume create foo --placement="label:mds"
You can also update the placement after-the-fact via:
.. prompt:: bash #
ceph orch apply mds foo 'mds-[012]'
For manually deploying MDS daemons, use this specification:
.. code-block:: yaml
service_type: mds
service_id: fs_name
placement:
count: 3
label: mds
The specification can then be applied using:
.. prompt:: bash #
ceph orch apply -i mds.yaml
See :ref:`orchestrator-cli-stateless-services` for manually deploying
MDS daemons on the CLI.
Further Reading
===============
* :ref:`ceph-file-system`
|
