Merge "Re-arranged DC Horizon page"

doc/source/dist_cloud/kubernetes/apply-a-kubernetes-upgrade-strategy-using-horizon-2bb24c72e947.rst

@@ -0,0 +1,40 @@
+.. _apply-a-kubernetes-upgrade-strategy-using-horizon-2bb24c72e947:
+
+=================================================
+Apply a Kubernetes Upgrade Strategy using Horizon
+=================================================
+
+You can use the Horizon Web interface to upgrade Kubernetes across the
+Distributed Cloud system by applying the Kubernetes upgrade strategy for 
+Distributed Cloud Orchestration.
+
+.. rubric:: |prereq|
+
+Before you can apply the Kubernetes Upgrade strategy, you must upload and apply
+one or more updates to the SystemController / central update repository, create
+the Kubernetes strategy for subclouds, and optionally adjust the configuration
+settings for updating nodes.
+
+.. rubric:: |proc|
+
+#. Select the SystemController region.
+
+#. Select **Distributed Cloud Admin** > **Orchestration**.
+
+#. On the **Orchestration** page, select the **Orchestration Strategy** tab.
+
+   .. figure:: figures/bqu1525123082913.png
+
+       Orchestration Strategy
+
+#. Click Apply Strategy.
+
+   *  To monitor the progress of the overall Kubernetes Upgrade orchestration,
+      use the **Orchestration Strategy** tab.
+
+   *  To monitor the progress of host Kubernetes Upgrade on RegionOne or a
+      subcloud, use the **Host Inventory** page on the subcloud.
+
+
+
+

doc/source/dist_cloud/kubernetes/apply-the-firmware-update-strategy-using-horizon-e78bf11c7189.rst

@@ -0,0 +1,35 @@
+.. _apply-the-firmware-update-strategy-using-horizon-e78bf11c7189:
+
+================================================
+Apply the Firmware Update Strategy using Horizon
+================================================
+
+You can use Horizon to update the device/firmware image across the Distributed
+Cloud system by applying the firmware update strategy for Distributed Cloud
+Update Orchestration.
+
+.. rubric:: |proc|
+
+#. Select the **SystemController** region.
+
+#. Select **Distributed Cloud Admin** > **Orchestration**.
+
+#. On the **Orchestration** page, select the **Orchestration Strategy** tab.
+
+   .. figure:: figures/bqu1525123082913.png
+
+       Orchestration Strategy
+
+#. Click **Apply Strategy**.
+
+   * To monitor the progress of the overall firmware update orchestration, use
+     the **Orchestration Strategy** tab.
+
+   * To monitor the progress of host firmware updates on RegionOne or a
+     subcloud, use the **Host Inventory** page on the subcloud.
+
+
+.. rubric:: |result|
+
+.. procedure results here
+

doc/source/dist_cloud/kubernetes/apply-the-upgrade-strategy-using-horizon-d0aab18cc724.rst

@@ -0,0 +1,37 @@
+.. _apply-the-upgrade-strategy-using-horizon-d0aab18cc724:
+
+========================================
+Apply the Upgrade Strategy using Horizon
+========================================
+
+You can upgrade the platform software across the Distributed Cloud
+system by applying the upgrade strategy for Distributed Cloud
+Upgrade Orchestration.
+
+
+.. rubric:: |prereq|
+
+Create the Upgrade  strategy for subclouds. For more information, see
+:ref:`create-an-upgrade-orchestration-using-horizon-9f8c6c2f3706`.
+
+.. rubric:: |proc|
+
+#. Select the **SystemController** region.
+
+#. Select **Distributed Cloud Admin** > **Orchestration**.
+
+#. On the **Orchestration** page, select the **Orchestration Strategy** tab.
+
+   .. figure:: figures/bqu1525123082913.png
+
+       Orchestration Strategy
+
+#. Click **Apply Strategy**.
+
+   * To monitor the progress of the overall Upgrade orchestration, use the
+     **Orchestration Strategy** tab.
+
+   * To monitor the progress of host Upgrades on RegionOne or a subcloud, use
+     the **Host Inventory** page on the subcloud.
+
+

doc/source/dist_cloud/kubernetes/applying-the-update-strategy-for-distributed-cloud.rst

@@ -6,12 +6,12 @@
 Apply the Update Strategy for Distributed Cloud
 ===============================================
 
-You can update the software across the |prod-dc| system by applying the update
-strategy for |prod-dc| Update Orchestration.
+You can update the platform software across the |prod-dc| system by applying
+the update strategy for |prod-dc| Update Orchestration.
 
 .. rubric:: |context|
 
-You can apply the update strategy from the Horizon Web interface or the CLI .
+You can apply the update strategy from the Horizon Web interface or the CLI.
 To use the CLI, see :ref:`Update Management for Distributed Cloud
 <update-management-for-distributed-cloud>`.
 
@@ -29,22 +29,23 @@ Distributed Cloud <update-management-for-distributed-cloud>`.
 
 #.  Select the **SystemController** region.
 
-#.  Select **Platform** \> **Software Management**.
+#.  Select **Distributed Cloud Admin** \> **Orchestration**.
 
-#.  On the Software Management page, select the **Cloud Patching Orchestration**
+#.  On the **Orchestration** page, select the **Orchestration Strategy**
     tab.
 
     .. image:: figures/bqu1525123082913.png
-    
+        :width: 1000px
+
 
 #.  Click **Apply Strategy**.
 
-    To monitor the progress of the overall update orchestration, use the Cloud
-    Patching Orchestration tab.
+    To monitor the progress of the overall update orchestration, use the
+    **Orchestration Strategy** tab.
+
+    To monitor the progress of host updates on RegionOne of System Controller
+    or a subcloud, use the **Host Inventory** page on the subcloud.
 
-    To monitor the progress of host updates on RegionOne or a subcloud, use the
-    Host Inventory page on the subcloud.
- 
 
 .. seealso::
 

doc/source/dist_cloud/kubernetes/configuring-kubernetes-update-orchestration-on-distributed-cloud.rst

@@ -6,8 +6,12 @@
 Configure Kubernetes Version Upgrade Distributed Cloud Orchestration
 ====================================================================
 
-You can configure a *Kubernetes Version Upgrade Distributed Cloud
-Orchestration Strategy* using the **dcmanager** CLI.
+You can configure a Kubernetes Version Upgrade Distributed Cloud Orchestration
+Strategy using the dcmanager CLI or the Horizon web interface.
+
+If you want to use the Horizon Web interface, see
+:ref:`create-a-kubernetes-upgrade-orchestration-using-horizon-16742b62ffb2`.
+
 
 .. note::
     Management-affecting alarms cannot be ignored using relaxed alarm rules

doc/source/dist_cloud/kubernetes/create-a-firmware-update-orchestration-strategy-using-horizon-cfecdb67cef2.rst

@@ -0,0 +1,99 @@
+.. _create-a-firmware-update-orchestration-strategy-using-horizon-cfecdb67cef2:
+
+=============================================================
+Create a Firmware Update Orchestration Strategy using Horizon
+=============================================================
+
+Use the Horizon Web interface as an alternative to the CLI for managing device
+/firmware image update strategies (Firmware update).
+
+To use the CLI, see :ref:`device-image-update-orchestration`.
+
+To update device/firmware image Central Cloud’s RegionOne and the subclouds,
+you must create an update strategy for Distributed Cloud fw-update-strategy
+Orchestration.
+
+
+.. rubric:: |context|
+
+Only one type of dcmanager strategy can exist at a time. The strategy controls
+how the subclouds are updated (for example, serially or in parallel).
+
+
+.. rubric:: |prereq|
+
+You must be in the SystemController region. To change the mode, see
+:ref:`regionone-and-systemcontroller-modes`.
+
+.. rubric:: |proc|
+
+#. Select the **SystemController** region.
+
+#. Select **Distributed Cloud Admin** > **Orchestration**.
+
+#. Select the **Orchestration Strategy** tab on the **Orchestration** page.
+
+   .. figure:: figures/update-strategy-1.png
+
+       Orchestration Strategy
+
+#. Create a new strategy.
+
+   Click **Create Strategy**. In the **Create Strategy** dialog box, adjust the
+   settings as needed.
+
+   **Strategy Type**
+      Firmware
+
+   **Apply to**
+      Subcloud or Subcloud Group
+
+   **Subcloud**
+      Enter the subcloud name
+
+   **Subcloud Group**
+      Enter the subcloud group name only if you select the **Apply to**:
+      **Subcloud Group** option.
+
+   **Stop on Failure**
+      Default: True
+
+      Determines whether update orchestration failure for a subcloud prevents
+      application to subsequent subclouds.
+
+   **Subcloud Apply Type**
+      Parallel or Serial, default Parallel.
+      Determines whether the subclouds are updated in parallel or serially.
+
+   **Maximum Parallel Subclouds**
+      Default: 20
+
+      If this is not specified using the CLI, the values for
+      ``max_parallel_subclouds`` defined for each subcloud group will be used
+      by default.
+
+   **Force**
+      Default: False
+
+   .. figure:: figures/create-strategy.png
+
+   .. figure:: figures/create-strategy-2.png
+
+       Create a strategy
+
+#. Adjust how device image nodes are updated on RegionOne and the subclouds.
+
+#. Save the new strategy.
+
+   Click **Create Strategy**.
+
+
+.. rubric:: |result|
+
+Only subclouds in the Managed state and whose patching sync status is
+``out-of-sync`` are added to the list. To change the firmware upgrade strategy
+settings, you must delete the current strategy and create a new one. You must
+confirm before applying the strategy. If the created strategy is older than 60
+minutes, a warning message will be displayed. You can simply apply
+the strategy or first verify that it is still valid.
+

doc/source/dist_cloud/kubernetes/create-a-kubernetes-upgrade-orchestration-using-horizon-16742b62ffb2.rst

@@ -0,0 +1,108 @@
+.. _create-a-kubernetes-upgrade-orchestration-using-horizon-16742b62ffb2:
+
+=======================================================
+Create a Kubernetes Upgrade Orchestration using Horizon
+=======================================================
+
+Use the Horizon Web interface as an alternative to the CLI for managing
+Kubernetes upgrade strategies.
+
+.. rubric:: |context|
+
+Only one update strategy can exist at a time. The strategy controls how the
+subclouds are updated (for example, serially or in parallel).
+
+
+.. rubric:: |prereq|
+
+Management-affecting alarms cannot be ignored using relaxed alarm rules during
+an orchestrated Kubernetes version upgrade operation. For a list of
+management-affecting alarms, see |fault-doc|: :ref:`fm-alarm-messages`.
+
+You can use the Horizon Web interface to check the alarm states:
+
+#. Select the **SystemController** region.
+
+#. Select **Admin** > **Fault Management**.
+
+#. Select **Active Alarms**.
+
+
+.. rubric:: |proc|
+
+#. Select the **SystemController** region.
+
+#. Select **Distributed Cloud Admin** > **Orchestration**.
+
+#. On the **Orchestration** page, select the **Orchestration Strategy** tab.
+
+   .. figure:: figures/update-strategy-1.png
+
+       Orchestration Strategy
+
+#. Create a new strategy.
+
+   On the **Orchestration Strategy** tab, click **Create Strategy**.
+   In the **Create Strategy** dialog box, adjust the settings as needed.
+
+   **Strategy Type**
+      Kubernetes
+
+   **Apply to**
+      Subcloud or Subcloud Group
+
+   **Subcloud**
+      Enter the subcloud name
+
+   **Subcloud Group**
+      Enter the subcloud group name only if you select the **Apply to**:
+      **Subcloud Group** option.
+
+   **Stop on Failure**
+      Default: True
+
+      Determines whether update orchestration failure for a subcloud prevents
+      application to subsequent subclouds.
+
+   **Subcloud Apply Type**
+      Default: Parallel
+
+      Parallel or Serial. Determines whether the subclouds are updated in
+      parallel or serially.
+
+   **Maximum Parallel Subclouds**
+      Default: 20
+
+      If this is not specified using the CLI, the values for
+      ``max_parallel_subclouds`` defined for each subcloud group will be used
+      by default.
+
+   **Force**
+      Default: False
+
+      Force kube upgrade to a subcloud which is in-sync with system controller.
+
+   **To version**
+      Not currently supported.
+
+   .. figure:: figures/create-k8s-strategy.png
+
+   .. figure:: figures/create-k8s-strategy-2.png
+
+       Create a strategy
+
+#. Adjust how Kubernetes is upgraded on RegionOne and on subclouds.
+
+#. Save the new strategy.
+
+   Click **Create Strategy**.
+
+
+.. rubric:: |result|
+
+Only subclouds in the Managed state and whose patching sync status is
+``out-of-sync`` are added to the list. To change the Kubernetes Upgrade
+strategy settings, you must delete the current strategy and create a new one.
+You must confirm before applying the strategy. If the strategy is older than 60
+minutes, a warning message will be display on this popup. You can simply apply
+the strategy or verify that it is still valid.

doc/source/dist_cloud/kubernetes/create-an-upgrade-orchestration-using-horizon-9f8c6c2f3706.rst

@@ -0,0 +1,93 @@
+.. _create-an-upgrade-orchestration-using-horizon-9f8c6c2f3706:
+
+=============================================
+Create an Upgrade Orchestration using Horizon
+=============================================
+
+.. rubric:: |prereq|
+
+You must have completed the procedure in
+:ref:`distributed-upgrade-orchestration-process-using-the-cli`.
+
+.. rubric:: |proc|
+
+#.  Review the upgrade status for the subclouds.
+
+    After the System Controller upgrade is completed, wait for 10 minutes for
+    the ``load_sync_status`` of all subclouds to be updated. To check the
+    subclouds status:
+
+    #. Select the **SystemController** region.
+
+    #. Select **Distributed Cloud Admin** > **Cloud Overview**.
+
+#.  Create the strategy.
+
+    #. Select the **SystemController** region.
+
+    #. Select **Distributed Cloud Admin** > **Orchestration**.
+
+    #. On the **Orchestration** page, select the **Orchestration Strategy** tab.
+
+    #. Create the new strategy.
+
+       On the **Orchestration Strategy** tab, click **Create Strategy**. In the
+       **Create Strategy** dialog box, adjust the settings as needed.
+
+       **Strategy Type**
+          Upgrade
+
+       **Apply to**
+          Subcloud or Subcloud Group
+
+       **Subcloud**
+          Enter the subcloud name
+
+       **Subcloud Group**
+          Enter the subcloud group name only if you select the **Apply to**:
+          **Subcloud Group** option.
+
+       **Stop on Failure**
+          Default: True
+
+          Determines whether update orchestration failure for a subcloud
+          prevents application to subsequent subclouds.
+
+       **Subcloud Apply Type**
+          Default: Parallel
+
+          Parallel or Serial. Determines whether the subclouds are updated in
+          parallel or serially.
+
+       **Maximum Parallel Subclouds**
+          Default 20
+
+          If this is not specified using the CLI, the values for
+          ``max_parallel_subclouds`` defined for each subcloud group will be
+          used by default.
+
+       **Force**
+          Default: False
+
+          Offline subcloud is not skipped. Applicable only when the strategy is
+          created to a single subcloud.
+
+       .. figure:: figures/create-strategy.png
+
+       .. figure:: figures/create-strategy-2.png
+
+           Create an orchestration strategy
+
+    #. Adjust how the Upgrade on subclouds will be performed.
+
+    #. Save the new strategy.
+
+       Only subclouds in the Managed state and whose patching sync status is
+       ``out-of-sync`` are added to the list. To change the Upgrade strategy
+       settings, you must delete the current strategy and create a new one.
+       Confirmation before applying strategy will be needed. If the created
+       strategy is older than 60 minutes, a warning message will be display on
+       this popup. The user can apply the strategy or verify if it is still
+       valid.
+
+

doc/source/dist_cloud/kubernetes/create-subcloud-groups-using-the-horizon-web-interface-69d357303531.rst

@@ -6,7 +6,7 @@ Create Subcloud Groups Using the Horizon Web Interface
 
 .. rubric:: |prereq|
 
-You must be in **SystemController** mode. To change the mode, see
+You must be in **SystemController** region. To change the region, see
 :ref:`RegionOne and SystemController Modes
 <regionone-and-systemcontroller-modes>`.
 
@@ -14,21 +14,22 @@ You must be in **SystemController** mode. To change the mode, see
 
 #.  Select the **SystemController** region.
 
-#.  Select **Distributed Cloud Admin** \> **Software Management**.
+#.  Select **Distributed Cloud Admin** > **Orchestration**.
 
-#.  On the Software Management page, select the **Subcloud Group Management**
-    tab.
+#.  On the **Orchestration** page, select the **Subcloud Group
+    Management** tab.
 
 #.  On the **Subcloud Group Management** tab, click **Add Subcloud Group**.
 
-    .. image:: figures/create-subcloud-1.png
+    .. image:: figures/create-subcloud-1.jpg
+        :width: 1000px
 
 #.  In the **Create New Subcloud Group** dialog box, adjust the settings as
     needed:
 
     -   Name
     -   Description
-    -   Update apply type: default Parallel
+    -   Update apply type: Parallel or Serial; default Parallel.
     -   Maximum parallel subclouds: default 2
 
     .. image:: figures/create-subcloud-2.png

doc/source/dist_cloud/kubernetes/creating-an-update-strategy-for-distributed-cloud-update-orchestration.rst

@@ -28,7 +28,7 @@ available on the Cloud Patching Configuration tab.
 
 .. rubric:: |prereq|
 
-You must be in **SystemController** mode. To change the mode, see
+You must be in **SystemController** region. To change the region, see
 :ref:`RegionOne and SystemController Modes
 <regionone-and-systemcontroller-modes>`.
 
@@ -36,29 +36,32 @@ You must be in **SystemController** mode. To change the mode, see
 
 #.  Select the **SystemController** region.
 
-#.  Select **Distributed Cloud Admin** \> **Software Management**.
+#.  Select **Distributed Cloud Admin** \> **Orchestration**.
 
-#.  On the Software Management page, select the **Cloud Strategy Orchestration**
+#.  On the **Orchestration** page, select the **Orchestration Strategy**
     tab.
 
-    .. image:: figures/update-strategy-1.png
+    .. image:: figures/create-strategy.png
+        :width: 1000px
 
 
-#.  On the Cloud Strategy Orchestration tab, click **Create Strategy**.
+#.  On the **Cloud Strategy Orchestration** tab, click **Create Strategy**.
 
-    In the Create Strategy dialog box, adjust the settings as needed.
+    In the **Create Strategy** dialog box, adjust the settings as needed.
 
     **Strategy Type**
-        Patch, Upgrade, Kubernetes, or Firmware.
+        Patch.
 
     **Apply to**
         Subcloud or Subcloud Group.
 
     **Subcloud**
-        Write the subcloud name.
+        Select the subcloud name, only if you have chosen the **Apply to:
+        Subcloud** option.
 
     **Subcloud Group**
-        Write the subcloud group name, only if you select the **Apply to: Subcloud Group** option.
+        Write the subcloud group name, only if you select the **Apply to:
+        Subcloud Group** option.
 
     **Stop on Failure**
         default true — determines whether update orchestration failure for a
@@ -68,14 +71,25 @@ You must be in **SystemController** mode. To change the mode, see
         Parallel or Serial, default Parallel — determines whether the subclouds
         are updated in parallel or serially.
 
+        This option is available when **Apply to** is set to "Subcloud" and
+        **Subcloud** is set to **All subclouds**.
+
     **Maximum Parallel Subclouds**
         default 20 — If this is not specified using the |CLI|, the values for
         max_parallel_subclouds defined for each subcloud group will be used by
         default.
 
+        This option is available when **Apply to** is set to "Subcloud" and
+        **Subcloud** is set to **All subclouds**.
+
     **Force**
         default False.
 
+        Offline subcloud is not skipped. Applicable only when the strategy is
+        created to a single subcloud.
+
+        This option is available when **Strategy Type** is set to "Upgrade".
+
     .. image:: figures/update-strategy-2.png
 
     .. image:: figures/update-strategy-3.png

doc/source/dist_cloud/kubernetes/customizing-the-update-configuration-for-distributed-cloud-update-orchestration.rst

@@ -24,11 +24,13 @@ independently.
 
 #.  Select the **SystemController** region.
 
-#.  Select **Distributed Cloud Admin** \> **Software Management**.
+#.  Select **Distributed Cloud Admin** \> **Orchestration**.
 
-#.  On the Software Management page, select the **Cloud Patching Configuration** tab.
+#.  On the **Orchestration** page, select the **Cloud Patching Configuration**
+    tab.
 
     .. image:: figures/qfq1525194569886.png
+        :width: 1000px
 
     Take one of the following actions:
 
@@ -37,14 +39,14 @@ independently.
         default, click **Edit Configuration** in the **all clouds default** row.
 
         .. image:: figures/brk1525194697928.png
-        
+
         To save your changes, click **Edit Cloud Patching Configuration**.
 
     -   To create custom settings for an individual subcloud, click **Create
         New Cloud Patching Configuration**.
 
         .. image:: figures/vzc1525194338519.png
-        
+
         In the **Subcloud** field, select the subcloud for the custom settings.
 
         To save your configuration changes, click **Create Cloud Patching

doc/source/dist_cloud/kubernetes/delete-subcloud-groups-22a7c65e66d7.rst

@@ -6,7 +6,7 @@ Delete Subcloud Groups Using the Horizon Web Interface
 
 .. rubric:: |prereq|
 
-You must be in **SystemController** mode. To change the mode, see
+You must be in **SystemController** region. To change the region, see
 :ref:`RegionOne and SystemController Modes
 <regionone-and-systemcontroller-modes>`.
 
@@ -14,15 +14,16 @@ You must be in **SystemController** mode. To change the mode, see
 
 #.  Select the **SystemController** region.
 
-#.  Select **Distributed Cloud Admin** \> **Software Management**.
+#.  Select **Distributed Cloud Admin** \> **Orchestration**.
 
-#.  On the Software Management page, select the **Subcloud Group Management**
+#.  On the **Orchestration** page, select the **Subcloud Group Management**
     tab.
 
 #.  Click on the **Edit Subcloud Group** dropdown and select **Delete Subcloud
     Group**:
 
     .. image:: figures/edit-subcloud-1.png
+        :width: 1000px
 
 #.  Confirm deletion:
 

doc/source/dist_cloud/kubernetes/device-image-update-orchestration.rst

@@ -129,6 +129,14 @@ device image updates, including |FPGA| updates.
 #.  Create an update strategy using the :command:`fw-update-strategy create`
     command.
 
+    The update strategy controls how FPGA updates are applied to hosts on
+    subclouds. Creating, applying and monitoring the strategy can be done using
+    CLI or Horizon web interface.
+
+    If you want to use Horizon, see
+    :ref:`create-a-firmware-update-orchestration-strategy-using-horizon-cfecdb67cef2`
+
+
     The update strategy controls how |FPGA| updates are applied to hosts on
     subclouds.
 

doc/source/dist_cloud/kubernetes/distributed-upgrade-orchestration-process-using-the-cli.rst

@@ -3,13 +3,13 @@
 .. _distributed-upgrade-orchestration-process-using-the-cli:
 
 =======================================================
-Distributed Upgrade Orchestration Process Using the CLI
+Distributed Upgrade Orchestration Process using the CLI
 =======================================================
 
 Distributed upgrade orchestration can be initiated after the System Controller
 has been successfully upgraded.
 
-For more information Prestaging Subcloud Orchestration see,
+For more information on Prestaging Subcloud Orchestration see,
 :ref:`prestage-subcloud-orchestration-eb516473582f`.
 
 .. rubric:: |context|
@@ -89,6 +89,11 @@ following conditions:
 
     :command:`sudo rm /opt/platform-backup/upgrade_data\*`
 
+You can configure an upgrade Distributed Cloud orchestration strategy using the
+dcmanager CLI or the Horizon web interface. If you prefer to use Horizon, see
+:ref:`create-an-upgrade-orchestration-using-horizon-9f8c6c2f3706`.
+
+
 .. rubric:: |proc|
 
 .. _distributed-upgrade-orchestration-process-using-the-cli-steps-vcm-pq4-3mb:
@@ -322,6 +327,8 @@ following conditions:
         | updated_at             | 2020-03-23T20:05:14.157352 |
         +------------------------+----------------------------+
 
+
+
 .. rubric:: |postreq|
 
 .. _distributed-upgrade-orchestration-process-using-the-cli-ul-lx1-zcv-3mb:
@@ -347,4 +354,4 @@ the secret payload is, "username: admin password:<password>", see,
 
    .. include:: /_includes/distributed-upgrade-orchestration-process-using-the-cli.rest
       :start-after: dcsubcloud-begin
-      :end-before: dcsubcloud-end
+      :end-before: dcsubcloud-end

doc/source/dist_cloud/kubernetes/edit-subcloud-groups-85232c3a7d33.rst

@@ -14,14 +14,15 @@ You must be in **SystemController** mode. To change the mode, see
 
 #.  Select the **SystemController** region.
 
-#.  Select **Distributed Cloud Admin** \> **Software Management**.
+#.  Select **Distributed Cloud Admin** \> **Orchestration**.
 
-#.  On the Software Management page, select the **Subcloud Group Management**
+#.  On the **Orchestration** page, select the **Subcloud Group Management**
     tab.
 
 #.  Click **Edit Subcloud Group**.
 
-    .. image:: figures/edit-subcloud-1.png
+    .. image:: figures/2-529_1_editSubcGroup.jpg
+        :width: 1000px
 
 #.  Edit fields for the Subcloud Group:
 

doc/source/dist_cloud/kubernetes/index-dist-cloud-kub-95bef233eef0.rst

@@ -118,6 +118,9 @@ FPGA device image update management
    :maxdepth: 1
 
    device-image-update-orchestration
+   create-a-firmware-update-orchestration-strategy-using-horizon-cfecdb67cef2
+   apply-the-firmware-update-strategy-using-horizon-e78bf11c7189
+
 
 --------------------------------------------------------------------
 Configure Kubernetes Version Upgrade Distributed Cloud Orchestration
@@ -128,6 +131,8 @@ Configure Kubernetes Version Upgrade Distributed Cloud Orchestration
 
     the-kubernetes-distributed-cloud-update-orchestration-process
     configuring-kubernetes-update-orchestration-on-distributed-cloud
+    create-a-kubernetes-upgrade-orchestration-using-horizon-16742b62ffb2
+    apply-a-kubernetes-upgrade-strategy-using-horizon-2bb24c72e947
 
 ---------------------------------------------------------
 Kubernetes Root CA Update Distributed Cloud Orchestration
@@ -148,14 +153,16 @@ Upgrade management
     upgrade-management-overview
     upgrading-the-systemcontroller-using-the-cli
 
-*******************************************************************
-Upgrade Orchestration for Distributed Cloud SubClouds using the CLI
-*******************************************************************
+*****************************************************
+Upgrade Orchestration for Distributed Cloud SubClouds
+*****************************************************
 
 .. toctree::
     :maxdepth: 1
 
     distributed-upgrade-orchestration-process-using-the-cli
+    create-an-upgrade-orchestration-using-horizon-9f8c6c2f3706
+    apply-the-upgrade-strategy-using-horizon-d0aab18cc724
     aborting-the-distributed-upgrade-orchestration
     configuration-for-specific-subclouds
     robust-error-handling-during-an-orchestrated-upgrade

doc/source/dist_cloud/kubernetes/reviewing-update-status-for-distributed-cloud-using-horizon.rst

@@ -14,7 +14,7 @@ If you prefer, you can use the |CLI|. For more information, see :ref:`Reviewing
 Update Status for Distributed Cloud Using the CLI
 <reviewing-update-status-for-distributed-cloud-using-the-cli>`.
 
-From the Horizon, you can use only the **SystemController** mode/region to
+From Horizon, you can use only the **SystemController** region to
 review updates in the central update repository and the update sync status of
 subclouds.
 
@@ -22,11 +22,12 @@ subclouds.
 
 #.  Select the **SystemController** region.
 
-#.  Select **Platform** \> **Software Management**.
+#.  Select **Distributed Cloud Admin** \> **Software Management**.
 
-#.  On the Software Management page, select the **Patches** tab.
+#.  On the **Software Management** page, select the **Patches** tab.
 
     .. image:: figures/tmj1525095688715.png
+        :width: 1000px
 
     .. note::
 

doc/source/dist_cloud/kubernetes/uploading-and-applying-updates-to-systemcontroller-using-horizon.rst

@@ -19,20 +19,21 @@ and Applying Updates to SystemController Using the CLI
 
 #.  Select the **SystemController** region.
 
-#.  Select **Platform** \> **Software Management**.
+#.  Select **Distributed Cloud Admin** \> **Software Management**.
 
-#.  On the Software Management page, select the **Patches** tab.
+#.  On the **Software Management** page, select the **Patches** tab.
 
     .. image:: figures/tmj1525095688715.png
-    
+        :width: 1000px
 
-#.  On the Patches tab, click **Upload Patches**.
 
-    In the Upload Patches dialog box, click **Browse** to select updates
+#.  On the **Patches** tab, click **Upload Patches**.
+
+    In the **Upload Patches** dialog box, click **Browse** to select updates
     \(patches\) for upload.
 
     .. image:: figures/cah1525101473925.png
-    
+
 #.  In the dialog, click **Upload Patches**.
 
     The update is added to the Patches list in the **Available** state.

doc/source/fault-mgmt/kubernetes/index-fault-kub-f45ef76b6f16.rst

@@ -99,6 +99,8 @@ Troubleshooting log collection
 
    troubleshooting-log-collection
 
+.. _fm-alarm-messages:
+
 **************
 Alarm messages
 **************