Neutron constrained the version of hacking < 1.2.0, but since then the
unit tests fails with:
ERROR: Double requirement given: hacking<1.2.0,>=1.1.0 (from -ri https://opendev.org/openstack/neutron/raw/branch/master/test-requirements.txt (line 4)) (already in hacking>=1.1.0 (from -r [..]networking-powervm/test-requirements.txt (line 4)), name='hacking')
So let's simply use the same constraint as set in neutron.
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
The appdirs lower constraint of 1.3.0 does not work with isort >=
4.3.5, which references appdirs.system, which wasn't added until
appdirs 1.4.0. Neutron addressed this by increasing the lower
constraint to 1.4.3  so we'll do the same.
Updated two config options namely heal_and_optimize_interval
and exception_interval with their default values and
description in the configuration table.
* Use openstack-lower-constraints-jobs template, remove individual
* Sort list of templates
Neutron has implemented policy-in-code , which broke some of our
unit tests that were trying to load defaults from a neutron
policy.json file that no longer exists. Since policy defaults are now
in code, we do not need to load defaults from a file anymore, so this
The Stein supported runtimes proposal  has chosen py36 over py35
due to the communities move to testing on Ubuntu 18.04, where py36
is the default runtime. We update tox.ini and setup.cfg accordingly.
Python 3.6 handles dict order differently than in previous python
versions, so to get py36 to work this uses a sorted() call to make
the behavior consistent across python versions for our network
bridge cleanup and adjusts the corresponding test accordingly.
We also add a py37 option to the tox.ini to facilitate future-looking
tests per the resolution on keeping up with Python 3 releases .
The py35 option will eventually need to be removed from tox.ini, but
this keeps it for now in order to allow time for folks to transition.
As previously commented, automatic tox envs (pyXX) will use the python
version appropriate to that env and ignore basepython inherited from
[testenv], so we no longer specify a basepython explicitly for these.
With moving away from required milestone releases, the version numbers
calculated by PBR on the master branch will not work for those testing
upgrades from the last stable release. More details can be found in the
mailing list post here:
This is an empty commit that will cause PBR to increment its calculated
version to get around this.
PBR will see the following which will cause it to increment the version:
Please merge this patch as soon as possible to support those testing
Signed-off-by: Sean McGinnis <email@example.com>
As part of the Denver PTG  we decided networking related projects
that are "current" and want to receive neutron-lib consumption patches
on an on-going basis should indicate such with a well defined comment
in their requirements.txt. This allows us to easily find the list of
project to receive neutron-lib consumption patches  by searching for
In addition, projects opting-in for these patches are also attesting
they will stay up to date with TC and infra initiatives to ensure
consumption patches can flow freely.
This patch adds the "neutron-lib-current" string to requirements.txt
opting in for neutron-lib consumption patches.
This cleans up .gitignore, removing things that no longer seem to be
relevant (e.g. .venv) and adding comments and formatting similar to
the suggestions proposed for openstack-dev/cookiecutter .
This adds a unit test job running under Python 3.6 as part of the
python3-first goal. See the python3-first goal document for details:
This is manually generated because the script doing this for other
projects does not currently handle the neutron special case.
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
See the python3-first goal document for details:
Neutron added an optional host argument to the get_device_details RPC
method a long time ago  but a recent change  has made that no
longer really optional, at least for our usage. This adds host to our
calls so that VIF plug will not timeout with an error in the neutron
logs stating "Device %s has no active binding in host None".
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.
The neutron project bumped its hacking level in test-requirements via
Ia7c7c5a44727f615a151e1e68dd94c7ed42f974f, causing a conflict with ours.
Make our pep8 pass by adding an ignore rule for W504 (line break after
binary operator) to match neutron.
Pulling neutron from pypi has been working because we happen to
work with neutron 12.x (queens), but we should really be testing
our master branch with neutron's master branch, not with queens.
This effectively reverts 3b55348dfb.
Some lower constraints needed to be updated to match neutron's
It also uses git.openstack.org instead of github.com in links.
In anticipation of repointing our tox to use neutron master (rather than
staying one release behind via requirements, as we have been), we needed
to fix some pep8 errors that got un-ignored.
Update translations for the Queens release.
Note: this is being cherry-picked from stable/queens to master
instead of the other way around. The translations were actually done
based on queens, so that is where they were originally merged. In
hindsight, they should also be merged in master so that it has the
latest translations as well, so we should have followed the normal
process of merging in master first, but too late for that now.
(cherry picked from commit eb5d4bf7f4)
We will manage the eventlet version using constraints now. See the
thread starting at
for more details.
Meanwhile, it was necessary to address these issues in
Package u'setuptools' is used in requirements.txt but not in
Package u'sphinx' is constrained to 1.6.5 which does not match the
minimum version specifier 1.6.2 in test-requirements.txt
Signed-off-by: Doug Hellmann <firstname.lastname@example.org>
We should use py3 for pep8 as it is stricter than pep8 on py2.7
and for consistency with nova-powervm .
Neutron was added to global-requirements  which breaks the tox
install of neutron. Neutron is now listed in requirements.txt and has
been removed as a dependency in tox.ini. One side effect is that we
based the policy.json path on the location of the neutron git directory
which is no longer the case. The test code has been updated to reflect
the new location of the policy file.
The neutron.common.topics module was rehomed into neutron-lib with
This patch consumes it by using neutron-lib's version of the module in
prep for Ia4a4604c259ce862597de80c6deeb3d408bf0e95
The link to hacking docs reroutes to a new location. This change
updates the link to the new location so that we're no longer dependent
on rerouting, which probably won't work forever.
This patchset handles maxcapacity in binding profile of Neutron port
for SR-IOV. maxcapacity is retrieved from binding profile and pushed into
vif object. Additional changes will be in nova_powervm vif driver to
gather and validate and pass onto pypowervm layer.
In both nova_powervm and pypowervm layers of code, maximum capacity is
validated. Maximum capacity cannot be less than capacity (minimum capacity)
and maximum capacity cannot be greater than 1 (100 %).