All Amphoras consume quotas for "admin" tenant in devstack
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octavia |
Invalid
|
High
|
Unassigned |
Bug Description
All amphoras are being created under the same tenant (in devstack, admin tenant).
The quota for that selected tenant will be used by all other tenants. For example: the default quota for instances for each tenant is: 10.
What happens if we exceed that number? Not to mention that in case that we have a pool or Active/Standby configuration, we will consume that quota even faster.
Possible solution:
In HA-Routers, ports[1] and networks[2] are being created under no tenant ("blank tenant")
Alternate solution:
Use a service account with a high quota for the Octavia service.
[1] https:/
[2] https:/
Changed in octavia: | |
importance: | Undecided → High |
Changed in octavia: | |
assignee: | nobody → Bharath (bharathm) |
summary: |
- All Amphoras consume quotas for a single tenant + All Amphoras consume quotas for "admin" tenant in devstack |
I guess neutron uses 'blank tenant' to prevent the HA ports from showing up in regular CLI outputs but not for addressing quota issues.
Either way, I would prefer using a separate project/tenant for octavia and set the respective quotas to indefinite. In fact, this is how it should ideally be done in a production environment.
I think for development purposes, quotas in Devstack under admin would suffice.
Should the need arise in Devstack, we can update octavia devstack scripts to create a separate project for octavia and set the quotas under this project.