akhiljain23 2ccf639a39 Add framework for magnum-status upgrade check

This commit adds the functionality of magnum-status CLI for performing
upgrade checks as part of the Stein cycle upgrade-checkers goal.
It only includes a sample check which must be replaced by real checks in
future.

Change-Id: Ia8a74fd8bd5a804e71bb04eb0615fa114a517bc4
Story: 2003657
Task: 26138

2019-01-27 04:26:30 +00:00

2.2 KiB

Raw Blame History

magnum-status

CLI interface for Magnum status commands

Synopsis

magnum-status <category> <command> [<args>]

Description

magnum-status is a tool that provides routines for checking the status of a Magnum deployment.

Options

The standard pattern for executing a magnum-status command is:

magnum-status <category> <command> [<args>]

Run without arguments to see a list of available command categories:

magnum-status

Categories are:

upgrade

Detailed descriptions are below:

You can also run with a category argument such as upgrade to see a list of all commands in that category:

magnum-status upgrade

These sections describe the available categories and arguments for magnum-status.

Upgrade

magnum-status upgrade check

Performs a release-specific readiness check before restarting services with new code. For example, missing or changed configuration options, incompatible object states, or other conditions that could lead to failures while upgrading.

**Sample Output**
Upgrade Check Results
Check: Sample Check Result: Success Details: Sample detail

Return Codes

Return code	Description
0	All upgrade readiness checks passed successfully and there is nothing to do.
1	At least one check encountered an issue and requires further investigation. This is considered a warning but the upgrade may be OK.
2	There was an upgrade status check failure that needs to be investigated. This should be considered something that stops an upgrade.
255	An unexpected error occurred.

History of Checks

8.0.0 (Stein)

Sample check to be filled in with checks as they are added in Stein.

2.2 KiB Raw Blame History