*** mhen_ is now known as mhen | 02:11 | |
jbernard | #startmeeting cinder | 14:01 |
---|---|---|
opendevmeet | Meeting 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 |
opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:01 |
opendevmeet | The meeting name has been set to 'cinder' | 14:01 |
jbernard | #topic roll call | 14:01 |
jbernard | o/ | 14:01 |
whoami-rajat | hey | 14:01 |
rosmaita | o/ | 14:01 |
jbernard | this looks to be a quick one, potentially | 14:02 |
eharney | o7 | 14:02 |
nileshthathagar | o/ | 14:02 |
tosky_ | o/ | 14:02 |
msaravan | hi | 14:02 |
jbernard | hello everyone! | 14:03 |
jbernard | we're back :) | 14:04 |
harsh_ | Hello :) | 14:04 |
jbernard | #link https://etherpad.opendev.org/p/cinder-epoxy-meetings | 14:04 |
jbernard | ^ etherpad for these meetings | 14:04 |
jbernard | the agenda is quite light | 14:04 |
jbernard | #topic annoucements | 14:04 |
jbernard | not much really, | 14:04 |
jbernard | we're working our way through M1 | 14:05 |
jbernard | #link https://releases.openstack.org/epoxy/schedule.html | 14:05 |
jbernard | M2 is early January | 14:05 |
jbernard | which will come much sooner than I anticipate, based on the last few weeks | 14:05 |
akawai | o/ | 14:06 |
jbernard | I was out last week, I have much to catch up on | 14:06 |
jbernard | if you've pinged me about reviews or questions, I'm working my way though my backlog and I will get to it | 14:06 |
whoami-rajat | it would be useful to review and merge the spec before year end so the author can work on implementation before M2 | 14:06 |
whoami-rajat | #link https://review.opendev.org/c/openstack/cinder-specs/+/935347/6/ | 14:07 |
jbernard | whoami-rajat: I agree | 14:07 |
jbernard | if anyone is willing to review the dm-clone spec ^ that would be very helpful | 14:08 |
whoami-rajat | I'm willing to be one of the reviewer | 14:08 |
eharney | i'd like to look at the dm-clone spec but it'll probably be a few days before i can get to it | 14:09 |
jbernard | whoami-rajat: +1 thank you | 14:09 |
jbernard | eharney: sounds good | 14:09 |
whoami-rajat | thanks eharney and jbernard | 14:09 |
jbernard | whoami-rajat, eharney: can we plan to have a consensus for next week's meeting? | 14:09 |
jbernard | that gives a week to process and review | 14: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 |
jbernard | harsh_: great, reach out if you have questions | 14:10 |
harsh_ | jbernard , thanks :) | 14:10 |
whoami-rajat | jbernard, sure, i can provide a first round of review before next meeting | 14:11 |
jbernard | whoami-rajat: thanks, im expecting december to go quickly; if the spec looks good I think Jan will need as much time as we can provide | 14:12 |
jbernard | that's all for annoucements from me | 14:13 |
jbernard | #topic issues / feedback | 14:13 |
whoami-rajat | +1, I expect my comments to be minor since we've already seen the demo and design at PTG | 14:13 |
jbernard | generally, 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 patch | 14:14 |
jbernard | harsh_: sure | 14:14 |
harsh_ | https://review.opendev.org/c/openstack/cinder/+/929777 | 14:14 |
harsh_ | I sent out an email for this. Subject: OpenStack Cinder - Volume-ID in cinder DB | 14: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.py | 14:17 |
jbernard | harsh_: i need to read the thread more carefully, but at first glance I agree with Gorka's last response | 14:18 |
harsh_ | I agree too. | 14:18 |
jbernard | harsh_: changing the behaviour of a base object is risky, and there are a few proposed alternatives in his mail | 14: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 |
nileshthathagar | Hi All, | 14:20 |
nileshthathagar | I have one query | 14:20 |
harsh_ | If anyone has any suggestions please do reply on the email thread. | 14:20 |
nileshthathagar | I’m encountering an issue with PowerMax related to multipathing. Specifically: | 14:22 |
nileshthathagar | 1. After an HBA rescan, devices under /dev/disk/by-id are appearing with a slight delay. | 14:22 |
nileshthathagar | 2. At times, the device-mapper (dm) ID does not get assigned immediately. | 14:22 |
nileshthathagar | To address this, I’ve made the following changes: | 14:22 |
nileshthathagar | 1.Updated the existing retry mechanism in linuxscsi.wait_for_rw: Old retry value: Default. | 14:22 |
nileshthathagar | 2.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 |
jbernard | harsh_: 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 alternatives | 14:22 |
nileshthathagar | These changes have been applied to the linuxscsi.py file. | 14:23 |
nileshthathagar | Please provide your feedback on whether this approach is acceptable during code review? | 14:23 |
whoami-rajat | harsh_, 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 |
jbernard | nileshthathagar: sure, you'll want to file a bug and reference that in your patch | 14: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 |
nileshthathagar | jbernard thanks :) So is it ok to change the os-brick code? | 14:26 |
jbernard | nileshthathagar: it's certainly okay to propose a change and present your logic | 14:27 |
jbernard | nileshthathagar: it should be reviewed and possibly merged if there is agreement | 14:27 |
nileshthathagar | great thanks | 14:27 |
whoami-rajat | nileshthathagar, 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 it | 14:28 |
whoami-rajat | in fact we even wait for the multipath device to show up, not exactly sure but probably 10 seconds | 14:29 |
nileshthathagar | whoami-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-id | 14:31 |
nileshthathagar | I will msg you the whole issue. If you need more details | 14:32 |
whoami-rajat | nileshthathagar, 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/+/920516 | 14:32 |
nileshthathagar | sure will check it. thanks | 14:33 |
whoami-rajat | harsh_, ack, would be useful to have an upstream patch with your solution and ask on the thread for further assistance | 14:33 |
harsh_ | whoami-rajat sure i will upload a patch with my solution. | 14:34 |
harsh_ | Thanks :) | 14:34 |
whoami-rajat | thanks! | 14:34 |
jbernard | that's all for our agenda today, | 14:36 |
jbernard | #topic open disucussion | 14:36 |
jbernard | anything else? | 14:36 |
nileshthathagar | I am good thanks :) | 14:37 |
* jungleboyj sneaks in way too late. | 14:38 | |
jbernard | jungleboyj: perfect timing :) | 14:39 |
jungleboyj | :-) | 14:39 |
jbernard | ok, thanks everyone! | 14:40 |
jbernard | #endmeeting | 14:40 |
opendevmeet | Meeting ended Wed Dec 4 14:40:07 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:40 |
opendevmeet | Minutes: https://meetings.opendev.org/meetings/cinder/2024/cinder.2024-12-04-14.01.html | 14:40 |
opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/cinder/2024/cinder.2024-12-04-14.01.txt | 14:40 |
opendevmeet | Log: https://meetings.opendev.org/meetings/cinder/2024/cinder.2024-12-04-14.01.log.html | 14:40 |
whoami-rajat | nileshthathagar, 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 up | 14:40 |
harsh_ | Thanks everyone ! | 14:40 |
*** tosky_ is now known as tosky | 15:40 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!