openstack/neutron-fwaas
Code Issues Proposed changes
master
neutron-fwaas/etc
History
ZhouHeng a9f26b81e2 revive neutron-fwaas project 
This reverts commit caae7b6a6f.

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
2022-03-01 01:01:47 +00:00
..
neutron/rootwrap.d revive neutron-fwaas project 2022-03-01 01:01:47 +00:00
oslo-config-generator revive neutron-fwaas project 2022-03-01 01:01:47 +00:00
oslo-policy-generator revive neutron-fwaas project 2022-03-01 01:01:47 +00:00
README.txt revive neutron-fwaas project 2022-03-01 01:01:47 +00:00

README.txt 

To generate the sample neutron-fwaas configuration files, run the following
command from the top level of the neutron-fwaas directory:

tox -e genconfig

If a 'tox' environment is unavailable, then you can run the following script
instead to generate the configuration files:

./tools/generate_config_file_samples.sh