Content Comparison

• Project Name:

• Proposed name for the project: Modeling
• Proposed name for the repository: org.onap.modeling modeling

Project description:

 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. In this project, we do not focus on model-driven system implementation. 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 iteration of model queries and manipulations..

• 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

Modeling project is mostly defining the information modeling, and get data model contributed from each project implementer?

if there are multiple projects are going to use this data model, then modeling project need to specify based on the consensus of multiple projects within the required timeframe.

if there is only 1 project is using this data model, modeling project will only review and document it here

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 workflowsthe 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.

...

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

• VF-C

• A&AI

• 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
• Policy Framework

• Are there dependencies with other open source projects?
• None
• etc.

The modeling team will collaborate with the data modelers/implementers from the following specific groups for release 1

VNF SDK/ICE

VNF Modeling

Network service Modeling

Policy Modeling

Parsers

 SO/SDC

VNF Modeling

Network service Modeling

Service Modeling

Parsers

VF-C

VNF Modeling

Network service Modeling

Parsers

CLAMP/Policy/DCAE

CLAMP Modeling

Policy Modeling

...

Deliverables for release 1

Modeling

...

...

APIs:

Parsers and translators:

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

Time plan:

Info Model (VNF, Network Service Service) specification to be finalize at 1.5 month before functional freeze(for R1, 20th June, 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

...

• Primary Contact Person : Rittwik Jana, Hui Deng, Amir Levy
• Names, gerrit IDs, and company affiliations
• Contributors:
  
  Hui Deng denghui12@huawei.com
  Rittwik Jana rjana@research.att.com
  Lingli Deng denglingli@chinamobile.com
  Shitao Li   lishitao@huawei.com
  Bruce Thompson  brucet@cisco.com
  Chengli Wang wangchengli@chinamobile.com
  Xinhui Li lxinhui@vmware.com
  Maopeng Zhang zhang.maopeng1@zte.com.cn
  Xiaodong Shang shang.xiaodong@zte.com.cn
  Yuanxing Feng  feng.yuanxing@zte.com.cn
  Zhaoxing Meng meng.zhaoxing1@zte.com.cn
  Weitao(Victor) Gao victor.gao@huawei.com
  Xin(Saw) Jin saw.jin@huawei.com
  Attila Horvat attila.horvat@huawei.com
  Segev Cohen segev.cohen@Amdocs.com
  Amir Levy amir@gigaspaces.com
  Arthur Berezin Arthur@gigaspaces.com
  Alex Vul alex.vul@intel.com 
  Uri Elzur uri.elzur@intel.com
  Thinh Nguyyenphu thinh.nguyenphu@nokia.com
  Nagesha Subramanya nagesha.subramanya@nokia.com
  Sandeep Shah ss00473517@techmahindra.com
  Segev Cohen segev.cohen@Amdocs.com
  Tal Liron tal@gigaspaces.com
  Ran Ziv ran@gigaspaces.com
  John Ng johnng@att.com
  Claude Noshpitz cn5542@att.com
  Gil Bullard gil.bullard@att.com
  Srinivasa Vellanki srinivasa.vellanki@amdocs.com
  Bin Yang bin.yang@windriver.com
  Andrew Mayer am803u@att.com
  Nigel 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@bocozhongheliu@boco.com.cn
  Yuanwei Yang  yangyuanwei@boco.com.cn
  Yannan Han hanyanan@raisecom.com
  Hu Dong donghu@raisecom.com
• Jacopo Pianigiani jpianigiani@juniper.net
• Kevin Scaggs ks0567@att.com
• Andrei Kojukhov andreik@amdocs.com
• Priya TG priya.g@netcracker.com
• Michael Brenner michael@cloudify.co

• Project Roles (include RACI chart, if applicable)
• Other Information:
• link to IM and DM from OPENECOMP and OPENO
  
  • OPEN-O NS Model
  • OPEN-O VNF Model
• link to seed code (if applicable)
  • https://github.com/apache/incubator-ariatosca

  • https://wiki.opendaylight.org/view/YANG_Tools:Main

  • https://gerrit.opnfv.org/gerrit/gitweb?p=parser.git;a=summary (include there parts: tosca2heat, yang2tosca, verigraph(Network Topology Check). )

• link to network service model

  • IMS: https://gerrit.open-o.org/r/gitweb?p=modelling-csar.git;a=tree;f=csars/nfv-ns/IMS;h=b6c6167861280103e9e0e5fca5506711bcf8a2bb;hb=HEAD

  • EPC: https://gerrit.open-o.org/r/gitweb?p=modelling-csar.git;a=tree;f=csars/nfv-ns/EPC;h=01021f9645840ffd2491e96a7dd29b584bebe838;hb=HEAD

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

...

Repo name: org.onap.modeling
Lifecycle State:
Primary Contact:
Project Lead:
mailing list tag [modeling] 
Committers:

...

...

...

...

...

...

...

Link to approval of additional submitters: 

...