Objectives

• Fully implement the SDC Informational Model, retain alignment with the ETSI NFV Informational Model
• Provide a higher abstraction layer for further implementations, such as the SDC catalog database schema, message formats for internal protocols and external APIs, code libraries in programming languages like Java, Python, JavaScript, etc.
• Serve a base for the ONAP Instance Model 

Overview

The SDC Data Model combines the following elements:

• A library of TOSCA normative types
• Patterns for translating ETSI IM abstractions into TOSCA constructs
• Conventions of naming, structuring, ordering, etc. 

References

• ECOMP SDC Data Model as a starting point. This ECOMP data model should then evolve towards this data model.
• Design Informational Model
• IFA 011 and 014. The mapping to the ETSI IM should not and will not be 1:1, but all ETSI IFA concepts and all their data attributes should be reflected in the data model
• Simple Profile in YAML v1.2, used as a Modellinglanguage and format
• NVF Profile v1.0 wd05 to get aligned with where possible

See also:

Design-Time Data Model: Conventions

Design-Time Data Model: Modelling Principles & Patterns

Design-Time Data Model: Resource Types Hierarchy

Design-Time Data Model: Reference