Cloud Native Introduction
Balaji Ethirajulu
Ericsson Internal | 2018-02-21 5G is use case driven
Massive MTC Critical MTC
Enhanced MBB Fixed Wireless Access
Ericsson Internal | 2018-02-21 Mobile data trafficoutlook
Global mobile traffic outlook (EB per month)
160 In 2024, 25 percent of mobile 140 data traffic will be 120 carried by 5G
100 networks.
80
60
40
20 x5 Total mobile data
0 traffic is expected to 2014 2016 2018 2020 2022 2024 increase by five times
Ericsson Internal | 2018-02-21 5G – Cornerstones and role of open source
— Cloud Native / Microservices
— Automation
— Orchestration
— AI and AI driven Policy
Ericsson Internal | 2018-02-21 Ericsson Demo’s – Booth 401
— Enabling Edge Cloud.
— 5G Automation & Network Slicing
— Cloud native 5G Core & Exposure
— Cognitive OSS & AI/ML Platform
Ericsson Internal | 2018-02-21 Ericsson – Tutorial Highlights
— Cloud native Introduction – Balaji Ethirajulu
— Cloud native design principles / Architecture – Tamas Zsiros
— A Cloud Native Application Design, Opportunities & Challenges – Henrik Saavedra Persson
— Cloud native “Dual-mode 5G cloud core” and Network Exposure (Programmability) – Jitendra Manocha
— Cloud Container distribution /Distributed cloud - Sampathkumar Santhanakrishnan
— Demo – Show the configuration and installation of CCD/k8’S and also show a scaling on a Kubernetes cluster - Sampathkumar Santhanakrishnan and Russ Mahon
Ericsson Internal | 2018-02-21 ONS2019 Cloud Native Tutorial Principles & Architecture
Tamas Zsiros
Ericsson Internal | 2018-02-21 Cloud native values 5G relies on an evolving ecosystem
Evolved Evolved network connectivity, and architecture & application architecture architecture Increased automation & New SW packaging, orchestration support, Devices/Local NW Access Sites Distributed Sites National Sites Global Sites and SW LCM, new evolved hardware, assets to expose leads to shift in Application Cloud functionality between virtual infra and physical infra Management and monetization
Network Slices
Access, Mobility, Network Applications
Cloud Infrastructure
Transport
Ericsson Internal | 2018-02-21 Cloud native values
Speed Scale Efficient Performance operations and capacity
̶ Fast, low-cost ̶ Scale fast at low cost ̶ Automation, no-touch ̶ Optimized capacity introduction of from hundreds of users operations throughput and new services in to millions ̶ Legacy and resource utilization small scale new services ̶ Life-cycle independence (services/infrastructure)
Software development in fast-moving, independent and empowered teams
Ericsson Internal | 2018-02-21 Design principles Cloud native design principles
State optimized Orchestration and Agnosticity Decomposed SW Application resiliency design automation
A cloud native application Decomposition enables Change of metrics with Handling state tailored for Reduce or remove the need has to be agnostic to unified and flexible LCM regards to resilliency»: application context and for human intervention to underlying infrastructure » and better resource — Pets vs Cattle state/data type » decrease OPEX and increase speed»: — IaaS utilization » — HA achieved through — Separation of — Bare metal — Microservice distribution and fault application logic and — Internal scaling and architecture state load distribution — Kubernetes based isolation hadleld by CaaS CaaS — Independant lifecycle — Proper state storage management per to guarantee — Network level microservice performance automation through model driven management
Ericsson Internal | 2018-02-21 Cloud native application stacks
Cloud native Cloud native network App A network App B
App business logic App business logic Cloud native Cloud native network App C network App D
App business logic App business logic
Kubernetes based CaaS: Any
IaaS*: Any Kubernetes based CaaS: Any
Hardware: Any x86 Hardware: Any x86*
CaaS on IaaS CaaS on bare metal — CaaS LCM: similar to any IAAS workload — CaaS LCM: specialized tools (e.g. MaaS)
— Virtualization overhead (KVM, VMWare) — No virtualization overhead — Security: harder to get from guest OS to — Security: easier to get from host user space host kernel to host kernel space — Advanced container runtimes with improved separation, i.e. katacontainers Ericsson Internal | 2018-02-21 Cloud Native Application using Kubernetes CaaS
— Clusters of Nodes, Pods, Services
— The dynamicity applies on many layers Cloud Native Application — Containers, PODs “come and go” Applications Entry/exit and — Higher layers depend on the state of load balancing clusters on lower layers (downward K8S Service K8S Service Services dependency) POD is subject for LCM and scaling — Ideally, every layer should handle its P P POD POD POD downward dependency on its own without PODs O O affecting layers above (e.g. the application D D layer should not care whether the HW is K8S K8S K8S K8S K8S K8S K8S operational or not etc.) K8S Nodes Master Master Master Node Node Node Node — Kubernetes keeps track of (dynamic) cluster members and does general housekeeping VMs or physical around them (starting, stopping, upgrading, machines health checking, etc…)
Ericsson Internal | 2018-02-21 PCC and PCG -Micro-service Architectures Packet Core ”Data Model”
PCC PCG
Pluggable service functions
Controller IP address Registration allocation Session TDF and mobility SGW Controller Signaling session Business Logic Business termination Charging I/O support IP session
Cache-optimized Logging Configuration Performance Fault load balancing management management management Database O&M NBI/ONAP
Generic Services Generic Container as a Service (CaaS)
Ericsson Internal | 2018-02-21 Deployment configurations of cloud native applications VMs vs Containers in Telco space? Or rather: IAAS vs CAAS Technologies emerging: Kata Containers, FireCracker, gVisor… Workload isolation o (+ virtlet, KubeVirt…)
Compute performance
I/O performance o / (PCI-PT / SR-IOV) / (Bare Metal / SR-IOV)
LCM operation efficiency o The Kubernetes ecosystem is evolving rapidly and ETSI and Platform maturity / ecosystem ONAP are adopting it
VNF package & deployment size
Support for (using Kubernetes) cloud native design o VMs & IaaS Containers & CaaS Ericsson Internal | 2018-02-21 Multi VIM -Carrier supported CaaS
Management & Orchestration
NFVO
VNF A VNF B
Cloud native Cloud native App business logic App business logic VNF C VNF D
App business logic App business logic
Guest OS Guest OS
c c c c c c c c c c c c c c c c c c c c VM VM VM VM VM VM VM VM VIM K8S IaaS CaaS
Hardware Hardware
Ericsson Internal | 2018-02-21 Carrier supported CaaS deployed on top of an IaaS
Management & Orchestration NFVO
VNF VNF Cloud native A B VNF C
App business logic App business logic App business logic
Guest OS Guest OS c c c c c c K8S CaaS
VM VM VM VM VM VM VM VM VM VM VM VIM IaaS
Hardware Note: no direct mapping between VMs and containers Ericsson Internal | 2018-02-21 Isolation domains: CaaS deployed on top of an IaaS
Management & Orchestration NFVO
Isolation Isolation domain domain ”X” Cloud native Cloud native Cloud native ”Y” VNF A VNF B VNF C No Isolation App business logic App business logic App business logic
c c c c c c c c c c c c c c c c c c K8S K8S
CaaS CaaS
Kernel isolation Kernel isolation Kernel VM VM VM VM isolation Kernel VM VM VM VM VM VM VM VIM IaaS (incl. Host OS)
Hardware
Ericsson Internal | 2018-02-21 CaaS evolution –supporting container and hypervisor workloads
Management & Orchestration
NFVO
Cloud native Cloud native network App A network App B Cloud native Cloud native App business logic App business logic network App C network App D
App business logic App business logic
Guest OS Guest OS
VM VM VM VM VM VM VM VM c c c c c c c c c c c c c c c c c c c c K8S CaaS VM VM VM VM VM VM VM VM VM VM
Hardware
Improved separation via alternative KubeVirt gVisor container runtimes Ericsson Internal | 2018-02-21 VM VIRTLETS Cloud Native Applications in relation to NFV
Service Orchestration Service Orchestration
Resource Orchestration & NFVO DC Networking Automation
Network Service NS NS
EMS VNF VNF VNF VNF VNF VNF VNFM VNF Lifecycle Management
Container Infrastructure CaaS CaaS Mgr Management
IaaS IaaS Mgr Virtual Infrastructure Management
Infrastructure Infra Mgr Infrastructure Management
Cloud 2 Cloud 1
Ericsson Internal | 2018-02-21 Orchestration Key building blocks to deliver Cloud Native values
Cloud Native WoW and operations
Continuous Software Software Orchestration & Automation release distribution upgrade for K8s and Cloud Native NF´s 1 2 3
Acceptance Cloud Native NF´s Ericsson Customer 4 tests
6 5 K8S based platform Data Feedback collection
Any Infrastructure
Ericsson Internal | 2018-02-21 Conclusions
— 5G use cases rely on flexibility of cloud native — Cloud native transformation is a holistic chalenge — Application architecture — Cloud Infrastructure — WoW & Operations — Cloud native design principles — Agnosticity, disaggregation, resiliency, state optimized, automation — NFV ecosystem compatibility is key
Ericsson Internal | 2018-02-21 Cloud Native Application Design Opportunities & Challenges
Henrik Saavedra Persson
Ericsson Internal | 2018-02-21 Ericsson application development framework
Application development framework
Application specific services Reference Container platform, 2 1 K8s based Generic Services Mgmt. Application Data Security Network Mgmt Monitoring Management & Orchestration stack & Service Services Services Services Services Services 3 Mgmt. 2 functionality for Services and Applications 4 Application development & onboarding environment Common (platform 3 type/generic) services for reuse across applications
Application & Service development & onboarding Any K8s Cloud Platform 4 environment, tools, DR´s and 1 interface to CI/CD
Cloud Any HW Platform
Ericsson Internal | 2018-02-21 Reuse – what is new?
— Cloud native and MSA with the use of containers — High degree of service isolation
— Dependencies are limited to exposed interfaces
— Strict backwards compatibility — following semantic versioning
Ericsson Internal | 2018-02-21 Reuse – CNCF
— Emergence of CNCF has created a new starting point when looking for reuse
— CNCF landscape — Structures and provides a map of potential realization
— Transfer of value
Ericsson Internal | 2018-02-21 CNCF landscape – are we done now?
— Big risk of failure — Without a clear view of — Context — Needed use cases for a selected service
— Architecture even more important — Clearly defined architecture principles, design rules and guidelines — Guides the different service and functional needs
Ericsson Internal | 2018-02-21 Architecture first
— Identify needed use cases
— How realizations in CNCF fulfill the needs — Make the selection
— The architecture need motivates the selected realization — Allows reevaluation of the selection
— Continuous evolution of the architecture — New use cases — Could lead to new realization selection
Ericsson Internal | 2018-02-21 Architecture first - Service Mesh example
— Define core functional use cases — What value a service mesh adds to your architecture for CNAs — What principles are important
— Disconnected from a specific realization — without being compromised or influenced by support/lack of support from specific realization
— Then make the selection!
Ericsson Internal | 2018-02-21 Separation of conserns – enabler for telecom use cases
— Rare to find these addressed out of the box
— 3GPP and other telecom standard interfaces
— Minimize the in-house development of the commodity part — Internal representation should be separated — No forking from external representation — Use of provided backwards compatible and version-controlled interfaces — If not applied, possibility of reuse for domain specific use cases will be minimized — Example: — Prometheus and building support for exposing 3GPP compliant xml report files
Ericsson Internal | 2018-02-21 How to make the right selection
— Clear definition of needed use cases
— Maturity of the project — Fulfillment of use cases — Size of the community — Backwards compatibility — How to engage in the project — Follow — How these aspects are handled — Active role — Gives a snapshot view — Influence backward compatibility — Longer history gives a better picture — Feature evolution
— Not for free — Important to build up internal knowledge
Ericsson Internal | 2018-02-21 Not jeoperdizing architecture values
— Created with a specific context in mind — Best-in-class project — Deployment footprint — Might still fit poorly — Characteristics aspects — Selecting a less capable project — Better fit given the overall architecture — Typically independent goals — Overlap of functionality — Provides value within the scope it was designed for
— Bigger architecture scope — Wider end-to-end value — Provided without any conflicting aspects
Ericsson Internal | 2018-02-21 Security – some things cannot be left out
— Expected from open source — Securing communication — Centered around TLS and OAuth2 — Evolution of 3GPP moving to HTTP/2 — A valid evolution of the project
— Source code reuse — Security hardening part of the building process — Full responsibility and controlled by the in- house team — CIS-CAT
Ericsson Internal | 2018-02-21 Cloud native organization
— An even bigger organizational and cultural — Much more frequent releases change — Automate everything! — Simplify few tasks not possible to automate — Organization is often structured around — Even eliminates some team needs architecture and processes
— Traditionally bigger teams — Speed is key — Larger software projects — Any slow down impacts the — Responsibility for benefit from cloud native horizontal tasks
Ericsson Internal | 2018-02-21 Organizational acceptance of Open Source
— Build trust and acceptance within the organization
— Bigger issue in areas traditionally solved with proprietary implementations
— Same team structure and the responsibility — Constant validation crucial
— Wrongly assumed to be free
— Build competence — Dependent on the community makes the organization very vulnerable — Understanding the need for evolution Having the right in-house talents — Troubleshooting involved makes use of open source a success Ericsson Internal | 2018-02-21 Dual-mode 5G cloud core and network exposure
Open Networking Summit 2019
Jitendra Manocha Strategic Product Manager 5G Core 2019-04-03 Ericsson Internal | 2018-02-21 Ericsson 5G platform Dual-mode 5G Cloud Core
Ericsson Digital BSS Smooth network Ericsson Management & Orchestration evolution and deployment at scale Ericsson Radio System Ericsson Ericsson Cloud Cloud 5G Access 5G Transport Core Communication
Ericsson Cloud Infrastructure
Ericsson Network Services
Ericsson Internal | 2018-02-21 Why 5GC
Optimized interworking with 5G NR Enhanced service capabilities — Reduced signaling — Improved network slice isolation and security — Lower control-plane latency (NSSF) — Only standardized solution for NR Stand- — One Core for all access types (incl fixed) alone (SA)
Service Based Architecture (SBA) Enable new revenues — IT architecture principles — Target architecture for cMTC — Fast service creation on 5GC VNFs — Multiple network slices per device, enabling — Extensibility and reuse new use cases — Support for MTC use cases with non-SIM devices
Ericsson Internal | 2018-02-21 Service Based Architecture Each 3GPP NF may produce and/or consume one or more services capabilities (3GPP NF Services) through a 3GPP defined Service Based Interface(SBI). • Implemented using REST UDR UDM AUSF PCF NRF NSSF architecture style and Application Function (AF) HTTP/2 over TLS/TCP Nudr Nudm Nausf Npcf Nnrf Nnssf with JSON bodies. • Allows fast new service Namf Nsmf Nnwdaf Nnef creation • Extensibility and reuse AMF SMF NWDAF NEF • Flexibility, scale & speed of adding new services N4 Service Based Architecture
Service Based Interface (SBI)
NF A NF B UPF Request NF Service A1 NF Service A1 5G Producer Reply Consumer
Subscribe NF Service B1 NF Service B1 Consumer Notify Producer
NF Service Operation Ericsson Internal | 2018-02-21 Service providers’ challenges on the path to 5G
Be first Protect early Manage traffic Improve network with 5G investments growth needs efficiency CAPEX efficiency Future Existing overlay Core Core Network OPEX Network efficiency
Support 5G + Simplify Capture new Open-up network legacy operations 5G business capabilities to networks opportunities business partners Revenue Growth
Ericsson Internal | 2018-02-21 EPC and 5GC will co-exist for many years
Long tail of Dual-Mode Core - Older smartphones (5G EPC, 5GC) - IOT devices with long replacement cycles - Roamers Option 1 Option 3 Option 2 100% 90% 80% EPC-only devices 70% - 4G MBB 60% - 4G IOT LTE LTE/NR NR 50% - 5G/NSA 40% 30% 5GC (+EPC) 1 capable devices 3 20% 2 10% 0% Time
Ericsson Internal | 2018-02-21 4G 5G How Dual-mode 5G Cloud Core addresses the challenges
Challenges Ericsson’s dual-mode 5G Cloud Core proposition
Manage growth One core network to manage 4G and 5G traffic growth, with investment re-use with CAPEX – User plane with high capacity, scalability and flexibility to manage 5G high-peak rates efficiency – Highly resilient and flexible data storage for network slicing and distributed cloud use cases Optimized TCO Reduce OPEX One cloud native software platform for (5G) EPC and 5GC and operational – Simplify operations with automation and common O&M across all products inefficiencies – Flexibility to manage 4G and 5G traffic; automated lifecycle and services provisioning
Grow revenue Fast time to market for the launch of 5G services Revenue with agility growth – Network exposure capabilities with open APIs enabling a partner ecosystem for innovation and speed – Network slicing solution customizable per use case
Ericsson Internal | 2018-02-21 New product family for future networks - Delivering a dual-mode 5G Cloud Core solution
Solution highlights Cloud Core Data-Storage Manager DATA LAYER
Cloud Core Cloud Core — Single platform for (5G) EPC and 5GC functionalities. Cloud Core Cloud Core Resource Subscription Policy Controller Exposure Server — Cloud native/microservice architecture. Controller Manager
— Automated and simplified O&M. SBA architecture — High user plane performance and scalability. Packet Core Controller
— Network exposure capabilities for programmability. CONTROL PLANE
NR SA Packet Core Gateway LTE/NR NSA LTE USER PLANE GSM/WCDMA
Ericsson Internal | 2018-02-21 Inside Ericsson’s dual-mode 5G Cloud Core Cloud Core Data-Storage Manager
UDSF UDR Network Functions (NF) grouped per DATA LAYER
network services, allowing deployment Cloud Core Cloud Core Cloud Core Cloud Core Resource Subscription flexibility and a smooth evolution to 5GC. Policy Controller Exposure Server
Controller Manager Interworking Interworking with networks (e.g legacy HLR/AuC,IMS) NSSF NRF UDM AUSF PCF NEF
EPC NSSF HSS 5G-EIR PCRF SCEF — Cloud native 5GC NFs microservice based. SBA architecture Packet Core Controller — EPC NFs re-architected into cloud native with secured feature parity. TDF-C AMF SMF SMSF SGSN MME SGW-C PGW-C CONTROL PLANE — Fully interworking with legacy networks and NR SA — Packet Core Gateway NFs. LTE/NR NSA LTE USER PLANE TDF-U UPF SGW-U PGW-U GSM/WCDMA
5GC Network Function EPC Network Function
CAPEX OPEX Ericsson Internal | 2018-02-21 REVENUE Key enablers for 5G programmability
These building blocks fulfill the requirements of programmability, making the network responsive to the future needs of high agility, flexibility and extensibility.
1. Service-based 2. Cloud-native 3. Continuous Architecture (SBA) implementation and Integration and Continuous Delivery microservices (CI/CD) approach architecture
Ericsson Internal | 2018-02-21 Exposure – Big Picture
OTT Apps & Ecosystems Untrusted domain
AF AF B2B2D
Operator — Monetization of the network AF capabilities Trusted domain — Hide the complexity of Exposure underlying network
— Secure/controlled access of
Core Network Comm. Management Digital BSS Cloud Partner network to external application Resources Resources Resources Resources Resources Supplier functions
Ericsson Internal | 2018-02-21 Exposure evolution
Massive IoT: NB-IoT/Cat-M1 use cases. Example: Smart meters, 4G EPC Limited mobile broadband connected water, capabilities exposure event monitoring
eMBB and FWA use cases Example: Gaming use cases 5G EPC covering NSA-NR requiring high throughput
All types of use cases: mMTC, eMBB, Example: Edge computing use 5G Core cMTC. Full programmability potential: cases (requiring low latency) Exposing capabilities from any NF in 5GC like immersive video/AR/VR
mMTC, eMBB, cMTC use cases Example: AI/analytics 5G Core >>> assisted with advanced machine based closed-loop use cases learning, network slicing
Ericsson Internal | 2018-02-21 Cloud Core Exposure Server
Cloud Core Exposure Server Centralized API management and exposure Portal Security capabilities, enabling: Service APIs API Exposure Layer Composition — Standard and tailored APIs per Application 4G Ntw APIs 5G Ntw APIs applications and use cases Function SCEF NEF — The ability to open 4G and 5G Core Business logic Business logic network capabilities to third parties. (3GPP events, 4G dev. Prov.) (generic events, insights, 5G ntw services, 5G dev. prov.)
T4, S6t, Rx T6a SGi Nnef — Increased network automation SMPP S6m for operational efficiency.
SBA
New Network
revenue programmability 2G/3G/4G 5G
Read the Ericsson report: Programmability in 5G Core networks
Ericsson Internal | 2018-02-21 API Overview
Standard technical use cases (3GPP R15) 1. Application Function influence on traffic routing (Nnef_TrafficInfluence) 2. Event exposure* (Nnef_EventExposure) 3. PFD management (Nnef_PFDManagement) 4. Resource Management of Background Data Transfer * (Nnef_BDTPNegotiation) 5. AS Session with required QoS * (Nnef_ChargeableParty) 6. Change the chargeable party* (Nnef_AFsessionWithQoS) 7. Parameter provisioning* (Nnef_ParameterProvision) 8. Application triggering* (Nnef_Trigger)
Green field for innovation, new APIs are possible faster then ever,
Ericsson Internal | 2018-02-21 *APIs Available in 4G and enhanced in 5G Optimized data transfer for automotive
Massive data Car manufacturer 5G segment: Enhanced Mobile Broadband communication server Business model: B2B Operator’s customer: Car manufacturer
Use Case: Backgorund data transfer of massive data
Description: Group of connected cars can automatically download massive amount of car’s maintenance data during a Time specific time window.
Location area
Ericsson Internal | 2018-02-21 Key Take away
— Service Based Architecture is the change in right direction, specially when implemented using cloud native and micrioservice architecture. As it paves the foundation for the next generation core networks. — Dual mode core will enable operators and enterprises to save opex, capex and simplify the network capabilities to fuel the eco-system development. — Open APIs are enabling programmability, new capability from the network can be exposed faster than ever. — Co-innovation (Open innovation) is key to succeed in this area as many usecases have not been conceptualized yet.
Visit our booth to learn more and share your feedback, insights, ideas!!!!!!!
Ericsson Internal | 2018-02-21 Cloud Container Distribution
Solution Line Distributed Cloud Solution Area Cloud and NFV Infrastructure Business Area Digital Services Content
— Container Introduction & Customer Challenges
— High-level Product Overview
— Architecture, Networking
— Deployment Models and Packaging
— Summary
Ericsson Internal | 2018-02-21 Cloud Container Distribution
Container Introduction & Customer Challenges Containers The foundation for the next generation of applications
— Support cloud native applications implemented with a microservices architecture — Decoupled, separately scalable services that can have separate life cycle management — Faster deployment compared to Virtual Machine based spin-up
— Common standardized application deployment (Docker image format) — Provide complete environment needed for application to execute
— Optimize resource usage (CPU, memory, network)
— Integration with CI/CD
— Isolation model using Linux kernel features
— Container runtime & image formats open standards are governed by OCI (Open Container Initiative)
Ericsson Internal | 2018-02-21 Containers and VMs
VM VM VM
App 1 App 1 App 2
Bins/Libs Bins/Libs Bins/Libs
App 1 App 1 App 1 App 2 App 2 App 2 D Guest OS Guest OS Guest OS Bins/Libs Bins/Libs Bins/Libs Bins/Libs Bins/Libs Bins/Libs o Hypervisor c Host OS k Host OS e Server r Server Containers Virtual Machines
Ericsson Internal | 2018-02-21 Container Orchestration and Management
— Container Orchestration and Management support using containers at production scale
— Open source Kubernetes is the de facto industry standard
— Rich community of open source value add plug-ins and components — Through the governance of the Cloud Native Computing Foundation (CNCF) Ericsson Internal | 2018-02-21 Containers at Scale via Orchestration Kubernetes Worker-Nodes
Kubernetes Master-Nodes (HA config) Ericsson Internal | 2018-02-21 Customer Challenges
Navigating the Complexities Build Your Own • Navigating the complexities of the CNCF landscape • Working directly with open source requires • Selecting the components and plug-ins that support resources for building, testing, integration your use cases • Building and Packaging • Continuous addition of new components • CI/CD pipeline • Versioning and compatibility • No single standard Kubernetes installer Security • Hardening • Tracking vulnerabilities and patching Vendor Lock-in • Some commercial vendors require you to use their distributions for technical support, muting the benefits Operational of open source • Lifecycle tasks: backup, restore, upgrades, scaling • Metrics and Monitoring
Ericsson Internal | 2018-02-21 Cloud Container Distribution
High-level product overview Cloud Container Distribution (CCD)
Kubernetes Distribution Advanced Features Includes Best of breed plug-in Handpicked CNI plugins components Multiple Network Interfaces,… Leveraging standard interfaces
Various open source software Fast Lifecycle Management components Install / Uninstall Ansible, Helm, Docker registry, Prometheus,… Scale in/out Upgrade
Ericsson Internal | 2018-02-21 Design and Development Principles
Unmodified open source CNCF certification components Tested and validated with CNCF
Additional value-add components to complete a Kubernetes conformance tests telco-grade offering
“Upstream first” Flexible infrastructure Open source community participation: deployment options • Kubernetes Network SIG Image-Based, Pre-provisioned servers • Kubespray • Multus • Helm • And more
Ericsson Internal | 2018-02-21 Design and Development Principles
Robust CI/CD Agile Release Cadence All components bundled as a single package & put Agile release cadence for internal stakeholder through the robust CI/CD system tests. Explore possibility of such release for customers as well
Every Kubernetes upstream is system verified with the packaged components
CNCF E2E & Conformance tests Security Hardening 200+ CNCF Kubernetes E2E tests are verified every release Run vulnerability reports
200+ CNCF Conformance tests are verified every release Provide Telco grade security capabilities
Ericsson Internal | 2018-02-21 CNCF Cloud Native Landscape: CCD scope
Ericsson Internal | 2018-02-21 Cloud Container Distribution
Architecture, networking Enabling container workloads
Ericsson Cloud Container Distribution
Security Loadbalancing
Package Mgmt Robustness Ingress controller Container Ericsson Cloud Registry Container ID & Access Mgmt Monitoring Service Mesh Distribution configuration / LCM / License mgmt Kubernetes
Container Storage Networking run-time plug-ins plug-ins
Cloud infrastructure
Ericsson Internal | 2018-02-21 Flexible networking with CNI plugins
node1 node1
POD1 POD2 POD1 POD2
Multus Calico
eth0 eth0 eth1 eth2
— Primary CNI assumed by — Meta CNI enabling several Cloud Container Distribution network interfaces towards — Flat routed network using BGP application workload
Ericsson Internal | 2018-02-21 Performance (data path) VM Container VM Container
Container CNF CNF
CNF veth veth
iptables iptables K8s K8s Calico veth K8s Calico Passthrough
OVS SR-IOV iptables
DPDK VF
Openstack Openstack K8s K8s Networking Calico NIC NIC NIC Host
Ericsson Internal | 2018-02-21 Components Evaluation
Kubernete Layers Solution s network IPv6 Networks Note used Policies
L3 Many networks on Scalable, may integrate — Industry trends/Telco use Calico Yes Yes (IPinIP, cluster. BGP no with infrastructure. cases BGP) overlay — Technological advancements Many networks on the Supports multiple — Ex: microVMs, Service Multus Yes Yes L2 Mesh same cluster network interfaces
Macvlan No Yes L2 Direct networking
SRIOV No Yes L2 Direct networking
Many networks on L2 Flannel No No same cluster with (VxLAN) multi daemon
Ericsson Internal | 2018-02-21 CCD – Kubernetes & IPV6
— IPv4 networking supported from the beginning — Kubernetes added IPv6 (single stack only) option as an alpha feature with the 1.9 release — CCD team is working within the Kubernetes project, driving the system design and code contribution to bring the dual-stack IPv6 support to Kubernetes in a future release (expect 2020 H2) — In the interim, IPv6-only clusters are achievable with NAT64.
Ericsson Internal | 2018-02-21 Cloud Container Distribution
Deployment Options and Packaging Containers on BM vs in VM
› In the BM case all containers ‘share’ the same kernel and the same hardware elements (for example, network interfaces) › In the VM case isolation between different containers is provided by the hypervisor › Main differences: › LCM › Security and isolation › Performance / footprint VM BM › Machine configuration Cloud Native Network App Cloud Native CaaS Network App
Openstack, VMware, Public Cloud CaaS
Hardware Hardware
Ericsson Internal | 2018-02-21 Supported Deployments
Container-enabled NFVi Enables cloud-native introduction for all Cloud-native applications in 3PP infrastructure
Ericsson 3PP VM-based Cloud-Native Cloud-Native VNF(s) VNF(s) VNF(s) Ericsson Cloud-Native VNF(s) Ericsson NFVI CaaS (CCD)
CaaS (CCD)
IaaS (CEE, SDN) 3PP Infra SDI (HDS)
Ericsson & 3PP HW
• Integrated feature in Ericsson NFVI • Bundled with containerized Ericsson Applications • Supports automated deployment onto VMs with • Supports deployment onto pre-provisioned servers image-based deployment (IBD) meeting minimum specified system requirements
Ericsson Internal | 2018-02-21 Cloud Container Distribution
Summary Value Proposition
Readymade for Telco Deployment Flexibility “Out-of-the box” Telco-grade container Image Based Deployment - provides flexibility and resource optimization orchestration and management platform ready by re-using existing virtualization infrastructure to deploy clusters and for production workloads. orchestrate containerized Network Functions. Unique full stack cloud portfolio along with Pre-Provisioned Servers Deployment - deploy clusters on any underlying Ericsson applications/VNFs portfolio. Ability to hosts which meets the minimum system requirements. This provides provide end-to-end verified solution including greater degree of flexibility for the customers in choosing the container infra and VNFs infrastructure for their container solutions.
Install
Teard Deploy own
Upgra Monit Life Cycle Management de or Forward looking container technology Provides tools for installation, upgrade and CCD adds value to Ericsson NFVI solution by providing container other LCM operations. orchestration and management capabilities to the existing virtualized Installation toolkit can be used to configure solution. clusters with the included plug-in By providing a common container platform that can be leveraged by components. multiple customer use cases, it provides the means for Ericsson customers to move to the next generation of telco applications.
Ericsson Internal | 2018-02-21