Wednesday, 2023-12-20

sp-bmilanovo/14:00
whoami-rajat#startmeeting cinder14:00
opendevmeetMeeting started Wed Dec 20 14:00:53 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
simondodsleyo/14:01
rosmaitao/14:02
akawaio/14:02
whoami-rajat#link https://etherpad.opendev.org/p/cinder-caracal-meetings14:02
whoami-rajatvery few people around today14:03
whoami-rajatwhich gives a good seg-way to our first announcement14:04
whoami-rajat#topic announcement14:04
whoami-rajatfirst, Canceling next week's meeting (27 December)14:04
whoami-rajatsince it's Year end break for many team members, we will be canceling next week's meeting14:04
whoami-rajati will send a mail after the meeting to ML14:04
whoami-rajatnext, Release stable branches14:04
whoami-rajat#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/EK2OQUO26ITYPYFYIVFSYM5CR2TVCZJL/14:05
tkajinamo/14:05
whoami-rajatit's been some time we entered 2024.1 development cycle14:05
whoami-rajati think it's a good time to EM yoga at this point and release other stable branches14:05
whoami-rajati will talk to Jon regarding this14:05
whoami-rajatnext, Python 3.12 issues and classes of bugs14:06
whoami-rajat#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/6QRQTJQF3KCJDYEYN6BVTUMFGXU7DTHW/14:06
whoami-rajatso someone ran UTs with py3.12 in debian and found a bunch of failures all around openstack14:06
whoami-rajatThere are two bugs related to Cinder14:06
whoami-rajathttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=103105714:06
whoami-rajathttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=99331114:06
whoami-rajatthe full list is here14:07
whoami-rajat#link https://bugs.debian.org/cgi-bin/pkgreport.cgi?which=maint&data=team%2Bopenstack%40tracker.debian.org&archive=no&raw=yes&bug-rev=yes&pend-exc=fixed&pend-exc=done14:07
whoami-rajati guess we have time so we will deal with it after the break when the team is back14:07
whoami-rajatnext, Upcoming Deadlines & Dates14:07
whoami-rajatCinder spec freeze: December 22nd, 202314:07
whoami-rajatCaracal-2 Milestone: January 11th, 202414:07
* jungleboyj is lurking14:07
whoami-rajatthere is one spec that was discussed as a potential one for this cycle14:08
whoami-rajat#link https://review.opendev.org/c/openstack/cinder-specs/+/86260114:08
whoami-rajatsadly in the recent update, no review comments were addressed so I've left a -114:09
whoami-rajatthere is a lot to address actually, 24 comments, I'm not sure if it will make it in time (in 2 days)14:09
whoami-rajatbut let's see14:09
whoami-rajatokay, final announcement for today14:10
whoami-rajatcinderlib status14:10
whoami-rajatand i think it's added by rosmaita 14:10
rosmaitayes, sorry i have not filled in the info14:10
rosmaitafirst thing is that the governance patch has merged, so we are OK stopping cinderlib development14:10
rosmaitanext thing is to merge some patches that clean things up14:11
rosmaitahttps://review.opendev.org/q/topic:%22deprecate-cinderlib%2214:11
rosmaitai will try to explain what's happening with those, because you can see they are all over the place14:11
rosmaitai think the most important ones right now are these:14:12
rosmaitapatch: https://review.opendev.org/c/openstack/cinder/+/90326314:12
rosmaitawhat: removes cinderlib testing from some jobs defined in cinder repo (but not the ones defined in cinder-tempest-plugin)14:12
rosmaitawho approves: cinder team14:12
rosmaitaand14:12
rosmaitapatch: https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/90326214:12
rosmaitawhat: stops testing cinderlib with master14:12
rosmaitawho approves: cinder team14:12
rosmaitai don't know what will happen to our gate if we delete cinderlib master before merging ^^14:13
rosmaitatechnically, we won't delete the master branch, just most of the stuff in it14:13
rosmaitathat's https://review.opendev.org/c/openstack/cinderlib/+/903264 if you are interested14:13
rosmaita903264 can't be merged until the infra team merges https://review.opendev.org/c/openstack/project-config/+/90326014:13
rosmaita903260 turns off zuul testing of cinderlib (just cinderlib) completely14:14
rosmaitaso i think what we need to do is merge https://review.opendev.org/c/openstack/cinder/+/903263 and https://review.opendev.org/c/openstack/cinder-tempest-plugin/+/903262 as soon as we can14:15
rosmaitathere isn't a dependency between the 214:15
rosmaitabut we need them both14:16
rosmaitai just did a recheck on 903262, zuul was complaining that the governance patch had not merged yet14:16
rosmaitaso hopefully it will be green14:16
whoami-rajatthanks for working on this, so from cinder side we can focus on 3 patches14:18
rosmaitaok, thanks to whoever is adding the notes in the agenda etherpad14:18
whoami-rajat1 in cinder, 1 in cinderlib and 1 in cinder-tempest-plugin14:19
tkajinamfeel free to add anything missing.14:19
tkajinam(I saw someone already did 14:19
rosmaitathe only one missing is an infra patch that handles the documentation redirection, but i don't think we need to worry about that14:19
rosmaitathat's https://review.opendev.org/c/openstack/openstack-manuals/+/90326114:20
rosmaitai need to work with the infra team to determine exactly what's needed on that one14:20
rosmaita(it has a -2 right now)14:20
rosmaitabut it doesn't impact any of the important stuff, which is getting our cinder gates in order14:21
rosmaitaok, that's all from me, i guess what would be good would be cinder-core volunteers to watch the 2 key patches14:22
rosmaitato be clear, those are:14:22
rosmaitahttps://review.opendev.org/c/openstack/cinder/+/90326314:22
rosmaitahttps://review.opendev.org/c/openstack/cinder-tempest-plugin/+/90326214:22
rosmaitaone problem is that since i'm the author, i probably shouldn't +2 my own work14:23
rosmaitabut i will be around all day today, if anyone has questions about what's going on in those patches14:24
rosmaitathe cinder one is pretty straightforward14:24
whoami-rajatI've reviewed the cinder patch but i think Gorka should also take a look (and be the second reviewer)14:24
rosmaitaand it only affects master, so cinder in the stable branches will still continue to test with cinderlib in the stable branches14:24
rosmaitathe cinder-tempest-plugin one is a little more complicated, but conceptually, it builds on stuff already in the cinder-tempest-plugin .zuul.yaml that creates a base lvm-barbican job and then creates child jobs for different branches14:26
whoami-rajatquite optimistic to mention that we will reach 9999.2 cycle14:26
rosmaita:D14:26
rosmaitai couldn't resist14:26
whoami-rajat:D14:26
tkajinamlol14:26
rosmaitaalso, we can make that change once no cinderlib stable branches are supported/unmaintained14:27
rosmaitaso around 2030 or so14:27
happystackerlol14:27
rosmaitaok, thanks everyone, that's all from me14:27
whoami-rajatthanks again rosmaita !14:28
rosmaitabtw, does anyone want a link to test RE2 expressions?14:28
rosmaita(to review the cinder-tempest-plugin patch)14:28
whoami-rajatplease go ahead14:29
rosmaitathis one seems pretty good:14:29
rosmaita#link https://www.regexplanet.com/advanced/golang/index.html14:29
rosmaitai'm pretty sure go uses RE214:30
rosmaita(at least i hope so!)14:30
whoami-rajatyeah i was confused as it said golang but looks like a good tool14:31
whoami-rajatokay moving on to topics14:32
whoami-rajat#topic Migration from Eventlet to AsyncIO14:32
whoami-rajati don't see Jon around14:32
whoami-rajati think he was planning to work on the eventlet issue14:32
whoami-rajatwe already have a community goal for that in place14:32
whoami-rajatthough I haven't gone through it14:32
whoami-rajatlet's see if we have project specific work items14:33
whoami-rajat#link https://review.opendev.org/c/openstack/governance/+/90258514:33
rosmaita(it's still under review ^^)14:33
whoami-rajatok, so Jon can take a look at that14:35
whoami-rajati think that's all for his topic?14:35
zaitcevI see a big problem with that review14:36
zaitcevIt approaches the problem by trying to highlight the issue and set a general direction.14:37
zaitcevThat's not going to yield a result14:37
zaitcevWhat we need instead is a guy to sit on the problem and deep-think about it, then implement a solution.14:37
zaitcevIt's going to happen anyway, no matter what that review says and regardless of Herve's efforts. Only we aren't helping it along, except in a most vague way by being supportive.14:38
zaitcevBut I'm not volunteering, so I continue playing in that charade by reviewing and discussing.14:39
whoami-rajatif the spec doesn't lay out a high level plan on how to tackle the issue, i see that as a problem for the person going to implement it, though i would need to go through the spec first to comment on it14:39
whoami-rajatbut thanks for looking into it zaitcev 14:40
whoami-rajati think that's all for this, moving on to next topic14:41
whoami-rajat#topic Storpool driver discussion14:41
whoami-rajatso during the midcycle, we discussed about the design of storpool reporting multiple pools under a backend14:41
whoami-rajatwhich seems to be an acceptable behavior14:41
sp-bmilanovhi all, I think Peter won't be able to make it to discuss this, but he wanted me to tell you that he says he has no objections to Rajat's suggestion of sending a second query without the host match, but for the same backend, but he is not sure exactly which cinder.db method to use for that, and he has not had the chance to try to experiment with such a second query and see whether it will help the StorPool "create a 14:42
sp-bmilanov from a Glance image" case14:42
whoami-rajatsp-bmilanov, no worries, i added the topic to share an update14:42
whoami-rajati discussed the scenario with Gorka and he agrees that reporting the cross pool cloning as a capability is a viable option14:43
whoami-rajatregarding simondodsley's concern about advertising it in the support matrix, we can remove that if storpool team is fine with it14:43
sp-bmilanovI will check with Peter14:44
whoami-rajatso we will have a capability reported by storpool driver that will allow it to perform the desired operation14:44
whoami-rajatat the same time we won't be adding it as a feature in the support matrix14:44
whoami-rajatsp-bmilanov, sure14:44
whoami-rajatthat's all from my side on this14:45
sp-bmilanovwhoami-rajat: thanks for making time for this14:45
whoami-rajatnp, thanks for working on this14:46
whoami-rajatokay, next topic14:46
whoami-rajat#topic NFS online volume extend14:46
whoami-rajatit was again added by me14:46
whoami-rajatso the author is working on adding a new API in cinder that nova will call for the nfs drivers to report success failure of extend operation from nova side14:47
whoami-rajati think we can extend the effort for nova to call the new API (extend volume completion) for all drivers14:47
whoami-rajatas this will allow us to report a user message if the extend fails on the nova side14:47
whoami-rajati will mention that in the nova review14:48
whoami-rajatbut just wanted to highlight here that it will improve our error reporting for other drivers as well14:48
whoami-rajatthat's all from my side on this one14:49
whoami-rajati guess we can move on to the next topic14:49
whoami-rajat#topic Implementation of the dedicated backup status field for cinder volumes14:49
whoami-rajatthat's added by Christian14:50
whoami-rajatbut he doesn't seem to be around14:50
whoami-rajatmaybe we can skip some topics and move on to Takashi's topic since he is around (and we've less time)14:50
whoami-rajat#topic Deprecation of VMWare drivers14:50
whoami-rajattkajinam, that's you14:50
tkajinamI wasnted to give you some updates about the global discussion.14:51
tkajinamso I started the mailing thread to ask if we can deprecate all the vmware support in multiple projects. there are some discussions going on in that thread and in short some people are interested in maintaining vmware virt driver in nova because they are using it14:51
tkajinamhowever nova team is careful about the situation and they will watch the status of the whole effort to restore CI coverage and maintain the driver for a while, even if they decide not to remove the vmware virt driver during this cycle.14:52
tkajinamI think the reasonable approach here is to anyway deprecate the driver, to warn more "hidden" users. if the situation with virt driver is recovered then we can undeprecate the volume driver as well.14:53
tkajinamnote that VMWare CI in cinder has been broken for a while. if we keep the vmware volume driver then we may need to ask these people to restore that CI as well.14:54
whoami-rajati think if the CI is broken, it makes sense to deprecate the driver irrespective of the nova support14:55
rosmaitawe should also put up a patch adding SUPPORTED = False for the driver14:56
whoami-rajatrosmaita, there is a patch already14:56
whoami-rajat#link https://review.opendev.org/c/openstack/cinder/+/90373714:56
tkajinamI've already pushed a patch to deprecate these vmware drivers and mark these unsupported14:56
tkajinamyes, that's the one14:56
rosmaitagreat!14:57
tkajinamCI failed for unrelated reasons but I'll try to get it passed. it'd be nice if we can merge this during this cycle.14:57
whoami-rajatok, thanks for working on this tkajinam , can you let me know once the CI passes and i can take a look14:57
tkajinamthanks14:57
whoami-rajatsorry for the recent gate failures, we are also struggling with it ...14:58
tkajinamand also take a look about windows deprecation patches I added to the agenda. I think we all agree with it since Winstackers has retired.14:58
tkajinamyeah, no problem.14:58
tkajinamI'll update the ml thread to hightlight again the situation of cinder CI to get some attention from people working on nova ci.14:59
whoami-rajatsounds good14:59
tkajinamthat's all from my side14:59
whoami-rajatthanks again14:59
whoami-rajatand with that we are out of time14:59
whoami-rajati will move rest of the topics to next meeting agenda14:59
whoami-rajatremember we are canceling next week's meeting on 27th December15:00
whoami-rajatso next meeting will happen on 3rd Jan 202415:00
whoami-rajatmerry christmas and a happy new year to the team!15:00
whoami-rajatsee you all next year15:00
whoami-rajat#endmeeting15:00
opendevmeetMeeting ended Wed Dec 20 15:00:40 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
opendevmeetMinutes:        https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-12-20-14.00.html15:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-12-20-14.00.txt15:00
opendevmeetLog:            https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-12-20-14.00.log.html15:00
tkajinamenjoy the holidays o/15:01
rosmaita\o15:02

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