Update the document for the reinstall/redeploy operation of the subcloud which is part of the SPG (dsr8mr3)

Change-Id: I5464bfda3d26c23332db30633c1e2803d5db2c1d
Signed-off-by: Ngairangbam Mili <ngairangbam.mili@windriver.com>
This commit is contained in:
Ngairangbam Mili 2024-04-25 03:10:23 +00:00
parent 88b0c96609
commit b63e9605a5

View File

@ -602,8 +602,17 @@ The table below lists the operations that can/cannot be performed on the protect
| | | list. |
| | | |
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
| Reinstall | Y | |
| Reinstall | Maybe | If the subcloud in the primary site is already a part of |SPG|, you need to remove it from the |
| | | |SPG|, unmanage and reinstall the subcloud, and add it back to |SPG| and perform the sync |
| | | operation. |
| | | |
| | | If the subcloud is in the secondary site, perform the following steps: |
| | | |
| | | #. Remove the subcloud from the |SPG| to make it a local/unprotected subcloud. |
| | | #. Unmanage the subcloud. |
| | | #. Re-install the subcloud. |
| | | #. (Optional) Manually rehome the subcloud to the primary site after it is restored. |
| | | #. (Optional) Re-add the subcloud to the |SPG|. |
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
| Remove from |SPG| | Maybe | Subcloud can be removed from the |SPG| in the primary site. Subcloud can |
| | | only be removed from the |SPG| in the secondary site if the primary site is |