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

OpenSourceSummit|2017.06.02|RedHat

Hyde SUGIYAMA

SeniorPrincipalTechnologistNFV|SDN|ICTRedHatAPACOfficeofTechnology

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

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

BBUpool

MULTI-SITE FOR TELCO

4

Customer site Distributed CO

Regional Data Center

Consolidated CO

1000servers~

<4km<20km(consolidatedopQcal),<100kmtwoQer

Access Network

Metro Network

Core Network

~2..20locaQons~10’s..100’slocaQons

100servers~

~1k..10k’slocaQons~10..100k’slocaQons

eNodeB(C-RAN)

~40km(CPRIFronthaul)

RRHco-locaQonspace

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

/ Lo

catio

n S

peci

fic N

etw

ork

AA

A

Dev

ice

/ Loc

atio

n S

peci

fic N

etw

ork

AA

A

CORD: Central Office Re-architected as a Datacenter M-CORD Mobile CORD R-CORD Residential CORD E-CORD Enterprise CORD

PON(PassiveOpQcalNetwork)WDM(WavelengthDivisionMulQplexer)Cu(Centralunit)DSL(DigitalSubscriberLine)HFC(HybridFiberCoax)

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.

EDGE COMPUTING USE CASE-2 ●  Mobile Edge Computing(MEC) at eNodeB node ●  Mobile Edge Computing at Mobile Packet Core node (vGiLAN,

MVNO, etc)

7

MEC APPLICATION USE CASE

8

KUBERNETES/OPENSHIFT Candidate PaaS for Container Applications in

Edge Computing

9

WHY KUBERNETES?

MEC NFVCloud CloudIaaS GCE Amazon Azure

ContainerPla_orm

ContainerApplicaQons

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

PaaS

10

DevOps

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

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

Externalaccess

Router

Policies

Logging

ELK

Volume

Service

12

PodtoPodVirtualNetwork

Networkplugins(Openshi`SDN,etc)

PodtoPodnetworkApplicaQonso`ware

projectbasedisolaQon

APIserver scheduler

controllermanager

MASTER Developer OperaQonsManagement

Toolsets

CI/CDSCM

External access

Dockerimage

Container

Pod PodC

kubeProxy kubeletWORKER / NODE

C C

Pod

K8s/OPENSHIFT NETWORKING

SDNforApplica.onDevOps-Awarenessnetworks

FW/LB

13

SDN controller

C Container

VIP

POD TO POD NETWORKING

14

Application DevOps awareness network

●  Service Providers; Google Compute Engine, etc 1.  Flannel2.  OVS(OpenVSwitch)3.  NuageVCS(VirtualizedCloudServices)4.  BigSwitchNetworksBigCloudFabric5.  Openshi`SDN(OVS,VXLAN)6.  OVN(OpenVirtualNetworking)7.  Calico8.  ConQv(naQveL3usingBGP,overlayvxlan,classicL2orCisco-SDN/ACI)9.  Contrail(JuniperContrail/OpenContrail)●  etc

15

MEC ADAPTATION K8s/Openshift on Openstack

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

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)

MEC REFERENCE ARCHITECTURE

17

ForEdgePla_ormasaService

OPENSTACKSHAREDSERVICES

K8s/OPENSHIFT ON OPENSTACK DockerimageContainerizedApplicaQons

K8s/OPENSHIFT

Master Nodes Registry

LBaaSv2(Octavia)

DNSaaS(Designate)

OrchestraQon(Heat)

Compute(Nova) Networking(Neutron) BlockStorage(Cinder)

FileStorage(Manilla)

HARDWARE

18

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,byenablingnaQveNeutron-basednetworkinginKubernetes.

KURYR CNI & KURYR CONTROLLER Kuryr-Kubernetes

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

20

K8s/OPENSHIFT ON OPENSTACK = MEC

21

Containers in Pod

MULTI-ACCESS EDGE COMPUTING PaaS for container applications

22

Containers in Pod

MEC ACROSS MULTI-CENTRAL OFFICES

23

Containers in Pod

Customer site Data Center

RRH

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

NetworkTrafficmanagement

Resourceplacement

Cross-cluster traffic distributer

Cluster Federation

BIMODAL ICT IN TELECOM INDUSTRY

25

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

THANK YOU

facebook.com/redhatinc

twitter.com/RedHatNews

youtube.com/user/RedHatVideos

plus.google.com/+RedHat

linkedin.com/company/red-hat