1. Defining ONAP VNF Package Model
30 June 2017
Andrew J. Mayer, Ph.D.
© 2016 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
AT&T Proprietary (Internal Use Only). Not for use or disclosure outside the AT&T companies except under written agreement.

2. What
Develop a common VNF Package Model (information model & TOSCA representation) for ONAP which will allow Service Providers to rapidly integrate VNFs into ONAP so that they can rapidly introduce capabilities to their customers and within their infrastructure
ONAP Architecture
Storage
Compute
VNFs / Applications
Networking
ONAP Portal
Design Functions
Operational Functions
E – Services BSS / OSS Big Data
External Data Movement & APIs
Data Collection & Analytics
Common Services, Data Movement, Access Control & APIs
Controllers Engineering Rules & Inventory
Service Orchestrator
Active & Available Inventory
Dashboard
OA&M Operation Administration & Maintenance
ONAP Controller
Recipe/Engineering Rules & Policy Distribution
Service Design & Creation
Analytic Application Design
Policy Creation

3. Why
Service Providers need to provide a clear and unambiguous abstraction of the Network Cloud so that VNFs can describe their infrastructure requirements in a common and consistent fashion.
Service Providers want to rapidly integrate VNFs into ONAP so that they can rapidly introduce capabilities to their customers and within their infrastructure.
Service Providers want to manage the entire lifecycle of VNFs within ONAP in a common way so that they can ensure orchestration, manageability and control of each VNF in an easily integratable and low cost way.
VNF Providers we want to know how to package and implement VNFs for any Network Cloud so VNF Providers can minimize cost and maximize value.
Model Driven approach: a cohesive way to have a shared view of information describing the VNF Package that can be used as input into a model driven process to enable automated on-boarding and lifecycle management of VNFs into the ONAP environment.

4. VNF SDK Project

5. VNF Package Model Within VNF SDK Project

6. VNF Package Initial Scope for Release 1

7. Related ONAP Projects VNF-SDK: VNF Package Creation
VNF-SDK: VNF Package Validation
VNF Requirements Project
VNF Validation Program (ONAP ICE)
Modeling Sub-committee
SD&C Project
Policy Project
Standards Coordination
Other projects that use VNF Package Info (APP-C, VF-C, DC&A, etc.)

8. High Level Project Plan For Release 1
Focus: Technical Requirements, Resource Metadata, Business Information, Fault and Performance
Analysis of current VNF Package Models and Requirements
Refine High Level Mindmap
Define UML Information Model for VNF Package (reuse existing models where appropriate, e.g. core node types from OASIS)
Define TOSCA Representation (build from OASIS effort)

9. Time Line M1 Project Scope 29 June M2 Functionality 3 August M3 API

10. Related Industry Activities
ETSI VNF Packaging Information Model
OPNFV On-Boarding
TM Forum ZOOM
TM Forum Multi-Provider VF On-boarding
ONAP VNF Requirements (particularly ECOMP & HEAT)
ONAP Open-O VNF Management Requirements & TOSCA Template
Open-O VNF Template
OASIS VNF Profiles
MEF TOSCA Guidelines
OSM (VNF Wizard, YANG)

11. VNF Package Mindmap (high level)

12. UML Model (example)

13. TOSCA (Example)

14. BACKUP MATERIAL
© 2016 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property.
AT&T Proprietary (Internal Use Only). Not for use or disclosure outside the AT&T companies except under written agreement.