get_network call always queries all ports
Bug #923510 reported by
dan wendlandt
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Fix Released
|
Medium
|
dan wendlandt | ||
| quantum (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
The call to get a single network always queries all ports on that network, regardless of whether the "details" where requested.
Note: the data returned by this call is correct in terms of the API, as the extra port data is stripped out before returning to the user, but at scale this adds a lot of load. This is particularly painful because of the inefficiencies of querying all ports mentioned in https:/
| Changed in quantum: | |
| importance: | Undecided → Medium |
| milestone: | none → essex-4 |
| assignee: | nobody → dan wendlandt (danwent) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to quantum (master) | #1 |
| Changed in quantum: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to quantum (master) | #2 |
| Changed in quantum: | |
| status: | In Progress → Fix Committed |
| Changed in quantum: | |
| status: | Fix Committed → Fix Released |
| Changed in quantum: | |
| milestone: | essex-4 → 2012.1 |
| Changed in quantum (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/