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

• Identify GAPs  and prioritize per release

   -Initial round should be based on SDC DM and OpenECOMP (Not relevant in the guidelines section. Consider moving to Principles)

  -Identify existing construct defined in SOL001 and TOSCA NFV Profile

  -Propose new constructs to TOSCA NFV profile when desired types are not defined (It would be good to define extensions to SOL001. VNF vendors will provide TOSCA VNFD compliant to SOL001. The new constructs in ONAP can be proposed in ETSI SOL001)

•Try to maintain backward compatibility

•Create a (class) diagram which outlines ONAP DM relationship to TOSCA Simple Profile 1.2 (Not clear. Consider rephrase)
   -Follow the principals define in next slide

•Validate the model using the selected use cases

•Tools: Papyrus

• IM Language: UML

 Principles:

•New constructs
   -Best effort to use TOSCA Simple Profile 1.2 “normatives”
   -Extend/Derive from Simple Profile 1.2 “normatives”s (Using simple profile 1.2 as basis and define new constructs taking in consideration both SOL001 and TOSCA NFV profile is the proposed way forward. Is that the correct understanding. Please clarify in either case)

   -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 to be progressed

•Properties
   -Best effort to put properties on capabilities (Not clear. Consider rephrase to clarify)

•Namespace
  -TBD