Wednesday, 2024-08-07

*** bauzas_ is now known as bauzas01:12
*** bauzas_ is now known as bauzas07:36
*** bauzas_ is now known as bauzas08:57
*** whoami-rajat_ is now known as whoami-rajat13:56
jbernard#startmeeting cinder14:00
opendevmeetMeeting started Wed Aug  7 14:00:50 2024 UTC and is due to finish in 60 minutes.  The chair is jbernard. 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
jbernard#topic roll call14:00
jbernardo/14:00
simondodsleyo/14:01
yuval0/14:01
akawaio/14:01
whoami-rajatHi14:01
rosmaitao/14:01
msaravanhi14:02
jbernard#link https://etherpad.opendev.org/p/cinder-dalmatian-meetings14:02
jungleboyjo/14:04
jbernardhello all, thanks for coming14:05
raghavendrathi14:05
jbernard#topic annoucements14:05
jbernardhttps://releases.openstack.org/dalmatian/schedule.html14:06
jbernardwe are fast approaching the third milestone (D-3) in a couple of weeks14:06
jbernardour midcycle is ptg is next week!14:07
jbernard#action jbernard to update the ptg etherpad14:07
whoami-rajatjust a note, I will not be around the PTG time next week14:08
whoami-rajathave a conflict with a family event during evening14:08
jbernardwhoami-rajat: ok, let us know if you need something raised or discussed14:08
whoami-rajatsure thanks jbernard 14:08
jbernardaside from the ptg, the non-client library freeze will happen on Aug 2214:09
jbernardand stable branches for those will be cut a bit before the rest of our repositories14:10
rosmaitawe need to prioritize review of os-brick patches14:10
jbernardthis means os-brick14:10
jbernardrosmaita: exactly14:10
jbernardin other words, if you have review cycles, os-brick needs some attention to make sure we get what we need14:11
jbernardthe freeze for everything else is the week following14:12
jbernardso there is much to do :)14:12
jbernardin other news, we've seen some movement in review requests from last week14:13
jbernardi tried to get to as many as I could and several were crossed off the list14:13
yuvalThanks you!14:13
jbernardthanks to everyone that reviewed14:13
whoami-rajatdo we have a list of os-brick patches that need attention? or maybe create an etherpad to track them?14:14
whoami-rajatthe open patches list seems broad14:14
whoami-rajat#link https://review.opendev.org/q/project:openstack/os-brick+status:open14:15
jbernardwhoami-rajat: not that I know of, i think that's a great idea14:15
whoami-rajatbut a lot are in merge connflict14:15
jbernardyuval: i saw your brick patch, will review today14:15
yuvalwait for it - I still have some issues14:15
yuvalbut thank you!14:15
jbernard#action jbernard to create etherpad for os-brick patch priority14:16
jbernardyuval: sure14:16
jbernardI'll send a link on the list later today14:16
jbernardthat's all I have for annoucments, things are winding down toward the release so be mindful of the schedule as we move through august14:17
jbernardas always, if you feel something is being overlooked, please reach out14:18
jbernard#topic scheduler related unite test hardening14:18
jbernardrosmaita: ^14:18
rosmaitathanks!14:18
rosmaitai was running unit tests in a weird environment recently and hit a bunch (around 284 failures) consistently14:19
rosmaitai traced it down to an issue with stevedore not locating the entry points in the cinder setup.cfg where we list the scheduler filters14:20
rosmaitawhich is not nice, but should not affect unit tests14:21
rosmaitasince the unit tests are supposed to be isolated to test the code they are designed to test, 14:21
rosmaitaanyway, i put up a series of small patches to fix this, so that the tests are isolated correctly14:21
rosmaitathey will be easy to review14:21
rosmaita(did i say they are small)14:22
rosmaitathat's basically it14:22
jbernardrosmaita: are they under a specific topic?14:23
jbernardnevermind, i see the relation chain14:23
rosmaitajust checking, yes, they are14:23
rosmaitahttps://review.opendev.org/q/topic:%22scheduler-tests%2214:23
whoami-rajatwe have festival of XS reviews next week but it's always good to even review them before that14:24
rosmaita:D14:24
yuvalopen discussion?14:26
jbernard#topic open discussion!14:27
whoami-rajatis anyone from storpool team around?14:27
whoami-rajatlooks like not14:30
whoami-rajatI had a PTL question for jbernard and probably rosmaita 14:30
whoami-rajatI wanted to backport this os-brick patch14:31
whoami-rajat#link https://review.opendev.org/c/openstack/os-brick/+/92051614:31
whoami-rajatbut it adds 2 new config options with suitable defaults14:31
whoami-rajatWe haven't allowed it in the past for Cinder but since os-brick was a library, I'm not sure14:31
whoami-rajats/was/is14:32
jungleboyjHmmm, that is an interesting one.14:32
jbernardim not personally opposed, i wonder what the rules and precedence are.14:32
jungleboyjI am trying to remember what the rules are if they are config changes.14:33
* jbernard is digging through old notes14:34
rosmaitai guess we can ask elod, but i think worrying about that is a relic from the old days before oslo.config14:34
rosmaitai mean, they have sensible defaults, so it's not like an operator needs to do anything14:35
rosmaitaand having them there allows for tuning14:35
jungleboyjRight.  And I think that adding a config to fix a bug with sensible defaults should be ok.14:35
rosmaitaotherwise, we would have to remove the options and hard-code the values14:35
rosmaitawhich would be pretty dumb, in my opinion14:35
jbernardi agree with all of that14:35
jungleboyjReading the rules it says 'no incompatible config file changes'.14:36
rosmaitathanks, jungleboyj14:36
jbernard#action whoami-rajat to run his patch by elod14:36
jbernardsounds like it will be fine thought14:36
rosmaitasounds like we are OK here14:36
jungleboyjLet's do that to be safe, but I think this should be ok.14:36
whoami-rajatthe initial patch did hardcode values but it only catered a small number of issues related to multipath, making it tune-able helps address broader issues like udev rules taking time to load14:37
jungleboyjYeah, makes sense to have that be configurable.14:38
whoami-rajatthanks jungleboyj rosmaita and jbernard for your opinions, i will propose a backport and we can run it by elod14:38
jungleboyj++14:38
jbernardanyone else? yuval - you mentioned you have issues?14:39
jbernardwe have a few more minutes if needed14:39
yuvalI want to ask14:40
yuvalif I run my setup with ACTIVE/ACTIVE14:40
yuvalthen the same setup - I want to disable the ACTIVE/ACTIVE14:40
yuvaljust removing the conf from the cinder.conf doesnt seems to do the trick14:41
jbernardcan you elaborate, what is the setup, what behaviour are you expecting, and what are you actually seeing?14:42
jbernardalso, is this a general issue, or one with your driver?  this might be better in general irc or email form, i guess it depends on how much info is needed to be exchanged - if it's a bug though - we will want to capture it14:44
yuvalI dont this its a bug just I dont fully understand how it works14:44
yuvalI am setting the "cluster" the config for cinder14:44
yuvalthen I see my cinder backend is running as a part of a cluster14:45
yuvalwith a single backend14:45
jbernardsomeone correct me if i am wrong, but to move from A/A to A/P, you would need to modify your deployment to include something like haproxy, no?14:45
yuvalI want to do some checks - afterwards run the same checks but not in a cluster 14:45
yuvalI am following this doc: https://docs.openstack.org/cinder/latest/contributor/high_availability.html14:46
yuvalbut have not see how to reverse it14:47
yuvalother than destroy my setup and re-create without the "cluster" config14:47
jbernardpersonally, i don't know - i would need to try it in devstack and see for myself14:47
simondodsleyi think the issue might be that volumes created under the cluster mode have the incorrect hostname in the DB after going back to non-cluster, so they will effectivley be unmanageable14:48
yuvalsimondodsley: thanks I will try to view the DB directly14:49
simondodsleyi guess if that is the issue, then there needs to be a process, after disabling cluster, to clean the DB with a cinde manage? Or we could just say that reversion is not supported14:50
yuvalyes I wonder if we have something like that14:51
jbernardyuval: probably not currently14:53
yuvalgot it14:53
jbernardok, last call14:54
jbernardthanks everyone!14:55
jbernard#endmeeting14:55
opendevmeetMeeting ended Wed Aug  7 14:55:09 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:55
opendevmeetMinutes:        https://meetings.opendev.org/meetings/cinder/2024/cinder.2024-08-07-14.00.html14:55
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/cinder/2024/cinder.2024-08-07-14.00.txt14:55
opendevmeetLog:            https://meetings.opendev.org/meetings/cinder/2024/cinder.2024-08-07-14.00.log.html14:55
jungleboyjThank you!14:55
yuvalThank you14:56
whoami-rajatthanks!14:57
*** bauzas_ is now known as bauzas18:15
*** bauzas_ is now known as bauzas18:26
*** bauzas_ is now known as bauzas19:36

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