doc/cephadm/service-management: Move "Updating Service Specifications"

into "Service Specification"

Signed-off-by: Sebastian Wagner <sewagner@redhat.com>

diff --git a/doc/cephadm/service-management.rst b/doc/cephadm/service-management.rst
index 284b1557ab73512bd21cdd42a0b85712ed661c1b..eaf0be9060f6987b7734343e04e29fd21050b94c 100644 (file)
--- a/doc/cephadm/service-management.rst
+++ b/doc/cephadm/service-management.rst
@@ -144,6 +144,32 @@ following these instructions:
 
 The Specification can then be changed and re-applied as above.
 
+Updating Service Specifications
+-------------------------------
+
+The Ceph Orchestrator maintains a declarative state of each
+service in a ``ServiceSpec``. For certain operations, like updating
+the RGW HTTP port, we need to update the existing
+specification.
+
+1. List the current ``ServiceSpec``:
+
+   .. prompt:: bash #
+
+    ceph orch ls --service_name=<service-name> --export > myservice.yaml
+
+2. Update the yaml file:
+
+   .. prompt:: bash #
+
+    vi myservice.yaml
+
+3. Apply the new ``ServiceSpec``:
+
+   .. prompt:: bash #
+
+    ceph orch apply -i myservice.yaml [--dry-run]
+
 .. _orchestrator-cli-placement-spec:
 
 Placement Specification
@@ -363,33 +389,6 @@ YAML can also be used to specify limits on hosts:
         - host2
         - host3
 
-Updating Service Specifications
-===============================
-
-The Ceph Orchestrator maintains a declarative state of each
-service in a ``ServiceSpec``. For certain operations, like updating
-the RGW HTTP port, we need to update the existing
-specification.
-
-1. List the current ``ServiceSpec``:
-
-   .. prompt:: bash #
-
-    ceph orch ls --service_name=<service-name> --export > myservice.yaml
-
-2. Update the yaml file:
-
-   .. prompt:: bash #
-
-    vi myservice.yaml
-
-3. Apply the new ``ServiceSpec``:
-   
-   .. prompt:: bash #
-
-    ceph orch apply -i myservice.yaml [--dry-run]
-
-
 .. _orch-rm:
 
 Removing a Service