Thursday, 2024-11-21

*** mhen_ is now known as mhen02:25
carloss#startmeeting manila15:00
opendevmeetMeeting started Thu Nov 21 15:00:17 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
carlosscourtesy ping: dviroel vhari gouthamr carthaca msaravan pulluri ashrodri15:00
carthacahi15:00
dviroelo/15:00
vharihi15:00
msaravanhi15:00
haixino/15:01
gireeshhi15:02
ashrodrio/15:03
carlosso/ hello everyone15:05
carlossgood quorum, let's get started15:05
carlosstoday's meeting agenda:15:05
carloss#link https://wiki.openstack.org/wiki/Manila/Meetings#Next_meeting (Meeting agenda)15:05
carloss#topic Announcements15:05
carlossSchedule and deadlines15:06
carlosswe are 1 week past the epoxy-1 milestone15:06
carlossI'll be retargeting the bugs taht did't make it15:07
carlossand I finally proposed the change that adds all of the manila specific deadlines to the official schedule15:07
carloss#link https://review.opendev.org/c/openstack/releases/+/935891 (Add manila deadlines to the epoxy schedule)15:08
carlossplease take a look at this change and provide feedback15:08
carlossmost of these dates shouldn't sound like news15:09
carlossbecause we've discussed them at the ptg15:09
carlossso again: feedback is welcome15:09
carlossfollowing the proposed deadlines, spec freeze is not that far away15:09
carlossand we will need to focus on the reviews for the next couple of weeks15:10
carlossthat's all I had for announcements though. Is there something else you'd like to share with us?15:10
carloss#topic CI documentation15:12
carlossso we've had a lot of discussions in the past around $topic15:12
carlossand it's always been something I to focus really bad15:13
carlosss/I/I wanted15:13
carlossthere was a discussion in a TC meeting two weeks ago where people mentioned some issues with setting up CI systems15:14
carlossand one thing that was mentioned was the lack of documentation that we have15:14
carlossand I'm saying we but I'm referring to other projects that also require third party systems to be set up and reporting15:14
kpdevo/15:14
* carloss waves at kpdev15:15
carlossso it would be nice if we could get something started and I know there are people that have been through that process here15:15
carlossour cinder folks are currently looking at consolidating what they have and enhancing that too15:17
carlossthat would be a good thing for us too15:17
carlossI can get this started but I will definitely need some help from people that have been working with third party CI systems lately15:18
carlossfor example: msaravan and gireesh mentioned they would start looking at issues and the deployment of their CI soon15:19
carlossI believe we can benefit from their experience15:19
carlossI will start an etherpad and draft something as a starting point, but would be ideal if you get involved as well15:19
carlossthe CI setup for vastdata has been completed not that long ago too, so that's other maintainer that I can reach out to help as well15:20
carlosswe should do this collaboratively because I believe the experience from everyone will benefit any new CI setup from now on15:21
carlosshow does that sound?15:21
vhari++15:22
gireeshYes, I have deploy the zuul from scratch, I have experience around this. there is node pool issue which msaravan is working on15:24
msaravan++15:25
carlossack, thank you very much. Your knowledge will be very much appreciated15:25
carlossany other thoughts on $topic?15:26
carlosstaking silence as no15:28
carloss#topic Review Focus15:28
carloss#link https://etherpad.opendev.org/p/manila-epoxy-review-focus (Epoxy review focus etherpad)15:28
carlosstwo specs to review on this cycle so far15:29
carloss#link https://review.opendev.org/c/openstack/manila-specs/+/933558 (Add spec for share group affinity policy)15:29
carlosskpdev carthaca: thank you for sharing your thoughts on this spec15:29
carlossI intend to review it soon and I am also hoping I can get some reviewers' attention to this too15:30
haixini will review that spec.15:30
carlosshaixin: thank you very much15:30
carlossgireesh gouthamr ashrodri: can you please take a look too?15:31
carlossthe other spec that is being proposed is:15:32
carloss#link https://review.opendev.org/c/openstack/manila-specs/+/932637 (Add spec for subnet force deletion)15:32
carlossanother feature we've discussed at the PTG15:32
carlossalso needs some reviews15:32
carlosscarthaca gireesh kpdev ashrodri haixin: can you please take a look at it too?15:33
haixinsure15:33
carlosstyvm15:33
carthacaack15:33
gireeshsure15:33
kpdevack, we better add them are reviewers15:34
kpdevthem *as15:34
carlossyep15:35
carloss#link https://review.opendev.org/c/openstack/manila/+/898306 (Improve DB queries by join-loading Share model )15:37
carlossthis change has been reviewed in the past15:37
carlossso I'd encourage the reviewers to revisit it15:37
carlossdoesn't seem far to be merged15:37
carloss#link https://review.opendev.org/c/openstack/manila/+/931050 (Allow to update access rule for type 'ip')15:38
carlossone of the features being proposed15:38
carlossseems to be in a good shape15:38
carlossI'll take a look and also ask gouthamr when he's back :)15:39
* ashrodri stepped away for a bit. yes i will take a look at both specs15:40
carloss#link https://review.opendev.org/c/openstack/manila/+/929091 (Pass share network subnet metadata updates to backend drivers)15:40
carlossanother feature we've discussed and it should sound familiar to the recent share metadata updates we've introduced15:40
carlossthere are some reviewers assigned, I hope they (myself included) can take a look at this and provide feedback until next week15:41
carlossand there are several other fixes waiting for reviews in the etherpad15:42
carlossmy ask is: please proactively take a look in the fixes in the etherpad15:43
carlosswe've a lot of bugs to go through today15:44
carlossso I'd like to leave at least a bit of time for that in this meeting15:45
carlosskpdev: thanks for sending your priority list to #openstack-manila15:45
carlossI hope that helps guiding reviewers15:46
carloss#topic Bug Triage15:46
carloss#link https://etherpad.openstack.org/p/manila-bug-triage-pad-new (Bug Triage etherpad)15:46
vharity carloss .. have a couple of bugs to start with 15:46
vhari#link https://bugs.launchpad.net/manila/+bug/208826915:46
vharithere is a fix proposed  https://review.opendev.org/c/openstack/manila/+/93534815:48
carlossyep, fix looks good, I've asked for a release note now15:48
carlosswe can target it to epoxy-2 and priority can be low on this15:49
carlossbut we are very close15:49
vhariI will move the bug to in progress 15:49
carlossack, ty15:49
vhariack gr8 15:49
vharinext #link https://bugs.launchpad.net/manila/+bug/208906215:49
carlossso our nova folks also dedicated some time to test share backups alongside the virtiofs patch series15:50
carlossvirtiofs is quite close to being merge15:50
carlossmerged*15:50
carlosshowever, there are two big backup issues, and one of them we've triaged last week15:50
carlossthe other I filed this week and we can triage it15:50
carlossduring the data copy process in the generic backup approach, we remove all of the access rules of the share15:51
carlossand that will make the VM lose connectivity to the share15:51
carlosswe should avoid that15:51
carlossso the initial idea is to prevent the backup to start in case the share and its access rules are locked, because that means someone is using the share and it will be harmful if we just drop them15:52
carlossmaybe this also impacts the generic share migration approach15:52
carlossso what we can do? in the backups API, if the share or its access rules have locks, we should prevent the backup creation15:53
carlossideally we'd do it only when we know we'll use the generic backup approach, but that can leave the API request hanging15:54
carlossand we'd fall into the same issue that we've discussed last week15:54
carlosswe need an assignee for this15:54
carlossas the response might change in some cases, we need to evaluate if we'll need a new API microversion15:54
carlossanyone familiar with backups willing to fix this issue? :)15:55
vhariwhile being considered ^^ :) that's all the time we have for bugs today 15:56
vhariand back to you carloss 15:57
carlossack, tyvm vhari 15:57
carlosswe can set this to medium priority and target to epoxy-315:58
carlossjust to get some closure to the triaging part :)15:58
vharisure, will do 15:58
carlosslet's wrap up15:58
carlossthanks for participating15:58
carlosslet's get back to #openstack-manila15:59
carlosshave a great day! :D15:59
carloss#endmeeting16:00
opendevmeetMeeting ended Thu Nov 21 16:00:19 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
opendevmeetMinutes:        https://meetings.opendev.org/meetings/manila/2024/manila.2024-11-21-15.00.html16:00
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/manila/2024/manila.2024-11-21-15.00.txt16:00
opendevmeetLog:            https://meetings.opendev.org/meetings/manila/2024/manila.2024-11-21-15.00.log.html16:00

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