Wednesday, 2023-01-04

*** keerthivasan is now known as keerthivasansuresh10:24
*** keerthivasansuresh is now known as keerthivasans10:24
*** keerthivasans is now known as keerthivasansuresh10:34
*** ttx is now known as ttx_11:14
*** dviroe|out is now known as dviroe11:32
*** dviroe is now known as dviroel11:32
whoami-rajat#startmeeting cinder14:00
opendevmeetMeeting started Wed Jan  4 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
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'cinder'14:00
whoami-rajat#topic roll call14:00
enriquetasohi14:00
simondodsleyo/14:00
eharneyhi14:00
harshailanihi14:00
Mounikahi14:00
mubeenhi14:00
whoami-rajat#link https://etherpad.opendev.org/p/cinder-antelope-meetings14:01
whoami-rajatHappy new year everyone!14:01
jungleboyjo/14:01
jungleboyjHappy New Year!14:01
rosmaitao/14:02
harshailaniHappy New Year :)14:02
MounikaHappy New Year!14:03
whoami-rajatgood amount of people are around after the break14:03
whoami-rajatlet's get started14:03
whoami-rajat#topic announcements14:03
whoami-rajatfirst, Status of Specs (deadline 23rd December, 2022)14:03
whoami-rajatso we're past the spec deadline14:03
whoami-rajatthere were 3 specs proposed out of which 1 merged14:04
whoami-rajatwhich is Extend in-use FS volumes14:04
whoami-rajatthe next one is, Encrypted Backup support14:04
whoami-rajatbut that currently has 2 -1s and I think Gorka is still not back from break14:04
whoami-rajatlast one is New backup field for allowing backups during live migration14:05
whoami-rajatwhich was recently proposed i think during year end14:05
simondodsleyWel that is well past spec freeze so it should wait14:05
whoami-rajatyes correct14:06
whoami-rajatwe could've considered them but they're way far from merging right now14:06
jungleboyj++14:06
whoami-rajatand extending it would only conflict with our next deadlines14:06
whoami-rajatstill I'm open to suggestions if the team thinks otherwise14:06
eharneyiirc we still need to assess whether fernet is a good solution for encrypted backups14:06
whoami-rajatthat's a good point14:07
eharneythere were some good concerns raised that haven't really been analyzed yet14:07
happystackerhey guys! Happy new year to all the community14:07
happystackernad especially my loved core reviwers ;-)14:08
whoami-rajatso it makes sense to push them to next cycle, I will do the procedural -2 later today14:09
whoami-rajatthanks for the discussion14:09
whoami-rajathappystacker, happy new year!14:09
whoami-rajatlet's move to the next announcement14:10
whoami-rajatDriver Merge deadline 20th Jan, 202314:10
whoami-rajatdeadline would've been this week but I shifted it based on past cycle experience so we've time to review them14:10
whoami-rajatok, let's discuss the drivers quickly14:10
whoami-rajat1) HPE XP14:11
whoami-rajat#link https://review.opendev.org/c/openstack/cinder/+/81558214:11
whoami-rajatI did a CI check yesterday and it hasn't responded yet14:11
whoami-rajatI used the same comment they did in os-brick14:11
whoami-rajatso not sure what's wrong14:11
simondodsleyis abdi: here?14:12
whoami-rajatregarding the code part, it has inherited everything from the hitachi driver, even supports the same features as the parent driver14:12
simondodsleyit's the same device just rebadbed14:12
simondodsleyrebadged14:12
whoami-rajatah, that makes sense now14:13
whoami-rajatok, I've left a comment for the author to check the CI14:14
simondodsleyrosmaita do you have your CI checklist somewhere? 14:15
whoami-rajatin the meantime, feel free to review the driver, the tests are good LOC so that could be reviewed14:15
rosmaitasightly off-topic, but whoami-rajat it would be a good idea to send something to the ML reminding vendors that we are requiring CI on os-brick changes for antelope14:15
rosmaita#link https://lists.openstack.org/pipermail/openstack-discuss/2022-August/030014.html14:15
rosmaitafollow-up to that ^^14:15
rosmaitasimondodsley: yes, i should put that up in an etherpad or something14:16
happystackerbtw, I have a few code changes I'd expect to be merged into Antelope, can someone take a look at them if I give you the list?14:16
rosmaita"that" == CI checklist14:16
whoami-rajatrosmaita, good idea, i will reply to that thread14:16
rosmaitasounds good14:17
whoami-rajathappystacker, we can discuss that towards the end in the open discussion14:17
happystackersounds good, preparing the code change IDs14:17
simondodsleyhappystacker, put them in the etherpad14:17
happystackerwill do14:17
whoami-rajathappystacker, better, I've added a review request section in the end, you can put the list there14:18
whoami-rajatall ^14:18
happystackerok Rajat, working on it14:18
whoami-rajatgreat14:18
whoami-rajatso moving on to the next driver14:18
whoami-rajat2) Fungible NVMe TCP14:18
whoami-rajat#link https://review.opendev.org/c/openstack/cinder/+/84914314:19
whoami-rajatI've reviewed it today, they seem to be doing something with a default volume type that they've defined14:19
whoami-rajatI'm not sure what's the idea there but probably they will clarify14:19
whoami-rajatalso I don't know if we support NVMe with TCP or not14:20
whoami-rajatfrom os-brick perspective14:20
simondodsleyyes - TCP and RoCE and supported. FC is not14:20
whoami-rajatoh that's good14:20
happystackerwhat's the etherpad link again?14:21
whoami-rajathappystacker, https://etherpad.opendev.org/p/cinder-antelope-meetings14:21
simondodsleyFC is delayed as Red Hat don't want Gorka working on it as they don't see their customers wanting it14:21
simondodsleywhich is a shame for other vendors that do, but don't have the os-brick skillset...14:21
whoami-rajatok, i think it also depends on vendors what protocol they use with nvme? do we have drivers (existing/upcoming) that would want nvme with FC?14:22
simondodsleyPure want it14:22
rosmaitasimondodsley: just out of curiosity, is that for customers who already have FC, or completely new customers?14:23
simondodsleyusually for existing customers. New ones tend to be greenfield and will go TCP or RoCE14:23
rosmaitathanks, that was my intuition, but i wanted a reality check14:23
whoami-rajatgood to know we've a use case for NVMe FC support14:24
whoami-rajatok, that's all for this driver as well14:25
felipe_rodriguesHi guys14:25
felipe_rodriguesNetApp wants to deliver a NVMe/TCP driver for the next release14:25
whoami-rajatthese are the 2 drivers we've for this cycle, reviewers please take a look14:25
felipe_rodriguesWe are working downstream on it.. probably, sending the patch upstream end of this week14:25
felipe_rodriguesis it possible yet ?14:26
whoami-rajatfelipe_rodrigues, if it's for next release, sounds good to me14:26
whoami-rajatfor this cycle, it needs to have a working CI and all the driver guidelines satisfied14:26
felipe_rodriguesThey are not available yet, because it is private.. The patch is a medium one.. because it is just about connection (initialize and terminate connection).. 14:28
felipe_rodriguesI mean.. The CI/patch would be available end of this week, is it possible to have the review and merge  to Antelope or it is too late ? 14:28
whoami-rajatthe deadline is 20th Jan so we've enough time14:29
felipe_rodriguesI see.. 14:29
felipe_rodriguesLet see if it possible, thank you so much! 14:29
enriquetasoremember that we are requiring CI on os-brick changes for antelope14:30
whoami-rajatthe idea is to have the driver and CI in a working state and respond quickly to review comments to have better chance to make it to the cycle14:30
whoami-rajatenriquetaso++14:31
whoami-rajatok, last announcement I've is for midcycle 214:31
whoami-rajatMidcycle-2 Planning14:31
whoami-rajat#link https://etherpad.opendev.org/p/cinder-antelope-midcycles#L3314:31
whoami-rajatwe hadn't finalized the date in the beginning since there were conflicts14:31
whoami-rajatcurrently I'm proposing the date 18th Jan which is next to next week14:32
whoami-rajatdo we have any known conflicts for that date?14:32
whoami-rajatit is a 2 hour video meet14:32
whoami-rajatit will be on wednesday and will overlap with 1 hour of cinder upstream meeting14:32
simondodsleyi'm not available then, but that shouldn't stop you14:33
rosmaitano conflicts from me, and at the risk of insulting someone, doesn't look like there's a national holiday in any of the major locations on that day14:34
harshyea no conflict with me as well14:34
enriquetasono conflicts from me either (but i'm also available any other day)14:35
whoami-rajatcool, let's fix this date for now and discuss this again next week14:35
whoami-rajatin the meantime, please add topics14:35
whoami-rajatthat's all i had for announcements14:36
whoami-rajatanyone has anything else?14:36
whoami-rajatlooks like not, let's move to topics then14:37
whoami-rajat#topic tox jobs failing in the stable branches14:37
whoami-rajatrosmaita, that's you14:37
rosmaitayeah, we are having tox 4 failures in all stable branches14:38
whoami-rajat#link https://review.opendev.org/q/topic:tox-4-postponed14:38
rosmaitathose are the patches ^^ that should fix it14:38
rosmaitaat least for now, they don't use tox 414:39
happystackerok so we'll continue to use tox 3 for now?14:39
rosmaitayes, in the stable branches14:39
happystackerok14:39
rosmaitayou can't use tox4 with python 3.614:39
whoami-rajatrosmaita, one question i had, i only see os-brick and cinder patches, don't we require it in cinderclient or other cinder projects?14:39
rosmaitayeah, i was waiting until the cinderclient patch to master was working14:40
happystackerDo we have an estimate of when the swicth to tox4 will happen?14:40
rosmaitawhich doesn't make sense, now that i think about it14:40
rosmaitahappystacker: december 23, 202214:40
whoami-rajatrosmaita, ah we still have cinderclient change open?14:41
rosmaitai can put up patches for the cinderclient stable branches too14:41
whoami-rajati mean the master one14:41
happystackerdecember 23 has passed14:41
rosmaitayeah, i think i figured out what was happening, and put up a new patch14:41
whoami-rajatok, i remember, it was failing gate14:41
rosmaitatake a look at this real quick: https://zuul.openstack.org/stream/6997323310894f48855e4b9139b26f10?logfile=console.log14:41
harshyes14:41
rosmaitathe functional-py38 are passing now, but it's going to timeout14:42
harshgate was failing but that was due to openstacksdk failures14:42
whoami-rajathappystacker, the tox4 migration has happened and that's why we're seeing gate breaking in stable branches, for master rosmaita already fixed it14:42
rosmaitaharsh: this is a different issue (i think)14:42
harshoh ok14:42
whoami-rajatharsh, that's a different issue which is fixed now14:42
whoami-rajatbut related to tox414:42
harshyea14:42
happystackermmh, ok14:43
rosmaitamaybe fungi is around?14:43
fungii am14:43
rosmaitathe func-py38 has been sitting for >20 min14:43
rosmaitafungi: happy new year! can you take a look at https://zuul.openstack.org/stream/6997323310894f48855e4b9139b26f10?logfile=console.log14:43
rosmaitalooks like the job is stuck?  hopefully it's not something on the cinder side?14:44
rosmaitathis is the patch being checked: https://review.opendev.org/86831714:45
fungiwhat does a run of that job normally look like after that point? is it maybe collecting files or compressing something?14:45
rosmaitafungi: should look just like the func-py39 job, i think14:45
rosmaitahttps://zuul.opendev.org/t/openstack/build/9ba34208232b4db49c48ceac72716c9814:45
fungisubunit file analysis?14:45
whoami-rajatit proceeded14:46
rosmaitafungi: maybe, guess i shoud wait until it actually reports back to zuul14:46
rosmaitaanyway, that's all from me ... i'll put up the cinderclient stable branch patches later today; in the mean time, we need to merge the cinder/os-brick stable patches14:47
fungiyeah, would be interesting to see what it was doing during that quiet period, but often it will be something like the executed commands generated waaaaay more logs than expected or tons more subunit attachments or something14:47
fungialso whether subsequent builds of the same job pause in the same place14:48
rosmaitai'll put something on the midcycle agenda about my reasons for not backporting the master branch changes, and we can discuss14:48
whoami-rajatsounds good, always up for topics14:48
rosmaitafungi: thanks, i'll put up a patch that removes the tempest test so we can get quicker response14:49
whoami-rajatI've reviewed all changes to pin tox<4, it is a straightforward 2 line change which also TC suggested so should be easy to review and fix our gate14:49
whoami-rajatother cores ^14:49
whoami-rajatposting the link again to patches14:50
whoami-rajat#link https://review.opendev.org/q/topic:tox-4-postponed14:50
whoami-rajatrosmaita, anything else on this topic?14:50
rosmaitanothing from me14:50
whoami-rajatgreat, thanks for bringing this up14:51
whoami-rajatnext topic14:51
whoami-rajat#topic Unit test will fail with python 3.1114:51
whoami-rajatenriquetaso, that's you14:51
enriquetasohello14:51
whoami-rajat#link https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031655.html14:51
enriquetasoQuoting the oficial bug: "An unfortunately common pattern over large codebases of Python tests is for spec'd Mock instances to be provided with Mock objects as their specs. This gives the false sense that a spec constraint is being applied when, in fact, nothing will be disallowed."14:51
enriquetaso#link https://github.com/python/cpython/issues/8764414:51
enriquetasoJust mentioning it because this would affect our future python 3.11 job CI. 14:52
whoami-rajatdo we have a debian job somewhere so we can reproduce this in gate?14:52
eharneyi worked on this some before the winter break, have at least one patch posted14:52
eharneyjust run tox -e py311 to repro14:52
enriquetasoWe need to update at least 250 tests from different drivers. 14:52
simondodsleyouch14:52
enriquetasoi've reproduce this with docker (python3.11 debian image)14:52
enriquetasoThomas Goirand discovered this and opened a bug report to track the work:14:52
whoami-rajatah so it fails even in other distros14:52
eharneyit has nothing to do with Debian...14:52
enriquetaso#link https://bugs.launchpad.net/cinder/+bug/200043614:52
enriquetasoit's related to python >3.11 14:53
eharneythis is a change in Python14:53
eharneyanyway, fixing it is not particularly hard, but it will involve shuffling around a lot of mocks in unit tests, so it's laborious14:53
whoami-rajatok, i got confused from the bug report14:54
enriquetasoyes.. i think we dont have plans to have a 3.11 job yet  14:54
eharneythe plans are: we definitely need it to work at some point, so we should fix it :)14:54
whoami-rajatfor antelope, the runtime is 3.8 and 3.10 but we need to be ready for next cycle runtimes14:54
*** dviroel is now known as dviroel|lunch14:54
eharneythe new restriction is, basically, you can't mock a mock now, so make the mock once in the unit tests14:55
eharneyhttps://review.opendev.org/c/openstack/cinder/+/867824 is the first fix i submitted for this14:55
enriquetasocool, i think we can use the bug number to track all the fixes or use a tag if needed 14:56
rosmaitawe should probably add a non-voting py3.11 job14:56
eharneythe bug number is less important than a patch that turns on 3.11 and depends-on: patches14:56
eharneyright14:56
whoami-rajatrosmaita++14:56
enriquetaso++14:57
rosmaitai thought that was going to happen as part of the antelope template14:57
enriquetasookay!14:57
rosmaitabut there were other issues that came up ... i can ask at the TC meeting later today14:57
rosmaitain any case, we can do it ourselves in cinder, i think14:57
whoami-rajatmaybe they plan to keep 3.10 for another cycle and add n-v template next cycle but not sure14:58
eharneyalso, fwiw, i just ran "tox -e py38" this morning and am seeing 3.11 failures in there14:58
whoami-rajatrosmaita, yep, even a DNM should be good to track the failing tests14:58
eharneymaybe some tox4 weirdness?14:58
rosmaitai hope not14:58
rosmaitabut probably so14:59
eharneyit appears to be running the wrong version of python in that env :/14:59
enriquetasotopics are not available in gerrit anymore?15:00
eharneyi think they are15:00
whoami-rajatwe're out of time, let's continue this next week and in the meantime hoping we will get some fixes in15:00
whoami-rajatalso want to mention the review request section15:00
whoami-rajatthere are a bunch of review requests to please take a look at them15:01
whoami-rajat#link https://etherpad.opendev.org/p/cinder-antelope-meetings#L12115:01
whoami-rajatthanks everyone!15:01
whoami-rajat#endmeeting15:01
opendevmeetMeeting ended Wed Jan  4 15:01:22 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
opendevmeetMinutes:        https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-01-04-14.00.html15:01
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-01-04-14.00.txt15:01
opendevmeetLog:            https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-01-04-14.00.log.html15:01
*** dviroel|lunch is now known as dviroel16:06
*** dviroel is now known as dviroel|ourt21:09
*** dasm is now known as dasm|off22:14

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!