08:02:52 <yasufum> #startmeeting tacker
08:02:52 <opendevmeet> Meeting started Mon Jun  1 08:02:52 2026 UTC and is due to finish in 60 minutes.  The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:02:52 <opendevmeet> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:02:52 <opendevmeet> The meeting name has been set to 'tacker'
08:03:28 <yasufum> #link https://etherpad.opendev.org/p/tacker-meeting
08:03:35 <yasufum> So, let's start the meeting.
08:04:10 <yasufum> #topic SRBAC: removal of enforce_scope
08:05:12 <yasufum> After the fix patch from Shivam,
08:05:14 <yasufum> https://review.opendev.org/c/openstack/tacker/+/973588
08:05:16 <yasufum> ,
08:05:42 <yasufum> I rebased this update to be merged.
08:06:48 <yasufum> However, it's failed because other failures happened I don't know the reason.
08:08:54 <yasufum> I've not tried to find out the cause of them, but working to fix the issue.
08:10:16 <yasufum> I'm not still sure it's only on this patch, or happend on other ones.
08:10:27 <yasufum> Any comment?
08:11:29 <shivam> yasufum-san, we have also faced the same issue on our Compliance testcase patch.
08:11:47 <yasufum> hmm
08:12:08 <shivam> I am also looking for the root cause and fix of the issue.
08:13:30 <yasufum> Any progress, or nothing yet?
08:13:32 <shivam> for k8s jobs.. intial analysis shows that it is failing during k8s vim setup due to unauthorized request for vim register
08:13:46 <yasufum> ok
08:13:51 <shivam> exact error message in logs: No details.: tacker.extensions.nfvo.VimUnauthorizedException: (403)
08:14:25 <shivam> currently.. I am trying to identify the change due to this issue started occurring.
08:15:20 <yasufum> thanks
08:16:44 <yasufum> I hope we can fix it soon.
08:17:10 <yasufum> It seems enough discussion for this topic today.
08:17:18 <yasufum> So, let's move on to the next item.
08:17:30 <yasufum> #topic Eventlet Removal activity in Tacker - follow-up update on Migration Planning
08:17:52 <shivam> This is a follow-up status update on the Eventlet Removal activity for Tacker, continuing from the previous discussion on 25/05/2026.
08:18:24 <shivam> The Etherpad page has been updated with a recommended order in which the Eventlet references should be migrated, this ordering helps avoid breaking things during the migration process.
08:18:59 <shivam> https://etherpad.opendev.org/p/tacker-eventlet-removal#L453
08:19:53 <shivam> Now that the analysis and ordering related information is updated, the next step is to decide how should the actual migration work be divided and assigned among community members?
08:20:25 <shivam> Few possible approaches are:
08:20:38 <shivam> Option 1 - By Phase: Split the work by migration phases for example, one person or group handles Phase 1, another handles Phase 2, and so on.
08:21:03 <shivam> Option 2 - By Category: Split the work by the type of Eventlet usage for example, one person handles all WSGI-related changes, another handles Monkey Patching changes, etc.
08:22:00 <shivam> These two options are just starting suggestions, I want community to share their thoughts on proposed approaches, or suggest some other different approaches that might be better.
08:22:12 <shivam> Thank you.
08:22:22 <yasufum> thanks
08:23:37 <yasufum> I'd like to hear a comment from guys already suggested to help for the issue.
08:24:10 <yasufum> Any comment?
08:24:32 <YuyaKuno> Which approach requires more wider knowledge? I guess it is better for members not to need wider knowledge to fix them.
08:27:34 <shivam> Kuno-san, I guess in both approaches... a good or basic knowledge of Eventlet references will be needed.
08:28:44 <YuyaKuno> It means that both is not big difference from knowledge perspective ?
08:28:56 <shivam> yes.
08:30:39 <yasufum> shivam: From the perspective of handling patches, do you have any suggestion?
08:31:26 <yasufum> "handling" means managing status of review for each patch.
08:32:52 <shivam> hmm... I guess patches can be submitted under one topic chain.. fox example: eventlet-removal
08:33:13 <shivam> similar was done in case of Neutron and Nova as well
08:34:16 <yasufum> thanks
08:38:35 <yasufum> IMO, it looks not so much different. Why don't we take easier way to decide each assignee?
08:44:12 <yasufum> shivam: seems no more comment.
08:46:09 <shivam> yes.. still i would like to know which approach should we proceed with?
08:47:21 <shivam> Is there any recommendation from community on the approaches for assigning tasks to community members?
08:47:30 <yasufum> It might be both are acceptable.
08:48:28 <yasufum> Although I don't have strong reason, +1 for option 2.
08:50:25 <YuyaKuno> Is there any limitation of order for step in phase ? For example, step 1, step 2, step 3 and step 4 in same phase can be developed in parallel? Or we need to follow order of steps?
08:51:30 <shivam> Kuno-san, steps in same phase can be developed in parallel
08:52:02 <shivam> but phases are in sequential. For example, phase 2 will start only once phase 1 is completed.
08:52:30 <YuyaKuno> OK, thank you. Then I also +1 for option 2 although no strong opinion.
08:53:30 <takahashi-tsc> Honestly, I also do not have any opinions. So it's OK to just decide by vote now.
08:53:36 <takahashi-tsc> So... option 2?
08:54:15 <yasufum> o/
08:56:08 <hi-koba> I also +1 for option 2, as it seems more efficient.
08:56:22 <yasufum> Thanks all.
08:59:46 <yasufum> shivam: Thank you for your contribution. Let's continue to fix eventlet removal by following option 2.
09:00:17 <shivam> Thanks all.. as we all agree for Option2. In this case, now how the need to decide how the members will be assigned the tasks. For example, members will assign themselves for the category they want to support the migration.
09:02:24 <shivam> If so.. members who want to support, can mention their names on the etherpad page itself.
09:03:30 <yasufum> agree
09:06:17 <yasufum> Any opposition?
09:07:37 <yasufum> Thank you shivam-san. Everyone looks agree your proposal.
09:07:54 <shivam> Thank you.
09:08:28 <yasufum> So, let's close this meeting it over the end of time.
09:08:39 <yasufum> Thank you for joining, bye!
09:08:53 <shivam> Thank you, Bye!
09:09:03 <YuyaKuno> bye
09:09:11 <yasufum> #endmeeting