ETSI's Bug Tracker - SOL003 - Or-Vnfm protocols spec
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0008207SOL003 - Or-Vnfm protocols spec[NFV Specifications] Feature Gappublic12-05-2023 05:3010-05-2024 07:26
ReporterSujeet Banerjee 
Assigned ToYinan Liu 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0008207: [4.3.1] [Table 5.5.3.5-1] The mandatory attribute "vduId" for type "VnfcResourceInfo" is non-existent as per SOL001
DescriptionThe SOL003 4.3.1, Table 5.5.3.5-1 defines an incorrect/non-existent attribute "vduId" as "Mandatory":

Attribute-Name: "vduId";
Data-type=IdentifierInVnfd;
cardinality=1
Description: "Reference to the applicable VDU in the VNFD. See note 1"

NOTE 1: ETSI GS NFV-SOL 001 [i.4] specifies the structure and format of the VNFD based on TOSCA specifications.

------
HOWEVER, the SOL001 4.3.1 does not define and identifier called "vduId" in the VNFD.

This is a BIG discrepancy, given the Orchestrator/VNFM does not know how to correlated a VNFC/MCIO resource with the corresponding VDU / OsContainerDeployableUnit defined in the VNFD.
Steps To Reproduce
Additional InformationHere is what SOL001 4.3.1, Table 6.2.12.2-1, NOTE-1 reads:

NOTE 1: "A vduId property, which exists in ETSI GS NFV-IFA 011 [1] is not needed, as the VduProfile is contained in the Vdu.Compute node(for VM based VDU) or Vdu.OsContainerDeployableUnit node (for Oscontainer based VDU)
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
12-05-2023 05:30Sujeet BanerjeeNew Issue
22-05-2023 15:40Sujeet BanerjeeNote Added: 0016478
07-06-2023 10:59Yinan LiuNote Added: 0016485
07-06-2023 10:59Yinan LiuStatusnew => confirmed
07-06-2023 11:33Sujeet BanerjeeNote Added: 0016488
29-06-2023 13:56Yinan LiuNote Added: 0016492
29-06-2023 13:56Yinan LiuAssigned To => Yinan Liu
29-06-2023 13:56Yinan LiuStatusconfirmed => resolved
29-06-2023 13:56Yinan LiuResolutionopen => fixed
10-05-2024 07:26Yuya KunoNote Added: 0016645
10-05-2024 07:26Yuya KunoStatusresolved => closed

Notes
(0016478)
Sujeet Banerjee   
22-05-2023 15:40   
This is reproducible for SOL003 R4.4.1 as well.

Additional Info: The Appendix D.2 in R4.4.1 SOL001 only maps
---
SOL001 'Node template name' of type tosca.nodes.nfv.Vdu.Compute ---> SOL APIs (IdentifierInVnfd)vduId
----

BUT, it does not map SOL001 'Node template name' of type tosca.nodes.nfv.Vdu.OsContainerDeployableUnit to SOL APIs (IdentifierInVnfd)vduId
(0016485)
Yinan Liu   
07-06-2023 10:59   
As you find that the Appendix D.2 maps.
---
SOL001 'Node template name' of type tosca.nodes.nfv.Vdu.Compute ---> SOL APIs (IdentifierInVnfd)vduId
----

For the lack of mapping information between Node template name' of type tosca.nodes.nfv.Vdu.OsContainerDeployableUnit and SOL APIs (IdentifierInVnfd)vduId, it is because this appendix was not updated to include new spec in Release 4, however they should be mapped. Therefore, there is no issue for SOL003, but I suggest to update SOL001 Appendix D.2 for including the above mapping. If commenter can agree with the suggestion, I can create a CR to resolve it.
(0016488)
Sujeet Banerjee   
07-06-2023 11:33   
Yes, please do. This will avoid any misunderstanding.
(0016492)
Yinan Liu   
29-06-2023 13:56   
As the resolution has agreed by reporter, NFVSOL(23)000208 is to propose this resolution. Because NFVSOL(23)000208 has been approved in SOL#250, this issue is closed.
(0016645)
Yuya Kuno   
10-05-2024 07:26   
No issue for long time after resolved.