Mention nova-status upgrade check CLI in upgrade doc
Mention nova-status upgrade check CLI in upgrade doc Closes-Bug: #1772973 Change-Id: I5e643febebd435550af2d7c49546a16ac5a21453
This commit is contained in:
parent
ff5cded9af
commit
a79e2885d0
@ -52,6 +52,8 @@ These sections describe the available categories and arguments for
|
||||
Upgrade
|
||||
~~~~~~~
|
||||
|
||||
.. _nova-status-checks:
|
||||
|
||||
``nova-status upgrade check``
|
||||
Performs a release-specific readiness check before restarting services with
|
||||
new code. This command expects to have complete configuration and access
|
||||
|
@ -89,6 +89,11 @@ same time.
|
||||
* For maximum safety (no failed API operations), gracefully shutdown all
|
||||
the services (i.e. SIG_TERM) except nova-compute.
|
||||
|
||||
* Before restarting services with new code, perform the release-specific
|
||||
readiness check with ``nova-status upgrade check``. See the
|
||||
:ref:`nova-status upgrade check <nova-status-checks>` for more details
|
||||
on status check.
|
||||
|
||||
* Start all services on the new code, with
|
||||
``[upgrade_levels]compute=auto`` in nova.conf. It is safest to
|
||||
start nova-conductor first and nova-api last. Note that you may
|
||||
|
Loading…
Reference in New Issue
Block a user