Multi-access Edge Computing & Openshift

Size: px

Start display at page:

Download "Multi-access Edge Computing & Openshift"

Adam Phelps
6 years ago
Views:

1 Multi-access Edge Computing & Openshift OpenShift Commons Briefing Red Hat Hyde SUGIYAMA Senior Principal Technologist NFV SDN ICT Vertical Red Hat APAC Office of Technology

2 WHO AM I? Hyde SUGIYAMA Senior Principal Technologist APAC Office of Technology, Red Hat Born in Yokohama, Age:52 Driving Technology partnership with Telco R&D and ICT Partners in Open Source NFV, SDN and Edge Computing domain. 29 years experience in the Information Communications Technology industry. (Service Providers: 14 years -> Juniper Networks: 10 years -> RedHat: 5 years) 2

3 AGENDA What is Edge Computing? OpenShift Edge PaaS Adoption OpenShift Edge PaaS PoC use case 3

4 Edge Computing 4 Edge Computing 2014 ( NTT R&D announced an Edge computing technology concept which can reduce the cloud application response time by factor of 100 at most, and demonstrated its first research outcome, the Edge accelerated Web platform prototype. Open Fog Consortium 2015: Cisco, ARM, Dell, Intel, Microsoft and Princeton University established OpenFog Consortium to promote and accelerate adoption of open fong computing. Mobile Edge Computing 2015: ESTI MEC ISG; Edge computing by placing compute resources on the edge of mobile network. ISG Name has been changed to Multi-access Edge Computing in Automotive Edge Computing 2017: DENSO, Ericsson, Intel, NTT and Toyota have initiated the formation of the Automotive Edge Computing Consortium which is tasked to develop an ecosystem for connected cars. It aims to support emerging services such as intelligent driving, the creation of maps with real-time data and driving assistance based on cloud computing.

5 MEC / Edge Computing Before IoT Edge devices, Automotive Edge devices, Mobile UE, Home Gateway and etc Cloud & Big Data Center Telco s Network Service 5

MEC / Edge Computing Edge Computing in Telco Central Offices IoT Edge devices, Automotive Edge devices, Mobile UE, Home Gateway and etc 6 Reduce Latency and bandwidth Data caching Data pre-processing

6 MEC / Edge Computing Edge Computing in Telco Central Offices IoT Edge devices, Automotive Edge devices, Mobile UE, Home Gateway and etc 6 Reduce Latency and bandwidth Data caching Data pre-processing Real-time CEP Industrial IoT, V2X Video analytics service Optimized local content distribution service Integration of Ent cloud service etc 3rd Party s AE(Application Entity) /CSE + SP s CSE(Common Service Entity) + Telco s NSE(Network Service Entity) Cloud & Big Data Center

7 Site / Location Specific Network AAA Device / Subscriber Specific Network AAA Telco Central Office (CO) Location Insensitive Mobile Subscribers Mobile ( 4G, 5G... ) Fixed Wireless (WiFi,... ) MNO s CO Mobile Packet Core BBU BBU BBU RRH Location Sensitive Fixed Subscribers FNO s CO OLT Core Network BNG Fixed Optical (xpon, WDM) Fixed Cu (xdsl, HFC) Fronthaul /Access Aggregation Network(s) Central Office Metro/Core Network IP/MPLS/Optical CORD / Virtual CO 7 MNO: Mobile Network Operator RRH: Remote Radio Head BBU: Base Band Unit CORD: CO Architected as Datacenter FNO: Fixed Network Operator OLT: Optical Line Terminal BNG: Broadband Network Gateway

8 Telco nodes Typical Central Office Outdoor in rural area 8 Base Station Base Station in Urban area

9 CO deployment options Rack space 9 Micro Pod Mini Pod Self contained ½ rack of equipment with Compute xx CPUs, Storage Up to 10 TB of local storage and Network connectivity WAN (Ethernet) 2 x 10GE ports (Hyper-converged node) Self contained 1-2 rack(s)of equipment with Compute xx CPUs, Storage Up to 20 TB of local storage and Network connectivity WAN (Ethernet) 2 x 10GE ports Small Pod (Typical Central Office) Self contained 5-10 rack(s)of equipment with Compute xx CPUs, Storage Up to 50 TB of local storage and Network connectivity WAN (Ethernet) 4 x 10GE ports

10 Central Office (CO) hierarchical design Big Data Center Centralized RAN/Cloud RAN CPRI Fronthaul (20km.. ) BBU hosteling EPC in Main CO Mobile Backhaul RRH Consolidated CO (Core small DC) Customer site Distributed CO (Edge mini /micro DC) Access ~ k s locations 10 Metro ~10 s..100 s + locations ~1k..10k s locations ( < 4km ) ( < 20 km consolidated optical ) < 100 km two-tier ( < 1000 km to closest) Core Network ~ locations RAN: Radio Access Network RRH: Remote Radio Head CPRI: Common Public Radio Interface BBU: BaseBand Unit EPC:Evolved Packet Core

11 Edge server co-location site is CO 11

12 Virtual Central Office demo at OPNFV summit 12

13 Fixed Network Operator s Edge PaaS solution DevOps Many open sources and Enterprise partner s applications Use cases; IoT Robotics V2X Video Analytics AR SmartCity etc 13

14 Framework and Reference Architecture (ETSI GS MEC 003) MEC Server 14 Deployment of MEC in NFV environment (ETSI GS MEC 017 draft)

15 Containerized enterprise application challenge for MEC in NFV environment 15

16 Edge PaaS possibility in Mobile (4G LTE Advanced Pro) Enterprise Service Domain Mobile Core site Mobile Edge Platform + Openshift on OpenStack Platform S1 interface 16 GiLAN / MVNO

17 Edge PaaS possibility - Edge Termination (4G LTE Advanced Pro) Mobile Core site Mobile Edge Platform + Openshift on OpenStack Platform S1 interface 17 GiLAN / MVNO

18 Flexible architecture for Multi-access Edge PaaS DevOps Many open sources and Enterprise partner s applications Use cases; IoT Robotics V2X Video Analytics AR SmartCity etc 18

19 Ingress enhancements for Edge PaaS Fixed Network Operator Mobile Network Operator SDN-C/ VNF-M SDN-C/ MEP-M Service A A A vbng Service A Service A A NFVI 19 N O D E 1 N O D E 2 Service A A A MEP Service A Service A A NFVI N O D E 1 N O D E 2

20 Edge Computing across multi-cos like a single DC Containers in Pod RRH Customer site 20 Data Center Distributed edge sites Core site

21 NTT NT Lab s Edge PaaS PoC - IoT Robotics(ongoing) vcpe: BNG, FW, Elastic Load Balancer, etc CSE in Infrastructure : IoT GW, AAA, etc User s AE: IoT Robotics controller (Edge DC) (Core DC) Service 1 Service 2 21 CSE(Common Service Entity) AE(Application Entity)

22 Carrier Edge PaaS strategy for Cloud Native service by NTT NT Lab & Red Hat 22

23 Potential Edge use case: Eclipse IoT projects -codestarter-red-hat-summit/ NFVI/MEC

Potential Edge use case: Connected Car 5G session at MPLS2016

24 Potential Edge use case: Connected Car 5G session at MPLS MPLS-Japan2016_Onishi.pdf 4G: Centralizing Big Data Center 5G: Exploring for Edge Computing deployment for Geo distribution 10 exabytes per month around

25 Edge PaaS in Red Hat NFV Stack (NSE) (NSE) (NSE) AE AE CSE CSE AE: Application Entity CSE: Common Service Entity NSE: Network Service Entity Smart NIC 25

26 Key Takeaways Keep flexible architecture in Telco Edge infrastructure by enhancing Ingress controller, in addition to Cloud infrastructure (AWS, GCE, Azure) OpenShift on OpenStack NFV in Mobile Network Operator s Edge Computing infrastructure OpenShift on OpenStack NFV in Fixed Network Operator s Edge Computing infrastructure B2B2X Cross-industry collaboration platform NTT NT Lab s Edge PaaS strategy session at OpenShift Commons Gathering, Dec 5th Austin TX 26

27 Q&A

28 THANK YOU plus.google.com/+redhat facebook.com/redhatinc linkedin.com/company/red-hat twitter.com/redhatnews youtube.com/user/redhatvideos

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

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