networking-vpp 20.05
Milestone information
- Project:
- networking-vpp
- Series:
- trunk
- Version:
- 20.05
- Released:
- Registrant:
- Jerome Tollet
- Release registered:
- Active:
- No. Drivers cannot target bugs and blueprints to this milestone.
Activities
- Assigned to you:
- No blueprints or bugs assigned to you.
- Assignees:
- No users assigned to blueprints and bugs.
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- No bugs are targeted to this milestone.
Download files for this release
Release notes
This latest version of Networking-vpp is updated to work with VPP 20.05. In this release, we've made the below changes:
- We've added a class that defines network type APIs and implements them. The network types supported are VLAN, Flat and GPE. Our intent is to add support for pluggable network types without the need to modify code. We'll be continuing our work to enhance this feature in the next release.
- We've updated the code to be compatible with VPP 20.05 API changes.
- We've added code to deal with poorly formed security group subnets. For instance, 1.2.3.4/0 is completely acceptable in a security group rule. Previously, VPP accepted this in its API calls but this is not currently the case. We've fixed this up at the high level to be acceptable to VPP.
- We've fixed an issue with missing package data required for VPP API message validation.
- We've dropped VPP 19.04 compatibility code.
- We've fixed an issue with the security group mechdriver code in which a SG rule is added but not pushed out to VPP until the next rule is added or the security group is changed.
- We've moved VPP specific constants to a dedicated vpp_constants.py file.
- Due to a VPP issue, GPE support will be deferred to the 20.05.1 release.
- We've been doing the usual round of bug fixes, clean-ups and updates - the code will work with VPP 20.05, the OpenStack Stein release & Python 3.
Changelog
This release does not have a changelog.
0 blueprints and 0 bugs targeted
There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.
