NFV - Network Functions Virtualisation issueshttps://forge.etsi.org/rep/groups/nfv/-/issues2022-10-27T06:51:41Zhttps://forge.etsi.org/rep/nfv/SOL006/-/issues/58Version Dependencies from IFA014ed431 FEAT21 MegaCR2022-10-27T06:51:41ZppreeVersion Dependencies from IFA014ed431 FEAT21 MegaCRNFVIFA(22)000188r1NFVIFA(22)000188r1v4.3.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/57Implementation of ENH02.04. from IFA0142022-10-27T06:51:38ZppreeImplementation of ENH02.04. from IFA014NFVIFA(21)000180NFVIFA(21)000180v4.3.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/56Addition of Affinity Rule to NS Profile from IFA0142022-10-27T06:51:29ZppreeAddition of Affinity Rule to NS Profile from IFA014NFVIFA(22)000200NFVIFA(22)000200v4.3.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/55New Scope for affinityorantiaffinity IFA0142022-10-27T06:50:49ZppreeNew Scope for affinityorantiaffinity IFA014NFVIFA(21)000150r4
NFVIFA(21)000205r1NFVIFA(21)000150r4
NFVIFA(21)000205r1v4.3.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/54New CP type to model networking MCIOs2022-10-27T06:49:02ZppreeNew CP type to model networking MCIOsNFVIFA(20)000442r5NFVIFA(20)000442r5v4.3.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/53Adding MegaCR FEAT17 Cloud-native VNFs2022-10-27T06:48:51ZppreeAdding MegaCR FEAT17 Cloud-native VNFsNFVIFA(21)000203r1NFVIFA(21)000203r1v4.3.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/52Adding MCIOP Profile and minor changes.2022-10-27T06:47:48ZppreeAdding MCIOP Profile and minor changes.MCIOP changes from NFVIFA(20)000479r6: IFA011ed411 MegaCR FEAT17 Cloud-native VNFs and few minor changes from the same CR.MCIOP changes from NFVIFA(20)000479r6: IFA011ed411 MegaCR FEAT17 Cloud-native VNFs and few minor changes from the same CR.v4.3.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/51Cloud-Native VNFs OSContainerDesc and minor changes.2022-10-27T06:47:14ZppreeCloud-Native VNFs OSContainerDesc and minor changes.Changes from Mega CR FEAT17 NFVIFA(20)000479r6: Change4, 6 and 10 along with NFVIFA(21)000767r1 and NFVIFA(22)000172r1Changes from Mega CR FEAT17 NFVIFA(20)000479r6: Change4, 6 and 10 along with NFVIFA(21)000767r1 and NFVIFA(22)000172r1v4.3.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/50Enhance applicability of additionalNetworkInterfaceRequirements and Changes i...2022-10-27T06:44:30ZppreeEnhance applicability of additionalNetworkInterfaceRequirements and Changes in SwImageDesc propertiesReference:
NFVIFA(21)000942r2
NFVIFA(22)000072r1Reference:
NFVIFA(21)000942r2
NFVIFA(22)000072r1v4.3.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL005/-/issues/35Missing `type: file` and relevant content-type/accept headers in some endpoin...2022-09-05T14:19:14ZkaidosMissing `type: file` and relevant content-type/accept headers in some endpoints in NSDManagement and VNFPackageManagementIn branch 2.8.1, 2.7.1-maintenance and possibly others, there are missing definitions on operations that accept or return files and relevant header restrictions. Here's two patches for the NSDManagement and VNFPackageManagement:
```diff...In branch 2.8.1, 2.7.1-maintenance and possibly others, there are missing definitions on operations that accept or return files and relevant header restrictions. Here's two patches for the NSDManagement and VNFPackageManagement:
```diff
diff --git a/src/SOL005/NSDManagement/NSDManagement.yaml b/src/SOL005/NSDManagement/NSDManagement.yaml
index f3dd8cc..eff8fd1 100644
--- a/src/SOL005/NSDManagement/NSDManagement.yaml
+++ b/src/SOL005/NSDManagement/NSDManagement.yaml
@@ -601,6 +601,8 @@ paths:
Content-Type:
description: The MIME type of the body of the response.
type: string
+ enum:
+ - application/zip
maximum: 1
minimum: 1
WWW-Authenticate:
@@ -617,6 +619,8 @@ paths:
type: string
maximum: 1
minimum: 1
+ schema:
+ type: file
206:
# description: >
# 206 PARTIAL CONTENT
@@ -702,6 +706,15 @@ paths:
type: string
enum:
- application/zip
+ - in: formData
+ name: file
+ required: false
+ type: file
+ description: >
+ The payload body contains a ZIP file that represents the NSD archive, as specified above.
+ The request shall set the "Content-Type" HTTP header to "application/zip"
+ consumes:
+ - multipart/form-data
responses:
202:
description: >
```
```diff
diff --git a/src/SOL005/VNFPackageManagement/VNFPackageManagement.yaml b/src/SOL005/VNFPackageManagement/VNFPackageManagement.yaml
index f53a644..f150517 100644
--- a/src/SOL005/VNFPackageManagement/VNFPackageManagement.yaml
+++ b/src/SOL005/VNFPackageManagement/VNFPackageManagement.yaml
@@ -540,6 +538,8 @@ paths:
Content-Type:
description: The MIME type of the body of the response.
type: string
+ enum:
+ - application/zip
maximum: 1
minimum: 1
WWW-Authenticate:
@@ -556,6 +556,8 @@ paths:
type: string
maximum: 1
minimum: 1
+ schema:
+ type: file
400:
$ref: "../responses/SOL005_resp.yaml#/responses/400"
401:
@@ -834,6 +832,9 @@ paths:
Content-Type:
description: The MIME type of the body of the response.
type: string
+ enum:
+ - text/plain
+ - application/zip
maximum: 1
minimum: 1
WWW-Authenticate:
@@ -850,6 +851,8 @@ paths:
type: string
maximum: 1
minimum: 1
+ schema:
+ type: file
400:
$ref: "../responses/SOL005_resp.yaml#/responses/400"
401:
@@ -941,6 +944,8 @@ paths:
Content-Type:
description: The MIME type of the body of the response.
type: string
+ enum:
+ - application/zip
maximum: 1
minimum: 1
WWW-Authenticate:
@@ -957,6 +962,8 @@ paths:
type: string
maximum: 1
minimum: 1
+ schema:
+ type: file
206:
$ref: "../responses/SOL005_resp.yaml#/responses/206"
409:
@@ -996,7 +1003,7 @@ paths:
consumes:
- multipart/form-data
parameters:
- - name: Accept
+ - name: Content-Type
description: >
Content-Types that are acceptable for the response.
in: header
@@ -1181,6 +1188,8 @@ paths:
Content-Type:
description: The MIME type of the body of the response.
type: string
+ enum:
+ - application/zip
maximum: 1
minimum: 1
WWW-Authenticate:
@@ -1197,6 +1206,8 @@ paths:
type: string
maximum: 1
minimum: 1
+ schema:
+ type: file
206:
description: >
206 Partial Content.
@@ -1220,6 +1231,8 @@ paths:
Content-Type:
description: The MIME type of the body of the response.
type: string
+ enum:
+ - application/zip
maximum: 1
minimum: 1
WWW-Authenticate:
@@ -1230,6 +1243,8 @@ paths:
has provided an invalid authorization token.
maximum: 1
minimum: 0
+ schema:
+ type: file
400:
$ref: "../responses/SOL005_resp.yaml#/responses/400"
401:
@@ -1460,6 +1475,8 @@ paths:
type: string
maximum: 1
minimum: 1
+ schema:
+ type: file
206:
description: >
Partial Content.
@@ -1497,6 +1514,8 @@ paths:
has provided an invalid authorization token.
maximum: 1
minimum: 0
+ schema:
+ type: file
400:
$ref: "../responses/SOL005_resp.yaml#/responses/400"
401:
```https://forge.etsi.org/rep/nfv/SOL005/-/issues/34Return schema in VNFPackageManagement shouldn't be nested in properties2022-09-05T13:26:38ZkaidosReturn schema in VNFPackageManagement shouldn't be nested in propertiesIn branches 2.8.1, 2.7.1-maintenance , 2.6.1-maintenance, the return schema in 3 operations is wrongfully nested compared to the spec. This:
```yaml
schema:
properties:
VnfPkgInfoModifications:
$ref: "definitions/SOL005VNFPa...In branches 2.8.1, 2.7.1-maintenance , 2.6.1-maintenance, the return schema in 3 operations is wrongfully nested compared to the spec. This:
```yaml
schema:
properties:
VnfPkgInfoModifications:
$ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/VnfPkgInfoModifications"
```
Should be like this:
```yaml
schema:
$ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/VnfPkgInfoModifications"
```
Here's a patch for it for branch 2.7.1-maintenance:
```diff
diff --git a/src/SOL005/VNFPackageManagement/VNFPackageManagement.yaml b/src/SOL005/VNFPackageManagement/VNFPackageManagement.yaml
index f53a644..69ab3a1 100644
--- a/src/SOL005/VNFPackageManagement/VNFPackageManagement.yaml
+++ b/src/SOL005/VNFPackageManagement/VNFPackageManagement.yaml
@@ -401,9 +401,7 @@ paths:
maximum: 1
minimum: 1
schema:
- properties:
- VnfPkgInfoModifications:
- $ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/VnfPkgInfoModifications"
+ $ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/VnfPkgInfoModifications"
400:
$ref: "../responses/SOL005_resp.yaml#/responses/400"
401:
@@ -648,9 +646,7 @@ paths:
maximum: 1
minimum: 1
schema:
- properties:
- ExternalArtifactsAccessConfig:
- $ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/ExternalArtifactsAccessConfig"
+ $ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/ExternalArtifactsAccessConfig"
416:
$ref: "../responses/SOL005_resp.yaml#/responses/416"
400:
@@ -731,9 +727,7 @@ paths:
maximum: 1
minimum: 1
schema:
- properties:
- ExternalArtifactsAccessConfig:
- $ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/ExternalArtifactsAccessConfig"
+ $ref: "definitions/SOL005VNFPackageManagement_def.yaml#/definitions/ExternalArtifactsAccessConfig"
202:
$ref: "../responses/SOL005_resp.yaml#/responses/202"
400:
```https://forge.etsi.org/rep/nfv/SOL005/-/issues/33In NSDManagement.yaml some parameter descriptions are in schema2022-09-05T08:12:14ZkaidosIn NSDManagement.yaml some parameter descriptions are in schemaI noticed this on 2.7.1-maintenance and 2.8.1. It may be in other branches too. Judging from the other operation parameters as well as the other swagger APIs in the repo this:
```yaml
schema:
$ref: "definitions/SOL005NSDescriptorManag...I noticed this on 2.7.1-maintenance and 2.8.1. It may be in other branches too. Judging from the other operation parameters as well as the other swagger APIs in the repo this:
```yaml
schema:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/CreateNsdInfoRequest"
description: >
Parameters of creating an NS descriptor resource, as defined in clause 5.5.2.3.
```
Should be like this:
```yaml
schema:
$ref: "definitions/SOL005NSDescriptorManagement_def.yaml#/definitions/CreateNsdInfoRequest"
description: >
Parameters of creating an NS descriptor resource, as defined in clause 5.5.2.3.
```
This may seems superficial but it creates issues with validators/generators.
I have the diff ready but I am `not allowed to push code to this project.`https://forge.etsi.org/rep/nfv/SOL005/-/issues/31Bugzilla [Bug 269] - SOL005NSLifecycleManagement_def.yaml VnfInstanceData.vnf...2022-09-01T15:42:52ZVlademir BrusseBugzilla [Bug 269] - SOL005NSLifecycleManagement_def.yaml VnfInstanceData.vnfProfileId is not requiredThis issue was reported in Bugzilla tool by Dominique SIDOU in 12/08/2022, as follows:
Bugzilla [Bug 269] - Missing requestBody definition in /ns_descriptors/{nsdInfoId}/nsd_content put
SOL005/NSLifecycleManagement/definitions/SOL005NS...This issue was reported in Bugzilla tool by Dominique SIDOU in 12/08/2022, as follows:
Bugzilla [Bug 269] - Missing requestBody definition in /ns_descriptors/{nsdInfoId}/nsd_content put
SOL005/NSLifecycleManagement/definitions/SOL005NSLifecycleManagement_def.yaml
vnfProfileId is not required (SOL5 spec alignment)
VnfInstanceData:
type: object
required:
- vnfInstanceId
- - vnfProfileId
+ # - vnfProfileId
The issue was reported for v3.3.1 but it shall be fixed in all subsequent versions.Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL005/-/issues/32Bugzilla [Bug 270] - SOL005_def.yaml DateTime missing type: string2022-09-01T15:42:43ZVlademir BrusseBugzilla [Bug 270] - SOL005_def.yaml DateTime missing type: stringThis issue was reported in Bugzilla tool by Dominique SIDOU in 12/08/2022, as follows:
Bugzilla [Bug 270] - SOL005_def.yaml DateTime missing type: string
SOL005/definitions/SOL005_def.yaml
definitions:
DateTime:
description: >
...This issue was reported in Bugzilla tool by Dominique SIDOU in 12/08/2022, as follows:
Bugzilla [Bug 270] - SOL005_def.yaml DateTime missing type: string
SOL005/definitions/SOL005_def.yaml
definitions:
DateTime:
description: >
Date-time stamp.
Representation: String formatted according toas defined by the date-time production in IETF RFC 3339.
+ type: string
format: date-time
The issue was reported for v3.3.1 but it shall be fixed in all subsequent versions.Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL005/-/issues/30Bugzilla [Bug 268] - Missing requestBody definition in /ns_descriptors/{nsdIn...2022-09-01T15:42:35ZVlademir BrusseBugzilla [Bug 268] - Missing requestBody definition in /ns_descriptors/{nsdInfoId}/nsd_content putThis issue was reported in Bugzilla tool by Dominique SIDOU in 12/08/2022, as follows:
Bugzilla [Bug 268] - Missing requestBody definition in /ns_descriptors/{nsdInfoId}/nsd_content put
Missing requestBody definition in /ns_descriptors...This issue was reported in Bugzilla tool by Dominique SIDOU in 12/08/2022, as follows:
Bugzilla [Bug 268] - Missing requestBody definition in /ns_descriptors/{nsdInfoId}/nsd_content put
Missing requestBody definition in /ns_descriptors/{nsdInfoId}/nsd_content put:
/ns_descriptors/{nsdInfoId}/nsd_content:
put:
description: |
The PUT method is used to upload the content of an NSD archive. See clause 5.4.4.3.3.
parameters:
- $ref: '#/components/parameters/ContentTypeZip'
parameters:
- $ref: '#/components/parameters/ContentTypeZip'
+ requestBody:
+ content:
+ application/zip:
+ schema:
+ type: string
+ format: binary
The issue was reported for v3.3.1 but it shall be fixed in all subsequent versions.Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL005/-/issues/28Bugzilla [Bug 260] - NsdInfoModifications: userDefinedData KeyValuePairs of w...2022-09-01T15:42:26ZVlademir BrusseBugzilla [Bug 260] - NsdInfoModifications: userDefinedData KeyValuePairs of wrong typeThis issue was reported in Bugzilla tool by Frank Bryden in 24/08/2020, as follows:
[Bug 260] NsdInfoModifications: userDefinedData KeyValuePairs of wrong type
The NsdInfoModifications datatype contains a section for showing modified u...This issue was reported in Bugzilla tool by Frank Bryden in 24/08/2020, as follows:
[Bug 260] NsdInfoModifications: userDefinedData KeyValuePairs of wrong type
The NsdInfoModifications datatype contains a section for showing modified userDefinedData. According to SOL005, this is of type KeyValuePairs. No issue there.
The OpenAPI specifies the latter datatype to be an array, when SOL013 specifies it must be an object (7.1.5 @ SOL0013v2.7.1).Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL005/-/issues/29Bugzilla [Bug 267] - SOL005NSLifecycleManagement_def.yaml, missing underscore...2022-09-01T15:42:15ZVlademir BrusseBugzilla [Bug 267] - SOL005NSLifecycleManagement_def.yaml, missing underscore typo for updateType ADD SAPThis issue was reported in Bugzilla tool by Dominique SIDOU in 12/08/2022, as follows:
Bugzilla [Bug 267] - SOL005NSLifecycleManagement_def.yaml, missing underscore typo for updateType ADD SAP
SOL005/NSLifecycleManagement/definitions/...This issue was reported in Bugzilla tool by Dominique SIDOU in 12/08/2022, as follows:
Bugzilla [Bug 267] - SOL005NSLifecycleManagement_def.yaml, missing underscore typo for updateType ADD SAP
SOL005/NSLifecycleManagement/definitions/SOL005NSLifecycleManagement_def.yaml
modified SOL005/NSLifecycleManagement/definitions/SOL005NSLifecycleManagement_def.yaml
@@ -2415,7 +2415,7 @@ definitions:
- MODIFY_VNF_INFORMATION
- CHANGE_EXTERNAL_VNF_CONNECTIVITY
- CHANGE_VNFPKG
- - ADD SAP
+ - ADD_SAP
- REMOVE_SAP
- ADD_NESTED_NS
- REMOVE_NESTED_NS
The issue was reported for v3.3.1 but it shall be fixed in all subsequent versions.Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL005/-/issues/27NsdInfoModifications: userDefinedData KeyValuePairs of wrong type2022-09-01T15:01:48ZGiacomo BerniniNsdInfoModifications: userDefinedData KeyValuePairs of wrong typecopied from: https://forge.etsi.org/bugzilla/show_bug.cgi?id=260copied from: https://forge.etsi.org/bugzilla/show_bug.cgi?id=260https://forge.etsi.org/rep/nfv/SOL005/-/issues/26Attribute dependency in ExtManagedVirtualLinkData data type2022-08-04T16:59:58ZPietro PiscioneAttribute dependency in ExtManagedVirtualLinkData data typeThe description of intCp attribute of ExtManagedVirtualLinkData data type says: "This attribute may only be present if the "netAttDefResourceData" is also present."
Currently, the Open API Specification does not support the attribute de...The description of intCp attribute of ExtManagedVirtualLinkData data type says: "This attribute may only be present if the "netAttDefResourceData" is also present."
Currently, the Open API Specification does not support the attribute dependency as reported in this issue: https://github.com/OAI/OpenAPI-Specification/issues/256.
However, a possible solution is to use an "intermediate" data type called, for instance, _VnfcConnectionInfo_ that contains two attributes, i.e., netAttDefResourceData (mandatory) and intCp (optional). This _VnfcConnectionInfo_ "intermediate" data type would be then included as an optional attribute in the ExtManagedVirtualLinkData data type, resolving the problem of the attribute dependency. On the other hand, this solution would make the ExtManagedVirtualLinkData, not in compliance with the SOL005ed431 specification.https://forge.etsi.org/rep/nfv/SOL005/-/issues/25Attribute dependency issue on InstantiateVnfData data type2022-08-04T16:59:50ZPietro PiscioneAttribute dependency issue on InstantiateVnfData data typeAccording to Note 6 of the InstantiateVnfData data type: "If the overridingVnfdId attribute is present the vnfProfileId attribute shall also be present.". It means that either both attributes must be defined or none of them.
Currently, ...According to Note 6 of the InstantiateVnfData data type: "If the overridingVnfdId attribute is present the vnfProfileId attribute shall also be present.". It means that either both attributes must be defined or none of them.
Currently, the Open API Specification does not support the attribute dependency as reported in this issue: https://github.com/OAI/OpenAPI-Specification/issues/256.
However, a possible solution is to use an "intermediate" data type called, for instance, _vnfdInfo_ that contains two mandatory attributes, i.e., overridingVnfdId and vnfProfileId. This _vnfdInfo_ "intermediate" data type would be then included as an optional attribute in the VnfInstanceData data model, resolving the problem of the attribute dependency. On the other hand, this solution would make the VnfInstanceData, not in compliance with the SOL005ed431 specification.