In DC system route needed in compute nodes to access ldap service (r8, dsr8)

- Indented the post-req.
- Removed post-req from:
  installing-and-provisioning-a-subcloud.rst and
  installing-and-provisioning-the-central-cloud.rst
- Removed "compute" word from topic.
- Updated a topic level.
- Added a requirement to Postrequisites section as required.
- Added the post req information for all Insall guides.

Signed-off-by: Elaine Fonaro <elaine.fonaro@windriver.com>
Change-Id: Ida5ed810b413f35d2078f6e3f3b1c53065bece5d
Signed-off-by: Elaine Fonaro <elaine.fonaro@windriver.com>

doc/source/dist_cloud/kubernetes/installing-a-subcloud-using-redfish-platform-management-service.rst

@@ -477,3 +477,79 @@ subcloud, the subcloud installation has these phases:
 -   For more information on bootstrapping and deploying, see the procedures
     listed under :ref:`install-a-subcloud`.
 
+-   Add static route for nodes in subcloud to access openldap service.
+
+    In DC system, openldap service is running on Central Cloud. In order for the nodes
+    in the subclouds to access openldap service, such as ssh to the nodes as openldap
+    users, a static route to the System Controller is required to be added in these
+    nodes. This applies to controller nodes, worker nodes and storage nodes (nodes
+    that have sssd running).
+
+    The static route can be added on each of the nodes in the subcloud using system
+    CLI.
+
+    The following examples show how to add the static route in controller node and
+    worker node:
+
+    .. code-block:: none
+
+        system host-route-add controller-0 mgmt0 <Central Cloud mgmt subnet> 64 <Gateway IP address>
+        system host-route-add compute-0 mgmt0 <Central Cloud mgmt subnet> 64 <Gateway IP address>
+
+    The static route can also be added using Deployment Manager by adding the route
+    in its configuration file.
+
+    The following examples show adding the route configuration in controller and
+    worker host profiles of the deployment manager's configuration file:
+
+    .. code-block:: none
+
+        Controller node:
+        ---
+        apiVersion: starlingx.windriver.com/v1
+        kind: HostProfile
+        metadata:
+          labels:
+            controller-tools.k8s.io: "1.0"
+          name: controller-0-profile
+          namespace: deployment
+        spec:
+          administrativeState: unlocked
+          bootDevice: /dev/disk/by-path/pci-0000:c3:00.0-nvme-1
+          console: ttyS0,115200n8
+          installOutput: text
+          ......
+          routes:
+              - gateway: <Gateway IP address>
+            activeinterface: mgmt0
+            metric: 1
+            prefix: 64
+            subnet: <Central Cloud mgmt subnet>
+
+        Worker node:
+        ---
+        apiVersion: starlingx.windriver.com/v1
+        kind: HostProfile
+        metadata:
+          labels:
+            controller-tools.k8s.io: "1.0"
+          name: compute-0-profile
+          namespace: deployment
+        spec:
+          administrativeState: unlocked
+          boardManagement:
+            credentials:
+              password:
+                secret: bmc-secret
+            type: dynamic
+          bootDevice: /dev/disk/by-path/pci-0000:00:1f.2-ata-1.0
+          clockSynchronization: ntp
+          console: ttyS0,115200n8
+          installOutput: text
+          ......
+          routes:
+              - gateway: <Gateway IP address>
+            interface: mgmt0
+            metric: 1
+            prefix: 64
+            subnet: <Central Cloud mgmt subnet>

doc/source/dist_cloud/kubernetes/installing-a-subcloud-without-redfish-platform-management-service.rst

@@ -308,3 +308,80 @@ subcloud, the subcloud installation process has two phases:
 
 -   For more information on bootstrapping and deploying, see the procedures
     listed under :ref:`install-a-subcloud`.
+
+-   Add static route for nodes in subcloud to access openldap service.
+
+    In DC system, openldap service is running on Central Cloud. In order for the nodes
+    in the subclouds to access openldap service, such as ssh to the nodes as openldap
+    users, a static route to the System Controller is required to be added in these
+    nodes. This applies to controller nodes, worker nodes and storage nodes (nodes
+    that have sssd running).
+
+    The static route can be added on each of the nodes in the subcloud using system
+    CLI.
+
+    The following examples show how to add the static route in controller node and
+    worker node:
+
+    .. code-block:: none
+
+        system host-route-add controller-0 mgmt0 <Central Cloud mgmt subnet> 64 <Gateway IP address>
+        system host-route-add compute-0 mgmt0 <Central Cloud mgmt subnet> 64 <Gateway IP address>
+
+    The static route can also be added using Deployment Manager by adding the route
+    in its configuration file.
+
+    The following examples show adding the route configuration in controller and
+    worker host profiles of the deployment manager's configuration file:
+
+    .. code-block:: none
+
+        Controller node:
+        ---
+        apiVersion: starlingx.windriver.com/v1
+        kind: HostProfile
+        metadata:
+          labels:
+            controller-tools.k8s.io: "1.0"
+          name: controller-0-profile
+          namespace: deployment
+        spec:
+          administrativeState: unlocked
+          bootDevice: /dev/disk/by-path/pci-0000:c3:00.0-nvme-1
+          console: ttyS0,115200n8
+          installOutput: text
+          ......
+          routes:
+              - gateway: <Gateway IP address>
+            activeinterface: mgmt0
+            metric: 1
+            prefix: 64
+            subnet: <Central Cloud mgmt subnet>
+
+        Worker node:
+        ---
+        apiVersion: starlingx.windriver.com/v1
+        kind: HostProfile
+        metadata:
+          labels:
+            controller-tools.k8s.io: "1.0"
+          name: compute-0-profile
+          namespace: deployment
+        spec:
+          administrativeState: unlocked
+          boardManagement:
+            credentials:
+              password:
+                secret: bmc-secret
+            type: dynamic
+          bootDevice: /dev/disk/by-path/pci-0000:00:1f.2-ata-1.0
+          clockSynchronization: ntp
+          console: ttyS0,115200n8
+          installOutput: text
+          ......
+          routes:
+              - gateway: <Gateway IP address>
+            interface: mgmt0
+            metric: 1
+            prefix: 64
+            subnet: <Central Cloud mgmt subnet>

doc/source/dist_cloud/kubernetes/reinstalling-a-subcloud-with-redfish-platform-management-service.rst

@@ -184,3 +184,105 @@ Executing the dcmanager subcloud reinstall command in the Central Cloud:
 
     #.  Click **Apply** to apply the change.
 
+.. rubric:: |postreq|
+
+-   Provision the newly installed and bootstrapped subcloud.  For detailed
+    |prod| deployment procedures for the desired deployment configuration of
+    the subcloud, see the post-bootstrap steps of the |_link-inst-book|.
+
+-   Check and update docker registry credentials on the subcloud:
+
+    .. code-block:: none
+
+        REGISTRY="docker-registry"
+        SECRET_UUID='system service-parameter-list | fgrep
+        $REGISTRY | fgrep auth-secret | awk '{print $10}''
+        SECRET_REF='openstack secret list | fgrep $
+        {SECRET_UUID} | awk '{print $2}''
+        openstack secret get ${SECRET_REF} --payload -f value
+
+    The secret payload should be :command:`username: sysinv password:<password>`.
+    If the secret payload is :command:`username: admin password:<password>`,
+    see, :ref:`Updating Docker Registry Credentials on a
+    Subcloud <updating-docker-registry-credentials-on-a-subcloud>` for more
+    information.
+
+-   For more information on bootstrapping and deploying, see the procedures
+    listed under :ref:`install-a-subcloud`.
+
+-   Add static route for nodes in subcloud to access openldap service.
+
+    In DC system, openldap service is running on Central Cloud. In order for the nodes
+    in the subclouds to access openldap service, such as ssh to the nodes as openldap
+    users, a static route to the System Controller is required to be added in these
+    nodes. This applies to controller nodes, worker nodes and storage nodes (nodes
+    that have sssd running).
+
+    The static route can be added on each of the nodes in the subcloud using system
+    CLI.
+
+    The following examples show how to add the static route in controller node and
+    worker node:
+
+    .. code-block:: none
+
+        system host-route-add controller-0 mgmt0 <Central Cloud mgmt subnet> 64 <Gateway IP address>
+        system host-route-add compute-0 mgmt0 <Central Cloud mgmt subnet> 64 <Gateway IP address>
+
+    The static route can also be added using Deployment Manager by adding the route
+    in its configuration file.
+
+    The following examples show adding the route configuration in controller and
+    worker host profiles of the deployment manager's configuration file:
+
+    .. code-block:: none
+
+        Controller node:
+        ---
+        apiVersion: starlingx.windriver.com/v1
+        kind: HostProfile
+        metadata:
+          labels:
+            controller-tools.k8s.io: "1.0"
+          name: controller-0-profile
+          namespace: deployment
+        spec:
+          administrativeState: unlocked
+          bootDevice: /dev/disk/by-path/pci-0000:c3:00.0-nvme-1
+          console: ttyS0,115200n8
+          installOutput: text
+          ......
+          routes:
+              - gateway: <Gateway IP address>
+            activeinterface: mgmt0
+            metric: 1
+            prefix: 64
+            subnet: <Central Cloud mgmt subnet>
+
+        Worker node:
+        ---
+        apiVersion: starlingx.windriver.com/v1
+        kind: HostProfile
+        metadata:
+          labels:
+            controller-tools.k8s.io: "1.0"
+          name: compute-0-profile
+          namespace: deployment
+        spec:
+          administrativeState: unlocked
+          boardManagement:
+            credentials:
+              password:
+                secret: bmc-secret
+            type: dynamic
+          bootDevice: /dev/disk/by-path/pci-0000:00:1f.2-ata-1.0
+          clockSynchronization: ntp
+          console: ttyS0,115200n8
+          installOutput: text
+          ......
+          routes:
+              - gateway: <Gateway IP address>
+            interface: mgmt0
+            metric: 1
+            prefix: 64
+            subnet: <Central Cloud mgmt subnet>

doc/source/dist_cloud/kubernetes/subcloud-deployment-with-local-installation-4982449058d5.rst

@@ -56,6 +56,109 @@ components and produces a 'Prestaging ISO'.
     fail, then ``Miniboot`` proceeds to install the subcloud using the existing
     Remote Install.
 
+.. rubric:: |postreq|
+
+-   Provision the newly installed and bootstrapped subcloud.  For detailed
+    |prod| deployment procedures for the desired deployment configuration of
+    the subcloud, see the post-bootstrap steps of the |_link-inst-book|.
+
+-   Check and update docker registry credentials on the subcloud:
+
+    .. code-block:: none
+
+        REGISTRY="docker-registry"
+        SECRET_UUID='system service-parameter-list | fgrep
+        $REGISTRY | fgrep auth-secret | awk '{print $10}''
+        SECRET_REF='openstack secret list | fgrep $
+        {SECRET_UUID} | awk '{print $2}''
+        openstack secret get ${SECRET_REF} --payload -f value
+
+    The secret payload should be :command:`username: sysinv password:<password>`.
+    If the secret payload is :command:`username: admin password:<password>`,
+    see, :ref:`Updating Docker Registry Credentials on a
+    Subcloud <updating-docker-registry-credentials-on-a-subcloud>` for more
+    information.
+
+-   For more information on bootstrapping and deploying, see the procedures
+    listed under :ref:`install-a-subcloud`.
+
+-   Add static route for nodes in subcloud to access openldap service.
+
+    In DC system, openldap service is running on Central Cloud. In order for the nodes
+    in the subclouds to access openldap service, such as ssh to the nodes as openldap
+    users, a static route to the System Controller is required to be added in these
+    nodes. This applies to controller nodes, worker nodes and storage nodes (nodes
+    that have sssd running).
+
+    The static route can be added on each of the nodes in the subcloud using system
+    CLI.
+
+    The following examples show how to add the static route in controller node and
+    worker node:
+
+    .. code-block:: none
+
+        system host-route-add controller-0 mgmt0 <Central Cloud mgmt subnet> 64 <Gateway IP address>
+        system host-route-add compute-0 mgmt0 <Central Cloud mgmt subnet> 64 <Gateway IP address>
+
+    The static route can also be added using Deployment Manager by adding the route
+    in its configuration file.
+
+    The following examples show adding the route configuration in controller and
+    worker host profiles of the deployment manager's configuration file:
+
+    .. code-block:: none
+
+        Controller node:
+        ---
+        apiVersion: starlingx.windriver.com/v1
+        kind: HostProfile
+        metadata:
+          labels:
+            controller-tools.k8s.io: "1.0"
+          name: controller-0-profile
+          namespace: deployment
+        spec:
+          administrativeState: unlocked
+          bootDevice: /dev/disk/by-path/pci-0000:c3:00.0-nvme-1
+          console: ttyS0,115200n8
+          installOutput: text
+          ......
+          routes:
+              - gateway: <Gateway IP address>
+            activeinterface: mgmt0
+            metric: 1
+            prefix: 64
+            subnet: <Central Cloud mgmt subnet>
+
+        Worker node:
+        ---
+        apiVersion: starlingx.windriver.com/v1
+        kind: HostProfile
+        metadata:
+          labels:
+            controller-tools.k8s.io: "1.0"
+          name: compute-0-profile
+          namespace: deployment
+        spec:
+          administrativeState: unlocked
+          boardManagement:
+            credentials:
+              password:
+                secret: bmc-secret
+            type: dynamic
+          bootDevice: /dev/disk/by-path/pci-0000:00:1f.2-ata-1.0
+          clockSynchronization: ntp
+          console: ttyS0,115200n8
+          installOutput: text
+          ......
+          routes:
+              - gateway: <Gateway IP address>
+            interface: mgmt0
+            metric: 1
+            prefix: 64
+            subnet: <Central Cloud mgmt subnet>
+
 .. _local-install-bundle-section:
 
 --------------------