6369796ebe
One of the community goals for Stein is to implement a command-line tool for operators that runs programmable checks that might impact upgradability. This commit lays down the basic structure for the upgrade checks and ties it up to `keystone-status` command. Story: 2003657 Task: 26135 Change-Id: I6586827104156ac549217967a1b9171f1a3b32e4
34 lines
1.1 KiB
Python
34 lines
1.1 KiB
Python
# Licensed under the Apache License, Version 2.0 (the "License"); you may
|
|
# not use this file except in compliance with the License. You may obtain
|
|
# a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
|
|
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
|
|
# License for the specific language governing permissions and limitations
|
|
# under the License.
|
|
|
|
from oslo_upgradecheck import upgradecheck
|
|
|
|
import keystone.conf
|
|
|
|
CONF = keystone.conf.CONF
|
|
|
|
|
|
class Checks(upgradecheck.UpgradeCommands):
|
|
"""Programmable upgrade checks.
|
|
|
|
Each method here should be a programmable check that helps check for things
|
|
that might cause issues for deployers in the upgrade process. A good
|
|
example of an upgrade check would be to ensure all roles defined in
|
|
policies actually exist within the roles backend.
|
|
"""
|
|
|
|
pass
|
|
|
|
|
|
def main():
|
|
return upgradecheck.main(CONF, 'keystone', Checks())
|