Wednesday, 2022-12-21

« Tuesday, 2022-12-20 Index Thursday, 2022-12-22 »
*** ChanServ changes topic to "OpenStack Meetings || https://meetings.opendev.org/"00:42
*** dviroel|out is now known as dviroel11:01
whoami-rajat#startmeeting cinder14:00
opendevmeetMeeting started Wed Dec 21 14:00:08 2022 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
simondodsleyhi14:00
toskyhi14:00
harshhi14:00
nahimsouza[m]o/14:00
rosmaitao/14:00
lucasmoliveira059\o14:00
whoami-rajat#link https://etherpad.opendev.org/p/cinder-antelope-meetings14:01
enriquetasohi14:01
MounikaHi14:02
whoami-rajatgood turnout today, let's get started14:03
caiquemello[m]hi14:03
whoami-rajatbut before that, thanks rosmaita for running last week's meeting and festival of XS reviews!14:03
rosmaita:)14:03
whoami-rajat#topic announcements14:04
whoami-rajatfirst, Cinderlib Zed released!14:04
whoami-rajat#link https://review.opendev.org/c/openstack/releases/+/86450414:04
whoami-rajat#link https://pypi.org/project/cinderlib/5.0.0/14:04
simondodsleywoohoo!!14:04
whoami-rajatthanks rosmaita and everyone else for making this possible14:04
whoami-rajatwe were very close to missing it14:04
whoami-rajatright now we've already opened cinderlib for Antelope to avoid any last minute issues14:05
whoami-rajatI assume the patch is merged14:05
enriquetaso\o/14:05
whoami-rajatso we're good on this one14:05
whoami-rajatnext, Extended spec deadline to 23rd December14:06
whoami-rajat#link https://lists.openstack.org/pipermail/openstack-discuss/2022-December/031542.html14:06
whoami-rajatI've extended the spec freeze deadline to this week14:06
whoami-rajatwhich also is in 2 days14:06
whoami-rajatthere are 2 specs that are good candidates to get included14:06
whoami-rajat1) Encrypted backups14:06
whoami-rajat#link https://review.opendev.org/c/openstack/cinder-specs/+/86260114:07
whoami-rajatgeguileo, started working on it but he's on leave now and will be back next year14:07
whoami-rajatI'm hoping if anyone else is interested in taking it up and addressing the feedback?14:07
whoami-rajatChristian wanted to have this feature but not sure if he's interested to take it up, also we're pretty close to deadline14:08
whoami-rajatIf someone takes it up, we can probably extend the deadline for this one14:09
whoami-rajatbut let's see14:09
whoami-rajat2) Extend in-use FS volumes14:09
whoami-rajat#link https://review.opendev.org/c/openstack/cinder-specs/+/86671814:09
whoami-rajatkgube proposed an original spec which was abandoned based on nova feedback but he has another spec up14:10
whoami-rajatI just finished reviewing it few minutes ago14:10
whoami-rajatoverall the idea looks good, all the cases in my mind have already been mentioned there like if nova-cinder loses connectivity, we will have a os-reset-state call for it14:11
whoami-rajatand other things14:11
whoami-rajatso it looks pretty good apart from few suggestions/questions I've on the spec14:11
whoami-rajatplease review this one as this is very close14:11
whoami-rajatkgube, if you're around, can you update with the status of nova spec?14:11
kgubeyeah14:12
kgubesean mooney had some suggestions but said it would be ready to merge if I addressed them14:13
kgubeI did, but he hasn't reviewed them yet14:13
whoami-rajatok, then it looks good from nova side as well14:14
kgubeoverall feedback was good14:14
whoami-rajatcool, thanks for the update14:14
whoami-rajatthere was another feature we discussed during midcycle but there is no spec up for it so we will leave it for next cycle14:15
whoami-rajatwith that we can move to next announcement14:15
whoami-rajatnext, 2023 PTGs + Virtual Team Signup14:15
whoami-rajatWe will be having 2 PTGs: one virtual (March 27 -31, 2023) and one in-person (June 14 -15th, 2023) along with summit14:15
whoami-rajatto be honest, I'm not really sure of the purpose of second PTG14:15
whoami-rajatsince we would already have discussed everything in the first one14:15
whoami-rajatfirst one is a virtual one which we've been conducted for few cycles now14:16
whoami-rajatsecond is an in-person along with summit14:16
whoami-rajat#link https://lists.openstack.org/pipermail/openstack-discuss/2022-December/031512.html14:17
simondodsleyI get the whole "we hate Elon" thing at the moment, but forcing a Mastadon username as a mandatory field is a bit much. If anything should be mandatory, it should be your IRC handle.14:17
whoami-rajatthere are 2 registrations, 1 team and 1 individual14:17
whoami-rajatI've registered our team for virtual PTG14:17
whoami-rajatyou can register yourself for the eventbrite one, it's free and only used as a head count14:18
whoami-rajat#link https://www.eventbrite.com/e/project-teams-gathering-march-2023-tickets-48397157099714:18
enriquetasosimondodsley++14:18
whoami-rajatsimondodsley, yeah, I had issues with that as well14:18
whoami-rajatthough i just mentioned my IRC handle and got away with it but that field seems to be a problem14:18
simondodsleyI just put "."14:18
whoami-rajatthat also works14:19
simondodsleymayne we should all put "elon"14:19
whoami-rajatlol14:19
whoami-rajatthat's all i had for the announcement, let's see what they're planning for in the second PTG14:20
whoami-rajatnext, Election dates finalized14:20
whoami-rajat#link https://governance.openstack.org/election/14:21
whoami-rajatthe TC have finalized election dates for PTL and TC14:21
simondodsleyDrinks and canopes14:21
whoami-rajat:D14:21
whoami-rajatso keep a look if you've planning to nominate yourself for any of those14:21
whoami-rajatnext, Next week meeting (28th December)14:22
whoami-rajatI figured most of the people will be on year end break so asking here14:23
whoami-rajatWill enough people be around to conduct the meeting or should we cancel it?14:23
harshI will be here14:23
simondodsleyi won't14:23
rosmaitanot me14:23
MounikaI won't14:23
whoami-rajatlooks like the majority isn't going to be here and some of the people have already left14:24
rosmaita"voting with their feet"14:24
whoami-rajatso let's cancel it and meet next year directly on 4th January14:24
harshokie14:25
whoami-rajatI will send out an email regarding this14:25
whoami-rajatthat's all I had for my announcements14:25
whoami-rajatbut rosmaita has added some14:25
whoami-rajatso i will hand it over to him to mention them14:26
rosmaitajust some general info for awareness14:26
rosmaitagates start using tox 4 by default starting tomorrow14:26
rosmaita#link https://lists.zuul-ci.org/archives/list/zuul-announce@lists.zuul-ci.org/thread/3NNATSUTSIGP5FE2MDY5X2KJ5X4NB4PT/14:26
whoami-rajatfingers crossed!14:26
rosmaitai am hoping we will be ok, but some stuff is beyond our control14:26
rosmaitai will discuss more later14:27
rosmaitanext, 2023.2 release name voting open until 4 January14:27
rosmaita#link https://lists.openstack.org/pipermail/openstack-discuss/2022-December/031551.html14:27
rosmaitait's the "B" release14:27
rosmaitaso get your vote in if you have a preference14:27
rosmaitanext, zuul project to switch from tox to nox14:27
rosmaita#link https://meetings.opendev.org/irclogs/%23openstack-tc/%23openstack-tc.2022-12-20.log.html#t2022-12-20T17:29:0714:28
rosmaitathey will still support the tox role14:28
rosmaitaso theoretically it should not impact tox users14:28
rosmaitabut it could mean that we could switch to nox ourselves14:28
harshphew14:28
rosmaita(though i am certainly not going to do that!)14:28
rosmaitaand then last thing, reminder: CFP for the OpenInfra Summit Vancouver (June 13-15, 2023) ends 11 Jan 2023 at 07:59 UTC14:29
rosmaita#link https://cfp.openinfra.dev/app/vancouver-2023/19/presentations14:29
whoami-rajatclarkb has points regarding it's easier than tox but I've no idea about it, also tox is working fine (until they move to 4 tomorrow)14:30
rosmaitasome employers won't send you unless you have a presentation accepted, so there's your chance14:30
rosmaitayeah, my worry is that they may stop full-heartedly supporting tox14:30
rosmaitaso we may have to migrate eventually14:30
rosmaitabut hopefully not until the K release14:31
rosmaitaok, that's all from me14:31
whoami-rajatlol, we've enough time until K14:31
whoami-rajatthanks rosmaita for the announcements/updates14:31
whoami-rajatanyone has anything else for announcements?14:32
whoami-rajatguess not14:33
whoami-rajatlet's move to topics then14:33
whoami-rajat#topic tox 414:33
whoami-rajatrosmaita, that's you again14:33
rosmaitaok14:33
rosmaitai've got patches up that we'll need to merge real soon14:33
rosmaita(like today)14:33
rosmaita#link https://review.opendev.org/q/topic:tox-4-ready14:34
whoami-rajatisn't that always the case?14:34
rosmaitathe ones that don't have a +1 from zuul yet have passed all the jobs that use *our* tox.ini file14:34
simondodsleyThey all look pretty simple and logical to me14:34
rosmaitaso hopefully tempest is ready with working tox.ini files14:35
rosmaitayeah, there is some weirdness14:35
rosmaitaso what I did is make us use tox 414:35
rosmaitaso we are running tox 4 in the gate even if zuul isn't 14:35
rosmaitabecause tox has the ability to update itself14:35
rosmaitaanyway, i tested these the best i could locally14:36
rosmaitabut you may have different experiences14:36
rosmaitadepending on what your system python is14:36
rosmaitamine is 3.1014:36
rosmaitathat's because some of our environments just ask to use "python3"14:36
rosmaitanot that there's anything wrong with that14:36
simondodsleywell I guess us vendors will see what happens when we move to 4 but it shouldn't be too much of a hardship14:36
whoami-rajatthanks rosmaita for all the changes, I think we still have an option to keep it to tox 3 even if they upgrade to v414:37
whoami-rajatbut we need to move some time so better now14:37
rosmaitaanyway, my suggestion is to merge these, and if we get weird local problems, we can fix those later14:37
whoami-rajatsounds like a good plan14:38
whoami-rajatI will take a look but need another core to merge it14:38
enriquetaso i can review as well14:38
rosmaitathanks!14:38
whoami-rajatgreat!14:38
rosmaitai tried to be specific in the commit message about what changes are made and why14:39
rosmaitabut i won't pretend to completely understand the workings of tox14:39
rosmaitafinal point14:39
rosmaitai don't know what we're supposed to do about the stable branches14:39
rosmaitai will ask at the TC meeting later today14:40
whoami-rajati thought this was a change only for master14:40
rosmaitayes, but there was some discussion that zuul should run tox 4 for everything14:40
whoami-rajatok14:41
rosmaitayeah, i will get details later, hopefully we won't need to do that immediately14:41
whoami-rajatok, sounds good14:42
rosmaitathat's all from me14:42
whoami-rajatagain thanks for all the work14:42
whoami-rajatcool, let's move to next topic then14:42
whoami-rajat#topic SVf bug fix review14:42
whoami-rajat#link https://review.opendev.org/c/openstack/cinder/+/85312614:42
whoami-rajatharsh, that's you14:42
harshyes14:42
harshi addressed the UT comments given by rosmiata14:42
whoami-rajati remember reviewing it, maybe there were changes after that14:43
harshyes14:43
harshearlier code had a logical error in the loops14:43
whoami-rajatok this is a different one14:43
harsheven if it fixed the issues, there was a redundency, 14:43
harshyea, you reviewed the feature for flashcopy, where you gave a +1 and said that once the IBM-CI passes then you will give a +214:44
harshhttps://review.opendev.org/c/openstack/cinder/+/85236414:44
harshThe review in the etherpad is regarding mkhost failure because of incorrect IP assignment in the storage_nodes dict.14:45
harshas rosmiata asked to write a UT which will fail in the older code but will pass in the fixed code. so about 2 hours ago i pushed the UT.14:46
harshrequesting rosmiata and enriquetaso to please verify if all of their comments are now addressed.14:46
rosmaitaharsh: thanks for updating the test, that's exactly what i was looking for14:46
harshawesome.14:47
harshonce zuul is passed, please give +2's so that it can be merged as the RedHat customer is waiting on this.14:48
enriquetasothanks14:49
harshthanks rosmaita14:49
whoami-rajatgreat, looks like we're covered on this then14:50
enriquetasoI'll review again!14:50
harshyes. also whoami-rajat if you could please address the flashcopy change it would be really great : https://review.opendev.org/c/openstack/cinder/+/85236414:51
harshthanks enriquetaso :)14:51
whoami-rajatack will take another look14:51
harshthank you :)14:51
whoami-rajatnp14:51
whoami-rajatanything else on this topic?14:51
harshno thats all from my side. 14:52
whoami-rajatgreat14:52
whoami-rajatso please review the changes14:52
whoami-rajatmoving to next topic14:52
whoami-rajat#topic request core reviews of Pure driver patches14:52
whoami-rajat#link https://review.opendev.org/c/openstack/cinder/+/85506014:52
whoami-rajat#link https://review.opendev.org/c/openstack/cinder/+/86236514:52
whoami-rajatsimondodsley, that's you14:52
simondodsleyyep. still looking for those final elusive core reviews...14:53
simondodsleyit would be a nice Xmas present to get those in...14:53
simondodsleythat's all - you can move on to the next topic (after reveiwing of course...)14:54
whoami-rajatcool, reviewers please take a note of these patches ^14:54
whoami-rajatok final topic which also looks like a review request14:55
whoami-rajat#topic SVf bug fix review14:55
whoami-rajat#link https://review.opendev.org/c/openstack/cinder/+/84841814:55
whoami-rajatMounika, that's you14:55
Mounikayes14:55
MounikaGot +2 from whoami-rajat on this patch. Requesting one more review for this patch to get merge.14:55
whoami-rajatit's a pretty straightforward patch, keeping extra info in their backend stats for replication14:56
Mounikayes14:56
whoami-rajatagain, reviewers please take a look at this one as well14:57
whoami-rajatI feel I should start keeping a review request section in meetings14:57
harshyea that would be good i guess14:57
whoami-rajatok, let's start it from next year14:58
harsh:)14:58
whoami-rajatwhich is in 2 weeks14:58
Mounikaok14:58
whoami-rajatanyway, that's all the topics for today14:59
whoami-rajatand we're out of time as well15:00
whoami-rajatthanks everyone for attending15:00
whoami-rajatmerry christmas and a happy new year15:00
whoami-rajat#endmeeting15:00
opendevmeetMeeting ended Wed Dec 21 15:00:26 2022 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
opendevmeetMinutes:        https://meetings.opendev.org/meetings/cinder/2022/cinder.2022-12-21-14.00.html15:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/cinder/2022/cinder.2022-12-21-14.00.txt15:00
opendevmeetLog:            https://meetings.opendev.org/meetings/cinder/2022/cinder.2022-12-21-14.00.log.html15:00
harshthankyou everyone. have a great holiday.15:00
*** dviroel is now known as dviroel|lunch15:03
*** dviroel|lunch is now known as dviroel16:29
*** dviroel is now known as dviroel|out21:26
*** dasm is now known as dasm|off21:48
« Tuesday, 2022-12-20 Index Thursday, 2022-12-22 »

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