doc/cephadm: Add `networks` to spec documentation

Signed-off-by: Sebastian Wagner <sewagner@redhat.com>
(cherry picked from commit fd32c1651b95ac14662bb5048e42f92fc1f45e56)

diff --git a/doc/cephadm/monitoring.rst b/doc/cephadm/monitoring.rst
index e87a006a0906acdb4559fb0afb3285fb1fe6214c..91b8742f3cfb9fa3653424e2bd6f4834ca79bed4 100644 (file)
--- 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 10d0280e4a51279c6d5cafc85d68cb8f58a9f7b7..6d382b6ec7b08cd2f00e653ef8819642f9e25bc4 100644 (file)
--- 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