March 2021 - Release-announce - lists.openstack.org

patrole 0.12.0 (wallaby)
by no-reply＠openstack.org 26 Mar '21

26 Mar '21

We are tickled pink to announce the release of: patrole 0.12.0: Patrole is a tool for verifying that Role-Based Access Control is being enforced across OpenStack deployments. This release is part of the wallaby release series. The source is available from: https://opendev.org/openstack/patrole Download the package from: https://tarballs.openstack.org/patrole/ Please report issues through: https://bugs.launchpad.net/patrole/+bugs For more details, please see below. 0.12.0 ^^^^^^ Prelude This release is to tag the Patrole for OpenStack Wallaby release. This release marks the start of Wallaby release support in Patrole. After this release, Patrole will support below OpenStack Releases: * Wallaby * Victoria * Ussuri * Train Current development of Patrole is for OpenStack Xena development cycle. Every Patrole commit is also tested against master during the Xena cycle. However, this does not necessarily mean that using Patrole as of this tag will work against a Xena (or future release) cloud. To be on safe side, use this tag to test the OpenStack Wallaby release. Changes in patrole 0.11.0..0.12.0 --------------------------------- 54fc749 Add releasenote to tag the Patrole for Wallaby release f64b81e Fix gate for handling of deprecated rules and image client 9ec7c46 Changed minversion in tox to 3.18.0 27f671f Reuse tempest to create admin client manager b73e108 Restore test user's original roles during clean up f569957 Remove the tests for unsupported Nova APIs 700c1db Remove stable/stein testing jobs 65fef1d Fix creating of client manager for network tests Diffstat (except docs and test files) ------------------------------------- .zuul.yaml | 12 --- patrole_tempest_plugin/policy_authority.py | 34 ++++--- patrole_tempest_plugin/rbac_rule_validation.py | 2 + patrole_tempest_plugin/rbac_utils.py | 26 +++-- .../api/compute/test_floating_ips_bulk_rbac.py | 112 --------------------- .../test_server_misc_policy_actions_rbac.py | 3 + .../api/compute/test_virtual_interfaces_rbac.py | 64 ------------ .../api/identity/v3/test_tokens_negative_rbac.py | 2 +- .../patrole-wallaby-release-cbc6687e4aeff56a.yaml | 17 ++++ tox.ini | 12 +-- 19 files changed, 126 insertions(+), 326 deletions(-)

1 0

masakari 11.0.0.0rc1 (wallaby)
by no-reply＠openstack.org 26 Mar '21

26 Mar '21

Hello everyone, A new release candidate for masakari for the end of the Wallaby cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/masakari/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Wallaby release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/wallaby release branch at: https://opendev.org/openstack/masakari/src/branch/stable/wallaby Release notes for masakari can be found at: https://docs.openstack.org/releasenotes/masakari/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/masakari/+bugs and tag it *wallaby-rc-potential* to bring it to the masakari release crew's attention.

1 0

masakari-monitors 11.0.0.0rc1 (wallaby)
by no-reply＠openstack.org 26 Mar '21

26 Mar '21

Hello everyone, A new release candidate for masakari-monitors for the end of the Wallaby cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/masakari-monitors/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Wallaby release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/wallaby release branch at: https://opendev.org/openstack/masakari-monitors/src/branch/stable/wallaby Release notes for masakari-monitors can be found at: https://docs.openstack.org/releasenotes/masakari-monitors/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/masakari-monitors/+bugs and tag it *wallaby-rc-potential* to bring it to the masakari-monitors release crew's attention.

1 0

masakari-dashboard 4.0.0.0rc1 (wallaby)
by no-reply＠openstack.org 26 Mar '21

26 Mar '21

Hello everyone, A new release candidate for masakari-dashboard for the end of the Wallaby cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/masakari-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Wallaby release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/wallaby release branch at: https://opendev.org/openstack/masakari-dashboard/src/branch/stable/wallaby Release notes for masakari-dashboard can be found at: https://docs.openstack.org/releasenotes/masakari-dashboard/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/masakari/+bugs and tag it *wallaby-rc-potential* to bring it to the masakari-dashboard release crew's attention.

1 0

openstack-heat 16.0.0.0rc1 (wallaby)
by no-reply＠openstack.org 26 Mar '21

26 Mar '21

Hello everyone, A new release candidate for openstack-heat for the end of the Wallaby cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/heat/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Wallaby release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/wallaby release branch at: https://opendev.org/openstack/openstack-heat/src/branch/stable/wallaby Release notes for openstack-heat can be found at: https://docs.openstack.org/releasenotes/heat/

1 0

heat-dashboard 5.0.0.0rc1 (wallaby)
by no-reply＠openstack.org 26 Mar '21

26 Mar '21

Hello everyone, A new release candidate for heat-dashboard for the end of the Wallaby cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/heat-dashboard/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Wallaby release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/wallaby release branch at: https://opendev.org/openstack/heat-dashboard/src/branch/stable/wallaby Release notes for heat-dashboard can be found at: https://docs.openstack.org/releasenotes/heat-dashboard/ If you find an issue that could be considered release-critical, please file it at: https://storyboard.openstack.org/#!/project/openstack/heat-dashboard and tag it *wallaby-rc-potential* to bring it to the heat-dashboard release crew's attention.

1 0

neutron 18.0.0.0rc1 (wallaby)
by no-reply＠openstack.org 26 Mar '21

26 Mar '21

Hello everyone, A new release candidate for neutron for the end of the Wallaby cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/neutron/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Wallaby release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/wallaby release branch at: https://opendev.org/openstack/neutron/src/branch/stable/wallaby Release notes for neutron can be found at: https://docs.openstack.org/releasenotes/neutron/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/neutron/+bugs and tag it *wallaby-rc-potential* to bring it to the neutron release crew's attention.

1 0

zaqar-ui 10.0.0.0rc1 (wallaby)
by no-reply＠openstack.org 26 Mar '21

26 Mar '21

Hello everyone, A new release candidate for zaqar-ui for the end of the Wallaby cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/zaqar-ui/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Wallaby release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/wallaby release branch at: https://opendev.org/openstack/zaqar-ui/src/branch/stable/wallaby Release notes for zaqar-ui can be found at: https://docs.openstack.org/releasenotes/zaqar-ui/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/zaqar-ui/+bugs and tag it *wallaby-rc-potential* to bring it to the zaqar-ui release crew's attention.

1 0

ovn-octavia-provider 1.0.0 (wallaby)
by no-reply＠openstack.org 26 Mar '21

26 Mar '21

We jubilantly announce the release of: ovn-octavia-provider 1.0.0: OpenStack Octavia integration with OVN This release is part of the wallaby release series. The source is available from: https://opendev.org/openstack/ovn-octavia-provider Download the package from: https://tarballs.openstack.org/ovn-octavia-provider/ Please report issues through: https://bugs.launchpad.net/neutron/+bugs For more details, please see below. 1.0.0 ^^^^^ New Features * Add support for the SCTP protocol in the OVN provider driver. Changes in ovn-octavia-provider 0.3.0..1.0.0 -------------------------------------------- 516e5c3 Start running the tempest API tests 7bd6936 Switch to new rolevar for run-temepst role b796f4e Add SCTP support bdb7ca6 Remove devstack-gate reference c7969b6 Update sample local.conf to mention OVN_BRANCH 6e30b85 Check if no members in pool better in batch update a641c2c Don't try to store protocol=None in OVSDB ffc3160 Update to pylint 2.6.0+ 13331aa Collect OVN logs 15b3ca3 Enable the IPv6 tempest tests 2399b69 Correctly set member operating status ba4c94e Change to build OVN from source 2225062 Delay string interpolations at logging calls 23f0bed Remove work around change for test_port_forwarding b882a7f Fix gate failure a238faf Return UnsupportedOptionError() on loadbalancer failover 037d3d0 Use get_ovn_ovsdb_retry_max_interval() 723ca5a Retry status updates to Octavia 5b0715d Fix leaked file descriptors by cleaning up objects aa4ffe5 Change devstack script to correctly configure driver 350a26b Include python36-devel in bindep 7a8e45b Add master and release tempest jobs b68d2a7 Fix and enable test_port_forwarding 884d5e1 Switch from unittest2 compat methods to Python 3.x methods a278e59 Add Python3 wallaby unit tests 76b2088 Fix the check for allowed_cidrs in listeners c2c87e6 Update master for stable/victoria 481f0b3 Mark test_port_forwarding unstable to fix gate 2476204 Set OPERATING_STATUS to ONLINE when pool created with listener Diffstat (except docs and test files) ------------------------------------- HACKING.rst | 1 + bindep.txt | 4 + devstack/local.conf.sample | 15 +- devstack/plugin.sh | 4 +- lower-constraints.txt | 78 +++++---- ovn_octavia_provider/common/clients.py | 2 +- ovn_octavia_provider/common/constants.py | 6 +- ovn_octavia_provider/driver.py | 41 ++--- ovn_octavia_provider/event.py | 6 +- ovn_octavia_provider/hacking/checks.py | 12 ++ ovn_octavia_provider/helper.py | 93 ++++++----- ovn_octavia_provider/ovsdb/impl_idl_ovn.py | 29 ++-- ovn_octavia_provider/ovsdb/ovsdb_monitor.py | 4 +- .../notes/add-sctp-support-bedfed905e1f5a58.yaml | 4 + releasenotes/source/index.rst | 1 + releasenotes/source/victoria.rst | 6 + requirements.txt | 16 +- test-requirements.txt | 10 +- tox.ini | 11 ++ zuul.d/base.yaml | 42 +++-- zuul.d/project.yaml | 8 +- 32 files changed, 464 insertions(+), 260 deletions(-) Requirements updates -------------------- diff --git a/requirements.txt b/requirements.txt index a311457..a4266b8 100644 --- a/requirements.txt +++ b/requirements.txt @@ -5 +5 @@ -keystoneauth1>=3.4.0 # Apache-2.0 +keystoneauth1>=3.14.0 # Apache-2.0 @@ -7,2 +7,2 @@ netaddr>=0.7.18 # BSD -neutron-lib>=2.1.0 # Apache-2.0 -oslo.config>=5.2.0 # Apache-2.0 +neutron-lib>=2.2.0 # Apache-2.0 +oslo.config>=6.0.0 # Apache-2.0 @@ -12 +12 @@ oslo.serialization>=2.28.1 # Apache-2.0 -oslo.utils>=3.33.0 # Apache-2.0 +oslo.utils>=4.5.0 # Apache-2.0 @@ -14,2 +14,2 @@ ovs>=2.8.0 # Apache-2.0 -ovsdbapp>=0.17.0 # Apache-2.0 -pbr!=2.1.0,>=2.0.0 # Apache-2.0 +ovsdbapp>=1.3.0 # Apache-2.0 +pbr>=4.0.0 # Apache-2.0 @@ -17,2 +17,2 @@ SQLAlchemy>=1.2.19 # MIT -tenacity>=5.0.2 # Apache-2.0 -octavia-lib>=1.3.1 # Apache-2.0 +tenacity>=6.0.0 # Apache-2.0 +octavia-lib>=2.2.0 # Apache-2.0 diff --git a/test-requirements.txt b/test-requirements.txt index bbd2336..eb79de9 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -13,3 +13 @@ stestr>=1.0.0 # Apache-2.0 -pylint==2.3.0 # GPLv2 -isort==4.3.21 # MIT -octavia-lib>=1.3.1 # Apache-2.0 +pylint>=2.6.0 # GPLv2 @@ -21,4 +19,2 @@ testtools>=2.2.0 # MIT -# NOTE: Precisely we need ussuri neutron and neutron 15.y.z is train release -# but zuul installs neutron master as we specify it as required-projects. -# Let's update the lower bound once neutron ussuri is releaesd including beta. -neutron>=15.0.0 # Apache-2.0 +# NOTE: Precisely we need ussuri neutron +neutron>=16.0.0 # Apache-2.0

1 0

monasca-events-api 3.0.0.0rc1 (wallaby)
by no-reply＠openstack.org 26 Mar '21

26 Mar '21

Hello everyone, A new release candidate for monasca-events-api for the end of the Wallaby cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/monasca-events-api/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Wallaby release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/wallaby release branch at: https://opendev.org/openstack/monasca-events-api/src/branch/stable/wallaby Release notes for monasca-events-api can be found at: https://docs.openstack.org/releasenotes/monasca-events-api/ If you find an issue that could be considered release-critical, please file it at: https://storyboard.openstack.org/#!/project/866 and tag it *wallaby-rc-potential* to bring it to the monasca-events-api release crew's attention.

1 0