Wednesday, 2023-06-21

whoami-rajat#startmeeting cinder14:00
opendevmeetMeeting started Wed Jun 21 14:00:13 2023 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
simondodsleyo/14:00
thiagoalvoravelo/14:00
eharneyhi14:00
enriquetasohi14:00
IPOhi14:00
felipe_rodrigueshi14:00
keerthivasansuresho/14:01
toskyhi14:01
whoami-rajat#link https://etherpad.opendev.org/p/cinder-bobcat-meetings14:02
whoami-rajathello everyone14:04
whoami-rajatand folks that are back from Vancouver PTG14:04
helenadantas[m]o/14:04
whoami-rajatlet's get started14:05
whoami-rajat#topic announcements14:05
whoami-rajatfirst, Spec freeze14:05
whoami-rajatThe deadline for spec freeze is tomorrow i.e. 22nd June14:05
whoami-rajat#link https://etherpad.opendev.org/p/cinder-2023-2-bobcat-specs14:05
nahimsouza[m]o/14:06
whoami-rajatwe only have 1 remaining spec for this cycle14:06
whoami-rajat#link https://review.opendev.org/c/openstack/cinder-specs/+/86876114:06
whoami-rajati see Christian has addressed the recent comments14:07
whoami-rajati will review the spec again14:07
whoami-rajatbut other cores, if you get some time, please take a look at the spec ^14:08
whoami-rajatsince we only have 1 day14:08
whoami-rajatwe might extend the deadline for this spec if it misses but it's always good to be on time14:08
whoami-rajatalso don't want to have conflicts during implementation since it adds a new field to the volume response14:09
whoami-rajatbetter to have the discussion complete on the spec itself14:09
whoami-rajatmoving on14:09
whoami-rajatwe have M-2 coming up in 2 weeks14:10
whoami-rajati.e. 6th July14:10
whoami-rajatwe have the driver merge deadline on M-214:10
whoami-rajat#link https://etherpad.opendev.org/p/cinder-2023-2-bobcat-drivers14:11
whoami-rajathere is the list of drivers currently under my track14:11
whoami-rajatif you are planning to propose a driver or have already proposed it, please add it to the above etherpad ^14:11
whoami-rajaton a related note, it's a good time to propose stable releases14:13
whoami-rajatjbernard doesn't seem to be around at this time but i can have a chat with him later14:13
whoami-rajat#link https://lists.openstack.org/pipermail/openstack-discuss/2023-June/034062.html14:13
whoami-rajatThierry mentioned a script that can provide list of unreleased changes14:14
whoami-rajattools/list_stable_unreleased_changes.sh14:14
whoami-rajatthat's all the announcements i had14:16
whoami-rajatlet's move to topics14:16
whoami-rajat#topic Vancouver 2023 Summit/PTG/Forum report14:17
whoami-rajat#link https://etherpad.opendev.org/p/cinder-vancouver-2023-followup14:17
whoami-rajatrosmaita wrote a great summary of the PTG14:18
whoami-rajatfor people who are not aware, we had in-person PTG in Vancouver from 13-15 June and some of the team members attended14:18
whoami-rajatyou can read through the summary but I have created a summary of the summary14:18
whoami-rajati.e. just the highlights of what rosmaita mentioned (according to me)14:19
whoami-rajatTC & Community Leaders Interaction14:19
whoami-rajatwe need to better communicate the available job troubleshooting tools that we have available14:19
whoami-rajatservices are encouraged to add sqlalchemy 2.0 jobs (as non-voting) to catch problems (and then fix them)14:19
whoami-rajatS-RBAC Operator Feedback14:19
whoami-rajatwe're sticking with only project scope for now14:19
whoami-rajatoperators would like some more default personas, but we need to get the current goal completed before thinking about these14:19
whoami-rajatglobal reader14:19
whoami-rajatL2-support-admin14:19
whoami-rajatdomain scope support14:19
whoami-rajatManaging OSC and SDK as multi-project deliverables14:20
whoami-rajatcinder-core will be added to osc-service-core and sdk-service-core as +2 (and not +W)14:20
whoami-rajatthis is really a good news, we will get to have faster code merges in osc and sdk ^14:20
whoami-rajatThe OpenStack Block Storage service ... how are we doing?14:20
whoami-rajatoperators would like multiple backup backends14:20
whoami-rajatHow do we end the Extended Maintenance "experiment"?14:21
whoami-rajatThere was agreement that the name "extended maintenance" is not accurate, and we need to come up with something different/update the docs14:21
whoami-rajatSeveral operators argued that keeping the branches available (even if CVE fixes are not merged into them) is useful for collaboration14:21
enriquetaso++14:22
whoami-rajatthough we didn't have any opposition on the ML, some operators seems to have issues with EOLing the EM branches ^14:22
IPO+14:23
enriquetaso++ to +2 to osc and sdk14:23
whoami-rajatyeah, we have been trying to get more involvement in those projects, good to see progress being made there14:24
whoami-rajati would still recommend going through Brian's summary but hopefully the information was helpful14:24
enriquetasoi will, thanks rajat14:25
whoami-rajatthanks enriquetaso 14:26
whoami-rajatthat was all for today14:26
whoami-rajatlet's move to open discussion14:26
whoami-rajat#topic open discussion14:26
zaitcevIs there a LP bug for multiple backup back-ends? I am not sure if I saw one or not.14:27
enriquetasoare you talking about https://review.opendev.org/c/openstack/cinder-specs/+/868761 zaitcev ?14:28
whoami-rajatenriquetaso, i think that is different14:29
whoami-rajatwe are referring to being able to configure multiple backup backends14:29
whoami-rajatlike we do for volume backends14:29
enriquetasooh sorry 14:29
zaitcevenriquetaso: no, unless having multiple back-ends requires the separate status. I don't think it does.14:30
whoami-rajatthe spec you referred is for allowing other operations like live migration along with backup14:30
whoami-rajatzaitcev, i remember we had discussions about it in the past, and maybe an old spec for it14:30
whoami-rajatlet me look14:30
zaitcevI seem to remember some kind of spec for the syntax... Like [backup-1] or something?14:30
whoami-rajatzaitcev, https://review.opendev.org/c/openstack/cinder-specs/+/71230114:31
IPOI'd like to sort out with Active/Active cinder cluster and allocated_capacity_gb - https://bugs.launchpad.net/cinder/+bug/1927186 - it there is some time and persons for it14:31
zaitcevwhoami-rajat: perfect, thanks. I got that. So, do we have a bug in LaunchPad to track the progress and issues of this?14:32
enriquetasoeharney, found a issue that may be related with configure multiple backup backends with ceph/rbd backup driver. Currently it's possible to select a diff backend/pool/container using the `--container` argument when creating the backup14:34
enriquetaso#link https://bugs.launchpad.net/cinder/+bug/202448414:35
eharneyhmm14:37
eharneylooks like a good thing to fix14:37
whoami-rajatif that's all for the discussion, we can end the meeting early today14:42
IPOI'd like to sort out with Active/Active cinder cluster and allocated_capacity_gb - https://bugs.launchpad.net/cinder/+bug/1927186 - it there is some time and persons for it14:42
whoami-rajatIPO, i think geguileo might be able to help in Active Active related things, though not sure if he is around since i don't see him in the meeting14:43
geguileowhoami-rajat: I'm around14:44
IPO:)14:45
whoami-rajatgreat!14:45
eharneydidn't hemna do some work that improved capacity tracking w/ multiple services running?14:45
geguileoeharney: I believe his work was around properly counting in all the missing cases14:45
geguileoThe problem with A/A is a different pain  :'-(14:46
eharneyah14:46
geguileoBasically all schedulers have different accounting, and also all the different volume services will have different numbers14:46
geguileoSo it's a literal mess14:46
IPOgeguileo: So you confirm that it is the bug and there is no some missconfuguratio, etc...14:48
whoami-rajatgeguileo, but i think IPO tried with a single scheduler but still sees issues with counting14:48
whoami-rajats/counting/allocated_capacity_gb14:48
IPOThx, rajat. Single scheduler, multiple cinder-volumes in cluster14:48
geguileowhoami-rajat: yeah, because in A/A you also have different values on the different cinder-volume nodes14:48
geguileoThe problem is that our current code does absolute accounting everywhere14:49
geguileoSo everyone thinks their value is "the right one"14:49
geguileoIt's a mess14:49
whoami-rajatgeguileo, hmm, i thought c-vol only sends the capabilities to the scheduler and scheduler caches it14:49
whoami-rajati could be wrong though14:49
geguileocinder-volume also changes those values during some operations14:49
geguileoiirc that's where hemna did changes14:50
whoami-rajatit's during host initialization IIRC14:50
IPOso looks like it is real bug... As I wrote, may be usage of memcached will help14:50
whoami-rajatbut IPO says the values get corrected during that but again it becomes inconsistent after a while14:50
IPOYes, it corrected after restart of all cinder volume14:51
IPOand than after time it go back to incorrec (even negative) values14:51
whoami-rajatyeah so I'm not sure apart from host initialization, we change the values anywhere else14:52
whoami-rajatin c-vol i mean14:53
IPOInstad of listening for RPC notifications to correct allocated_capacity_gb for each cinder volume and use memcached to share this value I think there is one way to correct it14:53
IPOless complicated... We can add one more pereodic task for recalculation of allocated_capacity_gb14:54
geguileoIPO: the problem with that approach is that we'd be adding a new service dependency14:54
IPOI even create POC with chunks of volume init code14:55
geguileoIPO does you POC make atomic modifications when cinder-volume or scheduler make changes to those values?14:56
IPONo ofcourse :) no locks and etc14:57
IPOBut it looks like better when to schedule cinder-volume service restart on pereodic basis14:58
geguileoIPO I think the whole "stats" model needs a rethink14:59
IPO++14:59
IPOBut we need to live somehow till bright future will come15:00
whoami-rajatwe're out of time15:00
whoami-rajatwe can continue discussion in #openstack-cinder15:00
whoami-rajatafter the BS meeting ofcourse15:00
whoami-rajatthanks everyone for joining15:00
whoami-rajat#endmeeting15:00
opendevmeetMeeting ended Wed Jun 21 15:00:27 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
opendevmeetMinutes:        https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-06-21-14.00.html15:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-06-21-14.00.txt15:00
opendevmeetLog:            https://meetings.opendev.org/meetings/cinder/2023/cinder.2023-06-21-14.00.log.html15:00
IPOthanks everybody !15:00
*** chuanm0 is now known as chuanm15:04
*** chuanm5 is now known as chuanm15:12
*** chuanm4 is now known as chuanm17:56

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