oslo.upgradecheck
Common code for writing OpenStack upgrade checks
Decision gist · record as of 2026-08-14
Yes, if you are developing or operating an OpenStack project. The package is actively maintained, has no known vulnerabilities, and provides a standardized framework that reduces duplication of upgrade-check logic across the OpenStack ecosystem. Not relevant for non-OpenStack use cases.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Python 3.11 or later; intended for use within OpenStack projects that integrate the framework.
- Low install friction with a wheel distribution.
- Active maintenance status with a recent release (35 days old).
License · maintenance · safety
Apache-2.0 (permissive) — Apache-2.0 permissive license allows use, modification, and distribution with minimal restrictions, suitable for both proprietary and open-source projects.
last release 2026-07-10 (35 days)
0 known vulnerabilities (OSV.dev, 2026-08-14) · 314,014 downloads/mo, #7,707 on PyPI
Alternatives
Verify before relying
pip install oslo.upgradecheck
from oslo_upgradecheck import upgradecheck
# Define a check class inheriting from upgradecheck.UpgradeCommands
class MyUpgradeChecks(upgradecheck.UpgradeCommands):
def _check_something(self):
return upgradecheck.Result(upgradecheck.Code.SUCCESS)- Whether this package is intended for end-user operators or for OpenStack project developers writing upgrade checks
- Specific OpenStack versions or projects that currently use this framework
- Performance characteristics or scalability limits for large-scale deployments
What it is and what it does
oslo.upgradecheck is a library that provides common infrastructure for writing upgrade checks in OpenStack projects. It supplies a base class and utilities that let OpenStack services define and run validation checks before performing version upgrades, helping operators verify system readiness and catch configuration or compatibility issues early.
The package is part of the oslo project—a collection of shared libraries across OpenStack—and is designed to be integrated into individual OpenStack projects rather than used as a standalone tool. It includes both the core framework module and an example of how to wire it into a project's command-line interface. It depends on oslo.config, oslo.i18n, oslo.utils, oslo.policy for configuration and utility support, and PrettyTable for formatting check results.
Use it for
- OpenStack project developers integrating pre-upgrade validation into their services
- Operators running upgrade checks to verify system state before applying version updates
- Automated deployment pipelines that need to validate upgrade readiness before proceeding
- Multi-component OpenStack environments checking compatibility across interdependent services
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you are developing or operating an OpenStack project.
The package is actively maintained, has no known vulnerabilities, and provides a standardized framework that reduces duplication of upgrade-check logic across the OpenStack ecosystem. Not relevant for non-OpenStack use cases.
Install
oslo-upgradecheck on PyPI
Before you install
Low install friction with a wheel distribution. Active maintenance status with a recent release (35 days old). Depends on five oslo.* libraries and PrettyTable, all standard OpenStack ecosystem packages.
Requires Python 3.11 or later; intended for use within OpenStack projects that integrate the framework.
License in practice
Apache-2.0 permissive license allows use, modification, and distribution with minimal restrictions, suitable for both proprietary and open-source projects.
Quickstart
pip install oslo.upgradecheck
from oslo_upgradecheck import upgradecheck
# Define a check class inheriting from upgradecheck.UpgradeCommands
class MyUpgradeChecks(upgradecheck.UpgradeCommands):
def _check_something(self):
return upgradecheck.Result(upgradecheck.Code.SUCCESS)Verify before relying
- Whether this package is intended for end-user operators or for OpenStack project developers writing upgrade checks
- Specific OpenStack versions or projects that currently use this framework
- Performance characteristics or scalability limits for large-scale deployments
Package facts
| License | Apache-2.0 permissive |
| Python support | Supports the current Python release >=3.11 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 5 packagesoslo.configoslo.i18nPrettyTableoslo.utilsoslo.policy |
| Maintenance | Actively maintained 35 days since the last release |
| First released | |
| Downloads | 314,014 / month, #7,707 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | Environment :: OpenStackIntended Audience :: Information TechnologyIntended Audience :: System AdministratorsOperating System :: POSIX :: LinuxProgramming Language :: PythonProgramming Language :: Python :: 3Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.14Typing :: Typed |
Evidence: oslo_upgradecheck-2.8.0-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “openstack upgrade checks”
- oslo.upgradecheckProvides a framework for writing and running upgrade checks in…
- oslo.versionedobjectsoslo.versionedobjects provides a versioned object model for…
- hackingHacking is a set of flake8 plugins that enforce the OpenStack Style…
Give your agent the search over MCP, or paste the wish link into any chat.
More Quality Assurance packages
Coverage.py measures which lines of Python code are executed during test runs, reporting coverage percentages and identifying untested code paths.
Install it if you want to measure test completeness or enforce coverage thresholds in your project.
Ruff is a Python linter and code formatter written in Rust that combines linting, formatting, and code fixing into a single tool, replacing Flake8, Black, isort, and related utilities.
Pexpect spawns and controls interactive console applications by sending input and matching output patterns, automating tasks that would otherwise require manual interaction.
Black reformats Python source code to a consistent style by parsing entire files and rewriting them according to an opinionated, deterministic set of rules, eliminating manual formatting decisions.
pytest-xdist distributes pytest tests across multiple CPU cores or machines to speed up test execution, with the simplest usage being `pytest -n auto` to spawn workers equal to available CPUs.
Install it if your test suite takes long enough that parallelization would save meaningful time.
Validates AWS CloudFormation templates in YAML or JSON format against resource provider schemas and best practices, checking property values and configuration correctness.
Install it if you work with CloudFormation templates.
See also oslo.db · oslo.service · oslo.cache · oslo.log · os-testr · oslo.versionedobjects · oslo.vmware · oslo.config · cursive · git-review