...
The unified model-driven approach uses unified source meta-models (that represent source models), for model transformation into unified target meta-models (that represent target models). The key function of any model-driven approach is the mentioned transformation, but also the fact that model-driven system uses models as sources of data for generating processes/codes and following workflows (not code development as source) – this way, the system can be more flexible and future proof, easy to update and use for cross-platform solutions since the “only” thing needed is Model update and manipulation through Engine. The word “unified” here refers to unified information models that are used in the system to describe meta-models and models in a platform independent wayIn this project, we do not focus on model-driven system implementation. AAI should use data models in runtime (ex. for LCM events), APIs use data models to expose specific data types with relationship to achieve programmability, while blueprints are updated through model transformation process where iteration of model queries and manipulations (using the transformation engine) are executed on the source (ex. VNF) and target model (ex. Blueprint).
This project will produce unified and consolidated data models together with related projects
This project will explore A&AI/SDC data for a common information modeling
This project will provide the foundation and framework to oversee and create a common ONAP information model across all ONAP projects
The information and data model will cover: Resource models (that contain VF and VFC), Service models (that are composed from resource models), Deployment/Lifecycle models and application modeling
The modeling group's objective is to define a unified model-driven approach for ONAP’s components
This project will investigate ways to meet ONAP’s overall orchestration needs by aligning and integrating its top-level imperative workflow capabilities with TOSCA-based declarative or imperative execution environments.
- this work is related to Service Orchestrator (5/14/17) and VF-C: Virtual Function Controller (5/16/17) about their implementation of workflow execution:
- This project will provide the guideline and frame work for workflow in other ONAP projects to stitch together
...
- How does this project fit into the rest of the ONAP Architecture?
- SDC
A&AI
VNF SDK/VNF Requirements
VF-C
SO
Policy
- CLAMP
- DCAE
ICE
- MultiVIM
- How does this align with external standards/specifications?
- Oasis Tosca NFV profile
- ETSI NFV SOL spec
- ETSI NFV IFA024: Report on External Touchpoints related to NFV Information Model
- Are there dependencies with other open source projects?
- None
- etc.
The modeling team will collaborate with the data modelers/implementers from the following specific groups for release 1
VNF SDK/ICE
VNF Modeling
Network service Modeling
Policy Modeling
Parsers
SO/SDC
VNF Modeling
Network service Modeling
Service Modeling
Parsers
VF-C
VNF Modeling
Network service Modeling
Parsers
CLAMP/Policy/DCAE
CLAMP Modeling
Policy Modeling
DCAE Modeling
Deliverables for release 1
...
- Information Modeling for VNF
- Informaiton Modeling for Network Service
- Information Modeling for service
- Tosca Data Modeling for VNF
- Heat Data Modeling for VNF
- Tosca Data Modeling for Network Service
- YANG Data Modeling for SDN
- Policy modeling
- DCAE modeling
- Clamp modeling
...