15:00:18 <e0ne> #startmeeting horizon
15:00:19 <openstack> Meeting started Wed Aug 19 15:00:18 2020 UTC and is due to finish in 60 minutes.  The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:22 <openstack> The meeting name has been set to 'horizon'
15:00:48 <vishalmanchanda> hi
15:00:52 <e0ne> hi
15:00:55 <tmazur> \o
15:01:09 <e0ne> tmazur: welcome back! :)
15:01:37 <tmazur> e0ne thanks! :)
15:01:37 <amotoki> o/
15:03:09 <e0ne> ok, let's start
15:03:13 <e0ne> #topic Notices
15:03:34 <e0ne> Virtual PTG planning
15:03:39 <e0ne> #link https://www.openstack.org/ptg
15:04:02 <e0ne> please, do not forget to register for PTG
15:04:34 <e0ne> it's free but TC kindly asked everybody to register for it
15:05:46 <e0ne> I'm going to ask the same time slots for horizon as we'd got in June
15:06:08 <e0ne> https://etherpad.opendev.org/p/horizon-v-ptg - here is our previous PTG schedule
15:06:48 <e0ne> is it suitable for everybody?
15:07:03 <e0ne> I'll try to not have a conflicts with cinder and neutron teams
15:07:43 <amotoki> sounds good.
15:08:24 <e0ne> tmazur: what timezone are you living in?
15:09:18 <tmazur> CDT, it's UTC -5
15:09:37 <tmazur> The previous schedule is ok for me as well
15:10:32 <e0ne> tmazur: it's good. we don't need to find new timeslots
15:11:04 <e0ne> I'll send a mail one I put horizon into the schedule https://ethercalc.openstack.org/7xp2pcbh1ncb
15:11:44 <rdopiera> sorry for being late
15:12:00 <e0ne> rdopiera: don't worry, you're almost at time
15:12:40 <e0ne> the next milestone Victoria-3 in at week of September 7th
15:13:11 <e0ne> it's a both feature freeze and community goals deadline
15:13:51 <e0ne> vishalmanchanda: do we have any issues with moving our gates to ubuntu focal?
15:14:27 <vishalmanchanda> e0ne: yeah some plugins gate are failing on focal.
15:14:31 <amotoki> the current topic is about "Notices". ins't it better to discuss it later?
15:14:44 <vishalmanchanda> like openstack/ironic-ui one of them.
15:15:20 <e0ne> amotoki: good point. do you have any update or I'll change a topic?
15:15:24 <vishalmanchanda> hmm Let's move to next topic
15:15:36 <amotoki> nothing to share from me
15:16:02 <e0ne> #topic community goals
15:16:38 <vishalmanchanda> So this is the patch in horizon for focal-migration https://review.opendev.org/#/c/744647/
15:16:44 <e0ne> vishalmanchanda: it's good to have plugins CIs moved to new ubuntu, but at lease we need to switch horizon job if we didn't do it
15:17:23 <vishalmanchanda> As of now npm-jobs are failings for some plugins.
15:17:24 <amotoki> the point is the job template which affects all plugins.
15:18:02 <e0ne> let's don't break  plugins gates again ;)
15:18:24 <amotoki> the way not to affect plugins is to introduce a new template variant, but naming choice might be a bit tricky.
15:19:09 <e0ne> amotoki: can we just add '-focal' suffix for the new job template?
15:19:46 <vishalmanchanda> I have pushed a patch to fix it but I don't what is the right way to fix it https://review.opendev.org/#/c/744708/
15:20:01 <amotoki> e0ne: yeah, it is one choice, but it means we need to rename it in all plugins in the next migration (even if we have no extra work)
15:20:49 <e0ne> amotoki: :(
15:22:17 <amotoki> one idea is to send patches to plugins and check their status
15:22:41 <amotoki> if not small number of plugins fail, a new template variant like -focal might make sense.
15:23:08 <amotoki> if a small number of plugins fail, we can continue to use the current template.
15:23:12 <e0ne> amotoki: +1
15:23:25 <vishalmanchanda> sounds good.
15:23:49 <amotoki> If they would like to keep bionic job to keep their gate healthy, they can define their own jobs with bionic
15:24:07 <e0ne> it makes sense
15:24:19 <amotoki> some clear messages to horizon plugins is required. ML message would be good.
15:25:30 <vishalmanchanda> amotoki: JFYI they are many patches already in plugins for focal-migration like this one https://review.opendev.org/#/c/744710/
15:25:51 <amotoki> vishalmanchanda: do they handle npm jobs?
15:25:56 <vishalmanchanda> But we need to check them with https://review.opendev.org/#/c/744647/
15:26:21 <vishalmanchanda> some of them may handle but i not tried.
15:26:37 <amotoki> there is no need to complete the focal migration in a single patch, and they can be handled separately
15:26:55 <vishalmanchanda> amotoki: ok.
15:27:20 <amotoki> we have a couple of weeks till milestone-3, so one possible way is to land horizon change soon.
15:28:49 <amotoki> if they consider they complete the focal migration only with l-c change, it would be a problem of cource :p
15:30:23 <vishalmanchanda> amotoki: +1.
15:33:38 <amotoki> have we agreed the plan?
15:33:49 <e0ne> +1
15:34:53 <vishalmanchanda> Who will send the mail on open-discuss for horizon-plugin
15:35:01 <vishalmanchanda> for focal-migration.
15:37:02 <e0ne> vishalmanchanda: since you're working on this effort, could you please do it?
15:37:36 <vishalmanchanda> e0ne: ok I will do that but plan is not clear to me yet.
15:37:59 <amotoki> what I suggest is to check plugin status first and if we decided to change the template to focal and it would trigger plugin gate braekage we can send a notice
15:38:36 <amotoki> s/decided/decide/
15:39:08 <vishalmanchanda> amotoki: Ok i will push Test-patches for plugins with depends-on https://review.opendev.org/#/c/744647/
15:39:29 <vishalmanchanda> then we can discuss.
15:41:42 <vishalmanchanda> I will paste the outcome on our etherpad https://etherpad.opendev.org/p/horizon-release-priorities
15:42:31 <e0ne> vishalmanchanda: sounds good
15:46:37 <e0ne> it seems we're done with this topic
15:47:12 <e0ne> amotoki: do you have any update about policies?
15:48:08 <amotoki> e0ne: it is a slow progress. sorry...
15:48:33 <e0ne> ok, I understand it
15:48:48 <e0ne> #topic Open Discussion
15:49:28 <e0ne> I'm moving 'Chinese translation lang codes' to the next meeting, because it'll take more than 10 minutes
15:49:38 <e0ne> do we have anything more to discuss?
15:50:45 <vishalmanchanda> I have a question to ask for stable/rocky nodejs job failure https://review.opendev.org/#/c/737490/
15:52:16 <vishalmanchanda> If we want to fix horizon stable/rocky then we need to fix it in opestack/openstack-zuul-jobs ?
15:52:55 <amotoki> vishalmanchanda: could you elaborate it more detail?
15:53:51 <amotoki> vishalmanchanda: doesn't a backport of a nodejs-job fix like https://review.opendev.org/#/c/737577/ work?
15:53:59 <vishalmanchanda> amotoki: I mean we are using this template https://opendev.org/openstack/horizon/src/branch/stable/rocky/.zuul.yaml#L81
15:54:52 <vishalmanchanda> which is defined here https://opendev.org/openstack/openstack-zuul-jobs/src/commit/27897ee9deafac6a8a7f1bc8c0c917abdbcb3155/zuul.d/project-templates.yaml#L1674
15:55:03 <vishalmanchanda> or I am wrong?
15:56:01 <amotoki> theoretically nodejs job template in horizon (in stein or later) and nodejs job template from openstack-zuul-jobs (in rokcy) are same.
15:56:19 <amotoki> when nodejs jobs with node10 was introduced the horizon job template was introduced.
15:56:27 <amotoki> perhaps as you may know.
15:57:15 <amotoki> Changes in openstack-zuul-jobs and zuul-jobs are intentional, so we need a similar pre-run for rocky nodejs4 jobs.
15:57:34 <amotoki> * in horizon side.
15:58:12 <amotoki> If you are not sure I can handle it.
15:58:31 <vishalmanchanda> amotoki: ohh I pushed a patch in openstack-zuul-job.
15:59:13 <vishalmanchanda> amotoki: thanks you can push a patch to fix it.
15:59:44 <amotoki> vishalmanchanda: I have one thing to clarify.
16:00:02 <amotoki> vishalmanchanda: is your patch related to the tox installation?
16:00:08 <e0ne> unfortunately, we're out of time. let's move our conversation into the #openstack-horizon channel
16:00:25 <vishalmanchanda> amotoki: https://review.opendev.org/#/c/746462/
16:00:40 <e0ne> #endmeeting