Strictly speaking, the new release only contains CI changes, but
we want them on stable/stein, so requesting a release anyway.
Change-Id: I7d024c0d8cd146ba43f367ec43e549270dca74ec
Release the latest code from neutron-lib so that we can begin to consume
it in networking related projects. Particularly, common codes related to
the upgarde check and policy-in-code efforts have been moved from neutron
to neutron-lib.
Change-Id: Iea19e683fdbea04e7f39c26e7b3bffa83031a811
Instead of statically listing the redirections move to a dynamic model.
We move the existing _extras/.htaccess to _templates/htaccess so we have
some control and safety of what goes in there. Connect 'build-finished'
from _exts.deliverables.py to trigger generating the redirects. Doing
so here avoids re-reading the data as deliverables.py ahas already done
that for us.
Change-Id: If6bd59fd478593a84ebcedc3a50af3720d620d3c
the 1.15.0 release of os-vif contained a bug
introduced as part of the brctl removeal.
os-vif 1.15.1 resolves this issue and adds
gate jobs to improve testing.
Depends-On: https://review.openstack.org/#/c/639732/
Change-Id: I58bab7bd8e82f8296a3c3344ac17659e14e0ceb2
senlin:
* Bug fixes and feature implementations that include changes to the API
and breaking change to health policy.
python-senlinclient:
* Bug fix in cluster delete and node delete to work with latest
openstacksdk
senlin-dashboard:
* Bug fix to work with latest openstacksdk
* Bug fix in profile create form submission
senlin-tempest-plugin:
* Add new tests for health policy
Change-Id: I6fb26da9742e31704ff2858bc2e3e3dc1a84d75c
We have static URLs redirecting /constraints/upper/series to the
appropriate git interface. In the next change in this series we move to
a data-driven model so let's supply the data :)
Even though we have tag history that goes back to Folsom only import
Juno and later because that's when we first added constraints support
This means as the create and delete branches for requirements, like
other projects, we have a central source of truth (other than git) from
which to update the htaccess redirects.
I had update deliverables.py to account for the fact most of the
requirements branches don't have a release. This does make the table
look a little funny (as the earliest release is the series eol tag :()
but I'm not sure how we can do better there.
Change-Id: Ie8e60dc865ab301539c0bb085a52dd25f3f62edf
This patch is for the octavia-lib 1.1.0 bugfix release, requirements.txt
update and Stein feature freeze.
Change-Id: If7e4edf1ed4ddc3af5eb5e1e84348b9c4bb2a8de
This is the first step to complete the process which doesn't hold
the whole series of tools available at our disposition in the repo.
Change-Id: I6468fb176d85d0b79cccf6746b8af7a127217b00
- os-vif 1.15.0 removes the use of brctl from the in-tree plugins.
- os-vif 1.15.0 contains minor datamodel changes for stricter
version backleveling and intodues a create_port field in the
VIFPortProfileOpenVSwitch object.
- os-vif 1.15.0 adds native python support for ovsdb commands.
Change-Id: If73c68ce40ed99d1f5e3dab91e505ce324b8837c
Depends-on: https://review.openstack.org/#/c/482226/
This bugfix release contains the backported fix [1]
that has been stuck in CI for a while until the stable/rocky
branch was fixed.
[1] https://review.openstack.org/#/c/631475/
Change-Id: Ibe5aa36cd7d2a5b37cac316aece9f65c10e1b4c6
Ultimately we'll do this dynamically but as a POC lets use the existing
.htaccess file[1] to add them statically. This allows us to test the
end results while we work out how to do this correctly *and* preserve
the current redirect for shade.
[1] This isn't working ATM as until https://review.openstack.org/#/c/638527/
has merged and puppet has been run we don't allow allow any options
in .htaccess.
Change-Id: I3a7d8f8af3d0f1301cbdbcaa5a46e9eb5672a151
The release model was changed in Stein release and
the neutron team only delivered neutron stein b1 only.
This causes a situation that major versions of neutron and
other stadium projects do not match and distributors are forced
to do some tricks so that neutron stein beta and rocky version
of stadium projects.
To address this situation, this commit cuts a new release of
stein b2 for neutron and stein b1 for stadium projects.
In addition, policy-in-code support in stadium projects have
completed, so it is a good timing to release them as well.
Note that this release may help gate failures of networking-bgpvpn
and networking-bagpipe because their gates assume released beta
deliverables. These projects are wokring on migrating legacy jobs
to cope with this situations but beta deliverables from other
neutron stadium projects would help them. This is why I prepare
beta deliverables just two weeks before Stein-3 milestone.
Change-Id: I42839e3168cd2ae2ee13b1fe96776d3982c58838
It contains critical fixes for telemetry integration tests and is
needed in order to pass the tests.
Change-Id: I1487b953c9c44c3d61c87282e36f1b6a654dd044
