Fix table (r9, dsr8MR3, dsr8MR2)
Add declaration and indent as block. Fixes: https://review.opendev.org/c/starlingx/docs/+/903075 Change-Id: Ib6f034addc73a4eea990eca000ec75f4af7227fb Signed-off-by: Ron Stone <ronald.stone@windriver.com>
This commit is contained in:
Ron Stone
Juanita-Balaraj
parent
da8043d782
commit
f7f89d204e
@ -524,92 +524,95 @@ The table below lists the operations that can/cannot be performed on the protect
|
||||
|
||||
**Local/Unprotected subcloud**: The subcloud that does not belong to any |SPG|.
|
||||
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Operation | Allow (Y/N/Maybe) | Note |
|
||||
+==========================================+==================================+=================================================================================================+
|
||||
| Unmanage | N | Subcloud must be removed from the |SPG| before it can be manually unmanaged. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Manage | N | Subcloud must be removed from the |SPG| before it can be manually managed. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Delete | N | Subcloud must be removed from the |SPG| before it can be manually unmanaged |
|
||||
| | | and deleted. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Update | Maybe | Subcloud can only be updated while it is managed in the primary site because the sync command |
|
||||
| | | can only be issued from the system controller where the |SPG| was created. |
|
||||
| | | |
|
||||
| | | .. warning:: |
|
||||
| | | |
|
||||
| | | The subcloud network cannot be reconfigured while it is being managed by the secondary |
|
||||
| | | site. If this operation is necessary, perform the following steps: |
|
||||
| | | |
|
||||
| | | #. Remove the subcloud from the |SPG| to make it a local/unprotected |
|
||||
| | | subcloud. |
|
||||
| | | #. Update the subcloud. |
|
||||
| | | #. (Optional) Manually rehome the subcloud to the primary site after it is restored. |
|
||||
| | | #. (Optional) Re-add the subcloud to the |SPG|. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Rename | Yes | - If the subcloud in the primary site is already a part of |SPG|, we need to remove it from the |
|
||||
| | | |SPG| and then unmanage, rename, and manage 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. |
|
||||
| | | |
|
||||
| | | #. Unmange the subcloud. |
|
||||
| | | |
|
||||
| | | #. Rename the subcloud. |
|
||||
| | | |
|
||||
| | | #. (Optional) Manually rehome the subcloud to the primary site after it is restored. |
|
||||
| | | |
|
||||
| | | #. (Optional) Re-add the subcloud to the |SPG|. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Patch | Y | .. warning:: |
|
||||
| | | |
|
||||
| | | There may be a patch out-of-sync alarm when the subcloud is migrated to another site. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Upgrade | Y | All the system controllers in the protection group must be upgraded first before upgrading |
|
||||
| | | any of the subclouds. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Rehome | N | Subcloud cannot be manually rehomed while being part of the |SPG| |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Backup | Y | |
|
||||
| | | |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Restore | Maybe | - If the subcloud in the primary site is already a part of |SPG|, we need to remove it from the |
|
||||
| | | |SPG| and then unmanage and restore 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. |
|
||||
| | | |
|
||||
| | | #. Unmange the subcloud. |
|
||||
| | | |
|
||||
| | | #. Restore the subcloud from the backup. |
|
||||
| | | |
|
||||
| | | #. (Optional) Manually rehome the subcloud to the primary site after it is restored. |
|
||||
| | | |
|
||||
| | | #. (Optional) Re-add the subcloud to the |SPG|. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Prestage | Y | .. warning:: |
|
||||
| | | |
|
||||
| | | The prestage data will get overwritten because it is not guaranteed that both the system |
|
||||
| | | controllers always run on the same patch level (ostree repo) and/or have the same images |
|
||||
| | | list. |
|
||||
| | | |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Reinstall | Y | |
|
||||
| | | |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| 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 |
|
||||
| | | currently down. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Add to |SPG| | Maybe | Subcloud can only be added to the |SPG| in the primary site as manual sync is required. |
|
||||
| | | |
|
||||
| | | |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
.. table::
|
||||
:widths: auto
|
||||
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Operation | Allow (Y/N/Maybe) | Note |
|
||||
+==========================================+==================================+=================================================================================================+
|
||||
| Unmanage | N | Subcloud must be removed from the |SPG| before it can be manually unmanaged. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Manage | N | Subcloud must be removed from the |SPG| before it can be manually managed. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Delete | N | Subcloud must be removed from the |SPG| before it can be manually unmanaged |
|
||||
| | | and deleted. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Update | Maybe | Subcloud can only be updated while it is managed in the primary site because the sync command |
|
||||
| | | can only be issued from the system controller where the |SPG| was created. |
|
||||
| | | |
|
||||
| | | .. warning:: |
|
||||
| | | |
|
||||
| | | The subcloud network cannot be reconfigured while it is being managed by the secondary |
|
||||
| | | site. If this operation is necessary, perform the following steps: |
|
||||
| | | |
|
||||
| | | #. Remove the subcloud from the |SPG| to make it a local/unprotected |
|
||||
| | | subcloud. |
|
||||
| | | #. Update the subcloud. |
|
||||
| | | #. (Optional) Manually rehome the subcloud to the primary site after it is restored. |
|
||||
| | | #. (Optional) Re-add the subcloud to the |SPG|. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Rename | Yes | - If the subcloud in the primary site is already a part of |SPG|, we need to remove it from the |
|
||||
| | | |SPG| and then unmanage, rename, and manage 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. |
|
||||
| | | |
|
||||
| | | #. Unmange the subcloud. |
|
||||
| | | |
|
||||
| | | #. Rename the subcloud. |
|
||||
| | | |
|
||||
| | | #. (Optional) Manually rehome the subcloud to the primary site after it is restored. |
|
||||
| | | |
|
||||
| | | #. (Optional) Re-add the subcloud to the |SPG|. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Patch | Y | .. warning:: |
|
||||
| | | |
|
||||
| | | There may be a patch out-of-sync alarm when the subcloud is migrated to another site. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Upgrade | Y | All the system controllers in the protection group must be upgraded first before upgrading |
|
||||
| | | any of the subclouds. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Rehome | N | Subcloud cannot be manually rehomed while being part of the |SPG| |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Backup | Y | |
|
||||
| | | |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Restore | Maybe | - If the subcloud in the primary site is already a part of |SPG|, we need to remove it from the |
|
||||
| | | |SPG| and then unmanage and restore 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. |
|
||||
| | | |
|
||||
| | | #. Unmange the subcloud. |
|
||||
| | | |
|
||||
| | | #. Restore the subcloud from the backup. |
|
||||
| | | |
|
||||
| | | #. (Optional) Manually rehome the subcloud to the primary site after it is restored. |
|
||||
| | | |
|
||||
| | | #. (Optional) Re-add the subcloud to the |SPG|. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Prestage | Y | .. warning:: |
|
||||
| | | |
|
||||
| | | The prestage data will get overwritten because it is not guaranteed that both the system |
|
||||
| | | controllers always run on the same patch level (ostree repo) and/or have the same images |
|
||||
| | | list. |
|
||||
| | | |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Reinstall | Y | |
|
||||
| | | |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| 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 |
|
||||
| | | currently down. |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
| Add to |SPG| | Maybe | Subcloud can only be added to the |SPG| in the primary site as manual sync is required. |
|
||||
| | | |
|
||||
| | | |
|
||||
+------------------------------------------+----------------------------------+-------------------------------------------------------------------------------------------------+
|
||||
|
||||
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user