Wednesday, 2025-01-08

*** mhen_ is now known as mhen02:30
*** bauzas_ is now known as bauzas07:05
*** bauzas_ is now known as bauzas08:16
*** bauzas_ is now known as bauzas08:28
*** bauzas_ is now known as bauzas10:32
rosmaita#startmeeting cinder14:00
opendevmeetMeeting started Wed Jan  8 14:00:15 2025 UTC and is due to finish in 60 minutes.  The chair is rosmaita. 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
jungleboyjo/14:00
rosmaita#topic roll call14:00
whoami-rajatHi14:00
jungleboyjHappy New Year!14:00
flelainHello everyone!14:00
flelainHappy New Year!14:00
andrehow can I joing the meeting? in order to watch it?14:00
whoami-rajathappy new year!14:00
andrehappy new year =)14:01
eharneyhi14:01
sp-bmilanovHappy New Year! :)14:01
abishopo/14:01
abishopandre: you've joined the meeting by being here!14:01
jhorstmanno/14:01
flelainandre: weird the first time, isn't it?! But pretty efficient you'll see :)14:02
akawaio/14:02
ccokeke[m]O/14:02
andreoh previously it was video call14:02
abishopoccasionally video, but typically just irc14:03
rosmaitausually video is the last meeting of each month14:03
rosmaitahello everyone14:04
rosmaitajon will be delayed, we are having bad weather here and the schools have a delayed opening14:04
rosmaitajungleboyj will laugh but it is very cold here at -7C14:04
rosmaitahere's a link to the agenda14:05
rosmaita#link https://etherpad.opendev.org/p/cinder-epoxy-meetings14:05
rosmaita#topic announcements14:05
jungleboyjLol.  -16 C here.  :-)14:05
jungleboyjBut -7 is cold for you guys.  :-)14:05
rosmaitayes indeed!14:05
rosmaitabeen that way for a few days now14:06
jungleboyjUnfortunately, I am getting old and don't handle the cold as well as I used to.14:06
rosmaita:D14:06
rosmaitaok, that's the weather report14:06
rosmaitanot on the agenda, but welcome back everyone14:07
hemnayough14:07
* whoami-rajat shivering in 7 degrees14:07
rosmaitathis week is Epoxy Milestone 214:07
jungleboyjlol14:07
hemnaonly 21F here.  so...hot14:07
rosmaitawe're supposed to release os-brick so that other teams can start working with any Epoxy changes we have14:07
rosmaitahemna: 18F here last i checked, which is weird since i am farther south than you14:08
rosmaitaweird for the northern hemisphere, i guess14:08
hemnabut you are in the "mountains"14:08
vdhakadhi14:08
rosmaitagood point14:08
* sp-bmilanov has a question about the os-brick release, but that's in the agenda in the reviews section14:08
rosmaitasp-bmilanov: yes, that was one of the changes i think we should get in14:09
Vivek_Hi 14:09
rosmaitaok, so my point about os-brick release is that no functional changes have merged since the last release14:10
rosmaitawhich would make a release right now kind of pointless14:10
whoami-rajatthis is an important change required by the dell nvme-fc driver14:10
rosmaitaso i would like to identify a few key patches that it makes sense to get in there14:10
whoami-rajat#link https://review.opendev.org/c/openstack/os-brick/+/92334514:10
rosmaitawhoami-rajat: thanks14:10
rosmaitaok, lets make a list on the agenda starting at line 7514:11
MengyangZhang[m]hello, is there a link to the cinder meeting? This is my first time joining14:12
Luzio/14:12
rosmaitaMengyangZhang[m]: you are in the cinder meeting!  here is a link to the agenda: https://etherpad.opendev.org/p/cinder-epoxy-meetings14:13
rosmaitawhoami-rajat: there seems to be controversy over https://review.opendev.org/c/openstack/os-brick/+/923345 , or am i looking at the wrong patch?14:13
whoami-rajatrosmaita, simondodsley can correct me but my understanding is, Simon is asking for FCZM support and the author just wants to add basic NVME-FC support14:14
whoami-rajatnot sure what changes are required in the connector to support it, i thought FCZM is a driver specific thing but i could be wrong14:15
MengyangZhang[m]rosmaita: have we talked about my proposal of Add Burst Length Support to Cinder QoS?14:16
rosmaitaMengyangZhang[m]: not yet14:16
whoami-rajatalso the NVMe-FC support is crucial for other vendors to enable support for NVMe over FC, currently we only support -TCP and -RDMA but FC seems to be an important alternative to support14:17
whoami-rajathence the patch is important to get in IMO14:17
vdhakadwhoami-rajat +114:17
rosmaitawell, what concerns me is this comment from simon: "These changes take no account of FCZM required items like initiator_target_maps which14:18
rosmaitamakes it very difficult, if not impossible, for other vendors who do support FCZM to implement NVMe-FC based on the14:18
rosmaitaos-brick changes implemented."14:18
abishopdoes the existing patch provide a partial implemenation that can be enhances later with FCZM? Or would the existing patch need to be significantly reworked?14:18
rosmaitaabishop: this comment makes it sound like it could be added fairly easily:14:21
rosmaitahttps://review.opendev.org/c/openstack/os-brick/+/923345/comment/c020d040_4eea715d/14:21
whoami-rajati think it provides the basic infra to connect to NVMe devices via FC, surely dell has tested it with their new driver so apart from FCZM changes, it should work14:21
flelainCould we get another vendor to test it out and shares his opinion?14:22
whoami-rajati missed that comment but it does confirm my understanding of the patch14:22
whoami-rajatflelain, currently no vendor has nvme-fc driver to test it apart from dell14:23
whoami-rajatalso to vendors, does anyone use the Cinder zone manager or the zoning is configured outside of openstack deployment?14:24
rosmaitamy worry at the moment is that the patch has been sitting for 6 weeks; the community should decide whether to accept it as is, or require the changes14:24
rosmaitahemna: iirc, you were a fczm user at some point?14:25
whoami-rajatpersonally, I haven't seen any deployment using the zone manager14:25
rosmaitai haven't either14:25
jungleboyjBeen a long time since I have heard it mentioned.14:26
abishopif fczm can be added later without significantly impacting the current code then I feel we should move forward with the current patch14:27
rosmaitaabishop: ++14:27
abishop"better is the enemy of good"14:27
jungleboyj__14:27
jungleboyjOoops.  ++14:28
whoami-rajatI agree with abishop 14:28
whoami-rajati can take a look at that patch14:29
flelainsame expression in French abishop lol ++14:29
rosmaitaok, great, and i will make sure jbernard is aware of this discussion as well14:29
rosmaitaok, sorry that took so much time ... any other key os-brick patches ?14:30
rosmaitaok, thanks everyone14:31
rosmaita#topic add burst length support to cinder qos14:32
rosmaitaMengyangZhang[m]: i think that is you?14:32
MengyangZhang[m]yes14:32
himanshuhi14:34
MengyangZhang[m]The change is really on nova side and I have created a nova spec https://review.opendev.org/c/openstack/nova-specs/+/932653. It was reviewd by nova team but since it is a cross project effort, they would like to hear opinions on cinder side first. 14:34
rosmaitamy understanding is that on the cinder side, we just pass the new keys/values along as we currently do, so not much to do on our side14:35
MengyangZhang[m]Correct 14:35
rosmaitabut the nova team doesn't want to make changes unless they know that we will be passing them the new keys and values!14:36
MengyangZhang[m]Correct14:36
rosmaitaMengyangZhang[m]: do you have a cinder spec in addition to the blueprint you linked?14:37
MengyangZhang[m]And nova just pass them to libvirt really. The burst length parameters are already supported in libvirt 14:37
whoami-rajatdon't we have a restricted set of QoS settings that we allow? or any variable can be set as QoS?14:37
rosmaitai think it's restricted, probably by the request schema14:38
abishopit sounds like the question is whether cinder needs to add support for new key (names)14:38
MengyangZhang[m]rosmaita: I don't since I wasn't sure what the code change would be on cinder side14:38
rosmaitaMengyangZhang[m]: ok, basically, that's what whoami-rajat and abishop are asking, whether we need to do anything14:38
whoami-rajatalso is it just related to front-end QoS or it impacts back-end QoS as well?14:39
MengyangZhang[m]It's just related to front-end policy and I don't think there's a restriction for the keys. We have already implemented a nova patch to support setting burst length parameters in my company. The burst length parameters are just stored in connection_info field and are passed to nova. 14:41
rosmaitai think you are correct about no restriction for key names14:43
abishopI think the nova team just needs confirmation that no cinder changes are required in order to support the new keys14:43
whoami-rajatMengyangZhang[m], which cinder driver are you testing this with?14:43
MengyangZhang[m]8.3.0 i think14:45
whoami-rajatMengyangZhang[m], i mean the backend driver, RBD, netapp iscsi/fc, pure etc?14:46
whoami-rajati don't see any restriction for adding front-end qos specs to connection info14:48
whoami-rajat#link https://github.com/openstack/cinder/blob/master/cinder/volume/manager.py#L1853-L185414:48
whoami-rajatso this should work14:48
rosmaitaMengyangZhang[m]: you didn't need to patch cinder, did you?14:48
MengyangZhang[m]I need to patch nova14:49
whoami-rajatthough it's still good to document the new options on cinder side14:49
rosmaitai agree with whoami-rajat, looks like no cinder changes are needed other than documentation improvement14:49
MengyangZhang[m]* patch nova since the latest version doesn't support passing the burst length parameters to libvirt. The relevant code is here https://github.com/openstack/nova/blob/23733b7f9b0e0db774b7eccc21daa604c01b69da/nova/virt/libvirt/volume/volume.py#L6514:50
whoami-rajatyep, doesn't seem to be restricted by schema either14:50
whoami-rajat#link https://github.com/openstack/cinder/blob/master/cinder/api/schemas/qos_specs.py#L19-L3714:50
rosmaitaok, so to summarize:14:51
rosmaita1. no cinder spec required, because no changes needed14:51
rosmaita2. whoami-rajat and rosmaita will leave comments on the nova spec saying that cinder is ok with the change14:52
rosmaita3. someone should take a look at improving the cinder docs around qos specs at some point14:52
rosmaita-- end ---14:52
rosmaitasound good?14:53
jungleboyjSounds like a good plan to me.  :-)14:53
abishop++14:53
rosmaitaMengyangZhang[m]: any questions?14:53
whoami-rajatone thing i forgot to mention14:54
andreI have a question, will there be any drivers deleted during this cycle?14:54
MengyangZhang[m]That's all for me. Thanks for the review!!14:54
rosmaitawhoami-rajat: what did you forget?14:54
whoami-rajatif there are per GB options in the new spec, then it does require cinder change https://github.com/openstack/cinder/blob/master/cinder/volume/manager.py#L1841-L185114:54
whoami-rajatMengyangZhang[m], can you confirm if that's the case or not? ^14:55
MengyangZhang[m]We don't touch the per GB options14:55
MengyangZhang[m]and this is to set the burst length 14:56
whoami-rajatack, then we are good14:56
rosmaitagreat!14:56
MengyangZhang[m]Thank you all!14:57
andre I have a question, will there be any drivers deleted during this cycle?14:57
rosmaitanot sure, that would be a question for the PTL ... we do have several deprecated drivers, though, that would be eligible to be removed14:58
rosmaitaand we probably should take a look at the CI results and deprecate some more drivers that aren't responding14:58
rosmaita#link http://cinderstats.ivehearditbothways.com/14:59
whoami-rajatrosmaita, regarding the os-brick release, isn't it during R-6 (Feb 17 - Feb 21) for the non-client release14:59
LuziI just want to give a heads up, mhen and i each have maybe 2 hours/week from now on to help working on image encryption and volume type metadata - so we will be able to address smaller review comments, but no big changes.14:59
andrewhen will it happen? My CI is broken so I would like to know how much time I have to fix it14:59
rosmaitawhoami-rajat: yes, that's the Epoxy release ... the one tomorrow is just so that other projects that use os-brick don't get surprises14:59
rosmaitaLuzi: thanks, noted15:00
rosmaitaandre: looking15:00
whoami-rajatrosmaita, ack, thanks15:00
whoami-rajatalso not sure about the spec deadline but projects keep it at M-215:00
rosmaitayes, nova spec freeze is this week15:01
abishopandre: I think your driver is safe because we know you're working on fixing CI. It's the abandoned drivers that we worry about15:01
rosmaitaandre: which driver are you working on ?15:01
whoami-rajatasking because I've a cinder spec up for review :D15:02
whoami-rajat#link https://review.opendev.org/c/openstack/cinder-specs/+/93158115:02
andrerosmaita: https://wiki.openstack.org/wiki/ThirdPartySystems/Open-E_CI15:02
abishop#link https://review.opendev.org/c/openstack/cinder-specs/+/937808 is mine15:02
rosmaitaandre: ok, what abishop says is correct, plus we will give advance notice, probably at the midcycle meeting15:03
andreabishop: yes, but things can happen, it is better not to leave to 'chance'15:03
andrerosmaita: thanks, I will work on figuring things out15:04
rosmaitasounds good!15:04
rosmaitawe are over time ... thanks for attending everyone, please prioritize reviewing specs (since i think the freeze is this week for cinder too)15:04
rosmaitaand don't forget the list of review requests on the agenda15:04
sp-bmilanovandre: I don't see you in #openstack-cinder, let me know if you have issues with your CI15:04
rosmaitasp-bmilanov: thanks for volunteering!15:05
sp-bmilanovrosmaita: :)15:05
rosmaitaandre: #openstack-cinder is the channel to discuss cinder outside of meeting times15:05
rosmaita#endmeeting15:05
opendevmeetMeeting ended Wed Jan  8 15:05:50 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:05
opendevmeetMinutes:        https://meetings.opendev.org/meetings/cinder/2025/cinder.2025-01-08-14.00.html15:05
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/cinder/2025/cinder.2025-01-08-14.00.txt15:05
opendevmeetLog:            https://meetings.opendev.org/meetings/cinder/2025/cinder.2025-01-08-14.00.log.html15:05
andresp-bmilanov: sure, I will join cinder chat and contact you there15:05
whoami-rajatthanks!15:06
sp-bmilanovthank you!15:06
*** tmazur is now known as tovchinn15:51
*** tovchinnikova is now known as tmazur17:59

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