| yasufum | Hi, tacker team. | 08:01 |
|---|---|---|
| takahashi-tsc | hi | 08:01 |
| yasufum | #startmeeting tacker | 08:03 |
| opendevmeet | Meeting started Mon May 18 08:03:15 2026 UTC and is due to finish in 60 minutes. The chair is yasufum. Information about MeetBot at http://wiki.debian.org/MeetBot. | 08:03 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 08:03 |
| opendevmeet | The meeting name has been set to 'tacker' | 08:03 |
| yasufum | #link https://etherpad.opendev.org/p/tacker-meeting | 08:03 |
| yasufum | looks many updates today. | 08:04 |
| yasufum | Let's start from the first item. | 08:04 |
| yasufum | #topic SRBAC: removal of enforce_scope | 08:05 |
| yasufum | takahashi-san, is it from your team, or Ghanshyam? | 08:08 |
| takahashi-tsc | I do not aware of this topic, maybe from Ghanshyam. | 08:08 |
| yasufum | OK | 08:09 |
| yasufum | I wonder the proposal patch can be merged if current issue on zuul test is fixed. | 08:13 |
| yasufum | Anyway, I'd like to review it after this meeting. | 08:14 |
| yasufum | Is there any other comment on the item? | 08:14 |
| yasufum | good | 08:16 |
| yasufum | Move on to the next item. | 08:16 |
| yasufum | #topic Review requests | 08:16 |
| bertys | As you know, pipeline is failing lately | 08:17 |
| bertys | #link https://zuul.opendev.org/t/openstack/builds?project=openstack%2Ftacker&branch=master | 08:17 |
| bertys | Several attempts have been made, e.g. #link https://review.opendev.org/c/openstack/tacker/+/973588 | 08:17 |
| bertys | For this one, docs job still failing #link https://zuul.opendev.org/t/openstack/build/815632c240a14057bc380323d163b6aa | 08:18 |
| bertys | If possible, I would like to restart upstream activities, so let's try to fix pipeline ASAP | 08:18 |
| bertys | This also includes reviewing my patches e.g. https://review.opendev.org/c/openstack/tacker/+/984772 | 08:19 |
| yasufum | bertys: Thank you for the proposal. | 08:21 |
| yasufum | takahashi-san | 08:21 |
| yasufum | Do you have anything shared about the current status of recovering the zuul test? | 08:22 |
| takahashi-tsc | In my understanding, some of issues analysis are already done, but there is one remaining issue. | 08:23 |
| takahashi-tsc | Shivam, could you share your views? | 08:24 |
| shivam_ | yes | 08:24 |
| shivam_ | Three CI issues were resolved and fix has been applied in the patch: https://review.opendev.org/c/openstack/tacker/+/973588 | 08:24 |
| shivam_ | But recently, docs job also started failing.. I am currently working on to fix the tacker-docs job issue. | 08:25 |
| shivam_ | Once the fix is identified... will apply the fix in the same patch. | 08:26 |
| yasufum | OK, thanks | 08:27 |
| bertys | thanks shivam_, once done please remove WIP and add yasufum and takahashi-san as reviewers | 08:27 |
| shivam_ | sure | 08:27 |
| yasufum | Thanks. | 08:31 |
| yasufum | So, can we go on the third item? | 08:31 |
| bertys | yes please, thanks | 08:32 |
| yasufum | thx | 08:32 |
| yasufum | #topic: ETag header support gap in Tacker and response to ETSI NFV TST010 feedback | 08:32 |
| shivam_ | Recently, Tacker submitted a DP to ETSI NFV flagging that certain TST010 test cases were checking for `ETag` header in GET responses, which Tacker did not expect as per individual API descriptions in the SOL specification. | 08:33 |
| shivam_ | To which, ETSI NFV clarified in their feedback that these headers are required as per SOL 003 v5.2.1 Clause 4.8, which is a general section applicable to all APIs, covering GET, POST, PUT, and PATCH operations. | 08:34 |
| shivam_ | SOL Specification Clause 4.8 (SOL 003 v5.2.1) HTTP Conditional Requests: https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/05.02.01_60/gs_nfv-sol003v050201p.pdf | 08:34 |
| shivam_ | But tacker currently does not support 'ETag' headers in any of its API responses, meaning this is a gap in Tacker's SOL compliance. | 08:35 |
| shivam_ | I would like to hear the community's thoughts on this gap and what should be Tacker's response to ETSI NFV: | 08:35 |
| shivam_ | Should Tacker formally acknowledge the gap to ETSI NFV and commit to implementing ETag support in a future release? | 08:36 |
| shivam_ | Should Tacker also raise a request to ETSI NFV asking them to add explicit cross-references to Clause 4.8 within individual API detail clauses, to improve clarity? | 08:36 |
| shivam_ | Thank you. | 08:36 |
| YuyaKuno | Since NFV has finished Rel5 maintenance, I do not know it is make sense to raise improvement of legacy specification. | 08:38 |
| yasufum | hmm... | 08:39 |
| yasufum | IMO, introducing etag to tacker is not so bad idea. But I don't know how it's difficult to implement the feature. | 08:42 |
| yasufum | shivam: Any idea about that? | 08:42 |
| yasufum | Or any other projects in OpenStack already introduced? | 08:42 |
| shivam_ | yasufum: regarding how to implement, will need to check. | 08:43 |
| yasufum | Thanks. | 08:44 |
| yasufum | If no one negative about to introduce this feature, let's start to check impact on implementation to understand which is acceptable or not. | 08:47 |
| yasufum | Move on to the next item if nothing other comment. | 08:48 |
| yasufum | #topic Eventlet Removal activity in Tacker - current status update | 08:49 |
| shivam_ | This activity was discussed at the PTG, where it was proposed that Tacker can follow a similar approach to what Neutron and Nova have already done for Eventlet removal. | 08:49 |
| shivam_ | In the PTG discussion, community feedback was to first identify all Eventlet references and categorize them by complexity, by separating easy changes from more complex ones. | 08:50 |
| shivam_ | Additionally, KDDI also said they might be able to support eventlet removal activities and they would like to know the more concrete activity details. NTT, DCM and KDDI need such document and they might support eventlet removal activities. | 08:50 |
| shivam_ | Based on the feedback received in PTG, an analysis document is currently being prepared to list all Eventlet references in the codebase along with their purpose and how difficult they are to remove. | 08:50 |
| shivam_ | As of now, all Eventlet references in the Tacker codebase have been identified and captured in the document. | 08:51 |
| shivam_ | and the next step "documenting the purpose and usage context of each reference" is currently in progress. | 08:51 |
| shivam_ | This is the current status of Eventlet Removal activity and hopefully in next IRC, will share a detailed analysis information. | 08:52 |
| shivam_ | Thank you. | 08:52 |
| yasufum | Thank you for your great effort for the issue. | 08:53 |
| yasufum | Is there any comment? | 08:54 |
| takahashi-tsc | Shivam, will you publish yout analysis result somewhere? Is it possible? | 08:54 |
| takahashi-tsc | Because I remember that you are creating work docs. | 08:54 |
| takahashi-tsc | It might be difficult to publish. | 08:55 |
| takahashi-tsc | s/work docs/word docs/ | 08:55 |
| shivam_ | takahashi-tsc: Hmm.. will check where we can publish our analysis document and will share in IRC during next discussion. | 08:58 |
| takahashi-tsc | Thanks. I think it's better to share it with all community members. | 08:59 |
| shivam_ | ok | 08:59 |
| yasufum | It's good suggestion. Thanks. | 09:00 |
| yasufum | So, go on to the next item. | 09:01 |
| yasufum | #topic Proposal for structured Bug Triage activity in Tacker | 09:01 |
| shivam_ | This topic is a follow-up of Bug Triage topic discussed in PTG. | 09:02 |
| shivam_ | Tacker has many open bugs on Launchpad that are unowned or assigned to contributors who are no longer active, making it hard to track and resolve them. | 09:02 |
| shivam_ | To fix this, it is proposed to use the "Tacker Bugs Team" on Launchpad as a central group for bug ownership, starting with updating its membership to reflect only active contributors. | 09:03 |
| shivam_ | All existing bugs whose reporter or assignee is no longer active should be identified and randomly reassigned to current "Tacker Bugs Team" members. | 09:03 |
| shivam_ | Each member will then validate their assigned bugs to check if they are still relevant, bugs confirmed as invalid will be closed, and valid ones will be fixed or kept open with updated context. | 09:03 |
| shivam_ | The same process should apply to future bugs as well, every new bug should be assigned to a team member from the start, either by an administrator or by members themselves. | 09:04 |
| shivam_ | I would like to hear the community's thoughts on the proposed Bug Triage approach. | 09:04 |
| shivam_ | Thank you. | 09:04 |
| YuyaKuno | I agree. | 09:05 |
| yasufum | thanks | 09:06 |
| bertys | Not sure about "randomly" but please add me if needed | 09:06 |
| yasufum | It seems nothing concerns and everyone agree. | 09:08 |
| shivam_ | bertys: here "randomly" means for the old issues (whose reporter or assignee has left their respective companies), assign those bugs to members of Tacker bugs team randomly (like 2-3 bugs to one member) | 09:08 |
| shivam_ | depending upon the number of such old bugs count | 09:09 |
| shivam_ | For new bugs, the process would be either Tacker Bugs team administrator assigns newly reported bug to any member specifcally or members can also assign themselves if they want. | 09:10 |
| yasufum | thanks | 09:12 |
| yasufum | So, let's move on to the next item. | 09:13 |
| yasufum | #topic Incorrect FieldType usage in PkgmNotificationFilterV2 | 09:13 |
| shivam_ | The next three topics: Incorrect FieldType usage in PkgmNotificationFilterV2, K8s Jobs fail during Kubernetes setup due to unsupported kubeadm config API version (v1beta4) and CoreDNS pods remain Running but Not Ready causing Tacker controller-k8s CI job timeout failure | 09:14 |
| shivam_ | these are related to three CI bugs that were resolved and fix was applied. | 09:14 |
| shivam_ | I think, there is no discussion needed as fix has already been applied in the patch: https://review.opendev.org/c/openstack/tacker/+/973588 and if required, fix approach can be discussed in the gerrit itself. | 09:16 |
| shivam_ | For any detailed information regarding the root cause or fix, please see the contents on etherpad. | 09:17 |
| shivam_ | Thanks. | 09:18 |
| yasufum | OK, thanks. | 09:18 |
| yasufum | Any comment or question? | 09:18 |
| yasufum | good | 09:19 |
| takahashi-tsc | Shivam, I think other topics are only bug fix and you already show the resolution. Any discussion is required? I think it's OK to discuss on Gerrit. | 09:20 |
| shivam_ | yes.. it can be discussed on Gerrit if required. | 09:21 |
| shivam_ | thanks | 09:21 |
| yasufum | OK, thanks. | 09:21 |
| takahashi-tsc | OK, if so, I suggest to close the meeting, and would like Tacker team to just see the desciption on etherpad. Discussion will be on etherpad or gerrit. | 09:22 |
| takahashi-tsc | Because meeting time is already over... | 09:22 |
| yasufum | So, let's close this meeting if no question through the last two items for now. | 09:23 |
| yasufum | good | 09:24 |
| yasufum | Thank you for joining and discussion. Bye! | 09:24 |
| takahashi-tsc | thanks, bye | 09:24 |
| shivam_ | Thank you, bye! | 09:24 |
| yasufum | #endmeeting | 09:25 |
| opendevmeet | Meeting ended Mon May 18 09:25:18 2026 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 09:25 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/tacker/2026/tacker.2026-05-18-08.03.html | 09:25 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/tacker/2026/tacker.2026-05-18-08.03.txt | 09:25 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/tacker/2026/tacker.2026-05-18-08.03.log.html | 09:25 |
| *** haleyb|out is now known as haleyb | 16:28 | |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!