1. ONAP Architecture Slides Current Plan of Record

2. Topics
Reflections on current R2 Architecture and proposed modifications
RO and layered orchestration and further proposed modifications
Discussion on how to document the next level of detail

3. FUNCTIONAL Architecture for R2+
As presented in the Virt Dev Event
Portal
OPEN-O UI
(GUI/CLI)
Run-time
Dashboard OA&M
(VID)
External Data Movement & APIs
Design-time
A&AI
Service
Orchestration
SDC
UI Server
Service Design
ESR
VNF Design
Interface
Common Service
Resource Orchestration
(using ETSI terminology – will refine label)
Workflow Design
DMaaP
Auth.
Microservice Bus
Policy Creation
Analytic Application Creation
Interface
DCAE
Alarm Correlation (Holmes)
Policy
SDN-C
APP-C
gvnfm
Other?
Recipie/
Engineering Rules & Policy Distribution
Catalog
NFV-O NFV Collector
(Monitor)
Multi-VIM/MultiCloud
VNF SDK
Cloud & WAN
OpenStack
VMware
RackSpace
Azure
......
Consensus on layered architecture. This picture does not imply project structure.

4. FUNCTIONAL Architecture for R2+
Missing definitions and interfaces
FUNCTIONAL Architecture for R2+
Significance of color?
Comments/Reflections
Portal
OPEN-O UI
(GUI/CLI)
Run-time
Dashboard OA&M
(VID)
External Data Movement & APIs
Design-time
A&AI
Service
Orchestration
SDC
There are many interfaces not shown, but these are …
UI Server
VNF Design
Service Design
ESR
Interface
Terminology
Common Service
Resource Orchestration
(using ETSI terminology – will refine label)
Workflow Design
DMaaP
Auth.
Microservice Bus
Policy Creation
Looks like Resource Orch doesn’t apply to transport
There will be more DCAE services
Why dotted line?
Analytic Application Creation
Includes interface to s-VNFM (IFA
Interface
DCAE
Alarm Correlation (Holmes)
Policy
SDN-C
APP-C
gvnfm
Other?
Recipie/
Engineering Rules & Policy Distribution
Is this still the conclusion?
Impression that DCAE doesn’t go through multivVIM
Catalog
NFV-O NFV Collector
(Monitor)
Multi-VIM/MultiCloud
VNF SDK
Cloud & WAN
OpenStack
VMware
RackSpace
Azure
......
Consensus on layered architecture. This picture does not imply project structure.

5. FUNCTIONAL Architecture for R2+
1 set of proposed changes
Portal
OPEN-O UI
(GUI/CLI)
Run-time
Dashboard OA&M
(VID)
External Data Movement & APIs
Design-time
A&AI
Service Orchestration
SDC
UI Server
ESR
Needed?
Interface
VNF Design
Service Design
Common Service
Resource Orchestration
(using ETSI terminology – will refine label)
Workflow Design
DMaaP
Auth.
Microservice Bus
Policy Creation
Better Name?
Analytic Application Creation
DCAE
Alarm Correlation (Holmes)
Policy
Interface …
SDN-C
APP-C
gvnfm
Other?
Recipie/
Engineering Rules & Policy Distribution
NFV-O NFV Collector (Monitor)
Catalog
Multi-VIM/MultiCloud
VNF SDK
Cloud & WAN
OpenStack
VMware
RackSpace
Azure
......
Consensus on layered architecture. This picture does not imply project structure.

6. For Discussions – Resource Orchestration & reference to ETSI-MANO
ETSI MANO IFA 009 describes the VNFO has having two functionalities:
Network Service Orchestration
Management of Network Services templates and VNF packages: (note in ONAP this in SDC)
Responsible for connectivity between VNFs, PNFs and any nested NSs (when applicable) i.e. VNF FGs and VLs by calling the respective ROs.
Unaware of resources status in each administrative domain, it’s only aware of the resource capacity exposed by the various ROs.
Resource Orchestration
provides an overall view of the resources present in the administrative domain to which it provides access
hides the interfaces of the VIMs present below it.
regions/NFVI-Pop and resource groups defined by the various VIMs in the administrative domain are visible at the RO interface.
aware of the resource usage and availability in the NFVI, of the logical grouping of the resource requirements e.g. per the VNF.
acts only based on instructions from either the relevant VNFM or the relevant NSO, does not take decisions based on VNF instances or on NS instances
Uses the NSD
From IFA 009, Figure
Similarity with Multi-VIM Role

7. Orchestration Layered approach
Layered approach is beneficial.
It needs to be considered beyond cloud infrastructure though
Different domains each with services and resource orchestration.
Need to consider the descriptors for each domain.
Cloud Infra
Transport
Application Domains
E2E Global Service
Service Orchestration
Resource Orchestration
Application Domain Service Descriptor (no ref)
Network Service Descriptor (ETS)
Global Service Descriptor (no ref)
Transport Service Descriptor (no ref)
Application Domain Resource Descriptor s(no ref)
VFD?
Global Resource Descriptor (no ref)
Transport Resource Descriptor?
No Ref = No external reference

8. FUNCTIONAL Architecture for R2+
2nd set of proposed changes
Portal
OPEN-O UI
(GUI/CLI)
Run-time
Dashboard OA&M
(VID)
External Data Movement & APIs
Design-time
A&AI
Service Orchestration
Domain Service Descriptors
Domain Service Descriptors
SDC
UI Server
ESR
VNF Design
Service Design
Common Service
Resource Orchestration
Workflow Design
Domain Resource Descriptors
Domain Resource Descriptors
DMaaP
Auth.
Microservice Bus
Policy Creation
Analytic Application Creation
DCAE
Alarm Correlation (Holmes) …
Policy
Interface
SDN-C
APP-C
vnfm
Other?
Recipie/
Engineering Rules & Policy Distribution
NFV-O NFV Collector (Monitor)
Catalog
Multi-VIM/MultiCloud
VNF SDK
Cloud & WAN
OpenStack
VMware
RackSpace
Azure
......
Consensus on layered architecture. This picture does not imply project structure.

9. How to document Next Level of Details?

10. How to document next level of detail
Avoid reference point descriptions
Provide a high level definition of the function
Show providing interfaces
Show consuming interfaces

11. How to document next level of details
Function 1 Definition: A B C
Interface 1
Function 1
Provided Interfaces:
Interface 1: <interface name>
Short description
Interface 2: <interface name>
Interface N
Consumed interface Interfaces:
Interface name, from:
Consumed Models
Note: Can be more than one page