...
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 work is related to Service Orchestrator and VF-C about their implementation of workflow execution:
- This project will provide the guideline and frame work for workflow in other ONAP projects to stitch together
...
- 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 and (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
- Are there dependencies with other open source projects?
- None
- etc.
Collaboration:
- Meeting every wed 9:00/10:30 00 EDT, 6:30 00/7:00 PDT, 15:30 00/16:00 CET, 9:00/10:30PM 00PM Beijing - https://gigaspaces.zoom.us/j/382129978
- IRC - https://www.irccloud.com/#!/ircs://irc.freenode.net:6697/%23onap-modeling
...
Repo name:
Lifecycle State:
Primary Contact:
Project Lead:
mailing list tag [modeling]
Committers:
foo@bar.com
baz@qux
*Link to TSC approval:
Link to approval of additional submitters: