14:01:54 #startmeeting cinder 14:01:54 Meeting started Wed Apr 2 14:01:54 2025 UTC and is due to finish in 60 minutes. The chair is jbernard. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:54 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:54 The meeting name has been set to 'cinder' 14:02:01 hi 14:02:03 #topic roll call 14:02:04 o/ 14:02:05 o/ 14:02:05 o/ 14:02:06 o/ 14:02:08 hi 14:02:09 o/ 14:02:12 #link https://etherpad.opendev.org/p/cinder-flamingo-meetings 14:02:15 o/ 14:02:18 ^ new etherpad for this cycle 14:02:29 o/ 14:02:36 hi 14:02:38 Hi 14:02:43 hi 14:02:54 hi 14:05:04 o/ 14:07:30 welcome everyone 14:07:40 #topic annoucements 14:07:56 2025.1 epoxy is done 14:08:08 i would like to thank everyone that contributed 14:08:26 and helped make it a good release 14:08:43 special thanks to rosmaita, our release liason, for managing all of the hashes 14:08:50 \o/ 14:09:01 almost messed up the last one! 14:09:07 ++ 14:09:39 rosmaita: ++ 14:11:30 as a quick aside, i really enjoy working with everyone on this team, it's been a great experience 14:11:50 we now begin the 2025.2 (Flamingo) cycle 14:12:00 the PTG is next week 14:12:00 thanks for your leadership over this past cycle as well 14:12:42 Agreed. Thank you jbernard ! 14:12:57 re the PTG, we have one pressing item: 14:13:04 thanks jbernard, great to have you as PTL! 14:13:13 nova and neutron would like to have a cross-project discussion 14:13:19 #link https://bugs.launchpad.net/neutron/+bug/2102184 14:15:14 i'm all for dynamic storage QoS changes on frontend QoS 14:15:45 currently, there is a 1h slot on wednesday at 1400 14:15:56 for glance/cinder/nova 14:16:10 and another on Thursday, 1300 (1h) 14:16:19 for neutron/cinder/nova 14:16:28 i just want to make sure that works for everyone 14:16:36 what TZ is that? 14:16:41 those are UTC 14:17:00 1300 is 9am EDT (for reference) 14:17:37 Wednesady is OK for me 14:17:41 ack 14:18:07 is there a link to the Cinder PTG schedule? 14:18:11 does anyone need/want to be present for those discussion that has a conflict? 14:19:02 #link https://etherpad.opendev.org/p/apr2025-ptg-cinder 14:19:04 simondodsley: ^ 14:19:49 last call for cross-project conflicts 14:20:25 ok 14:20:32 i remember there was going to be a cross project for new location APIs 14:20:36 need to check the date/time for that 14:20:57 that may be a topic for the already scheduled slot, i need to check on that 14:21:11 #action check on location API cross-project topic 14:22:22 thanks 14:22:38 ok, great 14:23:05 ill send a mail this week with finalized time slots for us, but I expect it to match previous years 14:23:48 #topic cli coverage (simon) 14:24:10 ok - this may be covered in the upcoming PTG topic. 14:24:40 I was wondering specifically about cinder manage and unmange which don't seem to have an openstack cli equivalent 14:24:48 rosmaita: i have another meeting in 6 minutes, can you wrap us up when the discussion concludes? 14:24:55 simondodsley, i remember adding them 14:25:03 what are they then? 14:25:08 jbernard: will do 14:25:14 rosmaita: thanks 14:26:03 manage: https://review.opendev.org/c/openstack/python-openstackclient/+/895214/9 14:26:06 unmanage: https://review.opendev.org/c/openstack/python-openstackclient/+/919820/5 14:26:52 the convention is pretty odd but that's how OSC team wants it to be 14:26:59 jbernard: i think you may need to #chair me or i won't be able to end the meeting 14:27:16 ok - that's why i couldn't find them... 14:27:18 #chair 14:27:18 Current chairs: jbernard 14:27:23 #chair rosmaita 14:27:23 Current chairs: jbernard rosmaita 14:27:30 \o/ 14:28:32 thanks whoami-rajat 14:29:12 I guess I can move on to the second topic which is also mine... 14:29:16 simondodsley, np, last i checked, OSC should be in parity with cinderclient but do let me know if we missed any commands 14:29:42 so the second topic is more of a question.... 14:30:43 has anyone seen strange behavioural differences between caracal and epoxy with multipath not connecting to all targets on a backend (iSCSI specifically) even though os-brick isbeing passed multiple targets but only connects to 1? 14:31:21 i've had a couple of anecdotal reports of this 14:31:52 config files are the same for both nova and cinder in both versions 14:32:20 if this is true, it is a worrying potential os-brick regression 14:35:04 Yes, we saw that when there are multiple targets, they are not connecting to all. 14:35:05 simondodsley, do you mean in epoxy deployment, multipathing is enabled with multiple targets but there is only single path visible under the mpath device? 14:35:48 correct 14:36:27 it looks like os-brick stops connecting after the fist target connects 14:36:40 i haven't seen it myself, so this is all second-hand 14:37:33 the logs show 4 ip addresses being sent to os-brick but it only connects to one of them 14:37:47 ack, would be good to have it reported in a bug with debug logs, as i remember, the iSCSI portals are connected in parallel in different threads 14:37:58 i'm asking for that bug report to be raised 14:38:16 so even though if one connection is made, other connect calls still execute 14:38:53 is that parallelism new or was it always like that? 14:38:54 https://github.com/openstack/os-brick/blob/master/os_brick/initiator/connectors/iscsi.py#L751-L754 14:39:01 always like this 14:40:28 i'll make sure the bug report is filed. 14:40:32 Subject over - thanks 14:41:08 thanks for raising this -- sounds pretty bad if it turns out to be an actual issue 14:43:33 ok, that's all that was on the agenda 14:43:38 #topic open discussion 14:44:33 watch for jbernard's email about PTG scheduling 14:45:21 he said it will be similar to previous PTGs, so probably tuesday-thursday with friday open for followup topics 14:45:45 but make sure you check your email monday morning in case i'm wrong about that and we are meeting on monday 14:46:52 anyone else have anything to say? 14:47:18 Sounds good. 14:48:15 ok, let's close this up ... happy Epoxy day everyone! 14:48:23 #endmeeting