Hi all, Here is a summary of Tacker's vPTG sessions[1]. ---------------------------------------------------------- ## Recap of Previously Discussed PTG Topics We recapped three items. 1. Enhancing Tacker Testing Coverage in the OpenStack Helm Check Pipeline - We discussed enhancing tests for Tacker's OpenStack Helm and done implementation. - Test coverage isn't enough yet. So, introduce attional tests using the OpenStack CLI for Tacker testing as similar to other existing projects. 2. New Compliance Testcase Implementation for ETSI TST010 Release 3 (v3.3.1) - Shared the current status of implementation for ETSI TST010 Release 3 (v3.3.1) compliant. 3. Enabling VNF Support in Prometheus Plugin for Fault Management - It's a proposal for adding Fault Management support for VNF in addition to CNF. - The development is going to be finished and released in this cycle. ## Support of higher K8s and CRI-O version in Tacker K8s jobs - Current tacker supports version 1.30 of k8s and cri-o, but 1.32 is recommended in ETSI SOL specification. Although 1.32 is also still old for considering k8s maintenance suppport, we've agreed to target the version. ## Tacker Wiki Page Utilization for SOL and Tacker Gap Documentation - As the first step for utilizing tacker's wiki, we've agreed to revise old contents describing SOL specifications. ## Tacker Bug Triage - There are a number of open bugs in Tacker that have not been updated or triaged for a long time. - We discussed how should we handle bugs whose assignee or reporter has already left. - As Pankaj proposed, we'll try to resume the bug triage activity by making a dedicated team and handle them instead of deciding each assignee. ## Eventlet Removal from Tacker (Community Goal) - The first analysis for Eventlet removal has been done by NEC team. - Although NEC team is going to continue to handle the activity, a few more contributors will be required. So, continue to discussion dividing tasks and assigning responsibilities among team members. ## [recap] Fix VNF-Package Multi-tenancy issues - Shared the current status of development of the proposed feature. - The target release cycle is Hibiscus, possibly. ## Many Tacker instance - A proposal from Docomo for introducing multi tacker conductors support mainly for resolving performance issue. - One of the discussion points is leader selection algorithm. Although there are several sophisticated algorithms such as raft consensus algorithm, we came to the conclusion that fixed leader(s) configuration is enough for their requirement currently. - We've agreed to implement multi tacker conductor support with the simple algorithm. ## TCA LCM Operator in Kubernetes infra-driver - Another proposal from Docomo for introducing a k8s operator for running life-cycle managment for CNFs. - Background: declarative approach is required in Kubernetes ecosystem and ETSI NFV Release 6, e.g. ETSI GS-NFV 008-1, ETSI GS-NFV 008-2, specified new architecture as Telco Cloud Orchestration (TCO), Telco Cloud Platform (TCP) and Telco Cloud Infrustracture (TCI). - The problem is that the current tacker impl of k8s infra driver only supports a fixed set of well-known resource kinds (Deployment, StatefulSet, DaemonSet, etc.) and Custom Resource (CR) is out of the scope. - Two main discussion points: Where we maintain the code (include the operator implemented in Go into tacker's repo or outside) and how we test it if it's in tacker's repo. - We didn't reach to a conclusion. So, continue the discussion. ---------------------------------------------------------- [1] https://etherpad.opendev.org/p/apr2026-ptg-tacker