14:00:01 #startmeeting cinder 14:00:01 Meeting started Wed Oct 11 14:00:01 2023 UTC and is due to finish in 60 minutes. The chair is whoami-rajat. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:01 The meeting name has been set to 'cinder' 14:00:04 #topic roll call 14:00:06 o/ 14:00:25 o/ 14:00:44 hi 14:00:49 hi 14:01:05 o/ 14:01:34 o/ 14:01:39 o/ 14:02:01 o/ 14:02:18 o/ 14:02:58 we've a new etherpad 14:03:00 #link https://etherpad.opendev.org/p/cinder-caracal-meetings 14:04:10 hello everyone 14:04:15 o/ 14:04:27 let's get started with the announcements 14:04:31 #topic announcements 14:04:47 Welcome to the first meeting of 2024.1 (Caracal)! 14:05:07 and so the cycle begins again 14:05:16 :-) 14:05:26 as i said we've a new meeting etherpad, please add your topics to that from now on until the end of 2024.1 14:05:31 for which we've quite some time 14:06:11 ok moving on 14:06:14 next, Congratulations Brian for becoming TC vice chair! 14:06:22 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-October/035272.html 14:06:22 ++ 14:06:24 Congrats 14:06:42 All the power -- use it wisely 14:06:54 thanks, though i prefer to refer to myself as the "chairman of vice" 14:07:13 LOL 14:07:16 :D 14:08:52 congratulations Brian! 14:09:04 we've another major related announcement 14:09:07 Congratulations Jon Bernard for becoming cinder stable core! 14:09:16 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-October/035310.html 14:09:21 congratulations Jon! 14:10:10 i think he's not around since i can't find his irc but Jon has been managing stable releases for past 3 or 4 cycles 14:10:20 so totally deserved, congratulations Jon 14:10:27 and thanks rosmaita for proposing him 14:11:06 ok i see jbernard joined 14:11:11 jbernard, we were just congratulating you for becoming a stable core 14:11:30 o/ 14:11:34 thanks everyone 14:11:35 Congratulations and thanks for helping out! 14:11:43 o/ 14:11:49 didn't receive the reminder 14:13:05 jproque-dell, did you change your irc nick? you can add it to the list here https://etherpad.opendev.org/p/cinder-caracal-meetings#L31 14:13:45 next, PTG Details 14:13:53 #link https://ptg.opendev.org/ptg.html 14:14:02 Room: Cactus 14:14:03 Date: 24 Oct - 27 Oct, 2023 14:14:03 Time: 1300-1700 UTC 14:14:07 I just realized that I logged in with my alternative nickname, thks womai-rajat 14:14:35 I've booked the Cactus room on the following date and time ^ as you can see in the PTG link i provided 14:14:47 jproque-dell, no problem 14:16:02 hope to see everyone at the PTG 14:16:15 cinder usually has the highest strength, which is really good to see 14:16:38 related to that, we've the PTG planning etherpad 14:16:40 #link https://etherpad.opendev.org/p/caracal-ptg-cinder-planning 14:16:50 so please add topics that you would like to be discussed during the PTG 14:17:23 remember we plan the next 6 months items during the PTG so it would be good to bring things up that you would like to work on during the 2024.1 cycle 14:17:50 last announcement, OpenInfra Live: 2023.2 Bobcat Updates 14:17:57 #link https://lists.openstack.org/pipermail/openstack-discuss/2023-October/035271.html 14:18:22 so we had the open infra live last week in which project PTLs provided their project update 14:18:41 the projects represented were nova, ironic, manila, neutron and cinder 14:18:53 #link https://www.youtube.com/watch?v=q7WDncK3YuM 14:19:02 we've the recording on youtube if you would like to watch ^ 14:19:33 thks 14:19:41 that's all the announcements from my side 14:19:50 anyone has anything else to announce? 14:22:49 guess not 14:22:49 let's move to topics 14:22:58 #topic PTG video conference tool 14:23:13 so as i announced earlier, we've upcoming PTG for 2024.1 release 14:23:38 unfortunately bluejeans is not available anymore and we need to switch to a new video conference tool 14:23:55 Zoom is the default option provided by the community 14:24:09 recently we've been keeping meetings on gmeet which has worked fine for us 14:24:25 but in the past, contributors from China had issues joining it 14:24:49 also rosmaita can correct me but TC is planning to use jitsi-meet this time 14:25:02 not sure about that 14:25:24 i read it in the TC meeting agenda, maybe it was just a discussion topic 14:25:28 there's discussion to hold the monthly TC meeting that's in video in jitsi-meet instead of zoom 14:25:42 ah ok 14:26:05 there's a limit on how many connections it can handle, that's why the foundation uses zoom 14:26:18 Is that jitsi-meet browser based? 14:26:46 SumitGupta1503: it uses a lot of browser capabilities, iiuc 14:27:45 Cinder usually has good strength at the PTG (20+ sometimes 30+ on initial days) 14:28:16 basically i just wanted opinions from the team if they've tried different tools and something which has worked best for them 14:28:25 Zoom works best for us :) 14:28:32 yeah, i am not sure what the jitsi-meet limit is 14:29:29 we use Zoom as well 14:29:33 works fine 14:29:38 Internet says 100 users with good performance for jitsi 14:29:46 Thereafter, lag.. 14:30:22 I have seen zoom working with 300+ users few times.. 14:30:58 i think the problem with jitsi for us is it doesn't have native recording capability 14:30:59 SumitGupta1503, that might be the ideal limit but practically it might differ, but I haven't used jitsi so can't comment really 14:31:28 rosmaita, ah, that's a big issue then ... 14:31:50 though maybe that has changed with more recent versions? 14:33:57 So, what are downsides to Zoom? If there are none, let's just agree to it, prepare rooms, write links to Etherpad and move on (I am dumping all this work implicitly on Rajat, sorry). 14:34:51 rosmaita, a quick search says it does allow recording but maybe it's a premium feature 14:35:08 zaitcev, right, based on the feedback here i feel zoom should be good for us 14:35:09 we'd have to check with #openstack-infra 14:35:37 zaitcev, it's the PTL responsibility to do all that so no worries :D 14:35:48 actually, should be no work if we pick zoom, it's the default for the ptg tooling 14:35:52 Right. If they veto Zoom for whatever reason, then tough luck. 14:37:09 ok great 14:37:35 let's try out Zoom this time and see how it goes 14:38:22 actually the PTG schedule link defaults to the zoom link so there is actually less or no work to do here 14:38:51 anyways, thanks everyone for feedback, we will go with Zoom this time 14:38:56 Cool. 14:38:56 next topic 14:39:05 #topic Operator Hour at PTG 14:39:12 this is another discussion that i need some help with 14:39:42 I'm not sure what would be the best time for the operator session 14:39:56 I've proposed 2 dates and 2 different times 14:39:58 Wednesday: 1400-1500 UTC or 1500-1600 UTC 14:39:58 Thursday: 1400-1500 UTC or 1500-1600 UTC 14:40:19 I haven't kept it as the starting session since everyone is gathering usually for the first 10-15 mins 14:40:33 good idea 14:41:07 also the last session for these two days are booked for cross project (just today) 14:41:20 let me just announce that as well 14:41:27 wednesday 1600-1700 Nova cross project 14:41:36 Thursday 1600-1700 Manila cross project 14:42:07 so yeah, enough from my side, please let me know which time seems more suitable for operators 14:42:35 i think just grab whichever one you prefer 14:43:44 ok, let's go with Wednesday 1400-1500 UTC 14:44:40 it also matches what we had the last time (IIRC) 14:46:02 i guess everyone agrees to it 14:46:16 i will book it after the meeting 14:46:22 last topic for today 14:46:25 #topic Having CI issues here 14:46:30 #link https://review.opendev.org/c/openstack/cinder/+/868485 14:46:33 drencrom, that's you 14:47:01 Yes, that patch had a wf+1 last week but zuul is failing 14:47:51 looks like timeout issue on the last run 14:48:24 the job cinder-tempest-plugin-lvm-lio-barbican passed on the last run so it looks unrelated 14:48:33 but we've been seeing these failures quite a lot 14:48:51 i stopped an lio-barbican failure related to oom-killer again today, is anyone still looking into that area? 14:48:53 Yes, it seems it is just flaky 14:48:54 i spotted* 14:49:12 yeah, looks like it can't ssh into the instance for the test 14:49:24 drencrom, one recommendation for recheck is to also mention the reason for failure after the recheck keyword 14:49:37 drencrom, eg: recheck lvm-lio-barbican job failed with reason <> 14:49:46 ack, will do 14:49:53 eharney: do you have a patch? 14:50:06 rosmaita: https://review.opendev.org/c/openstack/cinder/+/888296 14:50:43 oh, when you said "stopped" i thought you meant "fixed" 14:50:46 :D 14:50:54 yeah typo 14:53:21 I haven't really got time to look at the failures, but would be good if someone wants to volunteer to look into our gate issues 14:54:34 is "we're running out of memory and oom-killer is killing mysql" still a commonly seen problem? 14:54:48 looks like no oom on drencrom's patch for lio-barbican, just the instance didn't respond 14:55:36 eharney: your patch has 4 oom killed processes: mysqld, cryptsetup, qemu-system-x86, qemu-system-x86 14:56:32 my hunch is to either lower test concurrency or throw more swap space at it 14:56:33 but my impression is that mysqld getting killed is still pretty common 14:56:45 ok, i wasn't sure if we thought we had gotten that sorted out or not 14:57:22 yeah, i don't think so 14:59:19 we're out of time 14:59:33 there are a lot of review requests 14:59:39 some are follow ups from past cycles 14:59:42 so remmeber to take a look 14:59:59 also I'm planning to cancel next week's meeting since we will be meeting at the PTG 15:00:09 i will send a mail regarding that to ML 15:00:11 Thanks! 15:00:21 thks Rajat 15:00:30 thanks everyone, see you at the PTG! 15:00:33 #endmeeting