Versions Compared

Old Version 14

changes.mady.by.user Amir Levy

Saved on

compared with

New Version Current

changes.mady.by.user Michael Brenner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

  • Project Name:

  • Proposed name for the project: Modeling
  • Proposed name for the repository: org.onap.modeling 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:

 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.

  • This project will produce the tools related to modeling.

Scope:

  • Modeling tools and converters
  • Code - parsers (unified API interfaces) and tools (translators)
  • Support Use cases of ONAP: vCPE, vVoLTE, vFW, et al.
  • 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?
  • Following project is going to use this projects

    • SDC

      A&AI

    • VNF SDK/VNF Guidelines

    • VF-C

    • A&AI

    • SO

    • ICE

    • Policy

    • VNF certification

  • How does this align with external standards/specifications?
    • Oasis Tosca NFV profile
    • ETSI NFV SOL spec
    • Framework
  • Are there dependencies with other open source projects?
    • None
    • etc.

Deliverables for release 1

Parsers and translators:

  • Tosca Parsers
  • YANG Parsers
  • Tosca to Heat
  • YANG to Tosca


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:
foo@bar.com
baz@qux.com


CommitterEmailLinux Foundation ID
Alex Vulalex.vul@intel.comavul
Amir Levyamir@gigaspaces.comamirlevy
Arthur BerezinArthur@gigaspaces.comArthurBerezin
Bruce Thompsonbrucet@cisco.com
Chengli Wangwangchengli@chinamobile.comwangchengli
Ethan Lynnethanlynnl@vmware.comethanlynnl
Hu Dongdonghu@raisecom.comdonghu1102
Hui Deng denghui02@hotmail.comdenghui02
Ling Lilenon_lee@hotmial.comlenon_lee
Lingli Dengdenglingli@chinamobile.comlingli
Liuhe Zhongzhongheliu@boco.com.cnzhongheliu
Maopeng Zhangzhang.maopeng1@zte.com.cnMaopengzhang
Rittwik Janarjana@research.att.comRjana
Sandeep Shahss00473517@techmahindra.comSandeepLinux
Shitao Lilishitao@huawei.comLishitao
Thinh Nguyenphuthinh.nguyenphu@nokia.com
Xinhui Lilxinhui@vmware.comxinhuili
Yanbin Shishiyb.gd@chinatelecom.cnYanbinShi
Yannan Hanhanyanan@raisecom.comhanyanan
Yuanwei Yangyangyuanwei@boco.com.cnyuanweiyang
Zhaoxing Mengmeng.zhaoxing1@zte.com.cnZhaoxing



*Link to TSC approval: 

Link to approval of additional submitters: 

...