Thursday, 2024-06-27

*** bauzas_ is now known as bauzas05:13
*** bauzas_ is now known as bauzas06:57
*** bauzas_ is now known as bauzas09:42
*** bauzas_ is now known as bauzas09:50
*** bauzas_ is now known as bauzas11:21
carloss#startmeeting manila15:00
opendevmeetMeeting started Thu Jun 27 15:00:21 2024 UTC and is due to finish in 60 minutes.  The chair is carloss. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
opendevmeetThe meeting name has been set to 'manila'15:00
haixino/15:00
carlosscourtesy ping: dviroel vhari gouthamr carthaca msaravan pulluri ashrodri15:00
vhario/15:00
carthacahi15:00
gireeshhi15:01
msaravanhi15:01
gouthamrhello o/15:01
jayaanandhi15:02
ashrodrio/15:03
chuanmhi15:03
ccokeke[m]Hello15:04
carlosso/ hello everyone! good quorum15:04
carlosslet's get started15:04
carlossour meeting agenda for today:15:04
carloss#link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting15:04
carlossfirst up15:05
carloss#topic Announcements15:05
carlossSchedule and Deadlines15:05
carloss#link https://releases.openstack.org/dalmatian/schedule.html (Dalmatian release schedule)15:05
carlossThis is our spec freeze week15:06
carlossWe are currently targeting two specs for this deadline15:06
carlossthank you everyone for providing feedback on the specs!15:06
carlossI think we are getting close, but we still need to close some details on the two specifications15:07
carlossAdd spec lite for resource metadata backend operations15:08
carloss#link https://review.opendev.org/c/openstack/manila-specs/+/91659515:08
carlossand15:08
carlossAdd spec for ensure shares15:08
carloss#link https://review.opendev.org/c/openstack/manila-specs/+/91548015:08
carlossin case we can't hash out all of the details over this week, update and merge the specs15:09
carlosswe can have a one week extension15:09
carlossthat's all I had on the spec freeze deadline15:10
carlossalso, according to our first bugsquash event for this release is happening in two weeks15:11
carlossit will happen in the week of Jul 08 to Jul 1215:12
carlossdo you have any considerations to share on the dates? if a majority of us won't be able to spend the time in that week, we can discuss new dates close to this one15:12
carlossI think we can follow the same format as before: using a shorter contribution period, i.e. starting on Wednesday and ending on a Friday15:13
carlossany suggestions? thoughts?15:14
carlosstaking silence as no15:15
carlosswe will discuss it again in the next meeting15:16
carlossand the last announcement I'd like to share:15:16
carlossthe release naming process is open!15:16
gouthamr(next week's meeting is a holiday in the US)15:17
carlossoh, maybe we can discuss this in openstack-manila earlier then?15:18
carlossand send the email with at least 1 week notice15:18
gouthamr++15:18
carlossgouthamr: thanks15:18
carlossso on the release naming process: you might have received this email: 2025.1 E OpenStack Release Naming Poll15:18
carlossplease make your vote count15:19
carlossand help us chose what is going to be the next release name15:19
carloss#link https://civs1.civs.us/cgi-bin/results.pl?id=E_d8469898c60545f2 (Voting poll results)15:19
carlosscurrent leader is Epoxy, but Ermine is very close15:20
* carloss thinks Ermine is as close as we can get from a Zorilla :p15:20
carlossso please participate in the voting process :)15:20
carlossthat's all I had for announcements. Do you have something you'd like to share?15:21
carlosstaking silence as no...15:22
carloss#topic Review Focus15:22
carloss#link https://etherpad.opendev.org/p/manila-dalmatian-review-focus (Dalmatian review focus etherpad)15:22
carlossso as I said, this is spec freeze week, and we have some specs waiting to be merged15:23
carlossI think both are fine in terms of people reviewing15:23
carlossis there any concern that showed up on the reviews and you would like to bring up in this meeting?15:23
carlossalright15:26
carlosslet's try to keep up with the reviews in the specs and aim to merge them this week15:27
carlossif we can't, then I think merging them by the end of the next week would not be that bad15:27
carlossis there another change you'd like to get some reviewers attention?15:28
carloss#topic Bug Triage (vhari)15:29
carloss#link https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad)15:29
vharity carloss :)15:29
carlossnp15:30
carlossthankfully launchpad is working today15:30
vhariso all recent manila bugs are in progress - thanks to all contributors :)15:30
vhariack15:30
vhari#link https://bugs.launchpad.net/python-manilaclient/+bug/206863115:30
vharilooking for minor triage15:31
vharimaybe a good low-hanging-fruit 15:34
carlossnice use case, thanks for the bug report carthaca 15:35
carlossthis will require some changes in the API, but I think they are not major changes15:35
carlossso +1 for low-hanging fruit15:35
carlossin reality, I think this already works if we specify source share server id among the filters15:35
carthacaAPI changes are not required for that one, this is client only ;)15:36
carlossyeah15:36
carloss#link https://github.com/openstack/manila/blob/master/manila/api/v1/share_servers.py#L7415:36
carlossthis ^ should get us covered15:36
carlossis there anyone willing to give this fix a try?15:37
carlosslikely a good candidate for bugsquash too :)15:37
vharicarloss++15:37
vhariif anyone is interested pls assign the bug to yourself :)15:39
carlossso prio can be low, as it is an RFE, we can target it to m-315:39
vhariack15:39
vharijumping to next bug https://bugs.launchpad.net/python-manilaclient/+bug/206873215:39
carlosshmm, interesting15:43
* carloss looks at the code15:43
carthacaThat one is about a very interesting API, because the ID of the share server you can specify in the url is an ID of an object that can already be gone xD15:43
carlossyeah, a bit weird to think in that sense15:46
carlossI think this is happening in the CLI because of this: https://github.com/openstack/python-manilaclient/blob/85f21732176ed6218e4b8b64ac3261dd40f54c7a/manilaclient/osc/v2/share_servers.py#L53915:46
carlosswe are trying to look up the share server before we send the request15:47
carlosswhich makes sense when the share server still exists, but doesn't when the migration was successful15:47
carlossand the former share server was deleted15:47
carloss> yeah, a bit weird to think in that sense15:49
carlossI mean, the operation sounds confusing, but I think that's the expected behavior at the end15:49
carlossxD15:49
carlossiirc the get progress works for both source and destination15:50
carlossin this case, I think we would need to:15:50
carloss- try to get the share server that was specified15:51
carloss- if not found, we send a request to get share servers and filter by the source share server ID15:51
carloss- and then send the request to Manila using the destination share server15:51
carlossit will add a couple more steps for the OSC to perform and the operation can end up taking some seconds, but I think it would work15:52
carloss> - if not found, we send a request to get share servers and filter by the source share server ID15:52
carlossif none was found, then we just say the share server wasn't found15:52
carlosscarthaca: wdyt?15:52
carloss> iirc the get progress works for both source and destination15:53
carlossI meant you can specify either the source or the destination share server id in the request, and it should work just fine15:53
carlosslemme double check that15:53
carthacathe migration get progress API works with the source share server id, no need to do additional calls, I would say15:53
carlossyeah... I was confused because I remember we at least had the discussion of trying to make the get progress call work with both source and destination share server ids15:56
carlossso this could and could not be a low hanging fruit. I'd say we can try dropping the share server lookup and sending the request directly to Manila15:57
carlossthe share/api is handling that just fine15:57
carlossso I'd say this is also a low hanging fruit, and we can target this to the client release milestone15:58
carlosscarthaca: is there anyone from SAP willing to work on this?15:58
carlossif not, we can try to find volunteers or bringing this up at the bugsquash too15:59
carlosstime check :)16:00
carthacasorry, I don't have volunteers right now16:00
carlosscarthaca: no worries16:00
carlosswe can look for people that can fix the bug16:00
carlossthanks for the bug report16:00
carlossvhari: thank you for working on the list of bugs for this week16:00
vhariyw carloss 16:01
carlosslet's get back to #openstack-manila16:01
carloss#endmeeting16:01
opendevmeetMeeting ended Thu Jun 27 16:01:24 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
opendevmeetMinutes:        https://meetings.opendev.org/meetings/manila/2024/manila.2024-06-27-15.00.html16:01
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/manila/2024/manila.2024-06-27-15.00.txt16:01
opendevmeetLog:            https://meetings.opendev.org/meetings/manila/2024/manila.2024-06-27-15.00.log.html16:01
*** bauzas_ is now known as bauzas17:13
*** bauzas_ is now known as bauzas18:13
*** bauzas_ is now known as bauzas20:58

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