...
- SDC adopts SOL001 tosca.nodes.nfv.NS node type as the SDC NS node type; i.e., no mapping is necessary
- A new SDC SOL007 Design process generates SOL001 tosca.nodes.nfv.NS for the NS node type
- A new SDC SOL007 Onboarding process (stretch goal) copies the onboarded SOL001 tosca.nodes.nfv.NS contents to SDC AID DM tosca.nodes.nfv.NS contents
...
- The following covers the properties. Handling/Mapping of Requirements and Interfaces are under discussion.
NS-Level VirtualLink (between VNFs) Mapping
...
- SDC adopts a new VNF node type, org.openecomp.resource.abstract.nodes.ETSI.VNF, which is derived from org.openecomp.resource.abstract.nodes.VF.
- Merge of SOL001 VNF SDC VF node type attributes
- Non-ETSI modeling continues to use the existing org.openecomp.resource.abstract.nodes.VF
- ETSI VNF Design/Onboarding process uses the new VNF node type, org.openecomp.resource.abstract.nodes.ETSI.VNF as SDC AID DM VF
- For SOL001 VNF to SDC AID DM VNF mapping, SDC copies SOL001 VNF attributes to the corresponding attributes in the org.openecomp.resource.abstract.nodes.ETSI.VNF.
- SOL001 VNF attributes in SDC AID DM will be visible from SDC UI, so those attributes can be changed by SDC UI.
- But the onboarded vendor ETSI package will not be changed by the SDC UI users in Guilin.
- In Honolulu, the sync-up behavior will be be considered.
- For the reverse mapping, only the corresponding SOL001 VNF attributes will be copied
- In Guilin, SO NFVO, VFC and SVNFM get the SOL 001 attributes from descriptors, not from AAI
- AAI schema changes are not expected in Guilin
...
- The following covers the properties. Handling/Mapping of Requirements and Interfaces are under discussion.
VDU and VFC Mapping
...
Mapping between SOL001 Data Model and SDC AID DM Overall Summary
- Overall Mapping Summary
SOL001 VNFD and SDC AID DM VF Template Mapping
...