AGENDA Multi-access Edge Computing(MEC) use cases K8s/Openshift as - - PowerPoint PPT Presentation

▶
agenda
SMART_READER_LITE
LIVE PREVIEW

AGENDA Multi-access Edge Computing(MEC) use cases K8s/Openshift as - - PowerPoint PPT Presentation

Oct 10, 2023 473 likes •766 views

K8s(Kubernetes) and SDN for Multi-access Edge Computing deployment Open Source Summit | 2017.06.02 | Red Hat Hyde SUGIYAMA Senior Principal Technologist NFV | SDN | ICT Red Hat APAC Office of Technology AGENDA Multi-access Edge

slide-1
SLIDE 1

K8s(Kubernetes) and SDN for Multi-access Edge Computing deployment

Open Source Summit | 2017.06.02 | Red Hat

Hyde SUGIYAMA

Senior Principal Technologist NFV | SDN | ICT Red Hat APAC Office of Technology

slide-2
SLIDE 2

AGENDA

  • Multi-access Edge Computing(MEC) use cases
  • K8s/Openshift as candidate for Edge PaaS in MEC
  • Adapting to MEC - K8s/Openshift on OpenStack
  • Conclusion
slide-3
SLIDE 3

WHAT IS EDGE FOR YOU?

  • Regional Data Center ?
  • Network access node, core node(Telco Central Office) ?
  • eNodeB, Mobile Packet Core node(Telco Central Office) ?
  • CPE at customer site ?

3

slide-4
SLIDE 4

BBU pool

MULTI-SITE FOR TELCO

4

Customer site Distributed CO Regional Data Center Consolidated CO

1000 servers ~ < 4km < 20 km (consolidated opQcal ), < 100km two Qer Access Network Metro Network Core Network ~2..20 locaQons ~10’s..100’s locaQons 100 servers ~ ~1k..10k’s locaQons ~10..100k’s locaQons eNodeB(C-RAN) ~ 40 km (CPRI Fronthaul ) RRH co-locaQon space

slide-5
SLIDE 5

MULTI-ACCESS NETWORKS

5

Telco Central Office

Fixed Cu (xDSL, HFC) Fronthaul /Access Aggregation Network(s) Metro/Core Network IP/MPLS/Optical Fixed Optical (xPON, WDM) Fixed Wireless (WiFi,..... ) Mobile ( 4G, 5G... ) Location Sensitive “Fixed” Subscribers Location Sensitive “Mobile” Subscribers Site / Location Specific Network AAA Device / Location Specific Network AAA CORD: Central Office Re-architected as a Datacenter M-CORD Mobile CORD R-CORD Residential CORD E-CORD Enterprise CORD

PON(Passive OpQcal Network) WDM(Wavelength Division MulQplexer) Cu (Central unit) DSL (Digital Subscriber Line) HFC (Hybrid Fiber Coax)

slide-6
SLIDE 6

EDGE COMPUTING USE CASE-1

  • Residential vCPE

service at CO/DC

  • Enterprise vCPE/

Universal CPE* service at customer site(replacement of SD-WAN) and CO/DC

6

* Universal CPE is out of scope in this session.

slide-7
SLIDE 7

EDGE COMPUTING USE CASE-2

  • Mobile Edge Computing(MEC) at eNodeB node
  • Mobile Edge Computing at Mobile Packet Core node (vGiLAN,

MVNO, etc)

7

slide-8
SLIDE 8

MEC APPLICATION USE CASE

8

slide-9
SLIDE 9

KUBERNETES/OPENSHIFT

Candidate PaaS for Container Applications in Edge Computing

9

slide-10
SLIDE 10

WHY KUBERNETES?

MEC NFV Cloud Cloud IaaS GCE Amazon Azure Container Pla_orm Container ApplicaQons

Universal Edge service platform Application can be run Anytime Anywhere selected by user!

PaaS

10

DevOps

slide-11
SLIDE 11

Open Source platform Portable:

Public, Private, Hybrid, Multi-cloud, Bare metal

Extensible:

Modular, Pluggable, Hookable, Composable

Self-healing:

Auto-placement, Auto-restart, Auto-replication, Auto-scaling

Strong ecosystem

KUBERNETES

CONTAINER ORCHESTRATION AT SCALE

11

slide-12
SLIDE 12

Kubernetes

Cluster

WORKER

NODE

WORKER

NODE Registry MASTER Storage Pod Pod Pod Image

CORE CONCEPTS

  • Master(openshift master)
  • Worker Node(openshift node)
  • Pod (image -> Container -> Pod)
  • Service

Load-Balanced Virtual-IP (layer 4) Abstraction layer for your App Enables Service Discovery ○ DNS, ENV

  • Labels
  • Replication Controller
  • Router

Layer 7 LB /Reverse Proxy SSL/TLS Termination Name based Virtual Hosting Context Path based Routing Customizable (image) ○ HA-Proxy, F5 Big-IP etcd SkyDNS

Replication Controller

API Dev/Ops admin

External access

Router Policies Logging ELK Volume Service

12

Pod to Pod Virtual Network

slide-13
SLIDE 13

Network plugins(Openshi` SDN, etc) Pod to Pod network ApplicaQon so`ware project based isolaQon

API server scheduler controller manager MASTER

Developer OperaQons Management Toolsets CI/CD SCM

External access

Docker image Container Pod

Pod

C kube Proxy kubelet WORKER / NODE C C

Pod

K8s/OPENSHIFT NETWORKING

SDN for Applica.on DevOps- Awareness networks

FW/LB 13

SDN controller

C

Container

VIP

slide-14
SLIDE 14

POD TO POD NETWORKING

14

Application DevOps awareness network

  • Service Providers; Google Compute Engine, etc
  • 1. Flannel
  • 2. OVS(Open VSwitch)
  • 3. Nuage VCS (Virtualized Cloud Services)
  • 4. Big Switch Networks Big Cloud Fabric
  • 5. Openshi` SDN(OVS, VXLAN)
  • 6. OVN(Open Virtual Networking)
  • 7. Calico
  • 8. ConQv ( naQve L3 using BGP, overlay vxlan, classic L2 or Cisco-SDN/ACI )
  • 9. Contrail (Juniper Contrail/OpenContrail)
  • etc
slide-15
SLIDE 15

15

MEC ADAPTATION

K8s/Openshift on Openstack

OpenStack and Kubernetes better together: http://superuser.openstack.org/articles/openstack_kubernetes_better_together/

slide-16
SLIDE 16

16

MULTI-ACCESS EDGE COMPUTING(MEC)

Can become a major use case for Containerized VNFs (IoT, etc ) Opens for new services and development models in different market verticals (e.g. Edge PaaS for some of the IoT gateway functionalities)

slide-17
SLIDE 17

MEC REFERENCE ARCHITECTURE

17

For Edge Pla_orm as a Service

slide-18
SLIDE 18

OPENSTACK SHARED SERVICES

K8s/OPENSHIFT ON OPENSTACK

Docker image Containerized ApplicaQons K8s/OPENSHIFT Master Nodes Registry LBaaSv2

(Octavia)

DNSaaS

(Designate)

OrchestraQon

(Heat)

Compute (Nova) Networking (Neutron) Block Storage (Cinder) File Storage

(Manilla)

HARDWARE

18

slide-19
SLIDE 19

NEW PROBLEMS AT NETWORKING SETUP

19

  • OpenStack VM-to-K8s Pod data-plane performance
  • Double-tunneling will have negative impact on data-

plane performance (e.g. Kubernetes ‘flannel’ tunnel encapsulated in OpenStack ‘vxlan’ tunnel when running Kubernetes on top of OpenStack).

SoluQon : Kuryr-Kubernetes, by enabling naQve Neutron-based networking in Kubernetes.

slide-20
SLIDE 20

KURYR CNI & KURYR CONTROLLER Kuryr-Kubernetes

http://superuser.openstack.org/articles/networking-kubernetes-kuryr/

20

slide-21
SLIDE 21

K8s/OPENSHIFT ON OPENSTACK = MEC

21

Containers in Pod

slide-22
SLIDE 22

MULTI-ACCESS EDGE COMPUTING

PaaS for container applications

22

Containers in Pod

slide-23
SLIDE 23

MEC ACROSS MULTI-CENTRAL OFFICES

23

Containers in Pod Customer site Data Center RRH

slide-24
SLIDE 24

KUBERNETES FEDERATION - FUTURE

24

High Availability, Multi-Cloud, Multi-region, GEO locality to end users …….

MEC cluster in NFV

Customer

Reginal DC cluster Global DC cluster GCE,AWS MEC cluster in NFV Reginal DC cluster Global DC cluster GCE,AWS

Admin Network Traffic management Resource placement

Cross-cluster traffic distributer Cluster Federation

slide-25
SLIDE 25

BIMODAL ICT IN TELECOM INDUSTRY

25

slide-26
SLIDE 26

CONCLUSION

  • K8s/Openshift on OpenStack is adaptable to Edge

PaaS in Multi-access Edge Computing.

  • SDNs have to control traffic to;

○ Container in Pod, Container in Pod in VM(K8s on Openstack NFV) ○ ... Leaf/spine switch across multi DCs/COs

  • Many upstream projects in Kubernetes and etc

○ No need to create new feature spec from scratch for Multi-access Edge platform. ○ Evaluate existing upstream projects and find feature gap first.

26

slide-27
SLIDE 27

THANK YOU

facebook.com/redhatinc twitter.com/RedHatNews youtube.com/user/RedHatVideos plus.google.com/+RedHat linkedin.com/company/red-hat

slide-28
SLIDE 28