Model-Driven NFV (Models) Project 22 March 2016 Bryan Sullivan, AT&T

OPNFV’s Role and Needs for Models OPNFV integrates upstream projects into a coherent platform for NFV, starting from the infrastructure layer and moving up the management stack OPNFV does not have an information model nor plans to establish one –Relies on existing 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 specific adapters/translators –Have implicit models, but not maintained in formal modeling language –Are intended to have limited scope, yet sometimes compete, and evolve toward cleaner boundaries and model convergence over several releases March 20162Management and Orchestration Developer Meet-up

What’s this Model-Driven NFV project?Model-Driven NFV Information and Data Models for NFV are a hot but somewhat theoretical or at least cloudy topic This project intends to reduce the theory into practice, based upon existing examples and compatible open source projects, e.g. –Clearwater IMS as implemented by Orange in the OPNFV vIMS Functest using Cloudify as VNFMvIMS Functest using Cloudify –ODL Unimgr for MEF LSOUnimgr In the process we will clarify, assess, and promote –The role of various model representations (TOSCA, YANG) in VNFM use cases –Convergence on standardized models (e.g. TOSCA Simple Profile for NFV) –Expansion of configuration, lifecycle, and policy features that can be modeled March 20163Management and Orchestration Developer Meet-up

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 Functest scenario Any model-able object related to VNF configuration, lifecycle, or policy Modeling tools used in model and VNF development March 20164Management and Orchestration Developer Meet-up

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 March 20165Management and Orchestration Developer Meet-up

While I have your attention: Heresy? Delusion? Or? We should be able to use the same model-driven VNFM frameworks to manage NFVI (e.g. OpenStack service components) This may substantially simplify the testing of components, e.g. avoiding having to write installer-specific plugins or tests, or complex python scripts Example –An OpenStack service is described in a VNFD, with relationships as needed to other OpenStack services, and a desired execution host (BM, VM, container) –The VNFM sets up the host, networking as needed to fulfill the relationships, and executes the TOSCA “create” lifecycle script –The test driver is described in another VNFD and is similarly deployed –When tests are done, other lifecycle scripts are used to cleanup the environment March 20166Management and Orchestration Developer Meet-up

Some Upstream Projects in Scope ToscaYang OpenStack: Heat-translator Tosca-parser Tacker (VNFD, more blueprints)blueprints Murano (Mitaka)Mitaka App-catalog (blueprint)blueprint OpenDaylight: Controller MD-SAL Yangtools YangIDE UnimgrUnimgr for MEF LSO XOS (e.g. samples)samplesYangForge (see L3VPN demo)L3VPN demo Cloudify (e.g. Clearwater IMS demo)Clearwater IMS demoONOS (proposed, based upon YangForge)proposedYangForge JuJu ( (future… currently IF-MAP) OpenToscaOpenTosca and WineryWineryPyang (validator/converter) OpenBaton Rift.ware March 20167Management and Orchestration Developer Meet-up

Recommendations Accommodate REALITY TIMELY publication MODULAR design OPNFV as CATALYST March 20168Management and Orchestration Developer Meet-up Platforms Standards Customer Motivation Choice Realization Services OPNFV Open Source For SDOs Maximize REUSE Accommodate DIVERSITY without FRAGMENTATION Cross-project COLLABORATION OPNFV as INTEGRATOR For NFV Projects

Come collaborate with us in OPNFV! March 20169