orchestration and management for edge application with onap · orchestration and management for...
TRANSCRIPT
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
Agenda
2
- 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
Akraino
3
4
Development of Edge
Applications
Development of Edge
Middleware and API
Fully Integrated Open
Edge Stack
• Develop Edge applications and
create an app/VNF/CNF
ecosystem
• Development of Edge API,
Middleware, SDKs
• Cross Platform Interoperability (3rd
party clouds)
• Fully integrated, working Edge
blueprints
• Edge Stack Life Cycle – CI/CD &
Tooling
• Upstream collaboration
What is Akraino?Everything about Edge – Akraino is the Edge Stack
3
Akraino Edge Stack
3
Akraino
Upper
Cloud
Lifecycle
Tools
AirShip
Under
Cloud
Lifecycle
Akraino Chest
AI Tools box
Declarative Configuration
Narad
(Inventory)
ETE Testing Framework
(infra, UCP, VNF, App)
ETE Security tools
PINC
(N/W Orchestration)
CICD
Admin GUI User GUIAkraino GUI
APIs
Applications & VNFs/CNFs
Edge Application and APIs
Lightweight Edge App
Orchestration
Edge Application and
Orchestration
NFV Orchestration
Edge Platform
Software
NFV & Domain Specific
Orchestrator
Edge APIs
Any Edge Applications
ONAP
StarlingXInfra Orchestration
Community - TBD
Edge Cloud(s) Integration
APIs
SDS(Ceph)
Kubernetes
Akraino Workflow CamundaPlatform Workflows
Cruiser Tricycle RoverUnicycle Satellite
Network Control Plane
Operation System
SR-IOV
Linux Flavor
OVS-DPDK
Clear Linux
CNISimple SDN
Network Data Plane
Calico
Storage
ETE Operations tools
Documentation
Network & Customer
Edges Community
Dashboard
ONAP
6
What is ONAP?
7
“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).
Introduction to ONAP
8
• ONAP is a platform to orchestratethe lifecycle of VNFs/CNFs in an SDN.
• ONAP is a composition of several (10+) applications.
• ONAP is divided in 2 main functional areas: design & run-time.
GUI, CLI, API
Service and Recipe
Design
Run-Time
Service
Lifecycle
Management
FCAPS
NFVI/VIM/External
SDN controllers
FCAPS: Fault, Configuration, Accounting, Performance, and Security
ONAP Architecture
9
Design-time (SDC)
Service & Product Design
Change Management Design
Design Test & Certification
VN
F SD
K
Dashboard OA&M (VID)
A&AI/ESR
Virtual Function Controller (VF-C)
Application Controller
(APPC) (L4-L7)
MSB/DMAAP
Run-time
Inte
gra
tio
n
External Systems
SDN-C (L0-L3 Controller)
Multi-VIM/Cloud
Infrastructure Adaptation Layer
CLAMP
VN
F R
eq
uir
em
en
ts
Mo
delin
g(U
tilit
ies)
VN
F V
alid
ati
on
Pro
gra
m
External Gateway OSS/BSS ONAP CLI U-UI ONAP Portal
ONAP External APIs
Resource Onboarding
Policy Creation & Validation
Catalog
Policy Framework
DCAE
Correlation Engine (Holmes)
Service Orchestration
Project
Common Services
AAF
OOF
Logging
MUSIC
Others
Network Function Layer
Hypervisor/OS Layer OpenStack Commercial VIM K8SPublic Cloud
VNFs
PNFs
Private edge Cloud
Private DC Cloud
Public Cloud
MPLS IP
ON
AP
Op
era
tio
ns
Man
ag
er
ONAP Design Time - Onboarding
10
SO APP-C
SDC
VF-C SDNC…
• Upload descriptive model of the virtual function (Heat, TOSCA)
• Validate, assign, license, certify virtual function
• Create catalog entry, assign data/metadata
• Distribute for instantiation
ONAP Run Time
11
• Instantiate virtual functions.
• Lifecycle: start/stop/reset/scale up/scale down/configure…
• Monitoring metrics.
• Control loops.
UUI SO
SDNC
VF-C
Multi-
Cloud
OpenStack
Ocata
StarlingX
WindRiver
……
1
2
3.1
3.2.1 3.2.2
4.1
4.2
4.n
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, 2018.
• Growing community
• Inviting users, operators and developers to try out the software
and participate in the community
14
StarlingX Architecture
Networking Automation:Design->Create->Collect->Analyze->Detect->Publish->Respond
15
ONAP Control Loop – Design Time
16
• 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
ONAP Control Loop Run-time
17
• 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)
ONAP Control Loop Run-time
18
• 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)
ONAP Control Loop Run-Time
19
VNF
DCAE
Collector(VES, SNMP, …)
Analytics Micro service n
Closed Loop Flow’s
Drools Policy
PDP- POLICY engine
Action Execution
App-C
Events/Alarms
Signature
Action
Action’s
Docker/CDAP
Docker/CDAP
DMaaP DMaaP
DMaaP/REST
Analytics Micro service 1
Docker/CDAP
DMaaP
datandata1
Action Execution
SO
Analytics Micro service x: “TCA”, “Holmes”, …
Action Execution
…
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)
22
Policy
Policy Driven Decision & Enforcement
Framework
Customer/Partern
Input
A&AI
Policy
Policy Distribution
REST APIs/Event Driven
REST APIs
REST APIs
OOF
Policy Creation/Administrat
ion
SDC
"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",
} ] } ] } }
"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"
} ],
23
OOF Homing
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
VFC Policy
OOF -
HAS
AAI
MultiCloud
①②
③
*④
⑤
OOF-
OSDF
OOF: ONAP Optimization Framework
OSDF: Optimization Service Design Framework
HAS: Homing Allocation Service
24
MultiCloud to support StarlingX
ONAP
MultiCloudFramework
Plugin-
Ocata
Plugin-
WindRiverPlugin-
vmware
Ocata windriver vmware StarlingX
Plugin-
StarlingX
Other Components
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).
BRG vGLAN WANLogical Subscriber Link (LSL)
At Home Edge/Cloud NetworkNetwork
functions and
services, such
as DHCP, NAT,
…
Relatively simple
L2 switching
device
Edge Use Case - vCPE
27
Functions provided traditionally by RG are distributed between:
• On-site device (Bridged Residential Gateway — BRG)
• Edge/Cloud-based component (Virtual Gateway — vG)
BRG-LAN
Interface
BRG-LSL
Interface
Logical vG-LSL
Interface
Logical vG-WAN
Interface
Logical Subscriber Link (LSL)
BRG vG
Edge Use Case: vCPE
28
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.
Edge Use Case - vCPE
29
• From :
• To :
Internet
InternetEdge
NAT –
FW –
Media
Server –
AAA - ….
Simple
GW
Cheap –
Provider
agnostic
vAAA –
vFW –
vDLNA -
etc
Edge Use Case: vCPE
30
Web Server
vDNS + vPDHCP
Infrastructure
Per Customer
Control
Data + Control
SDNCDMaaPDCAE(Collector)
ONAP OAM Neutron Network
Home Network 2
vAAAAuthorization, Authentication,
Accounting
vDHCPDynamic Host Config Protocol
vG1(VPP)
vBNG
(VPP)
Home Network 1 BRG
Emulator 1(VPP)
vG MUX(VPP)
CPE Public
Neutron
Network
BRGEmulator 2
(VPP)vG2
(VPP)
31
Environment at China Mobile Lab
Controller-0 Controller-1
Compute0 Compute1 Compute2
Management Network
Data Network
OAM NetworkWindRiver
Controller-0 Controller-1
Compute0 Compute1 Compute2
Management Network
Data Network
StarlingX
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
https://wiki.onap.org/display/DW/ONAP+vCPE+VPP-
based+VNF+Installation+and+Usage+Information
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
@OpenStack
Thank you !
openstack openstack OpenStackFoundation