Skip to content

Commit 0455da2

Browse files
Merge pull request ceph#55670 from zdover23/wip-doc-2024-02-21-rados-ops-add-or-rm-mons
doc/rados: fix broken links
2 parents 8ffdab7 + 2e25193 commit 0455da2

File tree

1 file changed

+12
-11
lines changed

1 file changed

+12
-11
lines changed

doc/rados/operations/add-or-rm-mons.rst

Lines changed: 12 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -344,24 +344,25 @@ addresses, repeat this process.
344344
Changing a Monitor's IP address (Advanced Method)
345345
-------------------------------------------------
346346

347-
There are cases in which the method outlined in :ref"`<Changing a Monitor's IP
348-
Address (Preferred Method)> operations_add_or_rm_mons_changing_mon_ip` cannot
349-
be used. For example, it might be necessary to move the cluster's monitors to a
350-
different network, to a different part of the datacenter, or to a different
351-
datacenter altogether. It is still possible to change the monitors' IP
352-
addresses, but a different method must be used.
347+
There are cases in which the method outlined in
348+
:ref:`operations_add_or_rm_mons_changing_mon_ip` cannot be used. For example,
349+
it might be necessary to move the cluster's monitors to a different network, to
350+
a different part of the datacenter, or to a different datacenter altogether. It
351+
is still possible to change the monitors' IP addresses, but a different method
352+
must be used.
353+
353354

354355
For such cases, a new monitor map with updated IP addresses for every monitor
355356
in the cluster must be generated and injected on each monitor. Although this
356357
method is not particularly easy, such a major migration is unlikely to be a
357358
routine task. As stated at the beginning of this section, existing monitors are
358359
not supposed to change their IP addresses.
359360

360-
Continue with the monitor configuration in the example from :ref"`<Changing a
361-
Monitor's IP Address (Preferred Method)>
362-
operations_add_or_rm_mons_changing_mon_ip` . Suppose that all of the monitors
363-
are to be moved from the ``10.0.0.x`` range to the ``10.1.0.x`` range, and that
364-
these networks are unable to communicate. Carry out the following procedure:
361+
Continue with the monitor configuration in the example from
362+
:ref:`operations_add_or_rm_mons_changing_mon_ip`. Suppose that all of the
363+
monitors are to be moved from the ``10.0.0.x`` range to the ``10.1.0.x`` range,
364+
and that these networks are unable to communicate. Carry out the following
365+
procedure:
365366

366367
#. Retrieve the monitor map (``{tmp}`` is the path to the retrieved monitor
367368
map, and ``{filename}`` is the name of the file that contains the retrieved

0 commit comments

Comments
 (0)