a9f26b81e2
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
21 lines
746 B
YAML
21 lines
746 B
YAML
---
|
|
prelude: >
|
|
Enable quotas for FWaaS.
|
|
features:
|
|
- The FWaaS extension will register quotas.
|
|
The default values for quota_firewall and
|
|
quota_firewall_policy are set to 10.
|
|
The default value for quota_firewall_rule
|
|
is set to 100.
|
|
Quotas can be adjusted in the conf files, including
|
|
-1 values to allow unlimited.
|
|
issues:
|
|
- Tenants may receive a 409 Conflict error with a
|
|
message body containing a quota exceeded message
|
|
during resource creation if their quota is exceeded.
|
|
other:
|
|
- Operators that increase the default limit for quota_routers
|
|
from 10 may want to bump FWaaS quotas as well, since with
|
|
router insertion a tenant can potentially have a unique
|
|
policy and firewall for each router.
|