5 *config-key* is a general-purpose key/value storage service offered by
6 the mons. Generally speaking, you can put whatever you want there.
7 Current in-tree users should be captured here with their key layout
15 dm-crypt/osd/$OSD_UUID/luks = <json string>
17 The JSON payload has the form::
19 { "dm-crypt": <secret> }
21 where the secret is a base64 encoded LUKS key.
23 Created by the 'osd new' command (see OSDMonitor.cc).
25 Consumed by ceph-volume, and similar tools. Normally access to the
26 dm-crypt/osd/$OSD_UUID prefix is allowed by a client.osd-lockbox.$OSD_UUID
27 cephx key, such that only the appropriate host can retrieve the LUKS key (which
28 in turn decrypts the actual raw key, also stored on the device itself).
34 The convention for keys is::
36 mgr/$MODULE/$option = $value
40 mgr/$MODULE/$MGRID/$option = $value
44 mgr/dashboard/server_port = 80
45 mgr/dashboard/foo/server_addr = 1.2.3.4
46 mgr/dashboard/bar/server_addr = 1.2.3.5
52 Configuration options for clients and daemons are also stored in config-key.
56 config/$option = $value
57 config/$type/$option = $value
58 config/$type.$id/$option = $value
59 config/$type.$id/$mask[/$mask2...]/$option = $value
63 * `type` is a daemon type (`osd`, `mon`, `mds`, `mgr`, `client`)
64 * `id` is a daemon id (e.g., `0`, `foo`), such that `$type.$id` is something like `osd.123` or `mds.foo`)
65 * `mask` restricts who the option applies to, and can take two forms:
67 #. `$crush_type:$crush_value`. For example, `rack:foorack`
68 #. `class:$classname`, in reference to CRUSH device classes (e.g., `ssd`)