Cloud Native Computing Foundation KubeCon + CloudNativeCon Europe 2022, 1 Jun 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Lightning Talk: Introducing O-Cloud, or How 5G Leverages Kubernetes - Nikolay Nikolaev

Description

Don’t miss out! Join us at our upcoming hybrid event: KubeCon + CloudNativeCon North America 2022 from October 24-28 in Detroit (and online!). Learn more at https://kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects.

Lightning Talk: Introducing O-Cloud, or How 5G Leverages Kubernetes - Nikolay Nikolaev, Juniper Networks

Raise the awareness of the applications of the Cloud Native technologies in the modern generations of the Radio Access Network. Share the approach that the O-RAN Alliance is taking to solve the high demands towards the platform that handles the critical workloads with significant impact to their business and our daily live.

A

Hello, my name is nikola miklev, I'm a senior staff engineer with juniper networks. Currently, my focus is to the application of the cloud native technologies within the delco domain, and today I'm going to talk to you about the open run and how it adopts kubernetes. Let's start the modernization of the way we do. Networking started about 15 years ago with the introduction of the software defined networking and when this trend was combined with the concept of virtualization of the hardware resources uh the networking function.

A

Virtualization was about the nfv it allowed for running specialized networking workloads on top of the commodity hardware, like cpus memory and network interface cards, the rising proliferation of cloud native technologies in principles created a new wave of networking virtualization the clarification of the networking domain allowed for building currently scalable applications and creating closely coupled systems that are resilient, manageable and observable.

A

This is a direct quote from the cncf's cloud native definition, but my favorite part of these qualities make high impact changes frequently and predictably, with minimal tile. This is a huge game changer for the networking quote where typically, a new software rollout can take months.

A

While all of this was happening, the telecom industry kept running through the newer and newer generations of their networking, architectures 3g 4g, but when 5g was introduced, it proposed various new use cases such as self-driving cars and e-health.

A

This puts huge demand on the flexibility of the underlying infrastructure, where virtualizing networking functions was a natural fit, but adding the cloud native principles in the mix makes it even more appealing to the telcos to adopt let's zoom a bit. Atelico network is typically split into the core network: radio access network or run and uh the back home, uh which we call the infrastructure that connects the core and around while the core network was a relatively natural fit for the nfvm codification.

A

The radio access network was typically more rigid and hard to revolutionize, yet people started looking at it and in an attempt to align its implementation with any vm clarification trends. So that's how in 2018 the open run alliance was born. It defines the standardized logical architecture of the radioaccess network and the interfaces between its components. It also defines various splits or functionality distributions across physical and cloud instances to facilitate this design. The operon alien alliance defines 10 work groups.

A

What is most important here is work group 6, which is the clarification and orchestration, and it's this way group 6 to drive the decoupling of run software from the underlying hardware platforms and to produce technology and reference designs that would allow commodity hardware platforms to be leveraged for all parts of the radio access network deployment sounds familiar right.

A

The platform that hosts the software and hardware to implement the operon architecture is called old cloud. It comprises cpus memory, storage, other accelerators, such like fpgas and dpus, and the relevant networking infrastructure.

A

The specification does not mandate how the workloads that leverage these resources are orchestrated, one can run bare metal, workloads or virtualized, vnfs and, of course, container icns. However, the adoption of the cloud native principles is very appealing to the devops teams in the telco industry too. The flexibility that this approach brings allows for a tremendous change in the way the infrastructure is managed and operated.

A

A single old cloud can host several on-premise kubernetes clusters can also occur. Public cloud management manage kubernetes clusters as well as other types of workloads. This puts interesting challenges to implement where kubernetes, orchestrated workloads need to be able to communicate with remote kubernetes clusters, bare metals and virtualized workloads.

A

One can imagine that such scenarios go well beyond the traditional cni networking, for example, and include technologies. Like you know, motors silv and the high performance dpdk communications as a group in the workgroup system. Looking into the management interface with kubernetes as a platform to host the cna floor clouds, its job is to define part of the so-called o2 interface, which will allow for seamless integration of service management and orchestration platform. The smo and the multitude of kubernetes is cluster, hosted in the all clouds that this smo manages.

A

There are certain challenges that are still to be resolved, uh such as the aforementioned networking challenges accessing the accelerators that we talked about, but also simple things such as. How do we manage namespaces? How do we handle our bug?

A

Maybe even volume mounts, for example, in a conclusion, I'd like to highlight that open run is a prominent platform for the future of modern telecommunications, but also it's an interesting use case for the cloud native technologies that it adopts the development of the technology evolution that is to be made within this seemingly initial work.

A

We have a serious impact on the rest of the cloud native community, so if you want to know more visit the link that is on the slide here. Thank you.