1. 14 April 2016 Bryan Sullivan, AT&T
Model-Driven NFV (Models) Project
14 April 2016
Bryan Sullivan, AT&T

2. OPNFV’s Role and Needs for Models
OPNFV integrates upstream projects into a coherent platform for NFV
Starting from the infrastructure layer and up the management stack
OPNFV does not have an information model nor plans to establish one
We use running code and data models from OpenStack, ODL, etc
OPNFV relies upon upstream open source projects / components which
Expose/consume data via open APIs and adapters/translators
Have implicit models, but not maintained in formal model terms
Are intended to have limited scope (“do one thing”), yet …
April 2016
NFV World Congress

3. What’s this Model-Driven NFV project?
Information and Data Models for NFV are a hot topic, but somewhat theoretical or at least cloudy
This project intends to reduce the theory into practice, based upon existing examples and compatible open source projects, e.g.
OpenStack Tacker as used in the OPNFV SFC project
Clearwater IMS as implemented by Orange in the OPNFV vIMS Functest using Cloudify as VNFM
ODL Unimgr for MEF LSO
In the process we will clarify, assess, and promote
The role of various model representations (TOSCA, YANG)
Standardized models (e.g. TOSCA Simple Profile for NFV)
Configuration, lifecycle, and policy features that can be modeled
April 2016
NFV World Congress

4. So what’s in scope?
Any open source VNFM project that can be used as a test driver
Any standardized model representation supported by OPNFV VIMs or VNFMs, e.g. TOSCA for NFV and YANG
Any use case that can be modeled and run as a an OPNFV FuncTest scenario
Any model-able object related to VNF configuration, lifecycle, or policy
Modeling tools used in model and VNF development
April 2016
NFV World Congress

5. That’s a big scope… what’s the catch?
Model portability across VNFMs is assumed
VNFMs can internally translate models, if the VNF end-state is equivalent
We will focus on building a pipeline for use case testing that iteratively adds features under test
We will release test scenarios as the VNFMs develop support for them
We will focus a lot on cross-project, upstream, and SDO collaboration
April 2016
NFV World Congress

6. Some Upstream Projects in Scope
Tosca
Yang
OpenStack:
Heat-translator
Tosca-parser
Tacker (VNFD, more blueprints)
Murano (Mitaka)
App-catalog (blueprint)
OpenDaylight:
Controller MD-SAL
Yangtools
YangIDE
Unimgr for MEF LSO
XOS (e.g. samples)
YangForge (see L3VPN demo)
Cloudify (e.g. Clearwater IMS demo)
ONOS (proposed, based upon YangForge)
JuJu (
OpenContrail (future… currently IF-MAP)
OpenTosca and Winery
Pyang (validator/converter)
OpenBaton
Rift.ware
April 2016
NFV World Congress

7. For SDOs For NFV Projects Recommendations Accommodate REALITY
TIMELY publication
MODULAR design
OPNFV as CATALYST
Maximize REUSE
Accommodate DIVERSITY without FRAGMENTATION
Cross-project COLLABORATION
OPNFV as INTEGRATOR
Platforms
Standards
Customer
Motivation
Choice
Realization
Services
OPNFV
Open Source
April 2016
NFV World Congress

8. Come collaborate with us in OPNFV!
April 2016