You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 39 Next »

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 and consolidate the unified data models

  • This project will explore A&AI/SDC data from OPENO and OPENECOMP for information modeling purposes 

  • This project will provide the foundation and framework to oversee and create a common ONAP information model across all ONAP projects

  • 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 top-level imperative workflow capabilities with TOSCA-based declarative or imperative execution environments.

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

Scope:

  • Tools and Syntax 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

  • Support Use cases for R1: vCPE, vVoLTE, vFW/vDNS, example DMs for this use cases

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
    • ETSI NFV IFA024: Report on External Touchpoints related to NFV Information Model
  • Are there dependencies with other open source projects?
    • None
    • etc.

Collaboration:

Resources:

          Ramkumar Venketaramani rvenketarama@vmware.com

          Xiaojun Xie xiexj.gd@chinatelecom.cn


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:

Shitao Li   lishitao@huawei.com
Bruce Thompson  brucet@cisco.com
Xiaodong Shang  shang.xiaodong@zte.com.cn
Yuanxing Feng  feng.yuanxing@zte.com.cn
Weitao(Victor) Gao victor.gao@huawei.com
Xin(Saw) Jin saw.jin@huawei.com
Arthur Berezin Arthur@gigaspaces.com
Sandeep Shah    ss00473517@techmahindra.com
Andrei Kojukhov Andreik@amdocs.com

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

  • No labels