...
Xu Yang: In my opinion, the VnfInfo, InstantiatedVnfInfo, etc. can be mapped to attributes of the corresponding resource instance objects.
To complete the mapping, we should be more specific, I´ve not found any specific attributes in ECOMP IM UML documentation: ONAP Resource 2017-11-08.docx
Design Time Model
Resource General View Diagram
...
- Resource model includes design time model (ResourceDesc) and run time model (ResourceInstance). Based on one ResourceDesc, zero or more ResourceInstance(s) can be instantiated.
- “Resource” is a generalization of many objects, for example, VNF, PNF, entitlement, etc. In the above diagram, only VNF, PNF and ServiceVirtualLink (virtual link between NFs) are shown. More specifically,
- VnfDesc is derived from ResourceDesc, VnfInstance is derived from ResourceInstance. Based on one VnfDesc, zero or more VnfInstance(s) can be instantiated.
- PnfDesc is derived from ResourceDesc, PnfInstance is derived from ResourceInstance. One PnfDesc is used to describe one PnfInstance.
- SrvVlDesc is derived from ResourceDesc, SrvVlInstance is derived from ResourceInstance. Based on one SrvVlDesc, zero or more SrvVlInstance(s) can be instantiated.
- VnfDesc can be composed of one or more VnfcDesc(s) and zero or more VnfVlDesc(s). Correspondingly, VnfInstance can be composed of zero or more VnfcInstance(s) and zero or more VlInstance(s). It should be noted that a VnfInstance comprises zero VnfcInstance is a special case that the VnfInstance object is created but not instantiated.
- Based on one VnfVlDesc, zero or more VlInstance(s) can be instantiated. And Based on one VnfcDesc, zero or more VnfcInstance(s) can be instantiated.
VnfDesc General View Diagram
NOTE: This diagram is a proposed model for the VnfDesc, mainly inspired by the model from ETSI IFA015. Not all elements in the VnfDesc are depicted.
...
VnfVirtualLink, LinkPort, VirtualNetwork
1) InECOMP IM UML documentation: ONAP Resource 2017-11-08.docx and ONAP Service 2017-11-08.docx no class definition about Virtual Link, VnfVirtualLink and NSVirtualLInk, LinkPort, VirtualNetwork defined in ETSI IFA.
2) VNFCLinkPort class in Resource package as a group of connection points per VNFCInstance (1..*) not clearly mapped against the model above. Network modelling related terms are confusing, e.g. VDULinkPortDescriptor, VNFCLinkPort. Because LinkPort is the resource on VirtualLink, not on VDU or VNFC.
3) The external VL connectivity of VNF instance is missing in ONAP IM
relation in VNFDeploymentFlavor in ETSI
- MonitoringParameterDesc, ScalingAspects and LifeCycleManagementOperationDesc are modelled under VnfDeploymentFlavor in ETSI NFV, while under VnfDesc in ONAP.
A number of design-time items are missing in ONAP IM, e.g. ConfigurableProperties, VnfIndicator, AffinityOrAntiAffinityGroup, InstantiationLevel, etc
...