15:00:17 #startmeeting horizon 15:00:17 Meeting started Wed Jan 17 15:00:17 2024 UTC and is due to finish in 60 minutes. The chair is vishalmanchanda. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:17 The meeting name has been set to 'horizon' 15:00:43 hello anyone around for the horizon weekly meeting? 15:00:56 hi, I am 15:01:03 o/ 15:01:11 hello everyone 15:01:23 o/ 15:01:42 let's wait for few minutes if more people join us. 15:02:09 o/ 15:03:25 let's start the meeting. 15:03:47 agenda of the meeting can be found here https://etherpad.opendev.org/p/horizon-release-priorities#L46 15:04:01 #topic Notices 15:04:56 one announcement from my side for this week. 15:05:31 OpenStack D Release Name is announced last week. It is Dalmatian. 15:05:41 Yay! 15:05:43 https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/3OZILLG26HZ3KEDHGPB2HUDZ72WPP4JJ/ 15:06:27 moving to the next topic 15:06:48 #topic Release priorities 15:07:44 I discussed the status of all priorities items in the last weekly meeting but only radomir joined that meeting. 15:08:05 anyway let's discuss any update on those topic. 15:09:15 pytest-based selenium tests progress is good, patch to fix the CI job also got merged last week. 15:09:36 Migrate to Django version =>4.2 from Django 3.2 15:10:10 This migration is almost completed, I pushed a patch today to make django 4.2 job as voting 15:10:21 https://review.opendev.org/c/openstack/horizon/+/905864 15:10:48 Please review the patch once you have time. 15:11:38 I also pushed a patch to bump upper Django version in openstack/requirements. 15:11:53 https://review.opendev.org/c/openstack/requirements/+/904202 15:12:40 next is Migration to next nodejs LTS version nodejs v18-> nodejs v20 15:13:11 This migration is completed. So I will not discuss it in upcoming weekly meeting. 15:13:35 marking it as completed on etherpad. 15:14:26 next is Switching to openstacksdk 15:15:11 Initial Patch is up for this https://review.opendev.org/c/openstack/horizon/+/891205 15:15:49 thanks for mentioning it, I am strugling with one integration test 15:15:50 but CI is failing as of now. 15:16:00 ok 15:16:22 to tell the truth I am not sure if I really cause of it to fail, or if I cause it it what is it exactly 15:16:43 some time these failure for integration test are random and may not related to your change. 15:16:54 in the current state I skipped most of the integration tests to make debugging simpler (for me at least) 15:17:07 these fails randomly that's why we are switching to pytest based test. 15:17:25 lajoskatona: ok I will take a look. 15:17:59 ah,, ok, because the last failures (no instance is visible in list after clicking to launch instance seems unrelated (see the png from selenium: https://4d269e69f7d5f4f1ace3-14d2aaee87a52e6f9b0dc86ecc0fbd6c.ssl.cf2.rackcdn.com/891205/15/check/horizon-integration-tests/23998b1/tox/test_reports/TestInstances.test_create_delete_instance/screenshot.png ) 15:18:19 thanks anyway for the attention 15:19:04 lajoskatona: other than integration test your patch is ready to review? 15:19:48 I remove the tests skips and I think otherwise it is ready for review, tomorrow (perhaps even this evening) I push it again than 15:20:03 ok 15:20:45 thanks. 15:20:58 next is Use placement API for the hypervisor stats 15:21:35 This patch was merged for it: https://review.opendev.org/c/openstack/horizon/+/890525 15:21:37 One patch is already merge for this issue https://review.opendev.org/c/openstack/horizon/+/890525 15:22:09 tmazur: Is there anything pending for this issue which you are working on? 15:23:47 I need to submit a cosmetic patch correcting the confusing diagrams. 15:24:06 ok. 15:24:33 I asked this week a related question : is it possible to backport this to older branches 15:24:37 ? 15:25:01 What both hypervisors and placement call total VCPUs are in fact the cores, so the diagrams are incorrect 15:25:26 tmazur: ok. 15:25:34 lajoskatona: I was just about to raise this topic 15:25:45 Do we want it backported? 15:25:54 +1, sorry to be too quick 15:26:26 yes, acually we need it even on victoria for some of our customers, but any backport can help our downstream teams 15:26:41 I see it pretty reasonable. This issue was here for a long while, so we probably want it fixed in earlier versions 15:27:05 The question is: how far back do we want to do it? 15:27:06 as I checked you need placement microversion 1.6, and that is quite old, older than victoria so from tha perspective it is safe 15:27:29 but this is a grey area as it is not just a backport as I see 15:28:32 I am not sure if backport it to more stable branches may cause any issues. 15:28:35 tmazur: stable victoria would be the final as I wrote, we will see if it can work with CI and branches closing and moving to unmaintained.... etc... 15:29:02 vishalmanchanda: ok 15:29:33 vishalmanchanda: I see it the same way, but better to discuss such things 15:30:01 I am fine with backport it to till antelope release which I can test in my local env. 15:30:04 vishalmanchanda: agreed. what do you think will be the best? 15:30:21 Ok, sounds good 15:30:52 ack 15:30:54 but older than antelope release I see it as a risk. 15:30:54 And from antelope we can backport it downstream 15:31:02 yeah. 15:31:03 sounds great 15:31:38 Okay. I'll work on the upcoming cosmetic patch today and make those backports 15:31:45 ok let's wait for tmazur to push the patch 15:32:00 tmazur: +1. 15:32:47 tmazur: if you have no time for backports just ping me I can help with that of course 15:33:16 lajoskatona: thanks! 15:33:23 thanks for discussing this topic 15:34:15 ok that's all updated from my side for this week. 15:34:21 moving to the next topic 15:34:28 #topic open-discussion 15:34:41 Yes I have a small request please 15:34:42 Does anyone have any other topic to discuss? 15:34:52 profcorey: please go ahead. 15:35:07 I teach cloud computing and have a student who would like to contribute to your project this semester 15:35:29 profcorey: ok. 15:35:29 Is it possible to speak to someone about mentoring her to contribute 15:35:57 profcorey: I will be happy to help. 15:36:03 Thank you! 15:36:17 I am happy to help 15:36:25 Thank you so much! 15:36:38 Email or Dm here? 15:36:50 email is better 15:37:01 yeah. 15:37:07 Ok, my email is cleong2@valenciacollege.edu 15:37:24 I've been working with Kendall on other openstack projects as well 15:37:32 my email is manchandavishal143@gmail.com 15:37:36 Manila and Tempest 15:37:40 Great thank you! 15:37:48 I will email you, thanks! 15:37:50 she can ping me on irc dm. 15:37:56 t.v.ovtchinnikova@gmail.com 15:37:58 if need any help. 15:38:06 I'll have her start an irc account asap 15:38:11 Thank you! 15:38:46 I will email the two of you later this afternoon. 15:38:49 thanks! 15:38:56 cool. 15:39:25 That's all from me 15:39:43 anyone else have any topic to discuss? 15:40:00 Nothing from me 15:40:22 if no other topic to discuss, let's end this meeting. 15:40:45 thanks everyone for joining, see you in the next meeting. 15:40:55 #endmeeting