Add reno for "OVS based l2 Firewall driver for FWaaS v2"
This commit adds releasenote for https://review.openstack.org/#/c/447251 Change-Id: I70e2a6514459a0993246bb7cdcab9c2dae2344ea Partial-Implements: blueprint fwaas-api-2.0
This commit is contained in:
parent
4c97a1cf91
commit
b0b8d9e8df
16
releasenotes/notes/ovs-firewall-driver-c347ea0a560b7e38.yaml
Normal file
16
releasenotes/notes/ovs-firewall-driver-c347ea0a560b7e38.yaml
Normal file
@ -0,0 +1,16 @@
|
|||||||
|
---
|
||||||
|
issues:
|
||||||
|
- |
|
||||||
|
Currently, the FWaaSv2 L2 driver can be configured as:
|
||||||
|
|
||||||
|
``firewall_driver = ovs``
|
||||||
|
|
||||||
|
And the Security Group driver is specified as:
|
||||||
|
|
||||||
|
``firewall_driver = openvswitch``
|
||||||
|
|
||||||
|
If both are configured, the packet will still only hit the FWaaS table in
|
||||||
|
OVS and will not traverse the rules in the SG table. There are some fixes
|
||||||
|
needed to support this model which are being tested and will be merged
|
||||||
|
shortly. Currently there are no checks to allow only one of FWaaS L2 or SG
|
||||||
|
to be configured.
|
Loading…
Reference in New Issue
Block a user