ETSI's Bug Tracker |
Anonymous | Login | Signup for local Mantis account | 30-04-2024 15:21 IST |
Main | My View | View Issues | Change Log | Roadmap | Stop monitoring project |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
0008219 | SOL001 - TOSCA-based NFV descriptors spec | [NFV Specifications] Bug | public | 21-11-2023 14:43 | 21-11-2023 14:43 | ||||||||
Reporter | Sujeet Banerjee | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | ||||||||||||
Status | new | Resolution | open | ||||||||||
Product Version | 4.3.1 | ||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0008219: [R4.3.1] and [R4.4.1] SOL001; Appendix A.18 Example incorrectly add "artifacts" to the VNF node template definition | ||||||||||||
Description | According to 6.8.1.7 "Artifact" clause, there are None artifacts under the node type: tosca.nodes.nfv.VNF However, in the Appendix A.18, the example declares an 'artifact' in the node_template definition of the VNF type: ExampleCorp.vDB.0_1.0_2 (from with the LCM interface declarations) ---- artifacts: helm_test: description: Post instantiation test script type: tosca.artifacts.Implementation.Bash ---- This does not look correct - If the TOSCA VNF base type does not allow 'artifacts' keyword, then can there be one for VNF topology_template? | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files | |||||||||||||
Issue History | |||
Date Modified | Username | Field | Change |
21-11-2023 14:43 | Sujeet Banerjee | New Issue |
MantisBT 1.2.14 [^] Copyright © 2000 - 2024 MantisBT Team |