Project Name:
- Proposed name for the project: Modeling
- Proposed name for the repository: org.onap.modeling
Project description:
This project will explore both OPENO and OPENECOMP data models
This project will explore A&AI data from OPENO and OPENECOMP for information modeling purposes and create a unified information model
The information model will cover: Resource models (that contain VF and VFC), Service models (that are composed from resource models) and Deployment/Lifecycle models
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 imperative workflow capabilities with a TOSCA-based declarative execution environment.
Scope:
- IDM (Specification of Data model)
Prioritize needs of data model in the various projects.
Document: guideline, process of how to define the data model
Code - parsers and tools
- Support Use cases for R1: vCPE, vVoLTE, vFW/vDNS
Architecture Alignment:
- How does this project fit into the rest of the ONAP Architecture?
- SDC
A&AI
VNF SDK/VNF Guidelines
VF-C
SO
Policy
VNF certification
- How does this align with external standards/specifications?
- Oasis Tosca NFV profile
- ETSI NFV SOL spec
- Are there dependencies with other open source projects?
- None
- etc.
Collaboration:
Resources:
- Primary Contact Person : Rittwik Jana, Hui Deng, Amir Levy
- Names, gerrit IDs, and company affiliations of the committersHui 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.cn
- Yuanxing 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.comArthur Berezin Arthur@gigaspaces.comUri Elzur uri.elzur@intel.comThinh Nguyyenphuthinh.nguyenphu@nokia.comNagesha Subramanya – nagesha.subramanya@nokia.comSandeep Shah ss00473517@techmahindra.comAndrei Kojukhov Andrei.Kojukhov@amdocs.comAlla Goldner Alla.Goldner@amdocs.com
- Tal Liron tal@gigaspaces.com
- Ran Ziv ran@gigaspaces.com
John Ng johnng@att.com
Claude Noshpitz claude.noshpitz@att.com
Gil Bullard gil.bullard@att.com - Project Roles (include RACI chart, if applicable)
- Other Information:
- link to seed code (if applicable)
- 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:
- JIRA project prefix:
Repo name:
Lifecycle State:
Primary Contact:
Project Lead:
mailing list tag [modeling]
Committers:
foo@bar.com
baz@qux.com
*Link to TSC approval:
Link to approval of additional submitters: