Wednesday, 2022-07-06

*** dviroel|out is now known as dviroel11:25
*** dasm|off is now known as dasm13:39
whoami-rajat#startmeeting cinder14:00
opendevmeetMeeting started Wed Jul  6 14:00:06 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
geguileohi! o/14:00
whoami-rajat#topic roll call14:00
eharneyhi14:00
enriquetasohi14:00
rosmaitao/14:00
felipe_rodrigueso/14:00
luizsantos[m]o/14:01
caiquemello[m]o/14:01
jungleboyjo/14:01
whoami-rajat#link https://etherpad.openstack.org/p/cinder-zed-meetings14:01
simondodsleyhi14:01
HappyStackerhi 14:01
nahimsouza[m]o/14:02
lucasmoliveira059o/14:02
whoami-rajatgood turnout today14:03
toskyhi14:03
whoami-rajatwe don't have many things on the agenda today but anyway let's get started14:04
whoami-rajat#topic announcements14:04
whoami-rajatfirst, spec freeze exception week14:04
whoami-rajatso we had spec freeze on R-15 week14:04
TusharTgitehi14:04
whoami-rajatthen we provided the time of R-14 to request a spec freeze exception14:05
whoami-rajatand this is the week where the spec freeze exception deadline is14:05
whoami-rajatthere was only one request for the quota system spec from geguileo 14:05
whoami-rajat#link https://lists.openstack.org/pipermail/openstack-discuss/2022-July/029374.html14:05
whoami-rajatso please review that spec on priority14:06
geguileosorry about the size of the spec14:06
enriquetasoack14:06
whoami-rajatno worries, verbose = good (at least for me)14:06
whoami-rajatplease review and get it merged before 8th July!14:07
HappyStackerwhat is supposed to be the merge freeze for Zed? next week also?14:07
whoami-rajatHappyStacker, you mean the feature freeze? that's R-5 milestone 314:07
whoami-rajatHappyStacker, here's the whole schedule https://releases.openstack.org/zed/schedule.html14:07
HappyStackerfor any patchset which are pending, I think yes it's feature freeze14:08
whoami-rajatso M-3 is for features and then we've time till RC-1 for bug fixes14:08
whoami-rajatmoving on then, next announcement, October 2022 PTG Dates & Registration14:10
whoami-rajatI've brought this topic up before but doing it again just to get a realistic idea of the number of people visiting14:10
whoami-rajatfrom Red Hat's perspective, it is not final but might be 3-5 people visiting14:11
simondodsleyIt clashes with 2 other conferences so I have to see which takes priority14:11
whoami-rajatok14:11
hemnaI won't be able to make it.  no travel budget14:11
jungleboyjI haven't started investigating yet but I think it is unlikely that I will be in person.14:12
simondodsleyAnsibleFest always seems to clash - Red Hat should take note of this14:12
whoami-rajatoh ok, good to know14:12
jungleboyjWow, that is a clash for sure.14:13
geguileosimondodsley: we'll pass on the feedback14:13
geguileosimondodsley: will that be a problem for you?14:13
whoami-rajatthanks for bringing it up simondodsley 14:13
simondodsleyYes - I am a senior Ansible contributor as well.14:13
geguileoouch :-(14:13
simondodsleyPlus I have an Observability conference in NYC the same week14:13
simondodsleyAll my things at the same time14:14
jungleboyjsimondodsley:  I find you very observable.  So, all good there.  ;-)14:14
simondodsleyhe he14:14
jungleboyj:-)14:14
geguileosimondodsley: at least the Observability one is not RH's fault, right?14:15
simondodsleyTrue - that is DataDog14:15
geguileoso, is anybody actually going?14:15
whoami-rajatso if not a lot of people will be there in person then we can also continue with our current method of virtual PTG14:16
whoami-rajatgeguileo, good question lol14:16
whoami-rajati think sfernand said they might send someone for cinder14:16
rosmaitawell, i don't want to go if no one is going to be there!14:16
sfernandhi folks I will be there :)14:16
simondodsleyprobably not - I think either Ansible (Chicago) or DataDog will take precedence currently14:17
simondodsleyI did go to Berlin though...14:17
rosmaitaoh, good, sfernand and I can find a conference room and zoom with the rest of the team14:17
jungleboyj:-)14:17
HappyStackerI'm too newbie to attend ;-)14:17
sfernandNahim will be with me and we will be splitting between Cinder and Manila14:18
simondodsleynever to new to attend...14:18
geguileohemna: will you be attending?14:18
hemnaI won't be able to make it.  no travel budget14:18
geguileo:-(14:19
hemnayah :( 14:19
geguileothis isn't looking too good if only NetApp and RH plan to attend for Cinder...14:19
jungleboyjgeguileo:  True.14:20
sfernandyep14:20
hemnaSAP has locked down travel currently.   Otherwise I'd be there.14:20
rosmaitano, and i really don't want to go to Columbus to have virtual meetings14:20
whoami-rajatagreed14:20
simondodsleyDamn COVID. It's been a great excuse for companies to slash travel budgets14:20
jungleboyjrosmaita: Oh come on, that sounds like a blast.  ;-)14:20
geguileorosmaita: yeah, that's why whoami-rajat is asking14:20
sfernandhahaha rosmaita I'm  already paying for the US visa so please do not give up from attending14:21
sfernand:P14:21
geguileosimondodsley: true, because "virtual meetings are the same thing"  :-(14:21
rosmaitai've been to columbus ... would rather go to Hoboken14:21
simondodsleylol - so true14:21
* jungleboyj laughs14:21
geguileosfernand: to be honest it's not looking good14:21
hemnaworse than Atlanta though?14:21
simondodsleynothing wring with Hoboken14:21
jungleboyjhemna: It is Ohio.  14:21
simondodsleyLots of good bars and restaurants in Hoboken now14:22
hemnanever been, so I have no idea.  lots of good racing there afaik14:22
rosmaitasimondodsley: ++14:22
sfernandgeguileo: are you planning to attend?14:23
whoami-rajatthanks everyone for the feedback, it is helpful to plan further for the cinder PTG14:24
whoami-rajatwhich looks likely to be not many people there for cinder14:24
rosmaitaso how does the count stand?  sounds like sfernand ?14:24
geguileosfernand: not by the looks of it, because I'm not sure RH will consider it necessary if only NetApp is going to be there14:24
geguileoI've been told by management that there is budget and that RH would be sending Cinder people14:25
whoami-rajatrosmaita, looks like it14:25
geguileobut it's going to be hard to justify the expense if it's going to be mostly redhatters14:25
sfernandgeguileo: makes sense14:26
geguileowhich sucks :-(14:26
whoami-rajatas geguileo said, it is true for most/all of the red hatters14:26
sfernandin case I'm the only Cinder folk there I could bring some content to Cinder newcomers or something14:26
sfernandI don't know14:27
whoami-rajatsfernand, that would be great, and we will conduct the virtual PTG so you can join from there as well14:27
whoami-rajatbut i will leave that planning to the future and just proceed with the feedback received14:27
rosmaitasfernand: you will get a much better internet connection in Columbus!14:27
sfernandyes that would be actually very sad14:27
sfernandto join a virtual PTG in person14:27
sfernandhaha14:27
whoami-rajatlol true14:28
HappyStackernew concept14:28
geguileoyeah, the worst of both worlds14:28
rosmaitawell, this is a bummer, i was really looking forward to seeing people again for realz14:28
geguileome too  :-(14:29
whoami-rajatso i think we're done with the discussion or anyone has anything else to add to it?14:29
rosmaitawell, on the plus side, i dont' have to go to columbus14:30
simondodsleyROFL14:30
whoami-rajat:D14:30
jungleboyjrosmaita: ++14:30
simondodsleyfeedback for the next PTG - make it in Hawaii 14:31
jungleboyjBwah ha ha!14:31
enriquetasohawaii++14:32
HappyStackera newbie in Hawaii, that's a good starting point haha14:32
geguileothat actually sound great, but unlikely14:32
simondodsleybahamas then14:32
rosmaitaor Hoboken14:32
whoami-rajatok, moving on to the next announcement else we will never finish with the agenda (sorry guys), New project added Dell EMC PowerStore Charm14:33
whoami-rajat#link https://review.opendev.org/c/openstack/governance/+/84689014:33
whoami-rajatI'm not sure how much that affects us as a project but thought it would be good to mention14:33
whoami-rajatthe upstream repo is https://github.com/nobuto-m/cinder-dell-emc-powerstore.git (which is external)14:34
simondodsleygood luck to them - i did the Pure charm14:34
whoami-rajatcool, so we've a charm repo for each driver?14:35
simondodsleyonly if the vendor decides to do one14:35
whoami-rajatok, I'm not very much familiar with the project14:35
whoami-rajatnext announcement, SRBAC goals for Zed14:36
whoami-rajat#link https://review.opendev.org/c/openstack/governance/+/84741814:36
simondodsleyits basically for Canonical OpenStack deployment using JuJu14:36
whoami-rajatack14:36
whoami-rajatso we've discussed about the RBAC work for Zed, which is not much but we've to do a bunch of cleanup in policy files14:37
whoami-rajatbut the link points to an OpenStack wide goal, so feel free to go through it14:37
whoami-rajati won't recommend until it's merged due to it's nature of constant change14:37
whoami-rajatbut yeah, there's a patch on the revised goals based on the ops feedback at berlin14:38
whoami-rajatthat's all the announcements from my side, anyone has anything else?14:39
whoami-rajatokay, moving on to topics then14:40
whoami-rajat#topic RBD backend QOS14:40
whoami-rajat#link https://lists.openstack.org/pipermail/openstack-discuss/2022-July/029403.html14:40
whoami-rajatso there a mail thread asking for reviews on a patch implementing backend QoS for RBD driver14:41
geguileoIn my opinion that didn't need a spec14:41
whoami-rajatand the author has also proposed a spec which we traditionally don't require14:41
whoami-rajatbut anyway i thought it would be good for documentation14:41
geguileoit's just a cinder base feature implementation14:41
simondodsleyit does need a BP though14:41
whoami-rajatgeguileo, yep, same thoughts14:41
geguileosimondodsley: true, I forgot to say it in my reply14:42
whoami-rajatsimondodsley, yes, they've registered one, in the introduction part of the spec14:42
geguileooh, then I didn't forget, I saw it! I saw it!14:42
whoami-rajatgeguileo, i said it in my reply that they require one, but later noticed they already have one :D14:42
simondodsleyOK - I really don't care if they want to raise a spec but I get it isn't required14:43
simondodsleyit does need your reviews addressing though whoami-rajat14:43
whoami-rajatso my point of bringing this up is it doesn't have to follow the spec deadlines and can be merged even in the exception phase, at least that are my thoughts14:44
simondodsleyagreed14:44
whoami-rajatsimondodsley, yes, i left some comments, if they can address that then we should be good14:44
whoami-rajatokay, so i don't think we've much conflict there14:45
sfernandas soon as they send a blueprint in time for the driver feature proposal deadline they should be fine, right? I would say to ask them to abandon the spec..14:45
whoami-rajatlet's see if they can revise it in time14:45
whoami-rajatsfernand, so I did abandon it since it wasn't worked upon for > 4 months but recently they brought it up and i think the spec is a good point of documentation for the backend QoS14:46
whoami-rajatbut maybe it's just me14:46
geguileowhoami-rajat: I prefer they update the RBD driver docs, though  ;-)14:47
geguileoand I noticed that our QoS docs are a bit of a mess14:47
simondodsleythat is a given 14:47
geguileowe have it split in one without anything explaining how everything works together14:47
simondodsleythe main code patch will have to have that. It is is merge conflict as well at the moment14:47
geguileosplit in 2 14:47
whoami-rajatgeguileo, yeah, i was referring to apart from driver docs, since they're already written the spec so it at least provides the reasoning for why we are introducing it14:49
whoami-rajatanyway, let's see if there's an update by Friday14:50
whoami-rajatbut the spec shouldn't stop anyone from reviewing the actual code patch14:50
whoami-rajatso i don't see any other topics, let's move to open discussion14:51
whoami-rajat#topic open discussion14:51
geguileoI have a question for driver maintainers14:53
geguileoDo any of you use 2 synchronize decorators in a single method?14:53
geguileofor example in a migration to lock on the source and on the destination?14:54
simondodsleynot in Pure that I'm aware of14:54
eharneyremotefs does14:54
geguileoeharney: thanks, I'll see if I can find it14:54
eharney(create_cloned_volume)14:55
geguileook, doesn't look like problematic14:55
geguileosince it locks on the volume id and not on host or some other storage thingy14:56
geguileoI'm asking because I've noticed a driver that can have a deadlock14:57
geguileoand I'm working on some improvements to coordination.synchronized to make it easier for drivers14:58
geguileoand wondering if this could be happening for other drivers14:58
*** dviroel is now known as dviroel|lunch14:59
whoami-rajatwe're out of time, thanks everyone for attending!15:00
sfernandcould share the line with the possible deadlock you've found15:00
whoami-rajat#endmeeting15:00
opendevmeetMeeting ended Wed Jul  6 15:00:09 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-07-06-14.00.html15:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/cinder/2022/cinder.2022-07-06-14.00.txt15:00
opendevmeetLog:            https://meetings.opendev.org/meetings/cinder/2022/cinder.2022-07-06-14.00.log.html15:00
jungleboyjThanks all!15:00
enriquetasothanks!15:00
*** dviroel|lunch is now known as dviroel16:08
*** dviroel is now known as dviroel|out20:50
*** dasm is now known as dasm|off21:36

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