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