ETSI's Bug Tracker |
Anonymous | Login | Signup for local Mantis account | 17-05-2024 14:58 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 | ||||||||
0008129 | SOL001 - TOSCA-based NFV descriptors spec | [NFV Specifications] Feature Gap | public | 16-09-2022 07:57 | 15-05-2024 14:23 | ||||||||
Reporter | Sujeet Banerjee | ||||||||||||
Assigned To | |||||||||||||
Priority | normal | ||||||||||||
Status | new | Resolution | open | ||||||||||
Product Version | 4.2.1 | ||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0008129: [V4.3.1] [Table 6.10.10.2-1] "NOTE2" Discrepancy: does not support all use cases for HelmCharts | ||||||||||||
Description | Current state of the note2 in the document: ----- NOTE 2: The "container"namespace" is only applicable when the targets of the policy are exclusively nodes of type tosca.nodes.nfv.Mciop. ----- This is a problem because, some Helm-Charts may have the intent to create OS-containers that would be deployed in more than one Kubernetes namespace. So, "container_namespace" must be allowed at VDU level as well. | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files | |||||||||||||
Notes | |
(0016655) lishi (developer) 15-05-2024 14:23 |
My understanding is that the namespace related to VDU is defined inside MCIOP (e.g. Helm chart), it is not applicable for MANO to manage something inside MCIOP. |
Issue History | |||
Date Modified | Username | Field | Change |
16-09-2022 07:57 | Sujeet Banerjee | New Issue | |
15-12-2022 09:18 | Sujeet Banerjee | Issue cloned: 0008178 | |
15-05-2024 14:23 | lishi | Note Added: 0016655 |
MantisBT 1.2.14 [^] Copyright © 2000 - 2024 MantisBT Team |