a9f26b81e2
This reverts commit caae7b6a6f5e8944dbe359b6472be2507bbf5e12. Reason for revert: Many users still need L3 firewalls and Inspur team wants to maintain this project. Neutron drivers team discussed the topic of the maintenance of neutron-fwaas, and agreed to include neutron-fwaas again to Neutron stadium[1]. Some updates have been made: Remove use "autonested_transaction" method, see more [2] Replace "neutron_lib.callbacks.registry.notify" with "registry.publish" Replace rootwrap execution with privsep context execution. Ensure db Models and migration scripts are sync, set table firewall_group_port_associations_v2's two columns nullable=False [1] https://meetings.opendev.org/meetings/neutron_drivers/2022/neutron_drivers.2022-01-28-14.00.log.html#l-14 [2] https://review.opendev.org/c/openstack/neutron-lib/+/761728 Change-Id: I14f551c199d9badcf25b9e65c954c012326d27cd
17 lines
540 B
YAML
17 lines
540 B
YAML
---
|
|
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.
|