This page is about ONAP modeling design principles and guidelines for release 2+
Guidelines:
• Initial focus on a Unified IM and TOSCA construct representation
• Align terminology with ETSI (IFA11, IFA14) where appropriate
-Mapping needed between equivalent terms, identify the differences
-Based on use cases, select the appropriate model
•Identify all the types/constructs we need
-Initial round should be based on SDC DM and OpenECOMP IM
-Identify existing construct defined in SOL001 and TOSCA NFV Profile
-Propose new constructs to TOSCA NFV profile when desired types are not defined
•Try to maintain backward compatibility
•Create a (class) diagram which outlines ONAP DM relationship to TOSCA Simple Profile 1.2
-Follow the principals define in next slide
•Validate the model using the selected use cases
•Tools: IM – Papyrus
Principles:
•New constructs
-Best effort to use TOSCA Simple Profile 1.2 “normatives”
-Extend/Derive from Simple Profile 1.2 “normatives”s
-Derive directly from tosca.nodes.root
-DM does not need to match exactly the IM; DM can represent the IM
-DM are pruned and refactored from IM
-Discuss extensibility guidelines
•Properties
-Best effort to put properties on capabilities
...
NEW: Proposed ONAP Release Process Updates for Information and Data Modeling
Clean Version
ONAP Modeling Design Principles and Guidelines (20171023)