Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reverted from v. 59
  • Project Name:

  • Proposed name for the project: Modeling
  • Proposed name for the repository: org.onap.modeling

Project

...

description:

 The unified model-driven approach 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. In 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 iteration of model queries and manipulations..

  • 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 work with ONAP projects to achieve define a unified model-driven approach for ONAP’s components

  • This project will investigate ways to meet ONAP’s overall orchestration needs by aligning models as needed by ONAP projects. (there is an assumption that each project will be the expert in defining the specific model requirements and implementation.) and integrating its top-level imperative workflow capabilities with TOSCA-based declarative or imperative execution environments.

  • This project will provide the guideline and framework frame work for workflow in other ONAP projects to stitch together

...

if there is only 1 project is using this data model, modeling project will only review and document it here

 

Scope:

  • Tools and specification of CIM (Common information Model) and DM (Data model)
  • Prioritize needs of data model in the various projects.

  • Document: guideline, process of how to define the data model and information model, and design the architecture of workflows

  • Code - parsers (unified API interfaces) and tools (translators)

...

...

Heliu Liuhe Zhong  zhognheliu@boco.com.cn
Yuanwei Yang  yangyuanwei@boco.com.cn
Yannan Han hanyanan@raisecom.com
Hu Dong donghu@raisecom.comThinh Nguyyenphu thinh.nguyenphu@nokia.com

*Link to TSC approval: 
Link to approval of additional submitters: