ONAP Data Model - an SDC Perspective

Transcription

1 ONAP Data Model - an SDC Perspective Michael Brenner (Cloudify) Tom Nadeau (Cloudify) David Shadmi (AT&T) Anatoly Katzman (AT&T) December 2017

2 Design-Time Data Model - Principals The Design-Time model describes the end goal ( what we want ) The Design-Time model is independent of the infrastructure ( where ) and of how the model is orchestrated ( how ) Orchestration decisions are controlled using policies - Naming, Placement, Homing, IP Assignment, Scaling, etc. The Design-Time model is an implementation of the Information Model, leveraging TOSCA modeling language - In the spirit of ONAP IM (not perfect match) Design-time model Run-time model need to define integration points between the models

3 Design-Time Data Model Principals (Cont.) Data Model = Type Definitions Library + Design Patterns Design Patterns: cooking recipes of the designer cuisine - Methods of translating Information Model into Data Model - Help to understand existing models, guide creation of new models - Capture best practices of design Currently defines two patterns - Policies - Substitution We may need more patterns

4 Terminology Simple Resource - A node without associated topology template (can t be further decomposed) - Simple resource used to compose a composite resource or a service - Virtual Link, Connection Point, Virtual Storage, Virtual Compute, etc. Composite Resource - A resource which is composed from other resources (simple, composite) - A node which substituted by a topology template - VDU, VNF, etc. Service - A composition of one of more resources (simple, composite) and/or services that can be deployed by ONAP Resource Template - Occurrence of a resource in a composition - Refers to a resource type which defines the resource semantics (e.g., properties, attributes, requirements, capabilities, interfaces)

5 Terminology Simple Resource - A node without associated topology template (can t be further decomposed) - Simple resource used to compose a composite resource or a service - Virtual Link, Connection Point, Virtual Storage, Virtual Compute, etc. Composite Resource - A resource which is composed from other resources (simple, composite) - A node which substituted by a topology template - VDU, VNF, etc. Service - A composition of one of more resources (simple, composite) and/or services that can be deployed by ONAP Resource Template - Occurrence of a resource in a composition - Refers to a resource type which defines the resource semantics (e.g., properties, attributes, requirements, capabilities, interfaces)

6 Terminology Visualized Example VL VNF VNF SRV VL VL PNF PNF Resource Service

7 SDC Approach for Implementing ONAP IM TOSCA service template TOSCA node template

8 Groups Derived from tosca.groups.root Initially define two group types: - VF-Module - VNF-FG Groups templates associated by policies are created during the design process - derived from tosca.groups.root, onap.groups.vfmoudle, onap.groups.vnffg

9 Capabilities Added to simple resource to capture environment specific information - Neutron capability - Contrail capability Allow us to keep the model agnostic when the resource definition is targeting specific platform - HEAT to TOSCA

10 Policies Optional section in a service template (composite resource, service) Capture orchestration decision: - Homing, Placement - Naming - Network Assignment - Scaling - Auditing*

11 Deployment Flavor - Requirements A flavor definition should be able to express: - A different topology - A different set of properties, both definitions and values - A different set of capabilities and requirements, both definitions and values (props and occurrences) - A different set of policies (for scaling, affinity, etc.) The policies of one flavor should be isolated from the policies of another flavor Only policies of the selected flavors are applied - A different set of artifacts, like Software Image, License, scripts, etc. More than one dimension of flavoring - Flavor Dimension BySize: Small, Medium, Big - Flavor Dimension ByDeployEnv: Community, Enterprise, Government Can create flavors combination - myvnfforonaplab = use MyVNF (BySize=Big, ByAudience=Community) It should be easy to have a VNF without flavors The model should have the notion of the default deployment flavor

12 Namespace tosca_definition_version - tosca_simple_yaml_1_2 - Need to further discussion about using 1.0/1.1 Namespace Alias - No need to define ONAP specific alias Namespace URI - Need to publish under ONAP Namespace Prefix - Not supported in R2 onap.nodes. or telco.nodes.?

13 Thank You December 2017