From 06cb5652157a53b25e8ae588f375548b1df72d2d Mon Sep 17 00:00:00 2001 From: Ville Ojamo <14869000+bluikko@users.noreply.github.com> Date: Fri, 27 Jan 2023 14:54:11 +0700 Subject: [PATCH] doc/rados/configuration: add links to MON DNS Add two links to MON DNS lookup and an anchor in the destination document. Signed-off-by: Ville Ojamo <14869000+bluikko@users.noreply.github.com> --- doc/rados/configuration/ceph-conf.rst | 35 +++++++++++----------- doc/rados/configuration/mon-lookup-dns.rst | 2 ++ 2 files changed, 20 insertions(+), 17 deletions(-) diff --git a/doc/rados/configuration/ceph-conf.rst b/doc/rados/configuration/ceph-conf.rst index 6bf34017964e9..f62a215458d36 100644 --- a/doc/rados/configuration/ceph-conf.rst +++ b/doc/rados/configuration/ceph-conf.rst @@ -76,19 +76,19 @@ include the following: .. confval:: mon_host_override - :confval:`mon_dns_srv_name` -- :confval:`mon_data`, :confval:`osd_data`, :confval:`mds_data`, +- :confval:`mon_data`, :confval:`osd_data`, :confval:`mds_data`, :confval:`mgr_data`, and similar options that define which local directory the daemon stores its data in. -- :confval:`keyring`, :confval:`keyfile`, and/or :confval:`key`, which can be +- :confval:`keyring`, :confval:`keyfile`, and/or :confval:`key`, which can be used to specify the authentication credential to use to authenticate with the monitor. Note that in most cases the default keyring location is in the data directory specified above. In most cases, there is no reason to modify the default values of these options. However, there is one exception to this: the :confval:`mon_host` -option that identifies the addresses of the cluster's monitors. But when DNS is -used to identify monitors, a local Ceph configuration file can be avoided -entirely. +option that identifies the addresses of the cluster's monitors. But when +:ref:`DNS is used to identify monitors`, a local Ceph +configuration file can be avoided entirely. Skipping monitor config @@ -178,7 +178,7 @@ If multiple values of the same configuration option are specified in the same section, the last value specified takes precedence. Note that values from the local configuration file always take precedence over -values from the monitor configuration database, regardless of the section in +values from the monitor configuration database, regardless of the section in which they appear. .. _ceph-metavariables: @@ -191,7 +191,7 @@ metavariable is set in a configuration value, Ceph expands the metavariable at the time the configuration value is used. In this way, Ceph metavariables behave similarly to the way that variable expansion works in the Bash shell. -Ceph supports the following metavariables: +Ceph supports the following metavariables: .. describe:: $cluster @@ -273,7 +273,7 @@ surrounded by square brackets. For example: [global] debug_ms = 0 - + [osd] debug_ms = 1 @@ -427,7 +427,8 @@ stored in this database. Some settings might need to be stored in local configuration files because they affect the ability of the process to connect to the monitors, to authenticate, and to fetch configuration information. In most cases this applies only to the -``mon_host`` option. This issue can be avoided by using DNS SRV records. +``mon_host`` option. This issue can be avoided by using :ref:`DNS SRV +records`. Sections and masks ------------------ @@ -476,13 +477,13 @@ The following CLI commands are used to configure the cluster: * ``ceph config set