2. ONAP Architecture for Rel 1
should be aligned with VNF Guidelines and Artefacts … ?
ONAP User
ONAP Portal Admin
OSS/BSS
VNF SDK Onboarding
SDC
Portal
Design Studio
Distribution Service
Service Order Requests
Service & Resource Artifacts
VNF & Network Requests
Modelling
AAI
Service Orchestrator
Policy ?
Inventory
SDN-O
NFV-O
Create/Update Cloud Virtual Resources
Assign/Configure Network Resources
DCAE
Assign/Configure VNF/Application Resources
MSO metrics collection and fault monitoring
SDN Controller
OpenDaylight
APP Controller
OpenDaylight
Data Collector
Fault Collector
Infra Controller
OpenStack
3rd Party SDN-C
vRouter
SO Tosca Based
NFVO:
Tosca Recipe execution
Cloud Infra Instantiation
VNF VM
Switch
App
vSwitch VM VM VM VM
Cloud
Network
Application/VNF

3. Service Logic Interpreter & AdaptorsSO SO
NFVO
VF C
App C
App C
Service Logic Interpreter & Adaptors
NFVO
VNFM
Infra
Infra
VNF
VNF
VNF
VNF
DCAE
DCAE
Pro:
Simpler integration of Open-O
Con:
difficulties to keep 2 Controllers functionally aligned (SDC, VNF Guidelines, artefacts …)
Overlapping functionalities between the controllers (APIs, adapters, workflow engine, languages…)
Pro:
Integrated architecture with minimal overlap
Best of breed components
Single VNF Guidelines and reduce VNFM/EM dependency
Con:
More work on initial integration & APIs