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

  • Type of Submission

  • What Skill Level is this Best Suited for?
  • 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

  • Type of Submission

  • What Skill Level is this Best Suited for?
  • 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

  • Type of Submission

  • What Skill Level is this Best Suited for?
  • 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

  • Type of Submission

  • What Skill Level is this Best Suited for?
  • 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

  • Type of Submission

  • What Skill Level is this Best Suited for?
  • 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

  • Type of Submission

  • What Skill Level is this Best Suited for?
  • 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

  • Type of Submission

  • What Skill Level is this Best Suited for?
  • 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


  • No labels