Versions Compared

Old Version 17

changes.mady.by.user Beth Cohen

Saved on

compared with

New Version 18

changes.mady.by.user Gergely Csatari

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Toc

Table of Contents
absoluteUrltrue

...

  • 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

...

?

  • Speaker info: Georg Kunz , Gergely Csatari 
  • Select a Track

  • Type of Submission

    • Panel or
  • 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.

...


  • 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 panel discussion the panelists will discuss how these two communities should 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 panelists will need to find 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.)

...

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. 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 presentationpanel.

  • Have you given this presentation before?

...

  • 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?

...

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

...

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

...