We jubilantly announce the release of:
networking-generic-switch 7.4.0: Generic Switch ML2 Neutron Driver
This release is part of the dalmatian release series.
The source is available from:
https://opendev.org/openstack/networking-generic-switch
Download the package from:
https://pypi.org/project/networking-generic-switch
Please report issues through:
https://bugs.launchpad.net/networking-generic-switch/+bugs
For more details, please see below.
7.4.0 ^^^^^
New Features
* Adds a new device driver, "netmiko_cumulus_nvue", for managing NVIDIA Cumulus based switch devices via NVUE.
* Add support for *ngs_allowed_vlans* and *ngs_allowed_ports* configuration options to allow defining specific VLANs and ports allowed on a switch.
Changes in networking-generic-switch 7.3.0..7.4.0 -------------------------------------------------
6ec2946 Cumulus NVUE support 68fc9b0 Update to match latest development cycle f0655a9 Add VLAN and Port allowlist 92fd6b6 Fix codespell reported errors bc3511f [CI] Remove not defined job from queue 4ef0a04 reno: Update master for unmaintained/zed 6cde0aa Update master for stable/2024.1 253ee45 Replace usage of deprecated path for test decorators 54843db Add python3.10 support in testing runtime
Diffstat (except docs and test files) -------------------------------------
networking_generic_switch/devices/__init__.py | 35 ++++ .../devices/netmiko_devices/cumulus.py | 78 ++++++++ networking_generic_switch/generic_switch_mech.py | 40 +++- .../add-cumulus-nvue-support-2207d67edc12e866.yaml | 5 + ...d-vlan-and-port-allowlist-0b1c29967210fbfb.yaml | 6 + releasenotes/source/2024.1.rst | 6 + releasenotes/source/index.rst | 1 + releasenotes/source/zed.rst | 2 +- setup.cfg | 6 +- test-requirements.txt | 8 +- tox.ini | 12 +- zuul.d/project.yaml | 7 - 18 files changed, 594 insertions(+), 64 deletions(-)
Requirements updates --------------------
diff --git a/test-requirements.txt b/test-requirements.txt index 5a1cbbe..8995bed 100644 --- a/test-requirements.txt +++ b/test-requirements.txt @@ -1,4 +0,0 @@ -# The order of packages is significant, because pip processes them in the order -# of appearance. Changing the order has an impact on the overall integration -# process, which may cause wedges in the gate later. - @@ -6 +2 @@ -coverage!=4.4,>=4.0 # Apache-2.0 +coverage>=4.0 # Apache-2.0 @@ -8 +4 @@ fixtures>=3.0.0 # Apache-2.0/BSD -stestr>=1.0.0 # Apache-2.0 +stestr>=2.0.0 # Apache-2.0