SPC OPNFV TSC Discussion 2172020 OPNFV TSC attendees

SPC / OPNFV TSC Discussion – 2/17/2020 OPNFV TSC attendees: Al, Morton, Trevor Cooper, Georg Kunz, Scott Steinbrueck Meeting Notes: https: //wiki. lfnetworking. org/display/LN/SPC+2020 -02 -17+Meeting+notes • • • Scott doesn’t think CNTT should be exclusive focus of OPNFV, presented a high level tracking list for CNTT Baldy for ONES-NA as a starting point for developing list of tasks OPNFV to work on https: //wiki. lfnetworking. org/display/LN/CNTT+TSC+Master+Tracker+Baldy – How to translate into OPNFV activities (through TSC, CIRV project, other), what is OPNFV response? – OPNFV 2. 0 evolution too slow for current CNTT objectives to impact Trevor, Al, Georg emphasized lack of attracting developers is a key issue – Testing projects do not have enough critical mass of developers – Without showing corporate sponsors sufficient value, developers will not be reassigned – “the separation between CNTT and OPNFV seems to be the root of the problem” Discussed example of developers driving performance testing – Seen by some as low priority or not important but others believe value of CNTT cannot be realized without performance testing – Testers spent > 2 months struggling to get a stable install of RI using Airship due to lack of developer resources – Requirements and success criteria are not available from CNTT – developers taking a hands-on iterative approach to show what is possible (Open Source approach) • “Cloud-native is very different than anything most people are familiar with … to figure this out you need to get code under your fingernails” • Suggestion was for OPNFV TSC to pick up this discussion and there is another opportunity in 2 weeks to bring back to SPC 2022 -02 -16

OPNFV Status (Jan 2020) presented in SPC meeting 2/3/20 • Developer participation has been declining since 2018 (see slide) • No current plan for releases beyond Iruya (21 Jan 2020) • Ad hoc strategy discussions since Dec 2018 have not reached a clear consensus with action plan to re-focus and re-invigorate the community • TSC – Recent change in TSC chair (ad-hoc election in process) – Evaluating all participating projects / activities to accurately reflect community status – Re-focusing on technical strategy and opportunities (desire for faster progress) – Has requested direction and help from the LFN board (through SPC) • OPNV has unique assets and profile of expertise (see slide) • CNTT has emerged with clear asks and has renewed interest in OPNFV however this has not (yet) attracted new developers – General agreement by TSC in Prague to align with CNTT but still open questions as to execution – CNTT requirements and specifications from Carriers are highly aligned with original OPNFV charter 2022 -02 -16

OPNFV Development Activity (2015 – 2020) 2019 54% commits from one author

OPNFV Community Assets • Geographically distributed community labs and technically heterogeneous hardware including lab-as-a-service (UNH) • CI/CD pipelines, Dev. Ops tooling • Test Tools, Test Cases, Compliance framework • Strong expertise in Integration and Testing • Strong Telco expertise • Cross community upstream relationships 2022 -02 -16

OPNFV – Mission Statement • Open Platform for NFV (OPNFV) is a project and community that facilitates a common NFVI, continuous integration (CI) with upstream projects, stand-alone testing toolsets, and a compliance and verification program for industry-wide testing and integration to accelerate the transformation of enterprise and service provider networks. 2022 -02 -16 https: //www. opnfv. org/about/mission

COMMON NFVI TELCO TASKFORCE (CNTT) – Mission Statement • ESTABLISH NFVI REFERENCE MODEL, ARCHITECTURES & NFVI | VNF CERTIFICATION LIFECYCLE TO REDUCE COST, TIME TO MARKET & COMPLEXITY OF TELCO OPERATIONS FOR THE BENEFIT OF THE BROADER COMMUNITY 2022 -02 -16 https: //github. com/cntt-n/CNTT/blob/master/artefacts/CNTT_intro. pdf