15:00:10 <e0ne> #startmeeting horizon
15:00:11 <openstack> Meeting started Wed Apr 25 15:00:10 2018 UTC and is due to finish in 60 minutes.  The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:12 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:14 <openstack> The meeting name has been set to 'horizon'
15:00:17 <vladiskuz_> o/
15:00:23 <e0ne> hi
15:00:41 <e0ne> let's wait for minute or two while people joining us
15:02:39 <amotoki> o/
15:02:46 <amotoki> I just updated the agent wiki page.
15:02:56 <amotoki> reload might help you
15:03:06 <e0ne> amotoki: hi, thanks!
15:03:12 <e0ne> #link https://wiki.openstack.org/wiki/Meetings/Horizon
15:03:37 <e0ne> #topic Notices
15:04:26 <e0ne> I just want to notify that we passed rocky-1 milestone last week
15:04:39 <e0ne> hm...
15:04:50 <openstack> e0ne: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.
15:05:05 <e0ne> what is going with meeting bot?
15:05:13 <amotoki> e0ne: is something going wrong?
15:05:29 <amotoki> you've started the meeting
15:05:36 <e0ne> i didn't see meeting channel topic now
15:05:57 <e0ne> let's go forward. I hope, everything will be logges :)
15:06:02 <amotoki> but the meeting bot responded the meeting started,
15:06:24 <e0ne> thanks everybody for contribution in the rocky-1 timeframe
15:06:31 <e0ne> #topic use_mox is now disabled by default. it affect horizon plugins
15:06:49 <amotoki> the logging is available http://eavesdrop.openstack.org/meetings/horizon/2018/horizon.2018-04-25-15.00.log.txt
15:06:57 <betherly_> o/
15:06:59 <e0ne> amotoki: thanks for the confirmation
15:07:03 <amotoki> there is no thing we worry about.
15:07:43 <e0ne> message "[18:04:24] barjavel.freenode.net changed the topic to OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/" confused me a bit
15:08:01 <rdopiera> o/
15:08:08 <amotoki> re: mox, it breaks some plugin testings, but AFAIK most plugins are catching up the change
15:08:09 <e0ne> amotoki: do you want to give some input on use_mox=False?
15:08:54 <e0ne> #link https://docs.openstack.org/horizon/latest/install/plugin-registry.html
15:09:09 <amotoki> their CI failed temporarily, but most of them don't think it is a problem. they tend to fail to follow up the change.
15:09:30 <e0ne> amotoki: I can work with plugins teams on this issue
15:09:54 <amotoki> I try to keep my radar on plugins and help them.
15:10:05 <amotoki> e0ne: you are helpful too :)
15:10:20 <e0ne> amotoki: feel free to ping me if any help is needed
15:10:32 <amotoki> perhaps not from me :)
15:10:50 <e0ne> amotoki: get working plugins and CIs are in the top of my priority list
15:11:27 <e0ne> I'm ready to help plugin maintainers to fix their CI or make a patches with fixes
15:12:34 <amotoki> sometimes this link helps you all https://review.openstack.org/#/q/(project:%255E.*-ui+OR+project:%255E.*-dashboard)+AND+status:open
15:13:00 <amotoki> to check what happens around horizon plugins
15:13:04 <e0ne> amotoki: thanks a lot! I will add this dashboard to my gerrit settings
15:13:32 <amotoki> (this is just based on gerrit query)
15:14:07 <amotoki> this is #notice topic, so I would like to share more link
15:14:14 <amotoki> xstatic reviews: https://review.openstack.org/#/q/project:%255Eopenstack/xstatic-.*+status:open
15:14:32 <e0ne> #link  https://review.openstack.org/#/q/project:%255Eopenstack/xstatic-.*+status:open
15:14:37 <amotoki> most horizon cores tend to forget reviews them
15:14:52 <amotoki> s/reviews/review/
15:14:54 <e0ne> it's already on my list too
15:15:35 <vladiskuz> Good to know about that
15:15:43 <e0ne> #link https://review.openstack.org/#/q/status:open+AND+project:openstack/horizon+AND+NOT+branch:master - backports to stable branched
15:15:50 <e0ne> s/branched/branches
15:16:19 <e0ne> :)
15:16:24 <amotoki> :)
15:16:53 <vladiskuz> From my perspective we need more cores for stable/* branches
15:17:00 <e0ne> vladiskuz: ++
15:17:15 <rdopiera> maybe we can kindnap some
15:17:28 <amotoki> rdopiera: which releases are affected by a bug of keystone get_identity_provider typo ?
15:17:39 <rdopiera> amotoki: seems like it's 10-13
15:17:52 <amotoki> rdopiera: version of RHOSP?
15:17:56 <rdopiera> amotoki: though "affected" is a but much to say, as it's a bit cosmetic
15:18:07 <rdopiera> amotoki: Newton-Queens
15:18:16 <e0ne> FYI: I would like to get current backports merged and make a release for pike and queens
15:18:19 <rdopiera> amotoki: since it doesn't actually have any effect
15:18:55 <rdopiera> so I'm not sure if we even want to backport it to queens
15:18:55 <amotoki> rdopiera: in some releases we failed to sync policy files
15:19:05 <vladiskuz> e0ne: +1
15:19:42 <rdopiera> amotoki: we are not using that policy name anywhere, it's just there because we copied the whole file
15:19:48 <amotoki> perhaps we failed to sync policies in Pike. when I synced the policies in Queens, I updated some policy names
15:19:49 <e0ne> amotoki, rdopiera: we can try to make backports and check if there are any merge conflicts
15:20:15 <amotoki> so I think we need to check policy names carefully
15:20:20 <amotoki> during backports
15:20:26 <e0ne> +1
15:20:39 <e0ne> it would be good to have some CI checks for it
15:21:12 <rdopiera> amotoki: it was wrong back then, though, as it was only fixed more recently and backported all the way
15:21:33 <e0ne> amotoki: me too. that's why I didn't propose it yet
15:22:04 <rdopiera> a diff?
15:23:02 <amotoki> rdopiera: yeah. on the other hand, one question is whether we need to take care releases where we failed to sync policies.
15:23:29 <rdopiera> since this is cosmetic, I would leave it alone
15:24:18 <amotoki> rdopiera: okay. will you take care of stable backports on them?
15:24:40 <rdopiera> yes
15:24:40 <amotoki> perhaps s/on them/on that bug/
15:24:45 <amotoki> thanks
15:25:03 <amotoki> we can discuss it more in backport reviews (if needed)
15:25:14 <e0ne> amotoki: +1
15:25:50 <e0ne> do we want to go throw our agenda?
15:25:51 <e0ne> :)
15:26:02 <rdopiera> we have an agenda?
15:26:18 <amotoki> the agenda is https://wiki.openstack.org/wiki/Meetings/Horizon#Agenda_for_Next_Meeting
15:26:24 <rdopiera> by all means let's!
15:26:46 <e0ne> #topic Needs volunteers on mox->mock conversion
15:26:57 <e0ne> #link https://etherpad.openstack.org/p/horizon-unittest-mock-migration
15:27:29 <e0ne> amotoki: did awesome job on it! I very appreciate
15:27:33 <amotoki> I sent patches on mock migration for dashboards.identity.*
15:27:51 <amotoki> but I have no plan for the remaining modules.
15:28:25 <amotoki> the progress is tracked in https://etherpad.openstack.org/p/horizon-unittest-mock-migration
15:29:03 <amotoki> we need volunteers on openstack_auth/tests/unit/test_auth and openstack_dashboard/dashboards/admin/*
15:29:08 <e0ne> I'll raise this topic on the Onboarding Session at the Summit
15:29:21 <vladiskuz> I'm working on this, but I have no enough time for that
15:30:24 <amotoki> vladiskuz: hopefully you add your name to the etherpad when you start to work on some
15:30:39 <amotoki> it helps us to avoid duplicate efforts
15:30:46 <vladiskuz> Ok, will do that
15:30:54 <e0ne> vladiskuz: thanks for the help
15:31:09 <amotoki> vladiskuz: I hope I didn't beat your work
15:33:14 <e0ne> mox => mock migration is a community goal for this release
15:33:41 <e0ne> also, it's a good chance for new contributors to start work on horizon
15:35:02 <e0ne> I thinks, that's all for this topic
15:35:47 <amotoki> I think so. we can move.
15:35:54 <e0ne> amotoki: can we move to "horizon release model" topic now? IMO, It's extremly important
15:36:17 <amotoki> one small topic before that
15:36:20 <amotoki> "How can we gather more contributors on attractive features? "
15:36:30 <amotoki> it is related to the previous topic
15:36:44 <e0ne> ok
15:36:49 <e0ne> #topic How can we gather more contributors on attractive features?
15:37:05 <amotoki> i would like to have new contributors with topic which are relatively straight-forward
15:37:22 <e0ne> I'll work on cinder-related question later in rocky-2 after the Summit
15:37:39 <e0ne> mostly on multiattach and generic groups
15:37:43 <amotoki> I filed a blueprint https://blueprints.launchpad.net/horizon/+spec/multi-attach-volume as a result of mriedem's review
15:38:02 <amotoki> (as e0ne knows the context)
15:38:23 <e0ne> of course, if amotoki won't continue work on generic groups earlier than me
15:38:51 <amotoki> e0ne: i can take care of the generic groups and i hope reviews
15:38:59 <e0ne> multiattach feature is the most wanted cidner feature for the last 3 years!
15:39:05 <amotoki> e0ne: but more volume-related work overflow me
15:39:31 <e0ne> amotoki: I'll have a time for it after the Summit for sure
15:39:40 <amotoki> e0ne: sounds nice
15:40:32 <e0ne> I'll work with mriedem to be sure that we've got full TODOs list in the blueprint
15:40:43 <amotoki> e0ne: you are familar with cinder stuffs, so your reviews would be really appreciated.
15:41:12 <amotoki> re muti-attach, i think matt can work on nova microversion stuff.
15:41:12 <e0ne> amotoki: I will work on implementation too
15:41:28 <amotoki> so we need to continue the remaining effort.
15:41:34 <e0ne> amotoki: +++
15:41:52 <amotoki> e0ne: in the same page :)
15:42:05 <e0ne> :)
15:42:32 <e0ne> #topic horizon release model: cycle-with-milestone vs cycle-with-intermediary
15:42:56 <e0ne> I'm afraid that this topic will eat all the time, so let's start sooner
15:43:35 <amotoki> on this tipic, I first would like to confirm you are aware of the recent zuulv3/infra change which happened at one month before.
15:43:57 <e0ne> yes, let me find a lint to the openstack-dev@
15:44:03 <amotoki> this would helps the level  of our understading.
15:44:49 <amotoki> I don't think we need to have a conclusion this week. I would like just to raise this topic.
15:45:26 <e0ne> #link http://lists.openstack.org/pipermail/openstack-dev/2018-April/129833.html
15:45:43 <amotoki> is looking for the link of today's discussion in #-infra
15:45:53 <e0ne> we need to be careful on any decision on this topic
15:46:45 <amotoki> +1000
15:46:58 <e0ne> as I proposed earlier, I want to have cross-project jobs on each horizon commit
15:47:14 <amotoki> this is a log on this topic http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2018-04-25.log.html#t2018-04-25T07:13:47
15:47:15 <e0ne> at least, to run plugins unit tests against proposed change
15:47:23 <e0ne> #link http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2018-04-25.log.html#t2018-04-25T07:13:47
15:48:13 <e0ne> the issue is that plugins use the latest horizon release for the tests in their CI
15:48:23 <amotoki> but to fully understand this topic you perhaps need to follow the dev ML thread e0ne posted above + http://lists.openstack.org/pipermail/openstack-dev/2018-March/thread.html#128310
15:48:57 <e0ne> amotoki: it's a link I was searching for
15:49:03 <e0ne> #link http://lists.openstack.org/pipermail/openstack-dev/2018-March/thread.html#128310
15:49:05 <amotoki> the topic also leads to different behaviors on CI and local testing.
15:49:56 <amotoki> at least Andreas (from project-config team), mordred (from the infra team) and me are in the same page.
15:50:18 <amotoki> your involvement on this topic are really appreciated.
15:50:40 <amotoki> we need to discuss it as community-wide.
15:51:30 <e0ne> amotoki: it would be good to have a list of affected plugins
15:51:44 <e0ne> so I'll work with them on fix
15:52:31 <e0ne> from Horizon's perspective, I want to have plugins jobs on horizon gates to test each changes if we break them
15:52:46 <amotoki> yes. I raised this week because I noticed shu (active magnum-ui maintainer) is inventing another variant of tox_install.sh.
15:53:34 <amotoki> I at least together wit project-config and infra team are trying to address this issue togher.
15:53:38 <e0ne> I need to read todays conversations first
15:53:42 <amotoki> *together
15:54:07 <amotoki> feel free to ping me or infra channel on this topic!
15:54:22 <e0ne> amotoki: ok, will do
15:54:38 <amotoki> I would like to move this forward by Rocky-2 at latest
15:54:56 <amotoki> horizon and neutron have similar issues on this
15:55:02 <e0ne> amotoki: +1
15:55:12 <amotoki> and horizon issue seems to be easier to me so far
15:55:19 <e0ne> amotoki, rdopiera: could you please take a look on my thread http://lists.openstack.org/pipermail/openstack-dev/2018-April/129290.html
15:56:01 <amotoki> e0ne: this is another important topic!
15:56:04 <e0ne> I proposed an idea to implement cross-project jobs
15:56:19 <e0ne> amotoki: it relates a bit on the current one
15:56:38 <e0ne> I'll stand up with this proposal on the next meeting
15:57:17 <amotoki> perhaps we can spend on these two topic :)
15:57:25 <e0ne> amotoki: +1
15:57:46 <mordred> e0ne: fwiw, we've got some good examples of cross-project tox jobs across keystoneauth, python-openstackclient, openstacksdk, os-client-config and shade that can be cargo-culted
15:58:06 <e0ne> mordred: thanks. I will take a look on them
15:58:19 * e0ne 2 minutes reminder
15:58:45 <amotoki> I just raised cross-project topic to the horizon team so that they understand it more :)
15:59:58 <e0ne> we can move our discussion to the #openstack-horizon meeting
16:00:00 <amotoki> reminder on mock-migration https://review.openstack.org/#/q/topic:bp/mock-framework-in-unit-tests+status:open :)
16:00:05 <e0ne> *channel
16:00:09 <amotoki> on the identity panels
16:00:16 <e0ne> thanks everybody
16:00:22 <amotoki> thanks
16:00:24 <e0ne> #endmeeting