akhiljain23 fb06b7c96c Add framework for tacker-status upgrade check

This commit adds the functionality of tacker-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: I7bb127fa10dd168ab24dd8c42013576f84eadfbb
Story: 2003657
Task: 26158

2018-10-26 09:07:04 +00:00

2.5 KiB

Raw Blame History

tacker-status

CLI interface for Tacker status commands

Synopsis

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

Description

tacker-status is a tool that provides routines for checking the status of a Tacker deployment.

Options

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

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

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

tacker-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:

tacker-status upgrade

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

Upgrade

tacker-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.

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

0.11.0 (Stein)

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

2.5 KiB Raw Blame History