The blazar installation was removed in [1].
However, stevedore requires blazar to generate docs for
configuration. Currently, they are mostly empty.
Instead of removing the blazar installation, this change makes
sure that deps are installed with constraints so that blazar
installation does not bring havoc and the original issue is fixed.
[1] Ic55dba0038a2209e9fb291a604a5c1da57607e1e
Change-Id: I28d06ae31c4cf44d010e0892a094138112b08641
According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
Let's switch to stestr as other projects have already moved to it.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: I9d22be39bec67fc17841367a0ef0ac439143af6c
After installing doc build requirements with upper constraints, tox was
installing blazar without constraints, which was pulling Jinja2 3.1.0
(released today) as a Flask dependency. This caused a docs build failure
on stable/wallaby, because Jinja2 dropped support for environmentfilter
used by the version of Sphinx in upper constraints.
Use skip_install to instruct tox not to install blazar when not needed.
This requires adding oslo.config and oslo.policy to doc/requirements.txt
because we use their sphinx extensions.
Change-Id: Ic55dba0038a2209e9fb291a604a5c1da57607e1e
Tox trying to install latest versions for building releasenotes,
which may not be supported by stable and lower branches,
so should be restricted by respective version's upper-constraints.txt
This ps to reuse upper-constraints.txt from docs deps
Change-Id: I7c7c2bd998d1a457ae1d19f42993e05370aa4e78
Docs need to end in doc/build/html for proper publishing, fix
change I8c81e0c1944c239e460befbf886993270902ee04.
Change-Id: Iee0c8b481ecbe0187eb9acc13bf41c6363bd95ed
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
- Update requirements, no need for python_version anymore
- Switch to using sphinx-build; fix build warnings
- Cleanup doc/source/conf.py to remove now obsolete content.
- Use newer openstackdocstheme version
- Raise oslo.utils version, 3.36.5 introduced uuidsentinel.
Change-Id: I8c81e0c1944c239e460befbf886993270902ee04
The repo is Python 3 now, so update hacking to version 3.0 which
supports Python 3.
Fix problems found.
Update local hacking checks for new flake8.
Remove hacking and friends from lower-constraints, they are not needed
to be installed at run-time.
Move hacking tests to another subdir, import hacking failed since the
subdir was called hacking as well.
Change-Id: I684f0e4be28e529ae2c9d6f4bef5bd840adc8787
Sphinx 1.8 introduced [1] the '--keep-going' argument which, as its name
suggests, keeps the build running when it encounters non-fatal errors.
This is exceptionally useful in avoiding a continuous edit-build loop
when undertaking large doc reworks where multiple errors may be
introduced.
[1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045
Change-Id: I84e64e1ba60341408c400bef7c351ec0ebab2ef1
This patch changes it to raise error on 'tox -epep8' when added
function is too complex.
16 is currently the most complex thing we have:
'ManagerService.update_lease' - blazar/manager/service.py
Change-Id: Ie839351cfe8cdbc4947c4c64513ccd067e3d1cc7
We have unit tests but we didn't have the coverage report of the
unit tests. This patch adds a zuul job to report the coverage rate
of the unit tests.
It does NOT fail even if the coverage rate is too low. This is just
for reporting so far.
Change-Id: Idec8652cb92e30660546362b66115dd380c2f80e
The api documentation is now published on docs.openstack.org instead
of developer.openstack.org. Update all links that are changed to the
new location.
Note that redirects will be set up as well but let's point now to the
new location.
For details, see:
http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007828.html
Change-Id: Icee2189e5a56e06ae01c7e3eee585e4c7a9553a6
The unit tests fail since no mysqladmin command is installed. Add
bindep.txt to install the needed binaries in our CI environment.
Add also the usual bindep tox environment for developers.
Change-Id: If951f82d6610c6ee54d594d9a8985bc78e135d2b
pylint 2.0.0 and newer releases do not support Python 2, which breaks
Python 2 tests. This patch changes the requirement for pylint to use
version 1.9.1. The requirement is moved out of test-requirements.txt,
since pylint is not tracked in global requirements.
Change-Id: I2464ff2fc56b7fe7a92c40ec1555880f4e220479
This patch moves default policy definitions from file-based maintenance
to registering them in code following OpenStack standard[1].
[1] https://governance.openstack.org/tc/goals/queens/policy-in-code.html
Change-Id: I47afa929ebfa30e17c2dbeac31108ecbab67f067
Implements: blueprint policy-in-code
We want to default to running all tox environments under python 3, so
set the basepython value in each environment.
We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.
We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.
Change-Id: Ic5b3298c4ea7ebecac333418888335fc286c6489
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Create a tox environment for running the unit tests against the lower
bounds of the dependencies.
Create a lower-constraints.txt to be used to enforce the lower bounds
in those tests.
Add openstack-tox-lower-constraints job to the zuul configuration.
Uncap eventlet at the same time to make the requirements match the
global list.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: I3d4c66be32a7e5f1bae11fcba9491f9e26b59bb6
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The gating on python 3.4 is restricted to <= Mitaka. This is due to
the change from Ubuntu Trusty to Xenial, where only python3.5
is available. There is no need to continue to keep these settings.
Change-Id: Iabbbc57f359e0c47d87bbc9c90e62451389a96d7
Although the Climate project was renamed to Blazar in 2014, the code has
still been using the climate namespace.
This patch moves all code to the blazar directory and allows users and
operators to use the 'blazar' command namespace. The 'climate' namespace
remains O release to allow users of Blazar time to move their own
code to the blazar namespace, but will be removed in P release
development cycle.
Change-Id: Icbe6fab1051aae4ac819982a1fa4f323cb0bf2d0
Partial-Bug: #1662734
When tox runs commands which are installed in the system but not in its
virtual environments, we get a warning:
WARNING:test command found but not installed in testenv
This patch adds whitelist_externals into the testenv section of tox.ini
to avoid such warnings when running rm with tox -e docs.
Change-Id: I7144bd30483bb8068c2eda2c9e55ee9bee8be93d
This patch deletes the remaining oslo-incubator code. It is the last in
the series of oslo related patches. oslo-incubator code is now
completely removed from the Blazar code base.
Change-Id: Iead9cd224666dc15e14796f5454c835f293c282a
This commit replaces the old configuration file generator from the
openstack.common.config module by oslo-config-generator [1]. It also
deletes files under tools/config which are now unused. New files are
added for the generator:
- climate/opts.py is for collecting climate options
- etc/climate/climate-config-generator.conf contains generator configs
- etc/climate/README-climate.conf.txt describes how to generate a
sample configuration file
In addition, a testenv:genconfig section is added to tox.ini and
settings for the oslo.config.opts entry point are added in setup.cfg.
[1] http://docs.openstack.org/developer/oslo.config/generator.html
Change-Id: Ifd352dee176310fd667d1523a85afd3ddf9ab5da
Closes-Bug: #1658908
The Blazar code base is not yet compatible with Python 3. Having tox
environments for them is a first step towards fixing it.
Change-Id: I04441e4881eb7fe9b4c12d65392796c1020b41df
The aim is to remove the last user of posix-ipc so it can be removed
from global-requirements.txt.
This commit also re-generates the sample config to reflect the config
group change for 'disable_process_locking' and 'lock_path'.
Change-Id: I777424370dc02c3164803a63331a1befb8531de5
We need to use the newer hacking library to avoid conflicts when we
enable constraints. This in turn needs a newer pbr.
Do this as a separate change to make backporting easier.
Change-Id: I17df901a6e154dda23bf8eb883ed5ef74bf8e556
Python 2.6 support would be dropped by
Infra team from mitaka,CI would no longer be testing it,
so projects should drop it too.
Change-Id: Ib08718c5eec5b8b364b7e9a3deed11f7c080211c
Since Blazar was in Winter, lots of tech debt was added.
This big change is actually trying to provide a +1 from Jenkins voting jobs.
ie.
- fix calls to oslo_config
- correct unittests failing due to removed assert_called()
- remove pep8 check for verifying blazar.conf (can be readded later)
- fix oslo_messaging imports
Not sure it's fully functional, Tempest needs to be fixed too but I
hope the gate will allow that change to pass.
Change-Id: Ib70b5b48b47626fc2613ee894d1162219417994f
Manually update from global requirements.
Remove obsolete docutils pin.
Regenerate climate config file.
Fix testsuite for testtools change.
Workaround PYTHONHASHSEED setting in tox, disable for now so that tests
always pass.
Change-Id: I8c4a458371b28c91c5b848094e56038a16d6afc3
Pierre Riteau