ARC: Definitions and requirements
for SO/APP-C/VF-C discussion
Chris Donley
Date , 2017
Agenda
• Lingli’s presentation
• Review of ONAP Architecture Principles
• Definitions
• Goals/discussion questions
Proposed ONAP Architecture Principles (For Review – from May Developer meeting)

Support Complete Life Cycle Management of Software Defined Network Functions / Services


From VNF On-Boarding, Service Definition, VNF/Service Instantiation, Monitoring, Upgrade, to retirement
High Level of Automation at Every Phase of Life Cycle Management – e.g. Onboard, Design,
Deployment, Instantiation, Upgrade, Monitoring, Management, to end of life cycle:

Rich, User Friendly Design Studio to Capture Full Life Cycle Management (Recipes, Policy, Analytics,
etc.)

Common Approach to Manage Various Network Functions from Different Vendors

Standard templates for instantiations

Standard language for configuration

Standard Telemetry for monitoring and management

ONAP Platform is NF / Services / Product Agnostic (each service provider / integrator to use ONAP
to manage their specific environment with artifacts created via Design Studio)

Standard Interfaces for Integrating with External OSS / BSS / VNFM/ EMS systems

Standard interfaces / abstraction layer to support multiple infrastructure and network controllers

Maintain ONAP Platform Integrity while Evolving it to Target End State Vision

Maintain Platform Backward Compatibility with Every New Release
3
Definitions
• Orchestration - Wikipedia
- Aligning business request with applications, data, and infrastructure
• Service Orchestrator - Mulesoft
- The coordination and arrangement of multiple services exposed as a single aggregate service
• NFV Orchestrator (NFV-O) - Mehmet Ersue (ETSI NFV MANO Co-Chair at IETF 88)
- coordinates, authorizes, releases and engages NFVI resources
• on-boarding of new Network Service (NS), VNF-FG and VNF Packages
• NS lifecycle management (including instantiation, scale-out/in, performance measurements, event correlation,
termination)
• global resource management, validation and authorization of NFVI resource requests
• policy management for NS instances
• VNF Manager (VNFM) – Mehmet Ersue
- lifecycle management of VNF instances
• (including instantiation, scale-out/in, termination, etc.)
- overall coordination and adaptation role for configuration and event reporting between NFVI and the
E/NMS
• Controller - Margaret Rouse, Techtarget
- configure network devices and choose the optimal network path for application traffic
Goals and Questions
• Goals
- Flexibility for operator deployment
- Minimize impact to different
components (e.g. DCAE, A&AI)
• Some impacts to SO and possible
SDC
-
Minimize impact to VNF vendors
Align with ONAP charter
Capable of delivering for R1
Microservices-based
• Questions (Goals? Non-goals?)
-
Avoid replication of functionality?
ETSI MANO alignment?
Feature parity between APP-C/VF-C?
Modular? Well-defined interfaces?
Possible deployments
ONAP Controller – Option 1 (ONS starting point)
Service Orchestrator
New
Current APP-C NBI
APP-C
Os-Nfvo
VF-C
OpenStack/MultiVIM API
VNFs
Or-Vnfm
ONAP Controller – Option 2 (Jamil)
Service Orchestrator
New
Os-Nfvo
VF-C
New
APP-C
Or-Vnfm
APP-C as VNFM
OpenStack/MultiVIM API
VNFs
ONAP Controller – Option 3 (Vimal Option 2)
Service Orchestrator
Current APP-C NBI
APP-C
New
Os-Nfvo
VF-C
Or-Vnfm
OpenStack/MultiVIM API
VNFs
ONAP Controller – Option 4 (runtime selection)
Service Orchestrator
APP-C
VF-C
VNFs
ONAP Controller – Option 5 (runtime selection)
Service Orchestrator
APP-C
VF-C
VNFs