Wednesday, 2024-08-21

*** bauzas_ is now known as bauzas03:51
*** bauzas_ is now known as bauzas06:34
*** bauzas_ is now known as bauzas07:34
yuvalyo13:38
jbernard#startmeeting cinder14:03
opendevmeetMeeting started Wed Aug 21 14:03:36 2024 UTC and is due to finish in 60 minutes.  The chair is jbernard. Information about MeetBot at http://wiki.debian.org/MeetBot.14:03
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:03
opendevmeetThe meeting name has been set to 'cinder'14:03
jbernard#topic roll call14:03
whoami-rajathi14:03
simondodsleyo/14:03
Luzio/14:03
jbernardo/ hello everyeone14:03
rosmaitao/14:03
akawaio/14:03
eharneyhi14:03
msaravanHi 14:03
mheno/14:04
jbernard#link https://etherpad.opendev.org/p/cinder-dalmatian-meetings14:04
jbernard#link https://releases.openstack.org/dalmatian/schedule.html14:04
yuval0/14:04
yuvalwhats the meaning: "roll call"14:05
Saio/14:06
whoami-rajati think it means attendance14:06
jbernardyuval: yes, just who's here14:08
rosmaitayes, traditionally the names of members of an organization are kept on a "roll", and the "roll call" is just asking each member to identify as present14:08
simondodsleyah - the good old days14:09
jbernardalright, welcome everyone14:09
jbernardthanks for filling out the adgenda14:09
jbernardbefore we get started,14:09
jbernardthe cycle is winding down, and reviews are one of my highest priority right now14:10
yuvalthe roll is virtual14:10
yuvalis it powered by nova?14:10
jbernardim aware of the dell powerstore and lightbits review series14:10
rosmaitaprobably!!!  :D14:10
jbernardthere are a few others, i just wanted to say that I/We are aware and working on it :)14:11
yuvalThank you jbernard more mentioning - yes we do need your review - I am available for anyone that need my review14:11
jbernardsimondodsley: your summary for the dell powerstore series (specifically the NVMe work) will be helpful, I'll ask about that in a bit14:12
jbernardok14:12
whoami-rajatI haven't been active in reviews recently but can help if we have a list of priority items somewhere14:12
yuvalI will also review nvme related14:12
jbernardwhoami-rajat: ill make one, the requests in today's adgena are a starting point14:13
jbernardwhoami-rajat: thanks14:13
whoami-rajatokay, will take a look, thanks14:13
jbernard#topic dalmatian os-brick release14:13
jbernardim not sure who added this, rosmaita maybe?14:13
rosmaitayeah, forgot to put my nick14:14
jbernardtl;dr we need a few patches merged asap for the upcoming brick release14:14
rosmaitabasically, release is supposed to happen tomorrow14:15
rosmaitathough we can sometimes stretch it by a day14:15
jbernardyes, libraries is tomorrow, clients are next week I believe14:15
rosmaitabasically, what we need to do is have people commit to reviews right now if we are going to get them into the release14:16
jbernardrosmaita: does updating requirements fix anything, or is it just something we do before a release?14:17
jbernardrosmaita: wondering if/how to prioritize14:18
rosmaitahard to say ... what happens is that we are testing in the gate with whatever upper constraints are set to, which may be quite different from what's in requirements.txt14:18
eharneyi think we only have one open brick requirements change?14:19
rosmaitait's probably not a big deal unless we are relying on a feature of a req that's not present in the minimum14:19
rosmaitaso jbernard, basically up to you14:22
jbernardok, if we can get the patches that need landing reviewed, then I'm happy to submit a patch for requirements14:23
jbernardwe can circle back post-lunch and see where we're at14:23
*** bauzas_ is now known as bauzas14:23
jbernardhow does that sound?14:24
rosmaitaso how do people feel about the image encryption password handling patch: https://review.opendev.org/c/openstack/os-brick/+/92629314:24
rosmaitai am willing to look at that right after this meeting14:25
jbernardi can too14:26
rosmaitaok, cool14:26
mhennice :)14:26
rosmaitathe other one i identified is a small change in a privsep function, but will require a careful look: 14:26
rosmaitahttps://review.opendev.org/c/openstack/os-brick/+/92229814:27
rosmaitabut we could always hold off and backport it as a bugfix14:27
rosmaitai didn't see anything else that looks key to the release14:27
rosmaitaso if anyone has a favorite os-brick patch, speak up now!14:27
whoami-rajatI'm taking a look at that change14:28
Nilesh_ThathagarHi can we get review this os-brick patch https://review.opendev.org/c/openstack/os-brick/+/916062 ?14:29
rosmaitait's isolated to a single connector, so kind of low risk ... i am willing to look at it for the release14:30
jbernardme too14:30
jbernardi added it to the list14:30
yuvalme too14:30
Nilesh_Thathagarthanks14:30
rosmaitaok, so eharney please respond to whoami-rajat's comment on https://review.opendev.org/c/openstack/os-brick/+/916737 and we can get that one moving along14:32
jbernardsimondodsley: re os-brick patches,14:32
simondodsleyyes14:32
jbernardsimondodsley: dell have a couple, i belive you've looked at14:33
jbernardlet me get the urls, one sec14:33
jbernardhttps://review.opendev.org/c/openstack/cinder/+/90713314:33
jbernardand https://review.opendev.org/c/openstack/os-brick/+/92334514:33
jbernardi believe14:33
simondodsleyyes - we discussed this last week on the call. Neither Gorka or I are happy with the lack of FCZM support14:33
jbernardsimondodsley: ok, i just wanted to make sure that's still the case, I believe the cinder patches rely on the brick patch14:34
simondodsleyI actually have an NVMe-FC test system up right now and am going to look at the os-brick side of it14:34
jbernardi might be wrong about that though, Yian was asking earlier and I want to make sure I make a accurate statement14:35
simondodsleyyes - its a pre-req14:35
jbernardsimondodsley: that's good news \o/14:35
jbernardsimondodsley: ok, thank you!14:35
jbernardwhoami-rajat: do we have a url naming standard for review priority etherpads?14:36
jbernardwhoami-rajat: i think getting the list out of the meeting minutes will help folks to focus, certainly myself14:37
jbernard#topic review requests14:38
jbernardas i mentioned, this is the current priority14:38
jbernardill make an isolated etherpad14:39
whoami-rajatjbernard, sorry got distracted with reviews, which milestone are we referring to? I think i created one for os-brick, another for M1/M2 etc14:39
jbernardwhoami-rajat: im just wondering if we have a convention, before I just make one up :)14:39
whoami-rajatoh i don't think we have one, they are temporary and just useful until the milestone14:39
whoami-rajatso anything should be good14:40
jbernardok14:40
jbernard#link https://etherpad.opendev.org/p/cinder-dalmatian-reviews14:40
jbernard^ that will be it14:40
jbernardill move our adgenda requests there14:40
jbernardplus a few others on my dashboard14:41
yuvalcan we add the etherpad to the cinder header?14:41
yuvalThe Block Storage Project | https://wiki.openstack.org/wiki/Cinder | https://tiny.cc/CinderPriorities14:41
jbernardyuval: that's a good question, i think a channel operator must do this14:42
jbernardyuval: and im am not one of those, to the best of my knowledge14:42
jbernarddoes anyone know?14:42
rosmaitai think we will have to ask the openstack-infra team14:42
yuvalthe tiny.cc goes to:14:43
yuvalforeach=%28project%3Aopenstack%2Fcinder+OR%0Aproject%3Aopenstack%2Fpython-cinderclient+OR%0Aproject%3Aopenstack%2Fpython-brick-cinderclient-ext+OR%0Aproject%3Aopenstack%2Fos-brick+OR%0Aproject%3Aopenstack%2Fcinderlib+OR%0Aproject%3Aopenstack%2Frbd-iscsi-client+OR%0Aopenstack%2Fcinder-tempest-plugin%29+status%3Aopen&title=Cinder+Priorities+Dashboard&High+Priority+Changes=label%3AReview-Priority%3D2&Priority+Changes=labe14:43
yuvall%3AReview-Priority%3D1&Blocked+Reviews=label%3AReview-Priority%3D-114:43
yuvalhttps://review.opendev.org/dashboard/?14:43
simondodsleyIf you add the meeting URL to the header it will have to be changed every cycle14:44
yuvalyes - well if its a big deal leave it14:44
jbernard#topic open discussion14:45
jbernardreviews aside, any issues or things that need to be raised, please do so14:46
yuvalI have something to say but not related to current release14:48
jbernardshoot14:48
yuvalin os-brick, file: os-brick/os_brick/privileged/__init__.py14:48
yuvalhave these 2 lines:14:48
yuvalos-brick14:48
yuvalos_brick14:48
yuvalprivileged14:48
yuval__init__.py14:48
yuvalif os.environ.get('VIRTUAL_ENV'):14:49
yuval    capabilities.append(c.CAP_DAC_READ_SEARCH)14:49
yuvalI am working with kolla and its making my life hell14:49
simondodsleylol - kolla can do that14:49
yuvalI have to change the privsep section in the kolla-ansible files for cinder and nova to add "sudo -E..." and add the "VIRTUAL_ENV" variable14:50
yuvalto all dockers14:50
eharneyit seems weird to allow DAC_READ_SEARCH in that context but not others, i wonder why we can't just generalize it14:51
yuvaladding this capability regardless to the fact that I am using a virtual env or not - is a big risk?14:52
eharneywe already give SYS_ADMIN so there's probably a good argument for just saying that we need DAC_READ_SEARCH for things to work14:52
rosmaitacheck the blame on that ... i seem to remember it being added specifically for virtual envs, maybe the commit message explains14:52
yuvalthere is acomment above:14:53
yuval# On virtual environments libraries are not owned by the Daemon user (root), so14:53
yuval# the Daemon needs the capability to bypass file read permission checks in14:53
yuval# order to dynamically load the code to run.14:53
eharneyit was added to let privsep work in a venv14:53
eharneythe implication there is that production services wouldn't be running in a venv equivalent14:54
eharneybut if you are running in kolla and it runs the service that way...14:54
yuvalkolla - running in a docker. but sometimes it will run inside the docker a venv (on dev mode) adding the variable to kolla using kolla-ansible is really not trivial14:55
yuvalanyway - next release I would be happy to dig in the issue and understand what can be done (maybe the change need to be in the kolla side)14:56
eharneyrosmaita: whoami-rajat: i left a thought for you to chew on on https://review.opendev.org/c/openstack/os-brick/+/916737  -- probably doesn't taste too good though14:57
yuvalgorka is still around?14:58
rosmaitadon't see him around today14:59
jbernardyuval: he will repond to email as well, i dont' think he's online right now14:59
jbernardthat's our time14:59
jbernardthank you everyone, happy reviewing! :)14:59
jbernard#endmeeting15:00
opendevmeetMeeting ended Wed Aug 21 15:00:04 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
opendevmeetMinutes:        https://meetings.opendev.org/meetings/cinder/2024/cinder.2024-08-21-14.03.html15:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/cinder/2024/cinder.2024-08-21-14.03.txt15:00
opendevmeetLog:            https://meetings.opendev.org/meetings/cinder/2024/cinder.2024-08-21-14.03.log.html15:00
yuvalThanks all15:00
Nilesh_ThathagarThank you everyone15:00
whoami-rajateharney, i see, yeah i didn't like the noqa part stating we are skipping some python rule, but you are right, maybe it's not that useful15:00
whoami-rajatthanks everyone15:00
whoami-rajateharney, approved15:01
*** bauzas_ is now known as bauzas18:30

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