WRO installation procedure revision for Distributed Cloud

Update: Fixed al comments received.

solved merged conflict

Added new requirements for Central Cloud preparation.

Change-Id: I28821041c65e61f6b8067bf0703d62441a32f14e
Signed-off-by: Petsy Mathew <petsy.mathew@windriver.com>

doc/source/application-ref/application-reference-8916dfe370cd.rst

@@ -35,11 +35,10 @@ each application.
 |prod| provides a set of commands for managing the lifecycle of these
 containerized Platform Applications. For more information, see :ref:`application-management-commands`.
 
-Relationships between applications can also be defined to ensure that dependencies
-are handled in the correct sequence during deployment. For more information on
-managing these dependencies, see the `StarlingX Wiki
-<https://wiki.openstack.org/wiki/StarlingX/Containers/Applications/AppIntegration#metadata.yaml>`_.
-
+Some applications depend on others, requiring system applications to be
+uploaded and applied in a specific order. For more information on these
+dependencies, refer to the individual application entries in the table below,
+which include links to detailed documentation for each application.
 
 
 .. only:: partner
@@ -55,7 +54,6 @@ managing these dependencies, see the `StarlingX Wiki
     occur automatically when patches are removed. For uploaded  applications,
     manual updates require deleting the existing version before uploading a new
     one.
-
    
 
 

doc/source/dist_cloud/openstack/openstack-running-in-subcloud-255c72deaa1f.rst

@@ -3,45 +3,71 @@
 
 .. _openstack-running-in-subcloud-255c72deaa1f:
 
-============================
-Deploy Openstack in Subcloud
-============================
+==============================
+Deploy OpenStack in a Subcloud
+==============================
 
-This section provides the steps to support the |prod-os| in a subcloud deployment.
-
-.. note::
-    |prod-os| is not supported on a central cloud.
+|prod-os| is supported in Distributed Cloud environments. You can currently
+deploy it only on subclouds, not on the Central Cloud (System Controller).
+However, you will need to complete a few setup tasks in the Central Cloud before
+installing |prod-os| in any subcloud.
 
 
 .. rubric:: |proc|
 
-#.  On the System Controller
+#.  **Prepare the Central Cloud**. 
 
-    #.  Configure the |prod-os| user group before trying to upload stx-openstack
-        to any subcloud. For example,
+    #. Create |prod-os| Group in |LDAP|. Before uploading the |prefix|-openstack
+       application to any subcloud, ensure the OpenStack user group is
+       configured in |LDAP| on the System Controller. This involves creating the
+       OpenStack group with a fixed Group ID.
 
-        .. code-block:: none
+       .. code-block:: none
+            
+           ~(keystone_admin)]$ sudo ldapaddgroup openstack 1001
+            
+       This step ensures that OpenStack-related files and processes have
+       consistent group ownership across clouds. 
 
-            ~(keystone_admin)]$ sudo ldapaddgroup openstack 1001
+    #. Upload |prod-os| application with images. Use the --images
+       option to upload the application tarball and fetch the container
+       images up front.
 
-#.  On the subcloud
+       .. code-block:: none
 
-    #. Upload the |prefix|-openstack application. For example: 
+           ~(keystone_admin)]$ system application-upload --images <openstack-application-tarball>
 
-    .. code-block:: none
+       This step extracts the deployment tarball, downloads all
+       referenced container images, and pushes them to the local registry on
+       the Central Cloud. This ensures that subclouds can access the required
+       images during deployment. 
 
-        ~(keystone_admin)]$ system application-upload <helm-chart>
+#.  **Prepare the Subcloud**.
+    
+    Once the Central Cloud is configured, |prod-os| images will be in the
+    Central Cloud registry. After you have |prod| installed in the subcloud,
+    you now can proceed with |prod-os| installation in the subcloud.
 
+    #. Upload the |prod-os| application tarball to the subcloud (if not already
+       present).
 
-    #.  Apply the |prefix|-openstack application to subcloud.
+       .. code-block:: none
 
-        .. code-block:: none
+           ~(keystone_admin)]$ system application-upload <application-tarball>
 
-            ~(keystone_admin)]$ system application-apply |prefix|-openstack
+    #. Apply the |prod-os| application to subcloud using the following
+       command.
 
+       .. parsed-literal::
 
-    #.  Confirm that the apply operation completed successfully.
+           ~(keystone_admin)]$ system application-apply |prefix|-openstack
 
-        .. code-block:: none
+       .. note::
+        
+           This step may take several minutes to complete.
 
-            ~(keystone_admin)]$ system application-list
+    #. Confirm that the apply operation completed successfully.
+
+       .. parsed-literal::
+
+           ~(keystone_admin)]$ system application-show |prefix|-openstack