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.
Change-Id: Ic4d97db6c947264806e5ef9e35f21f764cbecf46
This is a mechanically generated patch to ensure unit testing is in place
for all of the Tested Runtimes for Train.
See the Train python3-updates goal document for details:
https://governance.openstack.org/tc/goals/train/python3-updates.html
Change-Id: I1f280a05e3d329abf07c9d50ae28aee602691369
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
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: Ia58fa2a5350d2c4d9dc8b54ac76a902005f85f30
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 [1] so we'll do the same.
[1] 9bfe63cf0786176cd48943d902690198e02fdb70
Change-Id: I5ba07e5504fe786bc7dcb42ef0f43034d5384f6f
Updated two config options namely heal_and_optimize_interval
and exception_interval with their default values and
description in the configuration table.
Change-Id: Ie75b787c302ddd7a5e81a9ff6e3208f72f94671a
Closes-Bug: 1610404
Small cleanups:
* Use openstack-lower-constraints-jobs template, remove individual
jobs.
* Sort list of templates
Change-Id: Ie5bec468aa6a8a8c437fd3196e1eeea039374f00
Needed-By: https://review.openstack.org/623229
Neutron has implemented policy-in-code [1], 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
removes that.
[1] f8984c66996c876d5bbd0cc0c4c47f567e515511
Change-Id: I862e27d9f2284415dcdc57074e2136603d79233d
The Stein supported runtimes proposal [1] 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 [2].
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.
[1] https://review.openstack.org/611080
[2] https://review.openstack.org/613145
Change-Id: Iebdc9357a79cae1923109fb5e37fefb8021af18d
The openstack-discuss mailing list has replaced openstack-dev. This
updates the email address accordingly.
Change-Id: I1e9f8f5d6767b170031012d7aa468c8d090f060d
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:
http://lists.openstack.org/pipermail/openstack-dev/2018-October/135706.html
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:
Sem-Ver: feature
Please merge this patch as soon as possible to support those testing
upgrades.
Change-Id: I93af9d7fc8605a751dfc017b818bbb6d5691a83c
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
As part of the Denver PTG [1] 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 [2] by searching for
the string.
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.
[1] https://etherpad.openstack.org/p/neutron-stein-ptg
[2] https://docs.openstack.org/neutron-lib/latest/contributor/contributing.html#phase-4-consume
Change-Id: I7a2e538ad345d4a2d1cb398c3c325916f54df9e1
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 [1].
[1] https://review.openstack.org/#/c/592520/
Change-Id: I49ef78256f1f6f3942663441e7708536687b2363
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:
https://governance.openstack.org/tc/goals/stein/python3-first.html
This is manually generated because the script doing this for other
projects does not currently handle the neutron special case.
Change-Id: I92e7b79df29031b6d94d6ab93305f4e20c1ec3a1
Story: #2002586
Task: #24324
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
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
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: If5013756f45f5ef18628694cc98eff78398810ad
Story: #2002586
Task: #24324
Neutron added an optional host argument to the get_device_details RPC
method a long time ago [1] but a recent change [2] 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".
[1] f7064f2b6c6ba1d0ab5f9872b2d5ad7969a64e7b
[2] 01bdb47199468805b714ce4c00c7492951267585
Closes-Bug: #1784950
Change-Id: Ida4102427405e17e42ddc463df4a63c2ba7dcb82
neutron has bumped the min requirement for neutron-lib to 1.18.0 [1]
and requested that other networking-* projects that depend on master
do the same [2]. This makes that change.
[1] 02e9f270e913f26a16f40f161c333e54f2dbdef7
[2] http://lists.openstack.org/pipermail/openstack-dev/2018-July/132412.html
Change-Id: I2e38a02c5d34b2b62241e8a3cb8aafffc3c48d6b
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: Id348ed0c3cb16637990acfa6aaf529cf2567de9a
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.
Change-Id: Ifb9583437edba41addff5d3650b350a8941d3150
This removes unused sections from tox.ini and fixes the coverage
section so that it will actually work.
Change-Id: I40c00c3a05d73f11605b0a415eccda447a36f6cd
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
master branch.
It also uses git.openstack.org instead of github.com in links.
Change-Id: I18050cfdf9401009f0a87d6cc8b968b7fe3a3bf0
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.
Change-Id: I1c25ebe62108e300c16c0a503f1dcc919259bf7d
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.
Change-Id: I03ab7bef6e9826631e45e3cb62c7f58600e3cd81
(cherry picked from commit eb5d4bf7f4)
We will manage the eventlet version using constraints now. See the
thread starting at
http://lists.openstack.org/pipermail/openstack-dev/2018-April/129096.html
for more details.
Meanwhile, it was necessary to address these issues in
check-requirements:
Package u'setuptools' is used in requirements.txt but not in
lower-constraints.txt
Package u'sphinx' is constrained to 1.6.5 which does not match the
minimum version specifier 1.6.2 in test-requirements.txt
Change-Id: Ie0e7b132acab2300e766ae57613a702db21b142f
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
We should use py3 for pep8 as it is stricter than pep8 on py2.7
and for consistency with nova-powervm [1].
[1] https://review.openstack.org/#/c/558868/
Change-Id: Ife99071b513f98fa2945444f7f969ed0ed4ffa42
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.
See http://lists.openstack.org/pipermail/openstack-dev/2018-March/128352.html
for more details.
Change-Id: I8e30d45a34c22e1225ad46f033495f14848c8819
Depends-On: https://review.openstack.org/555034
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Neutron was added to global-requirements [1] 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.
[1] https://review.openstack.org/#/c/550475/
Change-Id: Ibc42b8a835d1a5e6ce09640f5bdf833c2171a9a9
The neutron.common.topics module was rehomed into neutron-lib with
commit Ie88b84949cbd55a4e7ad06341aab77b286cdc485
This patch consumes it by using neutron-lib's version of the module in
prep for Ia4a4604c259ce862597de80c6deeb3d408bf0e95
Change-Id: I7de0ceeeeee4dc19cfce499dab1697c7e5cc2568
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.
Change-Id: Id84ff6a55e59604f9a5d24b97cb91d5ccc76b348
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 %).
Change-Id: I0eb627b94e66158c68fddd7a2a5fc90467efc20d
Elod Illes