Orchestration and Management for Edge Application with ONAP

Transcription

1 Orchestration and Management for Edge Application with ONAP Haibin Huang, Intel OTC Yan Yang, China Mobile Shane Wang, Intel OTC OpenStack Berlin Summit, Nov. 14

2 Agenda - Akraino Edge Stack - ONAP VNF/CNF Orchestrator - StarlingX Infrastructure as a Service - Close Control Loop for Network Automation - Hardware Platform Awareness - vcpe as an example 2

3 Akraino 3

4 What is Akraino? Everything about Edge Akraino is the Edge Stack Development of Edge Applications Develop Edge applications and create an app/vnf/cnf ecosystem Development of Edge Middleware and API Development of Edge API, Middleware, SDKs Cross Platform Interoperability (3 rd party clouds) Fully Integrated Open Edge Stack Fully integrated, working Edge blueprints Edge Stack Life Cycle CI/CD & Tooling Upstream collaboration 4 3

5 Akraino Edge Stack Akraino GUI Dashboard Admin GUI User GUI Akraino Chest Akraino Workflow Platform Workflows Camunda Edge Application and APIs Edge Application and Orchestration APIs Applications & VNFs/CNFs Lightweight Edge App Orchestration Edge APIs Any Edge Applications Community - TBD Edge Cloud(s) Integration APIs Akraino Upper Cloud Lifecycle Tools Declarative Configuration AI Tools box ETE Operations tools NFV Orchestration NFV & Domain Specific Orchestrator ONAP CICD ETE Security tools Edge Platform Software Infra Orchestration StarlingX Kubernetes Storage Network Control Plane Network Data Plane SDS(Ceph) Simple SDN SR-IOV Calico OVS-DPDK CNI AirShip Under Cloud Lifecycle Narad (Inventory) ETE Testing Framework (infra, UCP, VNF, App) Operation System Linux Flavor Clear Linux Network & Customer Edges Cruiser Tricycle Unicycle Satellite Rover Community PINC (N/W Orchestration) Documentation 3

6 ONAP 6

7 What is ONAP? The ONAP project was formed in March 2017 in response to a rising need for a common platform for telecommunication, cable and cloud operators and their solution providers to deliver differentiated network services on demand, profitably and competitively, while leveraging existing investments. 2+ years of Deployment Maturity at AT&T. Comprehensive: Design + Orchestration + Control + Policy + Analytics. Model-based design enabling self-serve capabilities for instantiation and closed loop automation. Open TOSCA model. Most Advanced Open Source Process & tool chain. Architected for ease of VNF insertion (SDK). 7

8 Introduction to ONAP FCAPS: Fault, Configuration, Accounting, Performance, and Security ONAP is a platform to orchestrate the lifecycle of VNFs/CNFs in an SDN. GUI, CLI, API ONAP is a composition of several (10+) applications. Service and Recipe Design Service Lifecycle Management FCAPS ONAP is divided in 2 main functional areas: design & runtime. Run-Time NFVI/VIM/External SDN controllers 8

9 VNF SDK ONAP Operations Manager Modeling (Utilities) Integration VNF Requirements VNF Validation Program ONAP Architecture External Gateway OSS/BSS ONAP CLI U-UI ONAP Portal ONAP External APIs Design-time (SDC) Resource Onboarding Service & Product Design Policy Creation & Validation CLAMP Dashboard OA&M (VID) Policy Framework DCAE Correlation Engine (Holmes) Run-time Service Orchestration Project MSB/DMAAP A&AI/ESR Common Services AAF OOF Change Management Design Design Test & Certification Multi-VIM/Cloud Infrastructure Adaptation Layer SDN-C (L0-L3 Controller) Application Controller (APPC) (L4-L7) Virtual Function Controller (VF-C) Logging MUSIC Others Catalog External Systems Network Function Layer VNFs Hypervisor/OS Layer OpenStack Commercial VIM K8S Public Cloud PNFs Private edge Cloud MPLS Private DC Cloud IP Public Cloud 9

10 ONAP Design Time - Onboarding Upload descriptive model of the virtual function (Heat, TOSCA) Validate, assign, license, certify virtual function Create catalog entry, assign data/metadata Distribute for instantiation SDC SO VF-C APP-C SDNC 10

11 ONAP Run Time Instantiate virtual functions. Lifecycle: start/stop/reset/scale up/scale down/configure Monitoring metrics. OpenStack Ocata Control loops. VF-C StarlingX UUI 1 SO Multi- Cloud 4.n SDNC WindRiver 11

12 StarlingX 12

13 What is StarlingX? New, top-level OpenStack* Foundation pilot project Software stack providing high performance, low latency, and high availability for Edge Cloud applications Aligned with the OpenStack Foundation Edge Working Group and the Linux Foundation Akraino Edge Stack Its R1 was released on Oct. 24, Growing community Inviting users, operators and developers to try out the software and participate in the community 13

14 StarlingX Architecture 14

15 Networking Automation: Design->Create->Collect->Analyze->Detect->Publish->Respond 15

16 ONAP Control Loop Design Time The core/main ONAP components involved in control loop are: DCAE, CLAMP, Policy, VF-C and SDC. A Control Loop does several functions: Collect data about VNFs/CNFs or VNF/CNF infrastructure Compute analytics based on collected data For open loop, send message to ticketing system for human intervention For closed loop, execute one of many actions to remediate the network condition For closed loop, detect that a network condition has been corrected through our actions 16

17 ONAP Control Loop Run-time Choose/create micro services sequence that makes the Control Loop Binding to a VNF/CNF in a Service Choose from pre-existing sequence Build a brand new sequence Generate model file (YAML and cloudify blueprint) to be distributed to run-time part of control loop (DCAE/CLAMP) 17

18 ONAP Control Loop Run-time Configuring the Control Loop Driven by the VNF/CNF (list of alarms, ) Configuring micro services parameters values (configuration policies) Configuring the action to be taken (operational policy) Trigger Deployment of the Control Loop Trigger API exposed by DCAE Lifecycle Management of the Control Loop Stopping/restarting/updating configurations Monitoring (status of the Control Loop) 18

19 ONAP Control Loop Run-Time Closed Loop Flow s Events/ Alarms DMaaP Collector (VES, SNMP, ) Docker/CDAP data1 Analytics Micro service x: TCA, Holmes, Analytics Micro service 1 Docker/CDAP datan DMaaP Analytics Micro service n Docker/CDAP DMaaP Signature Drools Policy PDP- POLICY engine DMaaP/REST Action DCAE Action Execution VNF Action s Action Execution App-C Action Execution SO 19

20 ONAP HPA Path: Policy OOF VFC MultiCloud 20

21 HPA for Performance Purpose HPA = Hardware Platform Awareness Describes a set of hardware features across orchestration and control domain software stacks Targets smarter hardware platform capability consumption Two key focus areas Detecting hardware platform capabilities Configuring hardware platform capabilities HPA requirements specification is part of the ETSI NFV Virtual Network Function Descriptor (VNFD) 21

22 Policy Policy Creation/Administrat ion Policy Distribution Policy REST APIs A&AI Custome r/partern Input REST APIs SDC REST APIs/Event Driven Policy Driven Decision & Enforcement Framework OOF "flavorfeatures":[ { "flavorlabel":"vcpe.vgmux", "flavorproperties":[ { "hpa-feature-attributes":[{ "hpa-attribute-key": "numvirtualcpu", "hpa-attribute-value":"4", "operator":"=" }, { "hpa-attribute-key": "virtualmemsize", "hpa-attribute-value":"8192", "operator":"=", "unit":"mb" "mandatory":"true", } ], "hpa-feature":"basiccapabilities", "architecture":"generic", "hpa-version":"v1" }, { "hpa-feature-attributes":[ { "hpa-attribute-key": "logicalcpupinningpolicy", "hpa-attribute-value":"dedicated", "operator":"=" } ], "mandatory":"true", "hpa-feature":"cpupinning", "architecture":"generic", "hpa-version":"v1", } ] } ] } } 22

23 OOF Homing OOF: ONAP Optimization Framework OSDF: Optimization Service Design Framework HAS: Homing Allocation Service VFC 5 1 OOF- OSDF 2 OOF - HAS Policy *4 AAI 3 MultiCloud 1. VFC sends out homing request to OOF(OSDF) containing resource info 2. OOF(OSDF) pulls all the related homing constraints from Policy 3. OOF(HAS) check AAI database to pull region(flavor) information 4. OOF(HAS) communicate with Multi-cloud to check cloud capacity (vims which fulfill the requirements) 5. OOF(OSDF) returns homing allocation solution to VFC 23

24 MultiCloud to support StarlingX ONAP Other Components MultiCloud Framework Plugin- Ocata Plugin- WindRiver Pluginvmware Plugin- StarlingX Ocata windriver vmware StarlingX 24

25 Edge Use Case: Can ONAP work with StarlingX under Akraino? Let s try out vcpe! 25

26 Network Enhanced Residential Gateway (NERG) The NERG specification splits the residential gateway into two distinct components: Bridged Residential Gateway (BRG) and Virtual Gateway (vg). LAN At Home BRG Logical Subscriber Link (LSL) Edge/Cloud Network vg Network functions and services, such as DHCP, NAT, WAN Relatively simple L2 switching device 26

27 Edge Use Case - vcpe Functions provided traditionally by RG are distributed between: On-site device (Bridged Residential Gateway BRG) Edge/Cloud-based component (Virtual Gateway vg) BRG Logical Subscriber Link (LSL) vg BRG-LAN Interface BRG-LSL Interface Logical vg-lsl Interface Logical vg-wan Interface 27

28 Edge Use Case: vcpe Virtual customer premises equipment (vcpe) is a way to deliver network services such as routing, firewall security and virtual private network connectivity to enterprises by using software rather than dedicated hardware devices. 28

29 Edge Use Case - vcpe From : NAT FW Media Server AAA -. Internet To : Simple GW Cheap Provider agnostic vaaa vfw vdlna - etc Edge Internet 29

30 Edge Use Case: vcpe DCAE (Collector) DMaaP SDNC Control Infrastructure ONAP OAM Neutron Network Data + Control Per Customer vdhcp Dynamic Host Config Protocol vaaa Authorization, Authentication, Accounting vdns + vpdhcp Home Network 1 BRG Emulator 1 (VPP) vg1 (VPP) Home Network 2 BRG Emulator 2 (VPP) vbng (VPP) vg MUX (VPP) vg2 (VPP) CPE Public Neutron Network Web Server 30

31 Environment at China Mobile Lab WindRiver OAM Network StarlingX Controller-0 Controller-1 Controller-0 Controller-1 Management Network Management Network Compute0 Compute1 Compute2 Compute0 Compute1 Compute2 Data Network Data Network 31

32 Engineering and Testing Status ONAP Casablanca (R3) is about to be released in the middle of Nov. HPA support is added. SR-IOV support as one of HPAs is just added. PoC to onboard vcpe with ONAP, StarlingX and SR-IOV is implemented and tested at local. Integration testing is ongoing at China Mobile ONAP Lab now. Another PoC is being demonstrated. StarlingX R1 is released in Oct. vcpe build from the source: see also 32

33 FlexRAN* onboarding with StarlingX and ONAP See Demo at Intel Booth Now FlexRAN is a reference implementation for Cloud enabled wireless access Virtual Network Functions DEMO: StarlingX enables Mobile Edge Computing (MEC) wireless workloads on Intel Xeon scalable processors using Intel AVX 512 and DPDK*. *Other brands and logo 33

34 Thank you! openstack OpenStackFoundation