15:01:55 <amotoki> #startmeeting horizon
15:01:56 <openstack> Meeting started Wed Apr 22 15:01:55 2020 UTC and is due to finish in 60 minutes.  The chair is amotoki. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:57 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:59 <openstack> The meeting name has been set to 'horizon'
15:02:06 <e0ne> hi
15:02:08 <amotoki> #chair e0ne
15:02:09 <openstack> Current chairs: amotoki e0ne
15:02:13 <amotoki> hi
15:02:13 <vishalmanchanda> hi
15:03:16 <amotoki> let's start
15:03:56 <rdopiera> hi
15:03:57 <amotoki> I would like to cover ussuri-related topic first and let e0ne lead the remaining if needed
15:04:07 <amotoki> #topic announcements/notices
15:04:41 <amotoki> This week is the hardstring freeze for ussuri.
15:05:05 <amotoki> we already cut stable/ussuri last week
15:05:24 <amotoki> so we don't have much on this.
15:05:48 <amotoki> what we need to do is to review stable/ussuri reviews as usual.
15:06:04 <amotoki> the master branch is now open for victoria.
15:06:56 <e0ne> amotoki: can we get this one https://review.opendev.org/#/c/721674/ backported to Ussuri? it's a bugfix with new management command?
15:07:08 <e0ne> I'm sorry, didn't file a bug yet :(
15:07:38 <amotoki> e0ne: it just depends on when it lands. I think it is a normal bug fix.
15:08:05 <e0ne> amotoki: ok. thanks. I'll propose a chery-pick once it will be merged to master
15:08:10 <amotoki> e0ne: perhaps we will have another release from stable/ussuri to import translations so it would be part of the ussuri release.
15:08:42 <amotoki> any other announcements?
15:09:01 <e0ne> I've created an ehterpad for PTG planning
15:09:03 <e0ne> #link https://etherpad.opendev.org/p/horizon-v-ptg
15:09:31 <e0ne> we should request a virtual room for ptg this week if we need it
15:09:40 <amotoki> it looks like 'v' means both 'virtual' and 'victoria' :)
15:09:45 <e0ne> I'm going to do it today
15:09:50 <e0ne> amotoki: :)
15:10:29 <amotoki> which timeslots do you plan to request?
15:11:07 <e0ne> it depends on whole the team
15:11:29 <e0ne> I'm in UTC+3 timezone
15:11:50 <e0ne> I would like to have a good time for the all cores
15:12:04 <amotoki> #link http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014126.html
15:12:19 <e0ne> and some small  slot to cover US timezone in case if we need to cover some cross-project  dicsuccions
15:12:33 <amotoki> timeslots are categorized into three zones.
15:13:03 <amotoki> #link https://ethercalc.openstack.org/126u8ek25noy
15:13:53 <e0ne> I'm OK for 13-21 UTC
15:14:01 <amotoki> I am okay either with 13-17UTC and 4-8UTC slots
15:14:09 <e0ne> 21:00 UTC is pretty late, so it's not my favorite time:)
15:14:24 <e0ne> vishalmanchanda, rdopiera: what about yuo?
15:14:53 <vishalmanchanda> I am fine with 13-21 UTC slot.
15:15:17 <amotoki> there is no such slot "13-21UTC" :p
15:15:35 <vishalmanchanda> oops:).
15:15:49 <amotoki> you can check the ethercalc link above
15:15:58 <vishalmanchanda> i am fine with any slot.
15:16:09 <vishalmanchanda> any time slot work for me:).
15:16:28 <vishalmanchanda> go ahead.
15:17:09 <e0ne> :)
15:20:55 <amotoki> it looks like we can move on
15:20:59 <amotoki> #topic ussuri
15:21:05 <rdopiera> e0ne: I don't have a preference
15:21:17 <amotoki> #undo
15:21:18 <openstack> Removing item from minutes: #topic ussuri
15:22:23 <amotoki> 13-17UTC is converted into 10pm-2am in my local time, but I think it fits most folks in horizon.
15:22:49 <amotoki> hopefully it can finish 16UTC but it is not a big problem to me.
15:23:55 <amotoki> anything else?
15:23:58 <e0ne> I think 2-3 hours will be enough
15:24:24 <amotoki> +1
15:24:35 <vishalmanchanda> +1
15:24:51 <amotoki> if we cannot cover all, perhaps we can reserve on-demand slots
15:25:32 <e0ne> +1
15:26:13 <e0ne> let's create a list of topics to discuss  https://etherpad.opendev.org/p/horizon-v-ptg before we request some timeslot
15:28:09 <amotoki> yeah, I will dump items in my mind this week
15:29:24 <e0ne> amotoki: +1
15:29:47 <amotoki> moving on
15:29:56 <amotoki> #topic ussuri release
15:30:14 <amotoki> we already covered most things for ussuri release above
15:30:38 <e0ne> great work!
15:30:59 <amotoki> tempest-horizon plugin 1.0.0 was also releaed https://review.opendev.org/#/c/721500/
15:31:15 <amotoki> it is cycle-automatic
15:31:44 <e0ne> v.1.0.0!
15:31:46 <e0ne> :)
15:31:53 <amotoki> hehe
15:32:22 <amotoki> it is 1.0.0 but I am not sure we would like to continue it or merge tempest tests into the integration tests :p
15:33:18 <e0ne> :)
15:34:05 <amotoki> it can be visit in V cycle. we run devstack only for one test.
15:35:26 <e0ne> :)
15:35:45 <e0ne> it's useful test to verify deployment with openstack services
15:35:56 <amotoki> apart from that, I just started a follow-up work on the community goal "Contributor and PTL guide"
15:36:29 <amotoki> it would be nice if we can finish it till the U release.
15:37:41 <amotoki> if you have bug fixes good for ussuri, feel free to backport them and ping us.
15:38:02 <amotoki> that's all from me on ussuri
15:39:04 <e0ne> amotoki: thanks a lot for leading us during this release!
15:39:33 <amotoki> yw. you all helped me a lot and we are the team.
15:40:12 <amotoki> #topic on-demand agenda
15:41:32 <amotoki> I would like to share two gate breakages we had last week for FYI
15:41:45 <e0ne> :(
15:41:58 <amotoki> the one is pytest usage broke all plugin UTs
15:42:26 <e0ne> I'm sorry for that:(. I broke plugins gates again :(
15:42:36 <amotoki> pytest availability is checked now to make pluginUTs work without pytest https://review.opendev.org/720844
15:42:54 <vishalmanchanda> amotoki: thanks for the fix.
15:43:01 <amotoki> perhaps we need to introduce a minimum cross gate with some horizon plugins
15:43:15 <e0ne> +1
15:43:22 <vishalmanchanda> amotoki: I want to raise this topic last week but i completely forgot:(.
15:43:28 <e0ne> it't in my TODO list for a while
15:43:52 <amotoki> it would be something like what requirements repo does.
15:44:16 <amotoki> the other thing is related to the migration to unittest.mock.
15:44:20 <e0ne> +1
15:44:37 <e0ne> oops. I broke everything again
15:44:51 <e0ne> amotoki: what was the issue with mock?
15:44:59 <amotoki> horizon migration to unittest.mock broke horizon plugin UTs which use create_mocks from the helper function.
15:45:32 <amotoki> create_mocks sets up mocks using unittest.mock and some other mocking use the mock library
15:45:57 <e0ne> oh.. :(
15:46:09 <amotoki> I haven't investigated the failure in detail but some inconsistency (mixed usage of unittest.mock and mock) caused the failure
15:46:23 <amotoki> it was observed in heat-dashboard
15:47:26 <amotoki> As far as I checked, it does not mean all plugin UT using create_mocks fail.
15:47:42 <amotoki> one example failure is https://zuul.opendev.org/t/openstack/build/1abdd087265648b68026a7f2ea6d590c
15:48:17 <amotoki> this is another reason that we need cross gate with horizon plugins
15:48:33 <amotoki> it is hard to detect such by human reviews
15:49:12 <amotoki> that's all I would like to share here.
15:49:31 <vishalmanchanda> I have a question to ask about pytest
15:49:39 <e0ne> amotoki: thank for pointing us in these topics
15:50:07 <amotoki> we had a lot of gate breakage in this cycle.....
15:50:29 <amotoki> django-babel, pyscss, unitest.mock, pytest.....
15:50:38 <amotoki> might had more
15:51:26 <amotoki> vishalmanchanda: go ahead. what is your question on pytest?
15:51:39 <vishalmanchanda> I have noticed some of plugins adds pytest in lower-constraints.txt and test-requirements.txt which fix their gate at that time.
15:51:49 <vishalmanchanda> So i have also purpose a patch in a plugin https://review.opendev.org/#/c/720652/
15:52:14 <vishalmanchanda> amotoki: Should i revert it now?
15:52:29 <amotoki> it is up to plugin team
15:52:46 <vishalmanchanda> ok.
15:52:49 <amotoki> pytest requirement was an accident
15:53:09 <amotoki> if a plugin would like to use pytest for test runner, they can continue to use it.
15:53:47 <vishalmanchanda> agreed.
15:54:05 <amotoki> if not, it would be nice to clean up it so that requirements files have no unnecessary stuffs.
15:54:35 <amotoki> I have no preference on changes you made.
15:54:45 <vishalmanchanda> amotoki: ok i will check with that team.
15:55:24 <vishalmanchanda> thanks.
15:56:44 <amotoki> anything else?
15:56:56 <e0ne> nothing from me
15:56:57 <vishalmanchanda> nothing from my side.
15:57:26 <amotoki> let's close the meeting. thanks for joining.
15:57:31 <amotoki> take care yourselves
15:57:32 <vishalmanchanda> bye
15:57:34 <amotoki> #endmeeting