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

Anuket TSC decided to require a CLA for incoming contributions. There is a CLA text proposed by LF for ICLA and CCLA here.

Some TSC members requested the comparison of the old CLA and the new CLA. As OPNFV had no CLA, but it had IPR related sections in its Charter the closest thing to fulfill this request is to compare the IPR related sections of the OPNFV Charter with the proposed CLA texts.

The result of the comparison is here: OPNFV Charter vs Anuket CLA.pdf

This page contains an analyzis on the list of test cases listed in the CNCF CNF Testsuite to determine if RA2 should contain related workload requirements.

Each test should be clearly documented - there is no documentation currently.
The test case description should be written describing expectation clearly 

(eg Test if the CNF crashes when disk fill occurs

should be written as

Test that the CNF does not crash when disk fill occurs)

Notes

• Tests defined here: https://github.com/cncf/cnf-testsuite/blob/2d875c66352e8dc5650c6fe7a1c43e744a7a2871/embedded_files/points.yml (10 out of the 15 'essential' test must be passed to get the certification)
• Rationale of the tests: https://github.com/cncf/cnf-testsuite/blob/main/RATIONALE.md

Issues raised to CNCF CNF Testsuite during this work

The analyzis

Derived RA2 requirements

hostNetwork attribute of the Pod specifications must be False or should not be specified. 

runAsUser and

runAsGroup attributes should be set to a greater value than 999.

hostPID

or the hostIPC attribute set to true.

readOnlyRootFilesystem attribute of the Pods in the their

securityContext should be set to true.

nodePort definition. 

Submitted: PDF

• CFP Closes: Monday, February 21 at 11:59 pm PST

Link: https://events.linuxfoundation.org/cloud-native-telco-day-europe/register/

Must be registered for Kubecon (IN-PERSON pre-registration is required): https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/register/

Speakers (2 max plus backup):

• Riccardo Gasparetto Stori ~50%
• Gergely Csatari ~50%
• Ulrich Kleber

Category (choice):

• Lessons Learned Adopting Cloud Native in Telco (ex. debugging & protocol, multi-cluster CNF setups, UPF failover and scaling models, security standards, etc.)
• Cloud Native Best Practices for Networking Applications
• Cloud Native Network Functions (CNFs) (development of, testing of, orchestration of, acceleration, integrations, deployment & lifecycle automation in operations etc.)
• Cloud Native Telco Services (e.g. how are people using Telco services in a cloud native way etc.)
• Networking and Kubernetes
• Telco Grade Resiliency and Service Availability in Dynamic Cloud Native environments (practices, patterns use cases, Infra uptime vs service availability)
• Multi-Cloud Portability for Telco (ex. Telco use cases built for the public cloud, identifying the “right” cloud: Public, Telco-cloud, Edge-cloud, Hybrid onprem + public)

Session type:

Session Presentation/Deep Dives (typically 30-40 minutes in length)

Session level: All-Levels

Title options:

• Cloud Native Matchmaking with Anuket
• Open Source Telco Cloud with Anuket
• Building an open, interoperable CNF platform in Anuket
• Anuket - The open telco cloud platform
• What does Anuket bring to cloud native

Abstract (max 1200 chars):

The Anuket Open Source Project empowers the global telco community to deliver network services faster, more reliably and securely, by developing reference cloud models, architectures and conformance programs.

Today, telcos need to spend high effort for the integration of CNFs with the different cloud native telco platforms. 

To reduce this effort, Anuket defines a Kubernetes Telco Cloud reference - this includes the mandatory capabilities, the reference implementation and conformance testing.

The presentation will introduce the RA2, RI2 and RC2 projects, their content and status, and how to benefit from them.

Participation is open to all - making collaboration between telcos and network vendors an ingredient for success.

Audience

The audience are telecom professionals in any phase of their cloud native journey. The audience of the presentation will get an overview on how Anuket decreases the integration cost of CNFs to Kubernetes platforms.

Benefits for the Ecosystem*

The Anuket projects are working to decrease the time and effort needed to integrate CNFs and Kubernetes platforms. This will make the ecosystem more effective and agile.

Have you or anyone else given this presentation before?*

No

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

Yes

Intro

Anuket specifications are written in GFM (GitHub flavored Markdown) what is a pretty weak markdown language (e.g.: It is not possible to scale images). These documents have three "output formats":

1. Readthedocs uses recommonmark to convert the documents to rst in compile time. Recommonmark is not supported anymore and should be changed to something else anyways.
2. GitHub "code view". Here GFM is the default format, but GitHub can render rst also without any problem.
3. Some of the documents are converted to word document and published by GSMA. Conversion fomr rst would be less difficult than form md

For these reasons we would like to convert the documents from markdown to rst. This page contains information and status progress for this work.

Issues

There are some issues what we need to solve on top of converting the documents.

• Things to be corrected in markdowns
  • Markdown issues
    • Removal of manual heading numbers
    • Removal of heading numbers from links (replace "[0-9]+\-" with "")
    • Replace raw html to markdown
      • images
      • br-s
      • Image captions ()
      • other <p>-s
      • remove internal references (html anchors)
  • Markdown best praciices
    • remove the ToC-s
  • Things needed for the conversion
    • Add blank lines before lists (like here)
  • Remove the bogometers from the chapters
• After the rst converison
  • Re-align the table line breaks
  • Move the (n)-s to supertext (if possible)

• Generate heading during the build
• fixing of broken intra-document links to GitHub generated anchors. These references/links only work on GitHub, but are broken in the Rtd builds already today
• consistent use of intra-document linking to auto-generated header anchors without including header numbers

Document responsibles

Details

• Schedule: https://sched.co/lStw
• Abstract:

  “Anuket References 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 Kali, the current Anuket release, and what are the plans for the next one, Lakelse.”

• Duration 30 min
• Speakers guide: https://events.linuxfoundation.org/open-networking-edge-summit-north-america/program/virtual-speaker-guide/#schedule-information
• Virtual Speaker Pre-Recording File Submission Due Date: Tuesday, September 14
• Upload Presentation Slides to Sched: Wednesday, October 6

Notes

• Agenda
  • What is Anuket, how it is structured, who are contributing - Gergely Csatari
    
  • What is RA2 - Gergely Csatari
  • What did we do in the past (Kali included) - Riccardo Gasparetto Stori
  • What are the plans for the future (Lakelse) - Riccardo Gasparetto Stori
  • How to get involved? - Riccardo Gasparetto Stori
    
    • Links to start reading, meetings and logistics
  • Q&A
• Actions
  • Gergely Csatari  to ask if we can survey the audience
• We can use this slideset as a basis
• This is the template: https://events.linuxfoundation.org/wp-content/uploads/2021/07/ONE-Summit_K8s-Edge_Final.ppt..pptx
  
• Add generic Anuket update
• Add Laklse updates - Riccardo Gasparetto Stori

Draft material

• Building the Cloud Native Reference Architecture for Telco Cloud – Update on Anuket RA2 - Gergely Csatari, Nokia & Riccardo Gasparetto Stori, Vodafone - v5.pptx
• Building the Cloud Native Reference Architecture for Telco Cloud – Update on Anuket RA2 - Gergely Csatari, Nokia & Riccardo Gasparetto Stori, Vodafone - v4.pptx
• Building the Cloud Native Reference Architecture for Telco Cloud – Update on Anuket RA2 - Gergely Csatari, Nokia & Riccardo Gasparetto Stori, Vodafone - v3.pptx
• Building the Cloud Native Reference Architecture for Telco Cloud – Update on Anuket RA2 - Gergely Csatari, Nokia & Riccardo Gasparetto Stori, Vodafone - v2.pptx
• Building the Cloud Native Reference Architecture for Telco Cloud – Update on Anuket RA2 - Gergely Csatari, Nokia & Riccardo Gasparetto Stori, Vodafone - v1.pptx

Details

• Schedule: https://sched.co/lStw
• Abstract:

  “Anuket References 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 Kali, the current Anuket release, and what are the plans for the next one, Lakelse.”

• Duration 30 min
• Speakers guide: https://events.linuxfoundation.org/open-networking-edge-summit-north-america/program/virtual-speaker-guide/#schedule-information
• Virtual Speaker Pre-Recording File Submission Due Date: Tuesday, September 14
• Upload Presentation Slides to Sched: Wednesday, October 6

Notes

• Agenda
  • What is Anuket, how it is structured, who are contributing - Gergely Csatari
    
  • What is RA2 - Gergely Csatari
  • What did we do in the past (Kali included) - Riccardo Gasparetto Stori
  • What are the plans for the future (Lakelse) - Riccardo Gasparetto Stori
  • How to get involved? - Riccardo Gasparetto Stori
    
    • Links to start reading, meetings and logistics
  • Q&A
• Actions
  • Gergely Csatari  to ask if we can survey the audience
• We can use this slideset as a basis
• This is the template: https://events.linuxfoundation.org/wp-content/uploads/2021/07/ONE-Summit_K8s-Edge_Final.ppt..pptx
  
• Add generic Anuket update
• Add Laklse updates - Riccardo Gasparetto Stori

This document was merged to Anuket Charter proposal for commenting

The document was accepted in the 2021-11-02 TSC meeting. The document was moved to Anuket Project Operations and Procedures .

Introduction

This page is created to provide a framework for the modifications of the proposed Anuket Charter. The baseline document was created by Pankaj Goyal based on the XGVela and CNCF and on the comments collected to the current Anuket charter.

History of this page was used to develop the now approved Anuket charter. This page is considered as retired.

The charter

The proposed charter was review-ed and approved by LF legal and voted by Anuket TSC.

Here is the charter in different formats:

• Full text of the charter
  • Anuket Proposed Charter v3.pdf
  • Anuket Proposed Charter v3.docx
• Text of the charter in comparision with the current charter of Anuket
  • Anuket Proposed Charter v3 - tack changes.pdf
  • Anuket Proposed Charter v3 - tack changes.pdf

Previous versions

Are in the history of this page. Last agreed version sent for legal review is in version 14.

Introduction

This page is created to provide a framework for the modifications of the Anuket Charter and the TSC Operational Guidelines. Both of these documents were inherited from OPNFV and had one set of editing. The final aim of this activity is to reach a TSC consensus and finally an approval on the content of the documents.

References

• Changes of the proposed Charter compared to the previous OPNFV Charter

• Clean version of the proposed Charter
• Clean version of the proposed TSC Operational Guidelines

Ways of working

• A copy of the proposed documents added to the following pages
  • Anuket Charter proposal for commenting
  • Anuket TSC Operations and Procedures document proposal for commenting
  • Anuket Project Operations and Guidelines document for commenting
• Please comment the text in the documents using the inline commenting feature of Confluence in a way that the whole text to be replaced is marked for commenting
• Propose a modified text in your comment if possible
• Once there is a consensus on the text to be modified it will be edited to the text

Obsolete documents to comment

These documents are the current Anuket Charter and TSC Operational Guidelines commented by the community. The commenting of the actual proposed document are in the following pages:

• Anuket Charter proposal for commenting
• Anuket TSC Operations and Procedures document proposal for commenting
• Anuket Project Operations and Guidelines document for commenting

These documents are kept in here to preserve the community comments of the original documents.

Please do not comment these anymore, but comment the referred pages instead. Any comments to this page will be deferred.