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

Compare with Current View Page History

« Previous Version 18 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

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

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

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:

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: 

  • No labels