Project Name:
- Proposed name for the project: Modeling
- Proposed name for the repository: org.onap.modeling
Project description:
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 way. 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 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
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)
- Support Use cases of ONAP: vCPE, vVoLTE, vFW, et al.
Architecture Alignment:
- 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.
Deliverables for release 1
Modeling
- Information Modeling for VNF
- Informaiton Modeling for Network Service
- Information Modeling for service
- Tosca Data Modeling for VNF
- Tosca Data Modeling for Network Service
- YANG Data Modeling for SDN
- Policy modeling
- DCAE modeling
- Clamp modeling
APIs:
Parsers and translators:
- Tosca Parsers
- YANG Parsers
- Tosca to Heat
- YANG to Tosca
Time plan:
Info Model specification finalize at 1.5 month before functional freeze(for R1, 20th June, 2017)
Data Model specification finalize at 1 month before functional freeze (for R1, 3rd, July, 2017)
Collaboration:
- Meeting every Tuesday 9:00/10:00 EDT, 6:00/7:00 PDT, 15:00/16:00 CET, 9:00/10:00PM Beijing -
- IRC - https://www.irccloud.com/#!/ircs://irc.freenode.net:6697/%23onap-modeling
Meeting bridge?https://zoom.us/j/137904496
Or iPhone one-tap (US Toll): +14086380968,137904496# or +16465588656,137904496#
Or Telephone: Dial: +1 408 638 0968 (US Toll) or +1 646 558 8656 (US Toll) Meeting ID: 137 904 496 International numbers available: https://zoom.us/zoomconference?m=mi-ad1sMLWlXByAKLio5vDnd9JYqUR_a
Resources:
- Primary Contact Person : Rittwik Jana, Hui Deng, Amir Levy
- Names, gerrit IDs, and company affiliations
- Contributors:Hui Deng denghui12@huawei.comRittwik Jana rjana@research.att.comLingli Deng denglingli@chinamobile.comShitao Li lishitao@huawei.comBruce Thompson brucet@cisco.comChengli Wang wangchengli@chinamobile.comXinhui Li lxinhui@vmware.comMaopeng Zhang zhang.maopeng1@zte.com.cnXiaodong Shang shang.xiaodong@zte.com.cnYuanxing Feng feng.yuanxing@zte.com.cnZhaoxing Meng meng.zhaoxing1@zte.com.cnWeitao(Victor) Gao victor.gao@huawei.comXin(Saw) Jin saw.jin@huawei.comAttila Horvat attila.horvat@huawei.comSegev Cohen segev.cohen@Amdocs.comAmir Levy amir@gigaspaces.comUri Elzur uri.elzur@intel.comThinh Nguyyenphu thinh.nguyenphu@nokia.comNagesha Subramanya nagesha.subramanya@nokia.comSandeep Shah ss00473517@techmahindra.comAndrei Kojukhov Andreik@amdocs.comTal Liron tal@gigaspaces.comRan Ziv ran@gigaspaces.com
John Ng johnng@att.com
Claude Noshpitz cn5542@att.com
Gil Bullard gil.bullard@att.comSrinivasa Vellanki srinivasa.vellanki@amdocs.comBin Yang bin.yang@windriver.comAndrew Mayer am803u@att.comNigel Davis ndavis@ciena.com
Cas Majd cas.majd@huawei.com
Hrvoje Kegalj hrvoje.kegalj@hr.ibm.com
Christian Destré christian.destre@orange.com
John Strassner john.sc.strassner@huawei.com
Ramkumar Venketaramani rvenketarama@vmware.com
Xiaojun Xie xiexj.gd@chinatelecom.cn
Liuhe Zhong zhognheliu@boco.com.cn
Yuanwei Yang yangyuanwei@boco.com.cn
Yannan Han hanyanan@raisecom.com
Hu Dong donghu@raisecom.com - Jacopo Pianigiani jpianigiani@juniper.net
- Project Roles (include RACI chart, if applicable)
- Other Information:
- link to IM and DM from OPENECOMP and OPENO
- link to seed code (if applicable)
- link to network service model
- Vendor Neutral
- if the proposal is coming from an existing proprietary codebase, have you ensured that all proprietary trademarks, logos, product names, etc., have been removed?
- Meets Board policy (including IPR)
Use the above information to create a key project facts section on your project page
Key Project Facts
Project Name:
- JIRA project name: modeling
- JIRA project prefix: modeling
Repo name: org.onap.modeling
Lifecycle State:
Primary Contact:
Project Lead:
mailing list tag [modeling]
Committers:
Chengli Wang wangchengli@chinamobile.com
Yuanwei Yang yangyuanwei@boco.com.cn
Yannan Han hanyanan@raisecom.com
Hu Dong donghu@raisecom.com
*Link to TSC approval:
Link to approval of additional submitters: