20:00:23 <ying_zuo> #startmeeting horizon
20:00:23 <openstack> Meeting started Wed Nov  1 20:00:23 2017 UTC and is due to finish in 60 minutes.  The chair is ying_zuo. Information about MeetBot at http://wiki.debian.org/MeetBot.
20:00:25 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
20:00:27 <openstack> The meeting name has been set to 'horizon'
20:00:31 <ying_zuo> Hi everyone
20:01:12 <makowals> Hello
20:01:45 <e0ne> hi
20:01:50 <rubasov> hello
20:02:18 <ying_zuo> #topic Notices
20:02:27 <ying_zuo> #info Moving the Heat dashboard as a separate project
20:02:30 <robcresswell> o/
20:02:35 <ying_zuo> #link http://lists.openstack.org/pipermail/openstack-dev/2017-October/124022.html
20:02:55 <ying_zuo> Thanks amotoki for working with the Heat-dashboard team on this transition
20:03:11 <ying_zuo> Heat-dashboard is targeted to be available in Queens-2
20:03:37 <ying_zuo> once it's stable, we will remove the Heat dashboard from Horizon
20:04:05 <ying_zuo> #info Sydney Summit next week
20:04:14 <ying_zuo> we won’t have the IRC meeting next week
20:04:19 <e0ne> it could be great to send notification not openstack-operators@ too
20:04:21 <ying_zuo> #link https://www.openstack.org/summit/sydney-2017/summit-schedule/global-search?t=horizon
20:04:45 <e0ne> my comment above was about heat dashboard
20:05:42 <ying_zuo> +1
20:06:16 <e0ne> it's important for operators and vendors
20:06:18 <ying_zuo> for the summit, we will have a user feedback session as usual
20:06:27 <ying_zuo> #link https://etherpad.openstack.org/p/horizon-queens-feedback
20:06:50 <ying_zuo> if you have any questions for the horizon users/operators, please feel free to add them to this etherpad
20:07:01 <ying_zuo> this session is on Monday afternoon
20:07:17 <ying_zuo> the project onboarding and project update sessions are on Tuesday afternoon
20:07:39 <ying_zuo> #topic Fetch resources in parallel discussion (e0ne)
20:07:57 <ying_zuo> #link http://lists.openstack.org/pipermail/openstack-dev/2017-October/124129.html
20:07:58 <e0ne> ying_zuo: thanks
20:08:08 <ying_zuo> #link https://blueprints.launchpad.net/horizon/+spec/fetch-resources-in-parallel
20:08:16 <e0ne> so, I discussed this issue with robcresswell few months ago
20:08:32 <e0ne> but for now, I've got some performance testing results
20:08:49 <e0ne> #link https://docs.google.com/spreadsheets/d/14zDpdkPUfGDR_ZycaGUoT64kHsGi1gL9JOha8n5PVeg/edit?usp=sharing
20:09:26 <e0ne> the idea is to switch to futurist.GreenThreadPoolExecutor instead of futuris.ThreadPoolExecutor
20:09:37 <e0ne> it' has better performance
20:10:03 <e0ne> and doesn't depend on web server configuration
20:10:09 <e0ne> but it depends on eventlet
20:11:24 <e0ne> robcresswell: I forgot to call eventlet.monkey_patch, so in my previous attempt (if you remember our conversation) I didn't get any performance benefits from using green threads
20:11:46 <robcresswell> I'd need to do some reading. I don't know a great deal about threading in Python. Are there any drawbacks to the switch?
20:12:43 <e0ne> robcresswell: eventlet
20:12:55 <e0ne> it's not a best lib, TBH
20:13:34 <e0ne> but we don't have a lot of options here because we've got WSGI app
20:13:40 <robcresswell> :/
20:14:21 <robcresswell> Okay, I'll look at the email and see
20:14:35 <e0ne> #link https://github.com/openstack-dev/devstack/blob/dec121114c3ea6f9e515a452700e5015d1e34704/files/apache-horizon.template#L3
20:14:48 <robcresswell> I've got 23 hrs of flights coming up so should have time I guess :)
20:15:01 <e0ne> for now, we have to allow 'threads' in WSGI to get futurist working
20:15:22 <e0ne> robcresswell: 23 hours w/o internet connection, I guess
20:16:42 <e0ne> so, it would be good if core team can take a look on this issue
20:16:47 <ying_zuo> I think we can move to the next topic
20:16:56 <ying_zuo> #topic Cinder volume type quotas in Horizon (makowals)
20:16:57 <e0ne> ying_zuo: +1
20:17:03 <robcresswell> Will do, e0ne
20:17:08 <e0ne> robcresswell: thanks
20:17:15 <ying_zuo> #link https://blueprints.launchpad.net/horizon/+spec/quotas-per-cinder-volume-type
20:17:19 <makowals> Hi, so this one is mine
20:17:43 <makowals> It's in fact implementing pie charts for what is already available in Cinder
20:18:14 <makowals> There was an RFE bug requesting this, but then I realized we already have this as a local patch since a long time
20:18:45 <makowals> #link https://review.openstack.org/#/c/511472/
20:19:09 <makowals> This is implementing this; at the moment some tests are failing, but the functionality seems to be working
20:19:18 <makowals> So would be good to get any feedback on this
20:19:36 <makowals> And also get the formal approval on the blueprint itself
20:20:41 <e0ne> makowals: I can test your patch
20:21:00 <e0ne> makowals: but I'm not sure that you'll get a lot of feedback until CI will be happy with it
20:21:41 <makowals> Yeah, I know, it was more "let's not spend too much time fixing tests if the blueprint may not get approved at all"
20:22:32 <ying_zuo> this is just for the create volume flow
20:22:44 <ying_zuo> how about the create instance flow?
20:23:16 <ying_zuo> can user select a specific type of volume to launch the instance with?
20:24:06 <makowals> It covers new volume and new volume from image. In the create instance flow there is so far not even a box to select the type
20:25:02 <ying_zuo> yes, probably not with this blueprint
20:25:09 <makowals> But I feel like this one deserves a separate patch, not to have all-in-one
20:25:11 <ying_zuo> just curious if it's possible
20:25:21 <makowals> At the moment it goes with "standard"
20:25:43 <ying_zuo> yes
20:26:08 <makowals> What by the way also causes problem in some corner cases, when user have a "non-standard quota" but no more "standard" -- they can't create new instance with the volume in one step
20:26:39 <makowals> But I don't think anyone ever complained on this
20:27:14 <ying_zuo> I thought there's a configuration for the default volume to use
20:28:16 <ying_zuo> anyway, it's not really related to your blueprint
20:28:25 <ying_zuo> I will take a look at it
20:29:01 <makowals> Cool, thanks
20:29:01 <ying_zuo> #topic Bug Reports Review
20:29:14 <ying_zuo> #link https://etherpad.openstack.org/p/horizon-bug-review
20:29:34 <ying_zuo> #link https://bugs.launchpad.net/horizon/+bug/1411239
20:29:36 <openstack> Launchpad bug 1411239 in OpenStack Dashboard (Horizon) "Policy checks for get_image, get_images not enforced when launching instances" [Medium,New]
20:31:49 <ying_zuo> looks like the get_images policy rule is only used for the images panel
20:32:21 <ying_zuo> oh wait, comment #1 says no
20:32:36 <ying_zuo> I think this one needs to be confirmed first
20:32:47 <ying_zuo> it was created a while back
20:33:12 <ying_zuo> #link https://bugs.launchpad.net/horizon/+bug/1728761
20:33:14 <openstack> Launchpad bug 1728761 in OpenStack Dashboard (Horizon) "[Pike support] Use volumev3 and cinderv3 in dashboard" [Undecided,New] - Assigned to Ivan Kolodyazhny (e0ne)
20:33:27 <e0ne> just assigned this issue to me
20:33:40 <ying_zuo> thanks e0ne
20:33:42 <e0ne> I've got similar issue in our internal bug tracker
20:33:49 <e0ne> so it's time to fix it :)
20:33:53 <robcresswell> I thought we already used v3?
20:34:36 <e0ne> robcresswell: not everywhere
20:34:47 <ying_zuo> the default on local_settings is v2
20:35:22 <ying_zuo> that's configurable
20:35:37 <e0ne> I'll check it tomorow if horizon can work only with cinder v3
20:36:01 <ying_zuo> thanks
20:36:13 <ying_zuo> #link https://bugs.launchpad.net/horizon/+bug/1627619
20:36:14 <openstack> Launchpad bug 1627619 in OpenStack Dashboard (Horizon) "Launch instance only lists snapshots of images not created with a new volume" [Medium,Confirmed]
20:38:06 <robcresswell> Looks like it was recently confirmed
20:38:10 <robcresswell> Not much else to do
20:39:21 <ying_zuo> oh yeah, just need to look into it
20:39:48 <ying_zuo> #topic Open Discussion
20:40:27 <ying_zuo> any code review requests or questions?
20:41:12 <e0ne> will we skip meeting next week?
20:41:17 <ying_zuo> yes
20:41:30 <e0ne> ok
20:41:44 <ying_zuo> alright. we will end early today.
20:41:48 <rubasov> I wanted to say thanks to everybody giving feedback on bp/neutron-trunk-ui
20:42:07 <rubasov> this way we are making nice progress
20:42:35 <rubasov> keep the comments coming
20:42:53 <ying_zuo> great! thanks for working on it
20:43:24 <ying_zuo> thanks everyone for joining
20:43:35 <ying_zuo> enjoy the rest of your day!
20:43:39 <ying_zuo> #endmeeting