yahoo-eng-team team mailing list archive

[Feilong Wang <flwang@xxxxxxxxxxxxxxx>]

Public bug reported:

This is a most like a RFE instead of a functional bug to improve the
performance of instances panel. There are several reasons I think we can
either remove the column or at least make it configurable.

#1 AWS is not doing this :)

#2 It's useless for more of the case, because I pretty much sure most of
the openstack deployment (65%+) is using ceph, and most of them will use
volume-based instance instead of image-based so that said, with volume-
based instances you can't see any image info on the list

#3 The API call to glance is very heavy and no cache
(10:31:29) flwang1: https://api.mycloud.com:9292/v2/images?limit=1000&sort_key=created_at&sort_dir=desc
Cloud provider may have hundreds public images and each time Horizon will try to list all of those public images and the private images of current tenant, even though all the instances are volume-based

And I got some feedback from Rob and David:

(02:04:26) robcresswell: flwang1: I disagree with removing the image column, personally.
(02:04:45) robcresswell: Just axing all the functionality of the panel is not a good way to make it fast :p
(04:00:46) david-lyle: robcresswell, you still have the image_id if you want to leave the column
(04:01:04) david-lyle: what do you use the image name in that table for?
(04:06:23) robcresswell: david-lyle: I would imagine there's some value in knowing what image its using, no?
(04:06:36) david-lyle: again, there is the ID
(04:06:52) david-lyle: but it's a very expensive call to map that ID to a name
(04:06:52) robcresswell: Hey if you can remember images by UUID, by all means, remove it...
(04:07:09) robcresswell: Yeah, true
(04:07:27) david-lyle: same for the project name, but I think that's far more useful
(04:07:45) david-lyle: maybe make image name column configurable
(04:07:55) david-lyle: the ability to turn it off
(04:08:27) david-lyle: so if you care you can leave it turned on, but if you want to optimize, enable a setting to skip it
(04:08:52) robcresswell: I prefer that
(04:09:03) david-lyle: leave the column actually (because that would get messy) but change the value between ID and name
(04:09:09) robcresswell: yes
(04:09:10) david-lyle: based on the setting
(04:09:14) robcresswell: ID is free anyway
(04:09:25) david-lyle: flwang1, ^^^ proposed compromise
(04:09:30) david-lyle: when you're on

** Affects: horizon
     Importance: Undecided
     Assignee: Feilong Wang (flwang)
         Status: New

** Changed in: horizon
     Assignee: (unassigned) => Feilong Wang (flwang)

-- 
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/1721686

Title:
  [Performance] Make image name column configurable

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  This is a most like a RFE instead of a functional bug to improve the
  performance of instances panel. There are several reasons I think we
  can either remove the column or at least make it configurable.

  #1 AWS is not doing this :)

  #2 It's useless for more of the case, because I pretty much sure most
  of the openstack deployment (65%+) is using ceph, and most of them
  will use volume-based instance instead of image-based so that said,
  with volume-based instances you can't see any image info on the list

  #3 The API call to glance is very heavy and no cache
  (10:31:29) flwang1: https://api.mycloud.com:9292/v2/images?limit=1000&sort_key=created_at&sort_dir=desc
  Cloud provider may have hundreds public images and each time Horizon will try to list all of those public images and the private images of current tenant, even though all the instances are volume-based

  And I got some feedback from Rob and David:

  (02:04:26) robcresswell: flwang1: I disagree with removing the image column, personally.
  (02:04:45) robcresswell: Just axing all the functionality of the panel is not a good way to make it fast :p
  (04:00:46) david-lyle: robcresswell, you still have the image_id if you want to leave the column
  (04:01:04) david-lyle: what do you use the image name in that table for?
  (04:06:23) robcresswell: david-lyle: I would imagine there's some value in knowing what image its using, no?
  (04:06:36) david-lyle: again, there is the ID
  (04:06:52) david-lyle: but it's a very expensive call to map that ID to a name
  (04:06:52) robcresswell: Hey if you can remember images by UUID, by all means, remove it...
  (04:07:09) robcresswell: Yeah, true
  (04:07:27) david-lyle: same for the project name, but I think that's far more useful
  (04:07:45) david-lyle: maybe make image name column configurable
  (04:07:55) david-lyle: the ability to turn it off
  (04:08:27) david-lyle: so if you care you can leave it turned on, but if you want to optimize, enable a setting to skip it
  (04:08:52) robcresswell: I prefer that
  (04:09:03) david-lyle: leave the column actually (because that would get messy) but change the value between ID and name
  (04:09:09) robcresswell: yes
  (04:09:10) david-lyle: based on the setting
  (04:09:14) robcresswell: ID is free anyway
  (04:09:25) david-lyle: flwang1, ^^^ proposed compromise
  (04:09:30) david-lyle: when you're on

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1721686/+subscriptions