starlingx/docs
Code Issues Proposed changes

Introduce system restore-complete command

Browse Source 
Update backup & restore guide

Closes-Bug: 1912485

Change-Id: Idc3f6fd86cdf6c1dbe7bd646ac57c625fbdd67fd
Signed-off-by: MCamp859 <maryx.camp@intel.com>
This commit is contained in:
MCamp859 2021-01-20 21:27:43 -05:00
parent ebdf63ec68
commit c6f5466952
1 changed files with 32 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
doc/source/developer_resources/backup_restore.rst
View File

@ -342,12 +342,26 @@ Steps:
**AIO-SX** **AIO-SX**
Unlock controller-0 and wait for it to boot. i. Unlock controller-0 and wait for it to boot.
#. Applications should transition from `restore-requested` to
`applying` and make a final transition to `applied` state. If
applications transition from `applying` to `restore-requested`
state, ensure there is network access and access to the Docker
registry. The process is repeated once per minute until all
applications are transitioned to the `applied` state.
**AIO-DX** **AIO-DX**
i. Unlock controller-0 and wait for it to boot. i. Unlock controller-0 and wait for it to boot.
#. Applications should transition from `restore-requested` to
`applying` and make a final transition to `applied` state. If
applications transition from `applying` to `restore-requested`
state, ensure there is network access and access to the Docker
registry. The process is repeated once per minute until all
applications are transitioned to the `applied` state.
#. Reinstall controller-1 (boot it from PXE, wait for it to become #. Reinstall controller-1 (boot it from PXE, wait for it to become
`online`). `online`).
@ -358,6 +372,13 @@ Steps:
i. Unlock controller-0 and wait for it to boot. After unlock, you will i. Unlock controller-0 and wait for it to boot. After unlock, you will
see all nodes, including storage nodes, as offline. see all nodes, including storage nodes, as offline.
#. Applications should transition from `restore-requested` to
`applying` and make a final transition to `applied` state. If
applications transition from `applying` to `restore-requested`
state, ensure there is network access and access to the Docker
registry. The process is repeated once per minute until all
applications are transitioned to the `applied` state.
#. Reinstall controller-1 and compute nodes (boot them from PXE, wait #. Reinstall controller-1 and compute nodes (boot them from PXE, wait
for them to become `online`). for them to become `online`).
@ -373,6 +394,13 @@ Steps:
and in the `available` state throughout the procedure. Otherwise, and in the `available` state throughout the procedure. Otherwise,
storage nodes must be powered off. storage nodes must be powered off.
#. Applications should transition from `restore-requested` to
`applying` and make a final transition to `applied` state. If
applications transition from `applying` to `restore-requested`
state, ensure there is network access and access to the Docker
registry. The process is repeated once per minute until all
applications are transitioned to the `applied` state.
#. Reinstall controller-1 and compute nodes (boot them from PXE, wait #. Reinstall controller-1 and compute nodes (boot them from PXE, wait
for them to become `online`). for them to become `online`).
@ -384,7 +412,9 @@ Steps:
#. (Optional) Reinstall storage nodes. #. (Optional) Reinstall storage nodes.
#. Re-apply applications (e.g. OpenStack) to force pods to restart. #. Wait for Calico and Coredns pods to start. Run the
``system restore-complete`` command. Type 750.006 alarms will disappear
one at a time, as the applications are being auto-applied.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
OpenStack application backup and restore OpenStack application backup and restore