The coe mesos has not been maitenaned for quite some
time and hasn't got much attetion from the community
in general. As discussed in the mailing list  we
are dropping for now.
In this patch, we start by removing the mesos driver
and its test cases. This part of the code has no impact
for other drivers. Then we can clean up mesos references
that affect the API.
UPPER_CONSTRAINTS_FILE is old name and deprecated
This allows to use upper-constraints file as more
readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>.
In Change I523a4a85867f82d234ba1f3e6fad8b8cd2291182, the pep8 test was
Fix up code so that pep8 passes.
In addition to that following change has been added here to unbreak CI:
Add WebTest as an indirect test dependency
Pecan has made webtest an optional dependency for testing only .
Since it is still used for testing we need to add it to our
Additionally remove non-voting status of coverage job. 1% toleration is
enabled for allowed_extra_missing lines. If we need to lower the 90%
threshold for coverage in the future, this can be decided then.
This commit drops magnum-functional-api (which uses legacy-dsvm-base due
to be removed in the V cycle) in favour of
magnum-tempest-plugin-tests-api defined in the magnum-tempest-plugins
repo (which uses the new devstack-tempest job recommended for running
Tempest tests in Zuul v3) for API Tempest tests.
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, those are not needed
Sphinx 1.8 introduced  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
According to Openstack summit session ,
stestr is maintained project to which all Openstack projects should migrate.
Let's switch to stestr as other projects have already moved to it.
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.
Signed-off-by: Doug Hellmann <email@example.com>
Bindep is a tool for checking the presence of binary packages needed
to use an application / library. It started life as a way to make it
easier to set up a development environment for OpenStack projects.
Signed-off-by: Paul Belanger <firstname.lastname@example.org>
pip_missing_reqs has some bugs and is renamed(see )
to pip_check_reqs since v2.0. Switch to pip_check_reqs
module to get the bug fixes and updates.
This change prepares the magnum project to start implementing
policies in code. Subsequent patches will register more magnum
policies in code and remove the corresponding entry from the
policy file maintained in source.
This is part of a community effort to provide better user
experience for those having to maintain RBAC policy. More
information on this effort can be found below:
Co-authored-By: Dai Dang-Van <email@example.com>
Implements: blueprint policy-in-code
Sphinx complaints about a missing file, fix this with renaming the file
to the intented name.
Treat sphinx warnings as errors to avoid these kind of problems. Remove
the not needed note anymore, this works fine as is.
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.
Similarly to pep8 checks, this allows enforcing a consistent
style of the shell scripts accross modfications. For now
only the indentation is enforced to reduce code churn.
Many deprecations are triggered early (on imports, for example).
To make sure all DeprecationWarning messages are emitted we enable
them via the PYTHONWARNINGS environment variable.