1. OPEN-O Modeling Directions (DRAFT 0.6)
OPEN-O Technical Steering Committee

2. OPEN-O is more than MANO…
Portals
OSS/BSS
Design- Time
Environment
NFV MANO
Virtualized Network Functions
(VNFs)
NFV Orchestrator
GUI
VNFM
NFV Infrastructure
(NFVI)
Modeling
VIM
Catalogues
Legacy Networks
SDN Infrastructure
Models need to extend beyond MANO as well…
Open-O covers more than MANO
MANO covers “greenfield” NFV functions
OPEN-O also integrates with legacy BSS/OSS
Service and Resource orchestration
OPEN-O orchestrates brownfield SDN and legacy networks
OPEN-O is building a design time environment (not just a runtime env.)

3. OPEN-O requires unified information & data models that encompass
OPEN-O Direction
It’s about the services
End-to-end
Model-driven
Support for brownfields
Connectivity services
Tailored to the operator
Modular framework
OPEN-O requires unified information & data models that encompass
physical, virtual and cloud based infrastructure, SDN & NFV, applications and complex datacenter and intra-datacenter connectivity

4. OPEN-O SDO and Open Source Ecosystem
IM/DM – ETSI, MEF, TMF, OASIS, ONF
Architecture – ETSI NFV & MEF LSO
Open Source (NFV) – OPNFV, OpenStack, Aria, etc.
Open Source (SDN) – Open Daylight, ONOS
Others…

5. Design Time vs Run Time Models…
CONSUMER
Customer Facing Service Model (Services)
PROVIDER
Design Time View (Desired)
Functional Topology
Deployment Requirements
Functional Requirements
Operational Requirements
Infrastructure Requirements
Run-Time View (Actual)
Deployment Topology
Health
SLO’s & OLO’s
Operational State
Operational Policies
Infrastructure Mappings (Physical/Virtual/Cloud)
Infrastructure Topology
Resource Health
Resource State
Network Service Model (Services)
VNF Model
(Applications)
Resource Mapping
Infrastructure Model (NFV-I)
Design time is different from run-time
We need to expose run-time models
SDOs: Please ensure alignment between design-time and run-time models

6. VNF lifecycle modeling and automation challenges…
Open-O General Approach:
Leverage OASIS/TOSCA model – TOSCA NVF Profile
Leverage ETSI/MANO model for design-time & run-time modeling – VNFD, VNFR, VDU, and VRU
Use requirement/capability matching for deployment
Identified TOSCA & ETSI/NVF Challenges
TOSCA and ETSI specifications are evolving at different rates, and maintaining alignment is a challenge
VNF model is too simplistic – need layers for services, applications, platform, infrastructure
VNF model is incomplete – missing infrastructure requirements, KPIs, and operational characteristics
Requirements and dependencies…
Policies, rules and plans…
Characteristics, metrics and ratings…
Instrumentation, KPIs and actions…
Model Attributes
Deployment Perspective
Functional Perspective
Operational Perspective

7. Possible Open Source Alignment with ETSI/TOSCA/YANG
Standard
（IM and DM）
Opensource（DM）
TOSCA
Tacker
tosca-nfv-profile-CSD03
ETSI MANO v1 ？ ？
ETSI IFA
tosca-nfv-profile based on IFA
Tacker
Open ECOMP ? ？
ETSI SOL
YANG
Rel.2-3 ？
OSM YANG
Rel. 1
ETSI OSM Rel.2

8. NFV template modeling language
Phase 1 Tosca Profile
Tosca NFVv1
Phase 1 Design
Tacker
ETSI MANO v1
Phase 1 Yang
ETSI OSM
YANG NFVv1
Descriptors with Para
Phase 2 Descriptors
Phase 3 Tosca Profile
ETSI IFA
Current ETSI/TOSCA NFV profiles are not sufficient
ETSI/OASIS developing new versions
Open source groups adopting & extending
Possible divergence in the industry
Close the loop from open source to SDOs
ETSI SOL
Tosca NFV v2
Phase 3 YANG
ETSI OSM

9. Possible alignment with MEF
Framework
End to End Services
Business Application
Business Applications
Business Applications
Customer Domain
SP Domain
Partner Domain
OSS
BSS
Portals
Legato
Service Orchestration
GS-O
NFV-O
SDN-O
Presto
Infrastructure Control
and Management
SDN Controllers
NFV MANO:
VIM, VNFM
Adagio
Element Control
and Management
EMS
NMS
Simplistic view for discussion

10. Open-O Modeling Approach
Using TOSCA for GS-O, SDN-O, and NFV-O northbound interfaces, VNF packaging
NFV-O: ETSI-aligned (existing and emerging)
Developing extensions based on specific use cases
Considering YANG for SDN-O southbound
Discussing MEF Presto alignment
Developing packaging format for VNFs
Interested in wider industry alignment

11. Challenges Ahead Models need to extend beyond MANO as well…
Services – customer facing, resource facing
Applications – middleware, VNFs
Infrastructure – physical, virtual, cloud based
Network Connectivity
VNF modeling & packaging
Service modeling & packaging
Alignment between SDN & NFV
PNFs and VNFs
“Northbound” interoperability across orchestrators