Wednesday, 2024-12-04

*** mhen_ is now known as mhen02:11
jbernard#startmeeting cinder14:01
opendevmeetMeeting started Wed Dec  4 14:01:09 2024 UTC and is due to finish in 60 minutes.  The chair is jbernard. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
opendevmeetThe meeting name has been set to 'cinder'14:01
jbernard#topic roll call14:01
jbernardo/14:01
whoami-rajathey14:01
rosmaitao/14:01
jbernardthis looks to be a quick one, potentially14:02
eharneyo714:02
nileshthathagaro/14:02
tosky_o/14:02
msaravanhi14:02
jbernardhello everyone!14:03
jbernardwe're back :)14:04
harsh_Hello :)14:04
jbernard#link https://etherpad.opendev.org/p/cinder-epoxy-meetings14:04
jbernard^ etherpad for these meetings14:04
jbernardthe agenda is quite light14:04
jbernard#topic annoucements14:04
jbernardnot much really,14:04
jbernardwe're working our way through M114:05
jbernard#link https://releases.openstack.org/epoxy/schedule.html14:05
jbernardM2 is early January14:05
jbernardwhich will come much sooner than I anticipate, based on the last few weeks14:05
akawaio/14:06
jbernardI was out last week, I have much to catch up on14:06
jbernardif you've pinged me about reviews or questions, I'm working my way though my backlog and I will get to it14:06
whoami-rajatit would be useful to review and merge the spec before year end so the author can work on implementation before M214:06
whoami-rajat#link https://review.opendev.org/c/openstack/cinder-specs/+/935347/6/14:07
jbernardwhoami-rajat: I agree14:07
jbernardif anyone is willing to review the dm-clone spec ^ that would be very helpful14:08
whoami-rajatI'm willing to be one of the reviewer14:08
eharneyi'd like to look at the dm-clone spec but it'll probably be a few days before i can get to it14:09
jbernardwhoami-rajat: +1 thank you14:09
jbernardeharney: sounds good14:09
whoami-rajatthanks eharney and jbernard 14:09
jbernardwhoami-rajat, eharney: can we plan to have a consensus for next week's meeting?14:09
jbernardthat gives a week to process and review14:10
harsh_This spec review is new for me. I work on the cinder driver for IBM Storwize. I will try to get more details on this spec review.14:10
jbernardharsh_: great, reach out if you have questions14:10
harsh_jbernard , thanks :)14:10
whoami-rajatjbernard, sure, i can provide a first round of review before next meeting14:11
jbernardwhoami-rajat: thanks, im expecting december to go quickly; if the spec looks good I think Jan will need as much time as we can provide14:12
jbernardthat's all for annoucements from me14:13
jbernard#topic issues / feedback14:13
whoami-rajat+1, I expect my comments to be minor since we've already seen the demo and design at PTG14:13
jbernardgenerally, how are things? aside from review bandwidth, is anyone blocked on anything? anything I can help with?14:13
harsh_I have a query with on of the review patch14:14
jbernardharsh_: sure14:14
harsh_https://review.opendev.org/c/openstack/cinder/+/92977714:14
harsh_I sent out an email for this. Subject: OpenStack Cinder - Volume-ID in cinder DB14:15
harsh_I am trying to use the provider_id field to map the cinder volume object with the backend volume_ID. Doing this for the clone volumes as the two are different in my case.14:16
harsh_Because the IDs are different i have to check for the provider_id field to for every volume operation that i can perform on a clone volume. For this i suggested a change in the file: cinder/cinder/objects/volume.py14:17
jbernardharsh_: i need to read the thread more carefully, but at first glance I agree with Gorka's last response14:18
harsh_I agree too. 14:18
jbernardharsh_: changing the behaviour of a base object is risky, and there are a few proposed alternatives in his mail14:18
harsh_So i am looking for an alternative for this.14:18
harsh_I tried to add an override fucntion in cinder/volume/drivers/ibm/storwize_svc/__init__.py file but that didnt override the _volume_name() function.14:19
nileshthathagarHi All,14:20
nileshthathagarI have one query14:20
harsh_If anyone has any suggestions please do reply on the email thread.14:20
nileshthathagarI’m encountering an issue with PowerMax related to multipathing. Specifically:14:22
nileshthathagar1. After an HBA rescan, devices under /dev/disk/by-id are appearing with a slight delay.14:22
nileshthathagar2. At times, the device-mapper (dm) ID does not get assigned immediately.14:22
nileshthathagarTo address this, I’ve made the following changes:14:22
nileshthathagar1.Updated the existing retry mechanism in linuxscsi.wait_for_rw: Old retry value: Default.14:22
nileshthathagar2.New settings: retry=5 and interval=2, to handle delays with /dev/disk/by-id. Implemented a retry mechanism for device-mapper IDs: Settings: retry=5 and interval=2.14:22
jbernardharsh_: if you've implemented one of gorka's alternatives and it's not working, you could post the link and ask for guidance.  At the moment, the last message from gorka has 3 alternatives14:22
nileshthathagarThese changes have been applied to the linuxscsi.py file.14:23
nileshthathagarPlease provide your feedback on whether this approach is acceptable during code review?14:23
whoami-rajatharsh_, IIUC, the only places you will need to handle the mapping is volume create operations like create volume, create cloned volume, create volume from snapshot etc, do you need the mapping anywhere else apart from this?14:23
jbernardnileshthathagar: sure, you'll want to file a bug and reference that in your patch14:24
harsh_Yes, two of them are what i am using and they work but thats a lengthy change. I was looking to make a change which could be used to get the volume_id from provider_id field just once during driver intialization. I am also working on the decorator alternative that Gorka suggested. Will reply to the thread if that didn't workout.14:24
harsh_whoami-rajat , i need the mapping for exrend operation, group operations, attach-detach as well.14:26
nileshthathagarjbernard thanks :) So is it ok to change the os-brick code?14:26
jbernardnileshthathagar: it's certainly okay to propose a change and present your logic14:27
jbernardnileshthathagar: it should be reviewed and possibly merged if there is agreement14:27
nileshthathagargreat thanks14:27
whoami-rajatnileshthathagar, I'm not sure where you are facing the issue, firstly we scan for device symlinks in /dev/disk/by-path and not in by-id, secondly there is already a retry mechanism for it14:28
whoami-rajatin fact we even wait for the multipath device to show up, not exactly sure but probably 10 seconds14:29
nileshthathagarwhoami-rajat: yes the device is getting under /dev/disk/by-path but during multipath find it is taking time to show under /dev/disk/by-id14:31
nileshthathagarI will msg you the whole issue. If you need more details14:32
whoami-rajatnileshthathagar, can you try this patch? it's specific to the issue when multipath device takes time to become writable https://review.opendev.org/c/openstack/os-brick/+/92051614:32
nileshthathagarsure will check it. thanks14:33
whoami-rajatharsh_, ack, would be useful to have an upstream patch with your solution and ask on the thread for further assistance14:33
harsh_whoami-rajat sure i will upload a patch with my solution.14:34
harsh_Thanks :)14:34
whoami-rajatthanks!14:34
jbernardthat's all for our agenda today,14:36
jbernard#topic open disucussion14:36
jbernardanything else?14:36
nileshthathagarI am good thanks :)14:37
* jungleboyj sneaks in way too late. 14:38
jbernardjungleboyj: perfect timing :)14:39
jungleboyj:-)14:39
jbernardok, thanks everyone!14:40
jbernard#endmeeting14:40
opendevmeetMeeting ended Wed Dec  4 14:40:07 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:40
opendevmeetMinutes:        https://meetings.opendev.org/meetings/cinder/2024/cinder.2024-12-04-14.01.html14:40
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/cinder/2024/cinder.2024-12-04-14.01.txt14:40
opendevmeetLog:            https://meetings.opendev.org/meetings/cinder/2024/cinder.2024-12-04-14.01.log.html14:40
whoami-rajatnileshthathagar, we can continue the discussion elsewhere but wait_for_rw might not be the right place for retries if your mpath device takes time to show up14:40
harsh_Thanks everyone !14:40
*** tosky_ is now known as tosky15:40

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