15:01:05 <e0ne> #startmeeting horizon
15:01:06 <openstack> Meeting started Wed May 22 15:01:05 2019 UTC and is due to finish in 60 minutes.  The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:07 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:09 <openstack> The meeting name has been set to 'horizon'
15:01:35 <e0ne> hi
15:01:45 <e0ne> is anybody around for horizon meeting today?
15:02:18 <Hanxiang> hi
15:02:28 <duochao> hi
15:02:54 <duochao> I'm from 99cloud Inc，my name is Duochao Wu
15:03:22 <e0ne> let's wait few minutes more if people join us
15:03:28 <Hanxiang> the first part of the auto refresh patch came
15:03:42 <vishalmanchanda> hi all
15:03:58 <e0ne> #topic Notices
15:04:15 <e0ne> #link https://releases.openstack.org/train/schedule.html
15:04:29 <e0ne> we're two weeks before Train-1 milestone
15:04:50 <e0ne> nothing special for horizon at this point
15:05:34 <e0ne> but I'm going to finally finish mox removing patch until that date and release horizon for train to check if it affects any plugin
15:05:53 <e0ne> that's all updates from me
15:05:56 <vishalmanchanda> e0ne: great
15:07:15 <amotoki> I would like to clarify the milestones on ini-based-configuration along with train stations (i.e. milestones) but it can be discussed later.
15:07:19 <e0ne> #topic Open Discussion
15:07:42 <e0ne> amotoki: I just opened your patches before the meeting
15:08:26 <e0ne> #link https://review.opendev.org/#/q/status:open+project:openstack/horizon+branch:master+topic:bp/ini-based-configuration
15:08:51 <amotoki> I think we can start with the planning document https://review.opendev.org/#/c/656181/
15:09:03 <e0ne> amotoki: I'll read once more time https://review.opendev.org/#/c/656181/ right after the meeting and +2 on it
15:09:07 <vishalmanchanda> amotoki: e0ne : any opinion on this bug https://bugs.launchpad.net/horizon/+bug/1829461
15:09:08 <openstack> Launchpad bug 1829461 in OpenStack Dashboard (Horizon) "Volume Group Under project panel not working " [Undecided,Confirmed]
15:09:25 <amotoki> let's discuss topics one by one
15:09:30 <e0ne> amotoki: +1
15:10:13 <amotoki> my current proposed patches are all related to step 1 in the planning document.
15:10:45 <amotoki> I will resolve merge conflicts once parent patches land.
15:11:10 <amotoki> I think it would be nice if one or two patches are ready for review.
15:11:14 <e0ne> amotoki: I'm ok with the proposal. just want to confirm that I didn't miss anything before I +2 on it
15:11:40 <amotoki> hopefully vishalmanchanda or other cores can sponsor this effort.
15:11:54 <amotoki> at now, e0ne is the only sponsor for it.
15:12:05 <vishalmanchanda> amotoki: sure.
15:12:42 <amotoki> I guess this effort will have more than 20 patches :) and :p
15:12:43 <e0ne> ini-based (oslo-based config) is one of the most asked thing by operators
15:13:50 <e0ne> amotoki: we'd got a great experience in the past with django2 support patches :)
15:13:53 <rdopiera> they might be expecting more from it than is feasible
15:15:58 <e0ne> rdopiera: who knows...
15:18:44 <amotoki> rdopiera: do you have more concrete examples? I haven't got your point fully.
15:19:20 <amotoki> I know they expect a lot by this word :)
15:19:35 <rdopiera> I was just thinking that people might expect this to solve all their problems related to configuration
15:19:59 <amotoki> hehe :p
15:20:27 <e0ne> the only way to solve configuration issues is to remove config:)
15:20:30 <rdopiera> amotoki: looking at your patches, I wonder if we want a helper function for definiting the settings and their defaults instead
15:20:54 <rdopiera> amotoki: something like "setting("NAME", "Description", default)"
15:21:05 <rdopiera> this way we can easily swap it later
15:21:36 <rdopiera> under the hood it can just set the variables like the current approach does, for now
15:22:29 <amotoki> rdopiera: yeah, good point. I thought this can be done as part of oslo.config migration but I am not sure it is better to be a separate step.
15:23:24 <amotoki> we need to merge "description" of settings and our document on settings at some time.
15:24:35 <rdopiera> a separate step is fine for me
15:24:47 <rdopiera> having the defaults in one place is already a big help
15:24:57 <rdopiera> and we can do the rest automaticlaly, I think
15:25:01 <e0ne> rdopiera: +1
15:25:04 <amotoki> rdopiera: +1
15:25:14 <e0ne> amotoki: I left few comments in your patch
15:25:44 <amotoki> e0ne: thanks.
15:26:35 <e0ne> nothing critical, so I put +1
15:26:39 <amotoki> I agree my plan has several (or many) discussion points and I hope my document helps clarify our understandng.
15:27:16 <rdopiera> I think that many of those details don't matter, as long as we are consistent
15:28:28 <rdopiera> but having it all captured in a document surely helps, and also makes it easier to cooperate
15:29:04 <rdopiera> amotoki: if you have a step that could be done in parallel, I'm happy to help
15:29:49 <amotoki> rdopiera: thanks. I would like to focus on the first step to define defaults in one place first. As of now, any reviews and comments would be appreciated.
15:31:02 <amotoki> Advices and ideas on how to handle settings on django and its ecosystem are welcome too :)
15:31:13 <amotoki> (it can be tackled as second step)
15:34:06 <e0ne> amotoki: thanks for this effort
15:34:36 <e0ne> vishalmanchanda: what do you want  to discuss about https://bugs.launchpad.net/horizon/+bug/1829461?
15:34:37 <openstack> Launchpad bug 1829461 in OpenStack Dashboard (Horizon) "Volume Group Under project panel not working " [Undecided,Confirmed]
15:36:30 <vishalmanchanda> e0ne: just wanted to confirm this bug, which i think you already confirmed.
15:36:58 <e0ne> I reproduced it but didn't look into the details what went wrong
15:37:20 <vishalmanchanda> e0ne: same here.
15:38:05 <amotoki> regarding bugs, I think we need to discuss how we can address important bugs **as a team**.
15:38:24 <amotoki> (it is also important to discuss specific bugs though)
15:39:14 <amotoki> we have 103 medium or higher bugs
15:39:46 <amotoki> and most of them have not been visit for long.
15:39:47 <e0ne> I think we can use this https://etherpad.openstack.org/p/horizon-release-priorities etherpad to track important bugs
15:40:31 <amotoki> e0ne: does it mean we have two places to track bugs?
15:40:37 <e0ne> no
15:41:11 <e0ne> launchpad should be the main source of truth for bugs
15:42:08 <e0ne> but if we need to have some place to have a list of most critical bugs to discuss on meeting - we can use etherpad or separate tag on launchpad
15:43:40 <amotoki> perhaps High priority bugs are such ones if the priority works.
15:43:52 <e0ne> makes sense for me
15:44:40 <e0ne> we've got 4 open high bugs and 3 more in progress
15:45:26 <e0ne> actually, 2 in progress and 1 has fix commited status
15:45:52 <amotoki> but 3 "in progress" bugs have no progress for a long time :(
15:46:39 <e0ne> :(
15:46:44 <amotoki> The status of 2 in progress bugs should be revisit as the proposed fixes have been abandoned.
15:47:36 <e0ne> I moved the to the confirmed status again
15:47:54 <vishalmanchanda> i will try to proposed a fix for this bug https://bugs.launchpad.net/horizon/+bug/1746184 asap.
15:47:55 <openstack> Launchpad bug 1746184 in OpenStack Dashboard (Horizon) "Table of networks or routers does't support pagination" [High,Confirmed]
15:47:58 <e0ne> we need to take care on bugfixing too
15:48:17 <amotoki> I tried to visit them but failed by myself alone...
15:48:40 <amotoki> I mean medium or higher bugs by "them".
15:48:49 <e0ne> we need to work together on this
15:49:28 <e0ne> we've got 10 minutes more
15:49:48 <e0ne> we can continue this discussion after the meeting on our channel or on the next meeting
15:50:17 <amotoki> Hanxiang and duochao: thanks for joining us. do you have anything to discuss?
15:50:36 <Hanxiang_> the first part of the auto refresh patch came
15:50:46 <Hanxiang_> Are you interested?
15:51:00 <Hanxiang_> https://review.opendev.org/#/c/660612/
15:51:14 <e0ne> #link https://review.opendev.org/#/c/660612/
15:51:40 <Hanxiang_> Implemented the common part of auto refresh, and added auto-refresh to the details page
15:51:52 <duochao> I committed a partial functional implementation.
15:52:15 <amotoki> this says "part 1". Could you share the whole picture/plan on this?
15:53:33 <Hanxiang_> amotoki: see this, https://blueprints.launchpad.net/horizon/+spec/auto-refresh  :)
15:54:48 <amotoki> Hanxiang_: thanks. If so, the blueprint needs to be linked from your patch(es) as recommended in the OpenStack contributor guide. this makes our reviewer life easier.
15:56:13 <Hanxiang_> amotoki：ok，thanks for your suggestion
15:57:11 <amotoki> https://docs.openstack.org/infra/manual/developers.html#development-workflow would help you
15:57:22 <amotoki> especially ""Starting a Change" section
15:58:30 <e0ne> we're almost out of time
15:58:50 <e0ne> thanks everybody for your contributions! see you next week
15:59:13 <Hanxiang_> e0ne: although it is still in debug, you can review it first and make good suggestions.
15:59:48 <duochao> Modify  patch and resubmit will come late.
16:00:24 <e0ne> let's move to #openstack-horizon if we've got anything more to discuss today
16:00:26 <e0ne> #endmeeting