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

Compare with Current View Page History

« Previous Version 57 Next »

  • 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 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)

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:

Resources:

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
Xinhui Li, xinhuili, lxinhui@vmware.com
Andrei Kojukhov Andreik@amdocs.com
Arthur Berezin Arthur@gigaspaces.com
Sandeep Shah    ss00473517@techmahindra.com

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

  • No labels