Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

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 fragmented CNF conformance verification can be?

  • 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”).)

OPNFV, later CNTT and Anuket were formed with the idea in mind to decrease the integration costs of cloud applications and clouds. OPNFV intended to build integrated cloud stacks, at that time only based on OpenStack, which would become the de-facto cloud stacks of the telecom industry, so every VNF would know what to expect from it. OVP provided a verification program around it. The integrated OPNFV stack did not really become the de-facto cloud stack of telecom workloads and only a small number of NFVI or NFV vendors verified their solutions with OVP. Then CNTT was formed. The idea of CNTT was to specify the properties of the cloud stacks, this time both OpenStack and Kubernetes, and build a certification framework for clouds and their workloads. Then CNTT and OPNFV merged under the name of Anuket. OPNFV stacks became the Anuket reference implementations, the OPNFV test frameworks and tools used for the Anuket reference conformance program and OVP became Anuket Assured. During this time, CNCF started to build the CNF Testbed to test infrastructure capabilities needed for networking applications. CNCF created the CNF WG to define the characteristics of CNF and the CNF Testsuite implemented a set of CNF tests. In its Moselle release, the Kubernetes based reference architecture in Anuket adopted most of the application tests from the CNF Testsuite as application requirements. In KubeCon EU 2022 CNCF announced their CNF Certification program based on the tests defined in the CNF Testsuite.

All of this sounds confusing? It is because it is. In their talk Georg and Gergely will uncover the details of this story and the current state of CNF conformance verification. They will do this from a very selfish CNF vendor perspective to draw the attention to the issues of the current situation. At the last part of the presentation, the presenters plan to invite a set of key actors from the Anuket and CNCF CNF communities to discuss possible solutions to the problems addressed.

  • 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, but that only makes the CNF vendors life more difficult. This session attempts to explain the current situation and trigger a discussion to make this situation better.

  • 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, Olivier Smith  

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

  • Speaker info: Gergely Csatari , Riccardo Gasparetto 
    • 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

  • 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


A Day 1, 2 and 3 in the life on an Edge Computing Deployment

  • Speaker info: Beth Cohen and Gergely Csatari Ildiko 
  • 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 PTG the edge sessions are organized around the dependencies and requirements for successfully launching and managing edge architectures in the field. Each session over the three days builds on the requirements and actions needed 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. The nomenclature for these three phases is borrowed from the  telecommunications industry, but they are applicable on a much wider scale and many more industries. 

    • Day-n concept and how it applies to Edge outside of telecommunications context
    • 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 .

  • 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
  • No labels