e338df4244
Builds on prior attempts to register FWaaS resources to the quota
engine, such as commit Ia4d6b9a65acd1111a050dc73b63a1f0ce619cb55
which had to be reverted for bug 1513280 for failing gate via commit
28948f6559.
Since with router insertion a user can have a separate firewall
and policy per targeted router in their tenant, the original
fixes which had defaults of only 1 were too low.
Also added the release notes and updated the options to reflect
the quota.
Change-Id: I68a5538f7bc8df78212633c73eeca0eaae0d8455
Closes-Bug: #1399280
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.
|