From: Sebastian Wagner Date: Tue, 14 Sep 2021 14:07:14 +0000 (+0200) Subject: doc/cephadm: Add `networks` to spec documentation X-Git-Tag: v17.1.0~803^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=refs%2Fpull%2F43160%2Fhead;p=ceph.git doc/cephadm: Add `networks` to spec documentation Signed-off-by: Sebastian Wagner --- diff --git a/doc/cephadm/monitoring.rst b/doc/cephadm/monitoring.rst index e87a006a0906..91b8742f3cfb 100644 --- a/doc/cephadm/monitoring.rst +++ b/doc/cephadm/monitoring.rst @@ -83,6 +83,8 @@ steps below: ceph orch apply grafana +.. _cephadm-monitoring-networks-ports: + Networks and Ports ~~~~~~~~~~~~~~~~~~ diff --git a/doc/cephadm/service-management.rst b/doc/cephadm/service-management.rst index 10d0280e4a51..6d382b6ec7b0 100644 --- a/doc/cephadm/service-management.rst +++ b/doc/cephadm/service-management.rst @@ -80,6 +80,8 @@ deployment of services. Here is an example of a service specification in YAML: - host2 - host3 unmanaged: false + networks: + - 192.169.142.0/24 ... In this example, the properties of this service specification are: @@ -94,6 +96,10 @@ In this example, the properties of this service specification are: The name of the service. * ``placement`` See :ref:`orchestrator-cli-placement-spec`. +* ``networks``: A list of network identities instructing the daemons to only bind + on the particular networks in that list. In case the cluster is distributed across multiple + networks, you can add multiple networks. See :ref:`cephadm-monitoring-networks-ports`, + :ref:`cephadm-rgw-networks` and :ref:`cephadm-mgr-networks`. * ``unmanaged`` If set to ``true``, the orchestrator will not deploy nor remove any daemon associated with this service. Placement and all other properties will be ignored. This is useful, if you do not want this service to be