yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #31320
[Bug 1442310] [NEW] Nova API in Horizon sometimes act as a bottleneck
Public bug reported:
The scale testing of Horizon faced a several problems with a lot of data
being received from Nova side when Horizon actually doesn't need so much
data.
First case is getting the volumes list from cinder, see
https://github.com/openstack/horizon/blob/2015.1.0b3/openstack_dashboard/dashboards/project/volumes/tabs.py#L90
- here all the instances are being requested from Nova side just to show
the names of Instances that Cinder volumes are attached to. In cases
when the total number of Instances is far more bigger than the number of
Volumes this causes a serious performance issues in Horizon where it
shouldn't.
Second case is getting Floating IPs list from Neutron,
https://github.com/openstack/horizon/blob/2015.1.0b3/openstack_dashboard/dashboards/project/access_and_security/tabs.py#L109
- here we again request all the instances from Nova just to show their
names for some Floating IPs (which number could be truly inferior to the
number of Instances).
Both cases could be avoided if we were able to request details for a
limited set of servers (specified by their IDs) from Nova.
** Affects: horizon
Importance: Medium
Assignee: Timur Sufiev (tsufiev-x)
Status: New
** Affects: nova
Importance: Undecided
Status: New
** Also affects: nova
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1442310
Title:
Nova API in Horizon sometimes act as a bottleneck
Status in OpenStack Dashboard (Horizon):
New
Status in OpenStack Compute (Nova):
New
Bug description:
The scale testing of Horizon faced a several problems with a lot of
data being received from Nova side when Horizon actually doesn't need
so much data.
First case is getting the volumes list from cinder, see
https://github.com/openstack/horizon/blob/2015.1.0b3/openstack_dashboard/dashboards/project/volumes/tabs.py#L90
- here all the instances are being requested from Nova side just to
show the names of Instances that Cinder volumes are attached to. In
cases when the total number of Instances is far more bigger than the
number of Volumes this causes a serious performance issues in Horizon
where it shouldn't.
Second case is getting Floating IPs list from Neutron,
https://github.com/openstack/horizon/blob/2015.1.0b3/openstack_dashboard/dashboards/project/access_and_security/tabs.py#L109
- here we again request all the instances from Nova just to show their
names for some Floating IPs (which number could be truly inferior to
the number of Instances).
Both cases could be avoided if we were able to request details for a
limited set of servers (specified by their IDs) from Nova.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1442310/+subscriptions
Follow ups
References