1. ONAP SDC TOSCA Import Gap Analysis
Michael Lando, Zahi Kapeluto, Eden Rozin,David Shadmi

2. Findings – General Statements
The provided CSARs represent services and not VNF’s.
Invalid TOSCA service template structure.
Not comply with OpenECOMP model.
Discussion item: Should ONAP model follows ETSI?

3. TOSCA Spec Compliancy
Provided CSAR were tested against TOSCA OASIS SPEC and Ubicity validator (
The TOSCA models need to start with tosca_definitions_version: tosca_simple_yaml_1_0
Under topology_template node_template the type needs to be directly under the node template name
Need to define a TOSCA validator used by ONAP to verify CSAR validity and compatibility with ONAP specification:
Apache ARIA TOSCA
AT&T TOSCA Parsers
OpenStack TOSCA Parser

4. OpenECOMP Compliancy
Missing OpenECOMP information needed by SO/SDNC/APPC/AAI/VID for orchestration
SO requires BPMN while the VoLTE services CSARs include BPEL
The current name spaces are not following OpenECOMP
GSAR and NSAR archive types are not supported by OpenECOMP

5. Gap Analysis and Comments
No.
Category
Feature
Potential Gap
SDC response 1
substitution_mappings
capabilities mapping
No mapping between the substituted node type and Topo template
This is a bug and we are working to fix it. 2
requirements mapping 3
Node
import node type
Can't import node type to SDC
We support importing of yaml files to create VFC/CP/VL which are used as basic building blocks for VF use on onboarding. The VF can be designed manually in the onboarding. 4
define node type
Can't define node type in SDC
Can be done manually using add vf scenario. 5
property setting
To be verified
SDC supports property add/remove/modify from UI. 6
metadata setting
Please provide a scenario for this feature,
This is partially supported on VF creation. 7
artifact setting
Artifact from TOSCA spec is not supported, the artifact are external to model. 8
attribute setting
Supported from UI. 9
requirement setting
Not supported. 10
capability setting 11
Relationship
import relationship type
Can't import relationship type to SDC 12
define relationship type
Can't define relationship type to SDC 13

6. Gap Analysis and Comments cont.
No.
Category
Feature
Potential Gap
SDC response 14
Group
import group type
Can't import group type to SDC
Can be done using API. 15
define group type
Can't define group type in SDC
Not supported. 16
property setting
Supported
Partial Support, we can assign values to existing properties. 17
metadata setting
Partial support. 18
members setting
To be verified 23
Inputs
input setting 24
input mapping 25
data type
Complex Data Type
Supported. 26
NFV
NFV node type
Not support
We are aligned with the openECOMP model.
 29
Nested Service design 30
Workflow design

7. SDC Suggestions
The CSAR needs to be aligned according to the current model supported.
tosca.nodes.nfv.NS.vIMS_NS and tosca.nodes.nfv.NS.vEPC_NS should be modeled as VNF.
Their internal components need to be defined as VFC/CP/VL.
Once this is aligned we will be able to import them and they can be add to a service in SDC and distributed.

8. Going Forward Parallel work on:
Align the models to standard as suggested.
Provide a development plan, for ONAP Amsterdam release, to enhance the support of TOSCA syntax.