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
23 lines
895 B
YAML
23 lines
895 B
YAML
---
|
|
prelude: >
|
|
Resource type **firewall group** has been supported for neutron packet
|
|
logging framework. You can specify firewall group as ``--resource-type``
|
|
for logging API.
|
|
features:
|
|
- |
|
|
Enable to collect network packet log for ACCEPT/DROP action from firewall
|
|
groups. Currently, packet logging supports only L3(router) ports.
|
|
issues:
|
|
- |
|
|
[`bug 1720727 <https://bugs.launchpad.net/neutron/+bug/1720727>`__]
|
|
Currently, we cannot specify the following combination on CLI due to
|
|
missing validation of --resource-type:
|
|
|
|
- --resource-type firewall_group --resource <ID of firewall group>
|
|
- --resource-type firewall_group --resource <ID of firewall group> --target <ID of port>
|
|
|
|
Therefore, you can only run with following combinations:
|
|
|
|
- --resource-type firewall_group --target <ID of port>
|
|
- --resource-type firewall_group
|