Anuket Release and Consumability enhancements.pptx

More information here

• Anuket resources are very thin so hard to get anyone to work on the project
• Review of the project within Anuket – Some do not need release managers (Thoth), Some are not active, Some need releases (Functest, VinePerf, CIRV, Kuberef) and finally the reference docs. 
• TSC could serve as a release manager with a stronger community
• We should support projects which do not follow the Anuket release model
• There are different categories of the projects
  • Projects that do not need releases (Thoth)
  • Inactive projects should just be archived
  • Reference docs – need minimal release support (set dates and gather requirements)
    • Set the dates for the release - TSC
    • Release plan - sub-project teams/PTL
    • Release tags in Jira and GitHub - TSC
    • Associate Issues with the GitHub project plan - PTL
    • Proofreading - PTL
    • Release branch creation - TSC
    • Readthedocs branch creation - TSC
    • Sub-project release highlights - PTL
    • Blogpost, release announcement - TSC
  • Test projects
    • Set the dates for the release - TSC
    • Release plan - sub-project teams/PTL
    • Release tags in Jira and GitHub - TSC
    • Associate Issues with the GitHub project plan - PTL
    • Documentation done - PTL/Team
  • Keep two releases per year
  • Update the release framework tasks with the slimmed down version 
• Next steps:
  • Gergely Csatari  Propose a new release process template based on this: Orinoco Release Progress

Devil Survivor MOD APK Version 1.0.11

This page collects the CNF requirements in RA2, RC2 and in CNCF CNF Conformance / CNF Testbed.

The original analyzis page for introducing the CNF requirements in RA2: Analyzis of CNCF CNF Testsuite tests for RA2

CNF Testsuite points.yaml

 pr-s

• RA2: https://github.com/anuket-project/anuket-specifications/pull/3352

Nile, the latest version of Anuket was released to the public on January 4, 2023, with add cloud native requirements and testing functionality!

Anuket Overview

Anuket is an LF Networking project occupies a unique position in the telecom industry incorporating both operator infrastructure specifications, implementations, and open source infrastructure test suite development, all under a single initiative. The community has subject matter expert representatives from telco operators and their technology suppliers, which means that it is well positioned to address the “real world” challenges of the telecommunications industry. If you or anyone you know would like to contribute to any of these important activities, the Anuket website is a great place to start.

Leadership

Anuket members, per its Charter, elected the 2023 Technology Steering Committee and Co-chairs: Scott Steele and Gergely Csatari. On behalf of outgoing 2022 TSC Co-chairs, Gergely and myself, we would like to thank all Anuket contributors for their fantastic efforts in 2022 and wish the new TSC and the new Co-chairs all the best in their 2023 work!

Anuket Nile Release

Numerous Anuket projects and work streams continued to strengthen container-based open infrastructure specifications and implementations – an area that is increasingly important to the telco industry. Some of the accomplishments include:

• ViNePerf - The ViNePerf project continued development efforts to automate test setup and benchmarking of container networking with various CNI plug-ins (Multus, Cillium) and kernel acceleration (AF_XDP, eBPF), with the help of a Student Volunteer and an Intern from the LFN program.
• Thoth - The Thoth project continues to focus on implementing E2E AI for NFV use case scenarios. The newly established NICIP project is a jointly organized data generation competition with ITU.  Thoth is also cooperating on AI frameworks such as Mindspore, and starting the R&D effort needed to create data anonymization tools to allow telecom companies to share without the fear of exposing actual customer data.

On the requirements side

• Reference Model (RM) changes (major):
• Infrastructure LCM Automation – re-edited and updated to improve readability and to ensure alignment with multi-cloud models
• Security sections updated to reflect (and refer to) evolving 5G security standards and best practices
• Added energy consumption metrics and related requirements
• Reference Architecture 1 (RA1) OpenStack changes:
• New chapter based on RC1 content integrates conformance and establishes the link between architecture requirements and tests, providing the mechanism to validate the cloud infrastructure against the set of defined requirements.
• Chapter 1 has been restructured with the addition of a bibliography and an abbreviations table.
• The whole document has been reviewed to ease the creation of version 2 of NG.133 GSMA document.
• 133 v2 has been officially published the 9^thof December.

• Updates have been made for the support of containerized applicationsand Cyborg accelerators drivers.
• Reference Conformance 2 (RC2) has been updated to align with the latest versions of Kubernetes and Functest.
  1. Added specific test references supporting workloads by referencing the CNCF CNF testsuite.

In the coming releases, Hybrid, Multi-Cloud model and AI/ML utilisation, will be the focus of Anuket work in the upcoming releases, reflecting a growing global interest in more sophisticated operating models for telecommunication operators facing the challenges of real-life 5G/Edge/IoT implementations.

In 2022, the Anuket Project continued its two release cadence with Moselle delivered in June and Nile following in December. As has been true for the last few years, Anuket has been focused on developing reference models, architectures and specifications in support of infrastructure for virtualized (CNF/VNF) telecom workloads.  The requirements have continued to evolve to cover more use cases in the Reference Model (RM), and align these use cases with changes in upstream communities in the Reference Architectures for OpenStack (RA1) and Kubernetes (RA2). The application requirement specification for the Reference Architecture for Kubernetes matches with the CNCF CNF Conformance program to avoid the fragmentation of conformance programs in the industry, while fostering continued collaboration with the CNCF community. Taking the Reference Model and the Reference Architecture for OpenStack, in 2022 the Reference Conformance for OpenStack has also been released as a GSMA Permanent Release document. We are working with the GSMA on a planned release of the Reference Architecture for Kubernetes (RA2) in 2023.  On top of the enhancement of collaboration with GSMA we plan to continue to evolve our specifications by adding new use cases, aligning with adjacent communities, such as Nephio, O-RAN and Sylva, and further increase the quality and coverage of our Reference Architecture for Kubernetes and conformance projects.  

On the testing side of the project, Functest, the testing framework that supports the conformance and Anuket Assured programs maintains continuous release updates in synch with the upstream OpenStack and Kubernetes releases.  The ViNePerf project continued development efforts to automate test setup and benchmarking of  container networking with various CNI plug-ins (Multus, Cillium) and kernel acceleration (AF_XDP, eBPF), with the help of a Student Volunteer and an Intern from the LF program. 

We also plan to continue the work we started in 2022 to increase the consumability of our project and our deliverables by enhancing our documentation, testing tools and web presence.

Intro

The target of this conspiracy to make Anuket more easy to understand for someone who is not involved in the project.

We would like to achieve this by tuning the already existing documentation created for the project. This includes applying consistent templates, linking the documents together in a meaningful way and many more listed in here.

This page is created to help the conspirators.

Current conspirators

• Gergely Csatari 
• Georg Kunz 
• Scot Steele 
• Beth Cohen 

Project management and communication

• GitHub project: https://github.com/cntt-n/CNTT/projects/34#card-85674686
• Meetings: we do not have a dedicated meeting, but use the Anuket Weekly Technical Discussions to discuss
• Communication: the common denominator is sending an email to the Current conspirators. If the issue is relevant for wider audience use the anuket-tech-discuss dl.

What is where

09 Aug 2022 

• Problem statement from
• We have a defined scope here: About Anuket
• Conclusions
  • We do not need to change the scope
  • We would need to have a survery on Anuket among the industry actors about the role and adoption of Anuket.

This is a list of active Anuket repos in the July of 2022

Toc

Logistics

• Conference time: November 15 – 16, 2022
• Conference place: Seattle, WA
• CFP deadline: Friday, July 8 at 11:59 PM PDT

Proposal template

• Speaker info:
  • Primary Speaker Full Name
  • Primary Speaker Company
  • Primary Speaker Job Title
  • Primary Speaker Email
  • Primary Speaker Country of Residence
  • Primary Speaker Biography (provide a biography that includes your employer (if any), ongoing projects and your previous speaking experience)
  • Primary Speaker Twitter Handle
  • Primary Speaker LinkedIn Profile
  • What gender does the primary speaker identify with?
  • Does the primary speaker identify as a person of color? 
  • If the primary speaker identifies with any other underrepresented group (disability, LGBTQIA+, etc.) please indicate below.
• Select a Track
  • Industry 4.0
  • Security
  • The New Networking Stack
  • Operationalizing Deployments: Case Studies, Successes, and Challenges
  • Looking Ahead: Emerging Technologies and Business Models
  • Other, please specify..

• Type of Submission

  • Session Presentation ((typically 30-40 minutes in length)
  • Panel Discussion ((typically 30-40 minutes in length)
  • Birds of a Feather (typically 30-45 minutes in length)
  • Lightning Talk (typically 5-10 minutes in length)
  • Tutorial/Workshop (Tutorial (typically 1.5 - 2 hours in length)
  • Other, please specify...
• What Skill Level is this Best Suited for?
  • Any
  • Entry-Level
  • Mid-Level/Intermediate
  • Senior Level/Expert
• Abstract Title (If your talk is selected, the Abstract Title you choose will be the Title shown in the conference schedule; often what attendees use as a starting point to determine if they will be interested in the talk. Choose your title carefully - make sure that it accurately describes what your talk will cover. )
• Abstract (Provide an abstract that briefly summarizes your proposal. Provide as much information as possible about what the content will include. Do not be vague. This is the description that will be posted on the website schedule if your talk is selected, so be sure to spell check, use complete sentences (and not just bullet points), and write in the third person (use your name instead of “I”).)
• Audience (Describe who the audience is and what you expect them to gain from your presentation.)
• Benefits to the Ecosystem (Tell us how the content of your presentation will help better the ecosystem. (We realize that this can be a difficult question to answer, but as with the abstract, the relevance of your presentation, and why people should attend the session, is just as important as the content).)
• Audience Engagement (In keeping with the spirit of bringing the “hallway track” into the program, please tell us how you intend to engage with the audience to foster interaction and collaboration.)
• Have you given this presentation before?
• If your session is accepted, would you be open to our PR team contacting you about speaking with media and press onsite?
• Additional Details & Speaker Agreements
• Travel Funding
• Code of Conduct
• Slide Deadline Agreement

Draft proposals

How to find a way to a harmonized and collaborative CNF conformance verification?

• Status: Submitted
• Speaker info: Georg Kunz , Gergely Csatari 
• Select a Track
  • Operationalizing Deployments: Case Studies, Successes, and Challenges

• Type of Submission

  • Session Presentation ((typically 30-40 minutes in length)
• What Skill Level is this Best Suited for?
  • Any
• Abstract (Provide an abstract that briefly summarizes your proposal. Provide as much information as possible about what the content will include. Do not be vague. This is the description that will be posted on the website schedule if your talk is selected, so be sure to spell check, use complete sentences (and not just bullet points), and write in the third person (use your name instead of “I”).)
  
  Cloud infrastructure and workload verification has a history in the telecom industry. As the workloads are dealing with extreme amount of traffic and/or extreme low latency requirements it is natural that they are more sensitive to their cloud platform than other applications. To decrease the cost of integration and expensive surprises during deployment there is a need to agree on what a telecom application can expect from its runtime environment and there is a need to certify if the applications expectations are correct and the platform can fullfill the expectations. Anuket defines a set of application requirements in its Kubernetes based Reference Architecture and plans to build the certification for it in its Anuket Assured certification program while CNCF announced in the 2022 KubeCon EU their CNF Certification program. While Anuket RA2 defines an opinionated Kubernetes distribution and its workload requirements ensure that the CNF is able to run in the distribution, the CNF Certification tests the adherence to cloud native principles. For a CNF vendor the ideal situation would be to run only one set of open source CNF certification tests, but due to the different targets of these certifications this is not the case today.
  In this presentation Georg and Gergely will discuss how these two communities could work together to achieve a good collaboration between the initiatives, how to draw the limit of the testings scope and how to minimalize the testing overhead for CNF vendors. For this the presenters will invite a set of key community members to disucss what is the common denominator of the tests and focus on the distinguishing parts.
• Audience (Describe who the audience is and what you expect them to gain from your presentation.)

CNF vendors and network operators who are using the CNF-s and paying the integration bill.

• Benefits to the Ecosystem (Tell us how the content of your presentation will help better the ecosystem. (We realize that this can be a difficult question to answer, but as with the abstract, the relevance of your presentation, and why people should attend the session, is just as important as the content).)

Due to the flexibility of cloud platforms and the sensitivity of CNF-s the integration of CNF-s and their platforms is a continuous issue. The industry tries to address this with different conformance programs. This panel is about the collaboration of these certification programs.

• Audience Engagement (In keeping with the spirit of bringing the “hallway track” into the program, please tell us how you intend to engage with the audience to foster interaction and collaboration.)

We plan to invite some key contributors form the CNCF CNF Certification program, Anuket Assured and Anuket RC2 programs and initiate a discussion in the last part of the presentation.

• Have you given this presentation before?

No

• If your session is accepted, would you be open to our PR team contacting you about speaking with media and press onsite?

Yes

• Additional Details & Speaker Agreements
• Travel Funding
• Code of Conduct
• Slide Deadline Agreement
• Panelists (4+1): Georg Kunz (Rihab), Gergely Csatari , Heather, Taylor (tentative), Olivier Smith  

How difficult can be to define a Kubernetes reference stack for CNF-s?

• Status: submitted
• Speaker info: Gergely Csatari , Riccardo Gasparetto Stori 
  
  • Primary Speaker Full Name
  • Primary Speaker Company
  • Primary Speaker Job Title
  • Primary Speaker Email
  • Primary Speaker Country of Residence
  • Primary Speaker Biography (provide a biography that includes your employer (if any), ongoing projects and your previous speaking experience)
  • Primary Speaker Twitter Handle
  • Primary Speaker LinkedIn Profile
  • What gender does the primary speaker identify with?
  • Does the primary speaker identify as a person of color? 
  • If the primary speaker identifies with any other underrepresented group (disability, LGBTQIA+, etc.) please indicate below.
• Select a Track
  • The New Networking Stack

• Type of Submission

  • Session Presentation ((typically 30-40 minutes in length)
• What Skill Level is this Best Suited for?
  • Any
• Abstract (Provide an abstract that briefly summarizes your proposal. Provide as much information as possible about what the content will include. Do not be vague. This is the description that will be posted on the website schedule if your talk is selected, so be sure to spell check, use complete sentences (and not just bullet points), and write in the third person (use your name instead of “I”).)

“Anuket specifications are a family of LFN initiatives to design, implement and test the conformance for Telco Cloud infrastructures. The aim of the specification work is to decrease the time and money needed to integrate Telco Cloud infrastructures and their workloads (Network Functions). Anuket specifications consist of a technology agnostic Reference Model (RM) and two technology-specific Reference Architectures and Reference Implementations, for OpenStack and Kubernetes, aligning with the Anuket Reference Model. In this talk Riccardo and Gergely will describe how RA2, the Kubernetes based Reference Architecture is enabling Telecommunications Providers and Vendors to deploy Containerised Network Functions (CNFs) on Kubernetes efficiently, and what’s new in Moselle, the current Anuket release, and what are the plans for the next one, Nile.”

• Audience (Describe who the audience is and what you expect them to gain from your presentation.)

Architects in telecom network operators and in CNF and cloud platform vendors.

• Benefits to the Ecosystem (Tell us how the content of your presentation will help better the ecosystem. (We realize that this can be a difficult question to answer, but as with the abstract, the relevance of your presentation, and why people should attend the session, is just as important as the content).)

This talk is a generic information sharing about Anuket RA2, a release update on its Moselle additions and information about the plans for Nile. 

• Audience Engagement (In keeping with the spirit of bringing the “hallway track” into the program, please tell us how you intend to engage with the audience to foster interaction and collaboration.)

Participate in the hallway track after the session.

• Have you given this presentation before?

A very similar about the previous release.

• If your session is accepted, would you be open to our PR team contacting you about speaking with media and press onsite?

Yes

• Additional Details & Speaker Agreements
• Travel Funding
• Code of Conduct
• Slide Deadline Agreement

Working towards a shared model for Telecom Cloud Infrastructure, an Overview of Anuket

• Status: submitted
• Speaker info: Beth Cohen and Gergely Csatari 
• Select a Track
  • Operationalizing Deployments: Case Studies, Successes, and Challenges

• Type of Submission

  • Session Presentation ((typically 30-40 minutes in length)
• What Skill Level is this Best Suited for?
  • Any
• Abstract (Provide an abstract that briefly summarizes your proposal. Provide as much information as possible about what the content will include. Do not be vague. This is the description that will be posted on the website schedule if your talk is selected, so be sure to spell check, use complete sentences (and not just bullet points), and write in the third person (use your name instead of “I”).):

Anuket grew out of a marriage of a requirements task force (CNTT) and a infrastructure test project (OPNFV).   The idea is to create a  single project that not only defines the reference requirements for infrastructure, but also creates and supports the code needed to test and valid these infrastructures,  As you can imagine, it is an LFN project with a difficult mission. In this session, the co-chairs of the Anuket TSC will explain the structure of Anuket sub-projects, the activities in these different sub-projects and how all of this works towards the mission. The presentation will cover release highlights from the latest Moselle release and provide some insights to the targets for the ongoing Nile release.

• Audience (Describe who the audience is and what you expect them to gain from your presentation.)

Anuket is a project that was designed to be a joint effort by and for Telecom vendors and operators.  This session will allow those who are Anuket curious to learn more about it a and those always wanted to ask what Anuket was but never had the chance.

• Benefits to the Ecosystem (Tell us how the content of your presentation will help better the ecosystem. (We realize that this can be a difficult question to answer, but as with the abstract, the relevance of your presentation, and why people should attend the session, is just as important as the content).)

Actors in the telecom industry need better understanding of the mission of Anuket and how the project works to make this mission reality.  Anuket is a project that supports other projects in LFN and across the Open Standards community in general.

• Audience Engagement (In keeping with the spirit of bringing the “hallway track” into the program, please tell us how you intend to engage with the audience to foster interaction and collaboration.)

This is intended as a fully interactive session with lots of opportunities for the audience to participate and ask questions.

• Have you given this presentation before?

No

• If your session is accepted, would you be open to our PR team contacting you about speaking with media and press onsite? Yes
• Additional Details & Speaker Agreements
• Travel Funding
• Code of Conduct
• Slide Deadline Agreement

Day 0, 1 and 2 in the life of an Edge Computing Deployment

• Speaker info: Beth Cohen and Gergely Csatari Ildiko Vancsa 
• Select a Track
  • Operationalizing Deployments: Case Studies, Successes, and Challenges

• Type of Submission

  • Panel Discussion ((typically 30-40 minutes in length)
• What Skill Level is this Best Suited for?
  • Any
• Abstract (Provide an abstract that briefly summarizes your proposal. Provide as much information as possible about what the content will include. Do not be vague. This is the description that will be posted on the website schedule if your talk is selected, so be sure to spell check, use complete sentences (and not just bullet points), and write in the third person (use your name instead of “I”).):

Theory and use cases are important, but what happens when the rubber hits the road, or in other words, when your edge infrastructure is ready to be deployed and run in production.  During this session we will look at the dependencies and requirements for successfully launching and managing edge architectures in the field. Grouped around the Telecom concept of what happens over the three "days" it takes to take an edge infrastructure from development to deployment and into production. Starting from “Day 0”, the preparation/development phase before the deployment so to speak, and moving into “Day 1”, the actual deployment into the field, followed by “Day 2” or Day N (depending on who you talk to) which includes the management of the systems in production, each step calls for different components that interrelate with each other. 

• • Day-0: "product development". Focus on bootstrapping, develop templates
  • Day-1: "service delivery". Instantiate/customize templates according to customer needs and deploy them. Validation.
  • Day-2: "production/operations"
• Audience (Describe who the audience is and what you expect them to gain from your presentation.)

Any person who is serious about Edge and operating an edge deployment in production.

• Benefits to the Ecosystem (Tell us how the content of your presentation will help better the ecosystem. (We realize that this can be a difficult question to answer, but as with the abstract, the relevance of your presentation, and why people should attend the session, is just as important as the content).)

The Open Source community tends to focus  on Day 0 or requirements, but increasingly the telecom industry is looking for community to standardize operations and deployment activities.  While the nomenclature is borrowed from the  telecommunications industry, but the steps are applicable on a much wider scale and many more industries. 

• Audience Engagement (In keeping with the spirit of bringing the “hallway track” into the program, please tell us how you intend to engage with the audience to foster interaction and collaboration.)

This is intended as a fully interactive session with lots of opportunities for the audience to participate and ask questions.

• Have you given this presentation before?

No

• If your session is accepted, would you be open to our PR team contacting you about speaking with media and press onsite? Yes
• Additional Details & Speaker Agreements
• Travel Funding
• Code of Conduct
• Slide Deadline Agreement

Building an Open Reference Cloud Native Platform for Telco Cloud -- Benefits Cost Saving Throughout whole process of development, testing and deployment.

• Speaker info:
  • Primary Speaker Dan Xu
  • Primary Speaker Company Huawei Technologies Co., Ltd.
  • Primary Speaker Title: Software Engineer
  • Primary Speaker Email: xudan16@huawei.com
  • Primary Speaker Country of Residence China
  • Primary Speaker Biography (provide a biography that includes your employer

    • Dan Xu is working in Huawei Technologies Co., Ltd for more than 6 years. I used to work on LFN OPNFV community for about 4 years and was the PTL of project Dovetail. Then she contributed in EdgeGallery community to be the leader of its CI/CD development for about 2 years. This year she is back to LFN Anuket community as the PTL of RI2 task force to do the k8s and infrastructure deployment. Dan Xu has given presentations and lead discussions about Dovetail Projects in ETSI Plugtest and OPNFV Plugfest for several times.

       
  • Primary Speaker Twitter Handle: None
  • Primary Speaker LinkedIn profile: None
  • What gender does the primary speaker identify with? Female
  • Does the primary speaker identify as a person of color? Asian
  • If the primary speaker identifies with any other underrepresented group (disability, LGBTQIA+, etc.) please indicate below. None
• Select a Track
  • The New Networking Stack

• Type of Submission

  • Session Presentation ((typically 30-40 minutes in length)
• What Skill Level is this Best Suited for?
  
  • Entry-Level
• Abstract Title

  • Cost Benefits of Building an Open Reference Cloud Native Platform for Telco Cloud

• Abstract 
  

  • Kubernetes-based Reference Implementation (RI2) is a project in LFN Anuket which focuses on providing reference k8s based Telco Cloud infrastructures for Telco Providers, Telco Cloud vendors and CNF software vendors. As a bridge of providers and vendors, RI2 gives providers a reference platform to test and choose both commercial Cloud infrastructures and CNFs running on it. Also it serves as a reference platform for Cloud vendors and CNF vendors to develop and test against. With this bridge, both providers and vendors can reduce the time and cost for developing, testing and integrating Telco Cloud infrastructures and CNFs. In this session, Dan Xu and Scot will give an introduction about what RI2 is, how to use RI2 to deploy a reference k8s based Telco Cloud infrastructure on bare metal and virtual machine, what’s new in Anuket Nile release, and what benefits users can get from RI2. Also will give a demo about how to use the tool kuberef to setup the k8s infrastructure on Baremetal.

• Audience 
  • All suppliers/operators that are considering the ways to reduce deployment costs of their cloud native Network/Network functions
• Benefits to the Ecosystem (Tell us how the content of your presentation will help better the ecosystem.
  • Adoption of the Anuket specifications will improve the Time to Install and Market for Operators and Suppliers 
• Audience Engagement (In keeping with the spirit of bringing the “hallway track” into the program, please tell us how you intend to engage with the audience to foster interaction and collaboration.)
• Have you given this presentation before?

No

• If your session is accepted, would you be open to our PR team contacting you about speaking with media and press onsite?

Yes

• Additional Details & Speaker Agreements
• Travel Funding
• Code of Conduct
• Slide Deadline Agreement

Cultural Transition: Open Source Across Telecom and Hyperscalers

• Speaker info:
  • Primary Speaker Scot Steele
  • Primary Speaker Microsoft
  • Primary Speaker Sr. Program Manager
  • Primary Speaker scotsteele@microsoft.com
  • Primary Speaker USA
  • Primary Speaker Biography (provide a biography that includes your employer (if any), ongoing projects and your previous speaking experience)
  • Primary Speaker Twitter Handle
  • Primary Speaker www.linkedin.com/in/scotsteele
  • What gender does the primary speaker identify with? Male
  • Does the primary speaker identify as a person of color? No
  • If the primary speaker identifies with any other underrepresented group (disability, LGBTQIA+, etc.) please indicate below. None
• Select a Track
  • Looking Ahead: Emerging Technologies and Business Models

• Type of Submission

  • Session Presentation ((typically 30-40 minutes in length)
• What Skill Level is this Best Suited for?
  • Any
• Abstract Title Cultural Transition: Open Source Across Telecom and Hyperscalers
• Abstract 

  As telecommunications is a backbone service to society the industry has been highly regulated since its inception. Thus Telcos must demonstrate a culture of high levels of operational availability, reliability, and recoverability in performance and cost management. Hyperscalers are relatively new entities in the communications space that leverage a more collaborative/adoptive culture with lesser concern for the operational efficiency. Open-Source specifications/code, and Hyperscaler partnerships can provide new features and greater capacities to their consumers with reduced time to market and lower capital costs. However, deltas between the operational efficiency culture of operators and the collaboration/adoption of hyperscalers could inhibit success on either side of the relationship. We posit that resolving conflict between cultures would allow consumer access to beneficial features that would improve the operator’s bottom line at a time when labor and cost challenges impact the industry’s overall growth and health.

  In this discussion, we ask the question “How can Open-Source impact and affect culture to support telco industry growth and health?” We will explore insights and possible paths through the lens of a significant and multi-faceted telco hyperscaler partnership.

• Audience: anyone Involved with technology selection, deployment, management, and leadership in the telco industry
• Benefits to the Ecosystem Transforming the culture of the industry to a more trusting, collaborative, and adoption mentality will provide numerous benefits to all participants through the improving the speed of development and adoption. This will generally support lower cost of implementation.
• Audience Engagement (In keeping with the spirit of bringing the “hallway track” into the program, please tell us how you intend to engage with the audience to foster interaction and collaboration.)
• Have you given this presentation before? o
• If your session is accepted, would you be open to our PR team contacting you about speaking with media and press onsite? Yes
• Additional Details & Speaker Agreements
• Travel Funding
• Code of Conduct
• Slide Deadline Agreement

• Porto-community-plenary-Anuket.pptx

Intro

LFN projects have the possibility to participate in review by the GB in every 6 months. This page was created to collect information about the 2022 mid year review by Anuket TSC.

Timeline

• Apr 15: Notification, template distribution & invites
• May 6: Completed slides are due in to your Project’s TCA
• May 10: Assembled GB deck completed by TCAs
• May 11: Final deck review by staff
• May 12: deck distributed to the GB
• May 18: TSC Chairs (or delegate) present to the GB

Final Presentation

Updated with input from TSC April 26 meeting. I included the notes from below and the notes from the email discussions.

Issues to address

• Response from GB companies to the Anuket Assured staffing request on the 2021 October review

EUAG is NOT the right place to validate Anuket's relevance, as I am planning on sunsetting the group as it has little participation and has outlived its usefulness.  I think that we can gain validation from within Anuket (the telco members) and the hopeful success of the Anuket Assured program.

Progress Against 2022 Project Objectives:

• I think we are okay with producing the releases -- Agree the releases have been more or less on time and had significant new requirements and features.
• We did not grew the technical community. Without knowing the numbers I have a feeling that we are losing technical contributors. I think this should be indicated -- Agree, my sense is that we have lost some of the less involved members, many reasons for it, but it is something that we should mention as an issue.
• We are working on the conversion and evolution. It is slower than what I’ve expected, but it is progressing. -- Yup.
• Validation: I think there was no progress here. We should indicate this to the GB and request feedback. -- I think that the launch of the ANuket Assured program was a step in the right direction, it just has not gotten the traction that we expected.  Or rather it has been going slower than expected.
• Linking the RC-s and Anuket Assured: I do not have any insights on this. Any opinion here? -- Needs more coordination.  I think that the Anuket Assured program is good, needs more publicity and better alignment/integration with the RC work.  The RC workstreams have been understaffed so that is something we should mention to the GB.

Key Call Outs for the LFN Governing Board (Gergely’s opinion, please comment):  Beth's adds

• What our community is doing well
• Producing releases
• Doing document conversion at the same time
• Broad support across the telecom and vendors in the community
• Areas that we can improve upon
• There are some sub-projects with very low resources. Even some are down to a single person, which makes them vulnerable. This is very bad bus factor.  Need to review the viability of some of the sub-projects and possibly archive them if they are no longer supportable or supported by the community.
• This is a documentation heavy project, we still do not have a functioning doc project and doc PTL
• Where we need help from the GB
• We need help from the GB member companies in supporting and validating that Anuket project is in alignment with their needs and requirements.
• We need help from the GB member companies in staffing the project with concrete resources. The same request was formulated in the previous review with no followup or response from the GB representatives.
• We would like to have better communication between the LFN Projects and the GB.

Stats

References

1. Template to be used: LFN Project Input for the Board template (1).pptx
2. Material the TSC provided for the previous round of project reviews: 2021-10-06 Anuket Project to GB-rev.pptx
3. Material presented for the GB during the previous round of project reviews, for reference: LFN Governing Board Meeting Day 2 - (Oct 20) Project Reviews (1).pdf