Cloud Native Computing Foundation Cloud Native + Open Source Virtual Summit China 2020, 11 Sep 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Intro: Birds of a Feather: Telecom User Group - Dan Kohn & Taylor Carpenter

Description

Don’t miss out! Join us at our upcoming events: EnvoyCon Virtual on October 15 and KubeCon + CloudNativeCon North America 2020 Virtual from November 17-20. Learn more at https://kubecon.io The conferences feature presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.

Intro: Birds of a Feather: Telecom User Group - Dan Kohn, Cloud Native Computing Foundation & Taylor Carpenter, Vulk Coop

CNCF hosts the Telecom User Group (TUG) for service providers and their vendors to discuss the adoption of cloud native technologies. The community is invited to join this birds-of-a-feather (BoF) session to discuss the status of various initiatives and white papers in this space as well as ideas, requirements and best practices to continue moving forward. Updates and discussions about the CNF Conformance testing initiative which provides visibility into how well Cloud native Network Functions (CNFs) and the underlying Telecom platform follows cloud native principles

https://sched.co/cpAM

A

Welcome and thank you for joining this session, I'm taylor carpenter with full co-op, I'm going to give an introduction to cncf's telecom initiatives on behalf of the cloud native computing foundation and dan khan. It's vp of strategic programs and the general manager of lf public health.

A

Currently there's three telecommunication focused initiatives within cncf, including the telcom user group, the cnf test fed and the cnf conformance initiative.

A

They all share the goals of helping telecom operators and developers in navigating the cloud native and open source landscape to obtain the benefits touted by cloud native technologies.

A

The telcom user group is a place for operators, vendors and telecom developers who are using our aim to use cloud native technologies to share their ideas, experiences, ask questions and voice their concerns and needs.

A

It's not expected that software development will occur within the telco music group, but it may write up documents covering requirements, best practices and tips that it's learned.

A

The telecom user group started as birds of a feather meetings in barcelona and shanghai during 2019 in a sense moved to once a month. Zoom calls and online conversations in slack and emails.

A

The testbed initiative is an open source platform tool chain and set of examples that supports reviewing the different emerging cloud native technologies within the telecom domain, supporting reproducing its test results and use cases, as well as building new prototypes and reference examples.

A

The third and newest initiatives is cnf conformance, it's an open source test, suite that supports validating cloud native network functions or cns, as well as telecom platforms, adherence to cloud native principles.

A

It helps to provide test results for the cns and the telecom platforms, which attest to operators to help them identify solutions which are observing cloud native capabilities and principles which are important to those telecom operators themselves.

A

It also helps to help cnf developers in demonstrating conformance to cloud native best practices and provide tools and feedback for those developers to improve their technology.

A

There's public telecom focused meetings, including the telcom music group's monthly meeting, which occurs at 1500 and 1100 utc, alternating monthly, with the next call on monday august 3rd at 1500. Utc there's also a weekly meeting on thursdays for the cnf conformance and testbed, which is a technical meeting occurring at 1400 utc.

A

In addition to those meetings, there's also a mailing list for the telcom user group, public cncf slack channels- and you can reach me directly via email at taylor, vault, co-op or dan khan viadan linuxfoundation.org cncf is collaborating with other communities, including the linux foundation, networking and all of its initiatives and projects.

A

The cloud infrastructure, telco task force cnt, as well as the new platform as a service initiative, xg vela, which china mobile, is a part of, in addition to cncf's own special interest groups and projects, we'd love to have your feedback. We've created a survey we'll show this again at the end, a little bit more about the telecom user group.

A

There's currently quite a few members, including vendors and operators like nokia, swisscom, t-mobile, huawei, china, mobile.

A

As well as direct collaboration with other groups like cndt ovp, we're currently working to share requirements with cntt ras2, the kubernetes reference work, as well as the reference implementation, where things are shared from the cnf testbed on tooling, and we're also providing a cloud native checkbox for the cnt's rc2 program regarding documentation papers, there's been a white paper. The cloud native thinking for telecommunication created it's in the telco music groups github and there's contribution and references to the cloud native networking principles, papers.

A

This leads us to something important, that's being discussed, what is cloud native and what does it mean for well cloud native, builds on existing principles and practices like devops processes, service-based architecture and agile software development, which may be familiar to many operators and telecom developers.

A

Cncf outlines some of these things in their cloud native definitions, including microservices, immutable infrastructure, declarative apis. These allow high impact changes frequently. Predictably, you can do things like moving security patches safely to production.

A

And the cloud native networking principles papers go in more depth on all of these principles and provide extensive references and allow you to ask questions and answer them, such as how are cloud native systems loosely coupled? How do you provision immutable infrastructure and how do you configure these cloud native systems as well as what are the underlying properties and principles?

A

This leads us to what is a cloud native networking function? Well, a cloud native network function is a cloud native application which implements network functionality.

A

We expect it to then follow cloud native principles like using microservices having immutable infrastructure having declarative apis and configuration using a repeatable deployment process.

A

Likewise, a telecom platform that is itself cloud native should follow these principles, providing service discovery, declarative configuration and resiliency for the workload and platform itself.

A

The cnf testbed, which has contributors like cisco, intel, samsung nokia, the fdio project from lfn.

A

Contributes to this open source initiative, which helps us review cloud native technology.

A

You can think of the cnf testbed as an innovation review tool.

A

It helps review this software by supporting different technology options, keeps things as simple as reasonably possible so that you can understand the different components and use upstream community tooling, like cubespray and nfebench, so that you can become familiar and we can provide bug, fixes and things we've learned to those upstream projects and of course it tries to follow cloud native principles as much as possible.

A

This goes all the way from hardware up through all the levels. So we try to focus on immutable hardware, providing configuration that saved inversion control even for the underlay network.

A

Bootstrapping is repeatable from the hardware all the way up through the workload, and then we try to highlight gaps that are missing and anaben procedures that had to be used, and then we try to find technology that can solve those out-of-bound procedures and we highlight any technology that meets cloud native principles.

A

It's fully repeatable in packet from hardware all the way up through the workload it uses, helm and cube. Cuddle for use cases cube spray, the kubernetes project, and we try to use kubernetes native replacements as much as possible.

A

Examples go from very minimal, simple things that you can try to see how technology is used all the way through service, chaining and use cases.

A

Some of the technologies that are demonstrated include network service, mesh, different cni's, different topology and pneuma cpu managers.

A

You can replicate this using the published code in the cnf testbed with an api key from packet.

A

If you package your own network function in containers, you should be able to run it in the testbed we'd, be happy to accept pull requests for improvements in the tool chain to add support for your own lab other cloud providers, as well as new use cases and examples.

A

The cnf conformance contributors include different vendors and operators.

A

This open source test suite is showing and focused on how well cnfs and platforms follow cloud native principles. It's based on the kubernetes conformance program, which is not only open source but focuses on self validation. So anyone can download and use this suite with your own cns and platforms.

A

We've organized the test into categories which we find helpful for discussion, including configuration life cycle, upgradeability, scalability and resilience. The different cloud native principles and capabilities are the tests that are covered that are within these categories.

A

These categories cover both platform and workload tests.

A

When we take a look at the workload tests, the first set that we've covered are part of these categories, including microservice security like privileged mode configuration looking at liveliness and readiness check upgradeability, as well as resilience where we look at stuff like chaos, testing, where we expect the workloads to continue to function if one of the nodes goes out or a pod on the platform conformance side, we're focused on kubernetes-based platforms and we expect to test a reference: cntt kubernetes reference requirements, direct feedback from operators and cnf developers, as well as the kubernetes community, best practice and collaborative principles themselves.

A

Some of those potential tests, in addition to kubernetes conformance, include horizontal, auto scaling capabilities include including hardware itself, where more nodes could be added as needed.

A

More resilience, testing, including intentional failures in nodes and verifying that if traffic and the signaling either fails or is under high load, that the data plane worklet will continue to function as expected,.

A

We also want to test not only the core platform but any type of add-ons for metrics, whether they're standardized kubernetes add-ons and whether or not they have network policies that are following the kubernetes network policies, so that you can use them together with all the other configuration.

A

We've included some cnf examples like coordinates envoy. A vpp based ip forwarder. Linker d is in progress. We have other examples that could be included in the future.

A

And when we get to using the cnf conformance suite, we have an extensive set of instructions and use this guide from a minimal set for cnf developer to quickly get started through extensive source based installation and usage for running individual tests or groups. We've outlined prereqs, we've shown how you can test using your own kubernetes cluster or how to deploy clusters that we use with our tool chain.

A

We've also included instructions for configuring and using cnfs with example, configuration files which you can copy and follow directly.

A

This is an example of how a test run would work for a cnf itself. If you ran all the tests, you should see the individual tests with pass or fill, and then a final score will be shown and all these results will go into a log file.

A

The scoring system itself consists of a summation of all the individual schools scores for the final score, which can be weighted for positive or negative, based on the importance and modified in an external yaml file. The test results themselves are saved into yaml configuration files. The summary, as well as all of the information for individual tests.

A

If you'd like to get involved, we have a contributing guide.

A

We have the installation and usage guide, which I mentioned before we'd be happy to receive pull requests for documentation, adding new cnfs or tests for both the platform and the workload.

A

If you can attend the upcoming meetings, there's a telecom user group on august 3rd, the weekly cnf test fit and conformance technical meetings august 6 at 14, 15., we'll also be speaking at kubecon eu on august 19th, as well as onees north america. On september 29th.

A

You can join us in the mailing list for telco music group on the cncs public slack channels. You can email me or dan khan directly. If you'd like to speak with dan khan, he's offered to speak. You can reach out to him on this calmly.

A

We'd love to have your feedback on how well this introduction to telecom initiatives, helped you, if you'd like to sign up for beta testing for cnf conformance and provide other feedback on how cncf can help you, as they see enough as a telecom operator or cnf developer.

A