development branch. You may choose other branches too.
- ``main``: The unstable development branch.
-- ``stable-release-name``: The name of the stable, `Active Releases`_. e.g. ``Pacific``
+- ``stable-release-name``: The name of the stable, :ref:`active-releases`. e.g. ``Pacific``
- ``next``: The release candidate branch.
::
git checkout main
-
-.. _Active Releases: https://docs.ceph.com/en/latest/releases/#active-releases
https://download.ceph.com/rpm-{version}
-The major releases of Ceph are summarized at: `Releases`_
+The major releases of Ceph are summarized at: :ref:`Releases <ceph-releases-index>`
.. tip:: For non-US users: There might be a mirror close to you where
to download Ceph from. For more information see: `Ceph Mirrors`_.
-.. _Releases: https://docs.ceph.com/en/latest/releases/
.. _the testing Debian repository: https://download.ceph.com/debian-testing/dists
.. _the shaman page: https://shaman.ceph.com
.. _Ceph Mirrors: ../mirrors
============
There are several methods for getting Ceph software. The easiest and most common
-method is to `get packages`_ by adding repositories for use with package
+method is to :ref:`get packages <packages>` by adding repositories for use with package
management tools such as the Advanced Package Tool (APT) or Yellowdog Updater,
Modified (YUM). You may also retrieve pre-compiled packages from the Ceph
repository. Finally, you can retrieve tarballs or clone the Ceph source code
.. toctree::
:maxdepth: 2
-.. _get packages: ../get-packages
enabled = 1
#. Ensure your YUM ``ceph.repo`` entry includes ``priority=2``. See
- `Get Packages`_ for details::
+ :ref:`packages` for details::
[ceph]
name=Ceph packages for $basearch
sudo ninja install
If you install Ceph locally, ``ninja`` will place the executables in
-``usr/local/bin``. You may add the Ceph configuration file to the
+``usr/local/bin``. You may add the :ref:`Ceph configuration file <configuring-ceph>` to the
``usr/local/bin`` directory to run Ceph from a single directory.
-.. _Get Packages: ../get-packages
a ``client.admin`` user. So you must generate the admin user and keyring,
and you must also add the ``client.admin`` user to the monitor keyring.
-The foregoing requirements do not imply the creation of a Ceph Configuration
-file. However, as a best practice, we recommend creating a Ceph configuration
+The foregoing requirements do not imply the creation of a :ref:`Ceph Configuration
+file <configuring-ceph>`. However, as a best practice, we recommend creating a Ceph configuration
file and populating it with the ``fsid``, the ``mon initial members`` and the
``mon host`` settings.
-3 1 host osd-node2
1 1 osd.1 up 1
-To add (or remove) additional monitors, see `Add/Remove Monitors`_.
+To add (or remove) additional monitors, see :ref:`adding-and-removing-monitors`.
To add (or remove) additional Ceph OSD Daemons, see `Add/Remove OSDs`_.
-.. _Add/Remove Monitors: ../../rados/operations/add-or-rm-mons
.. _Add/Remove OSDs: ../../rados/operations/add-or-rm-osds
.. _Network Configuration Reference: ../../rados/configuration/network-config-ref
.. _Monitor Config Reference - Data: ../../rados/configuration/mon-config-ref#data
For example, when you run multiple clusters in a :ref:`multisite configuration <multisite>`,
the cluster name (e.g., ``us-west``, ``us-east``) identifies the cluster for
the current CLI session. **Note:** To identify the cluster name on the
- command line interface, specify the a Ceph configuration file with the
+ command line interface, specify a :ref:`Ceph configuration file <configuring-ceph>` with the
cluster name (e.g., ``ceph.conf``, ``us-west.conf``, ``us-east.conf``, etc.).
Also see CLI usage (``ceph --cluster {cluster-name}``).
-3 1 host node2
1 1 osd.1 up 1
-To add (or remove) additional monitors, see `Add/Remove Monitors`_.
+To add (or remove) additional monitors, see :ref:`adding-and-removing-monitors`.
To add (or remove) additional Ceph OSD Daemons, see `Add/Remove OSDs`_.
-.. _Add/Remove Monitors: ../../rados/operations/add-or-rm-mons
.. _Add/Remove OSDs: ../../rados/operations/add-or-rm-osds
.. _Network Configuration Reference: ../../rados/configuration/network-config-ref
.. _Monitor Config Reference - Data: ../../rados/configuration/mon-config-ref#data