nova floatingip quota conflicts with neutron floating ip quota
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
In Progress
|
Medium
|
Yaguang Tang | ||
Bug Description
nova quota-show conflicts neutron quota-show
neutron quota-show
# neutron quota-show
-------
| Field | Value |
-------
| Floatingip | 50 | ←
| Network | 10 |
| Port | 50 |
| Router | 10 |
| Security_group | 10 |
| Security_group_rule | 100 |
| Subnet | 10 |
-------
# Nova quota-show
-------
| Property | Value |
-------
| Metadata_items | 128 |
| Injected_
| Ram | 51200 |
| Floating_ips | 10 | ←
| Key_pairs | 100 |
| Instances | 10 |
| Security_
| Injected_files | 5 |
| Cores | 20 |
| Fixed_ips | -1 |
| Injected_
| Security_groups | 10 |
security_groups, floating_ips security_group_rule should get from neutron when using Nuetron as network service.
| Changed in nova: | |
| assignee: | nobody → Yaguang Tang (heut2008) |
| Changed in nova: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: network |
| Joe Gordon (jogo) wrote | #1 |
| summary: |
- retrieve network related quota usage info from neutron instead of nova - db + nova floatingip quota conflicts with neutron floating ip quota |
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #3 |
| Changed in nova: | |
| status: | Triaged → In Progress |
When we are using neutron perhaps we should just disable the security_groups, floating_ips security_group_rule quota options. This goes in line with 'we don't want to be the proxy for all other services.' And to make for a clean user experience we should hide the complexity of having many different services behind a unified openstack client