nicira plugin: metadata access network management makes unnecessary calls to backend
Bug #1176963 reported by
Salvatore Orlando
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Salvatore Orlando | ||
Grizzly |
Fix Released
|
Medium
|
Gary Kotton |
Bug Description
The following operation:
is aimed at understanding wheter ports are already configured on the router.
It is executed with an elevated context in order to take into account 'provider router' use case.
However, since it is a plugin call, it goes all the way down to the backend NVP API.
The device_id filter is not applied to the backend API call, and therefore this can cause a very large query on the NVP platform.
This particular issue can be easily fixed by avoiding backend access at all, as it's not necessary.
Changed in quantum: | |
status: | New → In Progress |
tags: | added: grizzly-backport-potential |
tags: | removed: grizzly-backport-potential |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
tags: | removed: in-stable-grizzly |
Changed in neutron: | |
milestone: | havana-1 → 2013.2 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/28317 github. com/openstack/ quantum/ commit/ 0fee496538a36e7 db5b7e2c7e5bbd5 cff2aedd53
Committed: http://
Submitter: Jenkins
Branch: master
commit 0fee496538a36e7 db5b7e2c7e5bbd5 cff2aedd53
Author: Salvatore Orlando <email address hidden>
Date: Mon May 6 17:33:44 2013 +0200
Fetch routers ports for metadata access from DB
Bug 1176963
There is no need to retrieve the ports from the NVP backend, so
a DB query will be enough.
Change-Id: If3529cc5694434 e8cdc9d21a4043f 94212146d2d