This repo is now testing only with Python 3, so let's make
a few cleanups:
- Remove python 2.7 stanza from setup.py
- Add requires on python >= 3.6 to setup.cfg so that pypi and pip
know about the requirement
- Remove obsolete sections from setup.cfg
- Update classifiers
- Switch to using sphinx-build
- Cleanup doc/source/conf.py to remove now obsolete content.
- Use newer openstackdocstheme version
- Move constraints into deps
- Increase warlock dependency, glanceclient blocks version 1.3.0
Change-Id: I8feb2e86281f2250bdc379b7868c5e738c1a19e6
Add file to the reno documentation build to show release notes for
stable/train.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/train.
Change-Id: I8a13402cc47bc33a38182b3340987eefd9026850
Sem-Ver: feature
Add file to the reno documentation build to show release notes for
stable/stein.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/stein.
Change-Id: I2d9151ea3a2adf39255420aaa72e19e881679857
Sem-Ver: feature
Now when doing checkpoint copy failed, checkpoint
will be wait_copying status forever, and so we can
not do the restore anymore. So we should add an API
to support checkpoint status reset if we deeply knows
that the checkpoint is ok. This patch added API
support for doing checkpoint state reset.
Implements: bp checkpoint-status-reset
Change-Id: Iabaa98c9900fba554be2ad0833d438901e01147a
This commit adds the functionality of karbor-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: I8b75d516725c7cdf169d558b1c4b6f92a695ab2e
Story: 2003657
Task: 26134
Change I8ff60cc3793aea723a77d1b47a0f68c6c5c6ec62 left a broken
line in the tree such that releasenotes did not build anymore if karbor
was not installed, remove it.
Change-Id: I0dfb57c925b305e770e513586a1a1dea0df354f3
Release notes are version independent, so remove version/release
values. We've found that projects now require the service package
to be installed in order to build release notes, and this is entirely
due to the current convention of pulling in the version information.
Release notes should not need installation in order to build, so this
unnecessary version setting needs to be removed.
This is needed for new release notes publishing, see
I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting
at
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html
Change-Id: I8ff60cc3793aea723a77d1b47a0f68c6c5c6ec62
Building of releasenotes fails with
Could not import extension openstackdocsthemereno.sphinxext (exception:
No module named 'openstackdocsthemereno')
fix it - add a missing ","
Change-Id: I82441240c750a97a6bee12d204c5f143b3459d1e
It's hard to maintain karbor.conf by hand, let's switch to use
oslo-config-generator and follow OpenStack convention.
Change-Id: I0dd0a63267e14321ff723d32bd6d90db07cc5f95
Kendall Nelson
OpenStack Release Bot