yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #82569
[Bug 1877560] [NEW] Optimize "QosPolicy" OVO bound objects retrieve methods
Public bug reported:
The following methods are inefficient:
- get_bound_networks
- get_bound_ports
- get_bound_floatingips
- get_bound_routers
Those methods, using the "QosPolicy_XXXX_Binding" OVO interface, are
retrieving all objects with a certain policy ID and then returning only
the ID of the _XXXX_ object. That means we retrieve a full register list
from the DB, then those registers are converted to OVO and then we
extract only the _XXXX_ ID.
This is obviously inefficient, regardless of the simplicity of the
"QosPolicy_XXXX_Binding" OVO and the 1:1 parity to the DB associated
register. We should instead only retrieve the _XXXX_ object ID from the
DB and return it.
** Affects: neutron
Importance: Undecided
Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1877560
Title:
Optimize "QosPolicy" OVO bound objects retrieve methods
Status in neutron:
New
Bug description:
The following methods are inefficient:
- get_bound_networks
- get_bound_ports
- get_bound_floatingips
- get_bound_routers
Those methods, using the "QosPolicy_XXXX_Binding" OVO interface, are
retrieving all objects with a certain policy ID and then returning
only the ID of the _XXXX_ object. That means we retrieve a full
register list from the DB, then those registers are converted to OVO
and then we extract only the _XXXX_ ID.
This is obviously inefficient, regardless of the simplicity of the
"QosPolicy_XXXX_Binding" OVO and the 1:1 parity to the DB associated
register. We should instead only retrieve the _XXXX_ object ID from
the DB and return it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1877560/+subscriptions
Follow ups