NFV - Network Functions Virtualisation issueshttps://forge.etsi.org/rep/groups/nfv/-/issues2022-09-05T14:19:14Zhttps://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/23Cannot specify default NS instantiation level of InstantiateVnfData data type2022-07-29T09:53:10ZPietro PiscioneCannot specify default NS instantiation level of InstantiateVnfData data typeAccording to Note 4 of InstantiateVnfData data type: "[...] If none of the two attributes (vnfInstantiationLevelId or targetScaleLevelInfo) are present, the default instantiation level as declared in the VNFD shall be used."
It is not cl...According to Note 4 of InstantiateVnfData data type: "[...] If none of the two attributes (vnfInstantiationLevelId or targetScaleLevelInfo) are present, the default instantiation level as declared in the VNFD shall be used."
It is not clear in which attribute such default instantiation level should be placed.https://forge.etsi.org/rep/nfv/SOL012/-/issues/1pdf files for OpenAPIs v3.x.x wiki page2021-09-02T09:51:06ZVlademir Brussepdf files for OpenAPIs v3.x.x wiki pageThe pdf files for OpenAPIs v3.x.x wiki page (Release 3) shall be created as soon as a tool to generate the files is available. This shall be investigate and when the tool is available the STF team shall be noticed.
There is not yet such...The pdf files for OpenAPIs v3.x.x wiki page (Release 3) shall be created as soon as a tool to generate the files is available. This shall be investigate and when the tool is available the STF team shall be noticed.
There is not yet such tool compatible with OpenaAPI 3.0 (used for Release 3 SOLs).Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL011/-/issues/1pdf files for OpenAPIs v3.x.x wiki page2021-09-02T09:46:54ZVlademir Brussepdf files for OpenAPIs v3.x.x wiki pageThe pdf files for OpenAPIs v3.x.x wiki page (Release 3) shall be created as soon as a tool to generate the files is available. This shall be investigate and when the tool is available the STF team shall be noticed.
There is not yet such...The pdf files for OpenAPIs v3.x.x wiki page (Release 3) shall be created as soon as a tool to generate the files is available. This shall be investigate and when the tool is available the STF team shall be noticed.
There is not yet such tool compatible with OpenaAPI 3.0 (used for Release 3 SOLs).Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL009/-/issues/1pdf files for OpenAPIs v3.x.x wiki page2021-09-02T09:44:13ZVlademir Brussepdf files for OpenAPIs v3.x.x wiki pageThe pdf files for OpenAPIs v3.x.x wiki page (Release 3) shall be created as soon as a tool to generate the files is available. This shall be investigate and when the tool is available the STF team shall be noticed.
The PDF files for Rel...The pdf files for OpenAPIs v3.x.x wiki page (Release 3) shall be created as soon as a tool to generate the files is available. This shall be investigate and when the tool is available the STF team shall be noticed.
The PDF files for Release 2 OpenAPIs (using swagger 2.0) were autogenerated with a tool (compatible with swagger 2.0).
There is not yet such tool compatible with OpenaAPI 3.0 (used for Release 3 SOLs).Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL005/-/issues/20pdf files for OpenAPIs v3.x.x wiki page2021-09-02T09:40:25ZVlademir Brussepdf files for OpenAPIs v3.x.x wiki pageThe pdf files for OpenAPIs v3.x.x wiki page (Release 3) shall be created as soon as a tool to generate the files is available. This shall be investigate and when the tool is available the STF team shall be noticed.
The PDF files for Rel...The pdf files for OpenAPIs v3.x.x wiki page (Release 3) shall be created as soon as a tool to generate the files is available. This shall be investigate and when the tool is available the STF team shall be noticed.
The PDF files for Release 2 OpenAPIs (using swagger 2.0) were autogenerated with a tool (compatible with swagger 2.0).
There is not yet such tool compatible with OpenaAPI 3.0 (used for Release 3 SOLs).Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL002-SOL003/-/issues/2pdf files for OpenAPIs v3.x.x wiki page2021-09-02T09:36:59ZVlademir Brussepdf files for OpenAPIs v3.x.x wiki pageThe pdf files for OpenAPIs v3.x.x wiki page (Release 3) shall be created as soon as a tool to generate the files is available. This shall be investigate and when the tool is available the STF team shall be noticed.
The PDF files for Rel...The pdf files for OpenAPIs v3.x.x wiki page (Release 3) shall be created as soon as a tool to generate the files is available. This shall be investigate and when the tool is available the STF team shall be noticed.
The PDF files for Release 2 OpenAPIs (using swagger 2.0) were autogenerated with a tool (compatible with swagger 2.0).
There is not yet such tool compatible with OpenaAPI 3.0 (used for Release 3 SOLs).Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/api-tests/-/issues/188"api-tests" (2.7.1) tests do not set 'Version' header during the REST calls t...2021-08-31T04:27:26Zbanerjeesu"api-tests" (2.7.1) tests do not set 'Version' header during the REST calls to the MANO.The test-![SOL013_section_9_4_VersionSignaling](/uploads/9a6b106a2f7f19466e5e5bd0cc0c8fd4/SOL013_section_9_4_VersionSignaling.png)cases should pass on the 'Version' HTTP header while making REST calls to MANO, as per SOL003, 005, 002 spe...The test-![SOL013_section_9_4_VersionSignaling](/uploads/9a6b106a2f7f19466e5e5bd0cc0c8fd4/SOL013_section_9_4_VersionSignaling.png)cases should pass on the 'Version' HTTP header while making REST calls to MANO, as per SOL003, 005, 002 specs. Attahed is a screenshot from SOL013 which describes the parameters, details etc while making REST calls.
As per the spec, any API-client that intends to call SOL APIs for versions beyond 2.5.1, "shall" provide the 'Version' HTTP header.https://forge.etsi.org/rep/nfv/SOL005/-/issues/19Swaggers make the 'Version' field as 'required'; However the SOL spec (SOL013...2022-11-03T07:24:26ZbanerjeesuSwaggers make the 'Version' field as 'required'; However the SOL spec (SOL013) marks 'Version' as optional.List of swagger / yaml files, along with the line numbers:
./src/SOL005/components/SOL005_params.yaml-1-components:
./src/SOL005/components/SOL005_params.yaml-2- parameters:
./src/SOL005/components/SOL005_params.yaml-3- Version:
./...List of swagger / yaml files, along with the line numbers:
./src/SOL005/components/SOL005_params.yaml-1-components:
./src/SOL005/components/SOL005_params.yaml-2- parameters:
./src/SOL005/components/SOL005_params.yaml-3- Version:
./src/SOL005/components/SOL005_params.yaml-4- name: Version
./src/SOL005/components/SOL005_params.yaml-5- description: >
./src/SOL005/components/SOL005_params.yaml:6: Version of the API requested to use when responding to this request.
./src/SOL005/components/SOL005_params.yaml-7- in: header
./src/SOL005/components/SOL005_params.yaml-8- required: true
./src/SOL005/components/SOL005_params.yaml-9- schema:
./src/SOL005/components/SOL005_params.yaml-10- type: string
./src/SOL005/components/SOL005_params.yaml-11-
./src/SOL005/NSPerformanceManagement/NSPerformanceManagement.yaml-661-# - name: Version
./src/SOL005/NSPerformanceManagement/NSPerformanceManagement.yaml-662-# description: |
./src/SOL005/NSPerformanceManagement/NSPerformanceManagement.yaml:663:# Version of the API requested to use when responding to this request.
./src/SOL005/NSPerformanceManagement/NSPerformanceManagement.yaml-664-# in: header
./src/SOL005/NSPerformanceManagement/NSPerformanceManagement.yaml-665-# required: true
./src/SOL005/NSPerformanceManagement/NSPerformanceManagement.yaml-666-# type: string
./src/SOL005/NSPerformanceManagement/NSPerformanceManagement.yaml-441-# type: string
./src/SOL005/NSPerformanceManagement/NSPerformanceManagement.yaml-442-# - name: Version
./src/SOL005/NSPerformanceManagement/NSPerformanceManagement.yaml-443-# description: |
./src/SOL005/NSPerformanceManagement/NSPerformanceManagement.yaml:444:# Version of the API requested to use when responding to this request.
./src/SOL005/NSPerformanceManagement/NSPerformanceManagement.yaml-445-# in: header
./src/SOL005/NSPerformanceManagement/NSPerformanceManagement.yaml-446-# required: true
./src/SOL005/NSPerformanceManagement/NSPerformanceManagement.yaml-447-# type: string
That's causing issues with the generated Java code, as the API makes the 'Version' mandatory, and non-compilant with the SOl013 Spec.
--- From Sol013 ---
"The API producer shall support receiving and interpreting the "Version" HTTP header. The API producer shall include
in the response the "Version" HTTP header signaling the used API version, including the "impl" version parameter if
available. If the "impl" version parameter has been omitted in the request, the API producer shall use the combination of
MAJOR, MINOR and PATCH as requested and the highest supported value for the "impl_version" field of the "impl"
version parameter for that combination, if available."
-----https://forge.etsi.org/rep/nfv/api-tests/-/issues/185Parameter value settings in VNFPackageManagementAPI SOL003/SOL0052021-09-22T08:37:04ZyaoyuyParameter value settings in VNFPackageManagementAPI SOL003/SOL005According to the specification file,
when getting the VNF Packages with attribute-based filter, the format should be like (eq,vnfdId,41fdd38a-3d4c-465c-83e0-f80e014425f8)
But now in the parameter text file, the sample settings are offere...According to the specification file,
when getting the VNF Packages with attribute-based filter, the format should be like (eq,vnfdId,41fdd38a-3d4c-465c-83e0-f80e014425f8)
But now in the parameter text file, the sample settings are offered like "vnfdId=41fdd38a-3d4c-465c-83e0-f80e014425f8 ,vnfProvider=NXW"
The reference files are as followed:
https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf (Table 10.4.2.3.2-1: URI query parameters supported by the GET method on this resource)
https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/013/02.06.01_60/gs_NFV-SOL013v020601p.pdf (5.2 Attribute-based filtering)
(Maybe it won't be an issue, since the values can be changed when testing.(`・ω・´))https://forge.etsi.org/rep/nfv/SOL006/-/issues/44Issue in the Pipeline script for Yang Tree generation2021-04-21T07:18:21ZramanathanIssue in the Pipeline script for Yang Tree generationThe HTML tree creation process throws an error in Pipeline. However the tree creation is still successful and the tree has been manually verified for correctness as well. Why the pipeline throws this error needs to be understand and fixe...The HTML tree creation process throws an error in Pipeline. However the tree creation is still successful and the tree has been manually verified for correctness as well. Why the pipeline throws this error needs to be understand and fixed. Please note the line numbers where the errors occur preexisted even in release 3.3.1 (master branch), as in this is a preexisting issue even in prior releases.
Error thrown:
16:31:35 /yang/etsi-nfv-ns.yang:154: error: etsi-nfv-ns:nfv in the path for vnfd-id at /yang/etsi-nfv-descriptors.yang:75 (at /yang/etsi-nfv-ns.yang:152) is not found
16:31:35 /yang/etsi-nfv-ns.yang:165: error: etsi-nfv-ns:nfv in the path for pnfd-id at /yang/etsi-nfv-descriptors.yang:75 (at /yang/etsi-nfv-ns.yang:163) is not found
16:31:35 /yang/etsi-nfv-ns.yang:200: error: etsi-nfv-ns:nfv in the path for vnfd-id at /yang/etsi-nfv-descriptors.yang:75 (at /yang/etsi-nfv-ns.yang:197) is not found
16:31:35 /yang/etsi-nfv-ns.yang:207: error: etsi-nfv-ns:nfv in the path for pnfd-id at /yang/etsi-nfv-descriptors.yang:75 (at /yang/etsi-nfv-ns.yang:204) is not found
16:31:35 /yang/etsi-nfv-ns.yang:534: error: etsi-nfv-ns:nfv in the path for vnfd-id at /yang/etsi-nfv-descriptors.yang:75 (at /yang/etsi-nfv-ns.yang:530) is not found
16:31:35 /yang/etsi-nfv-ns.yang:549: error: etsi-nfv-ns:nfv in the path for pnfd-id at /yang/etsi-nfv-descriptors.yang:75 (at /yang/etsi-nfv-ns.yang:545) is not found
16:31:35 /yang/etsi-nfv-ns.yang:785: error: etsi-nfv-ns:nfv in the path for vnfd-id at /yang/etsi-nfv-descriptors.yang:75 (at /yang/etsi-nfv-ns.yang:782) is not found
16:31:35 /yang/etsi-nfv-ns.yang:954: error: etsi-nfv-ns:nfv in the path for pnfd-id at /yang/etsi-nfv-descriptors.yang:75 (at /yang/etsi-nfv-ns.yang:952) is not found
16:31:35 /yang/etsi-nfv-ns.yang:1814: error: etsi-nfv-ns:nfv in the path for vnfd-id at /yang/etsi-nfv-descriptors.yang:75 (at /yang/etsi-nfv-ns.yang:1812) is not found
16:31:35 /yang/etsi-nfv-vnf.yang:117: error: etsi-nfv-vnf:nfv in the path for nic-io-requirements at /yang/etsi-nfv-descriptors.yang:61 (at /yang/etsi-nfv-vnf.yang:114) is not found
16:31:35 /yang/etsi-nfv-vnf.yang:117: error: etsi-nfv-vnf:nfv in the path for nic-io-requirements at /yang/etsi-nfv-descriptors.yang:61 (at /yang/etsi-nfv-vnf.yang:114) is not found
16:31:35 /yang/etsi-nfv-vnf.yang:381: error: etsi-nfv-vnf:nfv in the path for int-virtual-link-desc at /yang/etsi-nfv-descriptors.yang:61 (at /yang/etsi-nfv-vnf.yang:379) is not found
16:31:35 /yang/etsi-nfv-vnf.yang:404: error: etsi-nfv-vnf:nfv in the path for nicio-requirements at /yang/etsi-nfv-descriptors.yang:61 (at /yang/etsi-nfv-vnf.yang:402) is not found
16:31:35 /yang/etsi-nfv-vnf.yang:1543: error: etsi-nfv-vnf:nfv in the path for int-virtual-link-desc at /yang/etsi-nfv-descriptors.yang:61 (at /yang/etsi-nfv-vnf.yang:1536) is not found
16:31:35 /yang/etsi-nfv-vnf.yang:1581: error: etsi-nfv-vnf:nfv in the path for nicio-requirements at /yang/etsi-nfv-descriptors.yang:61 (at /yang/etsi-nfv-vnf.yang:1579) is not found
16:31:35 /yang/etsi-nfv-vnf.yang:1775: error: etsi-nfv-vnf:nfv in the path for id at /yang/etsi-nfv-descriptors.yang:61 (at /yang/etsi-nfv-vnf.yang:1773) is not found
16:31:35 /yang/etsi-nfv-vnf.yang:3627: error: etsi-nfv-vnf:nfv in the path for virtual-link-desc at /yang/etsi-nfv-descriptors.yang:61 (at /yang/etsi-nfv-vnf.yang:3625) is not foundramanathanramanathanhttps://forge.etsi.org/rep/nfv/SOL006/-/issues/42Fix tree Build issue2021-07-05T09:56:59ZppreeFix tree Build issueIn jenkins pipeline of could see testing compilation happening
However building tree is not complete, looking for an unknown file
15:53:04 Building HTML tree
15:53:05 error /yang/etsi-nfv.yang: [Errno 2] No such file or directory: '/yang...In jenkins pipeline of could see testing compilation happening
However building tree is not complete, looking for an unknown file
15:53:04 Building HTML tree
15:53:05 error /yang/etsi-nfv.yang: [Errno 2] No such file or directory: '/yang/etsi-nfv.yang'https://forge.etsi.org/rep/nfv/SOL006/-/issues/37SAPD: Missing inherited attributes from CPD2021-03-30T04:30:07ZgarciaaleSAPD: Missing inherited attributes from CPDAccording to section 6.2.3.1 of IFA014:
> "A Sapd inherits from the corresponding Cpd Class [...] All attributes of the Cpd are also attributes of the Sapd"
These attributes are specified on section 7.1.6.3 of IFA011 and include a des...According to section 6.2.3.1 of IFA014:
> "A Sapd inherits from the corresponding Cpd Class [...] All attributes of the Cpd are also attributes of the Sapd"
These attributes are specified on section 7.1.6.3 of IFA011 and include a description, the layer protocol, the CpProtocolData, the trunkMode and the id of a security group rule. However, these attributes seem to be missing on the [SAPD YANG definition](https://forge.etsi.org/rep/nfv/SOL006/blob/dev-v3.4.1/src/yang/etsi-nfv-ns.yang#L167) so they cannot be specified at the NSD level.ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/35NFVIFA(20)000201r1_IFA014ed341_fix_Sapd_attribute_associatedCpd2021-03-24T13:08:59ZramanathanNFVIFA(20)000201r1_IFA014ed341_fix_Sapd_attribute_associatedCpdIn the current GS, if a SAPD is re-exposing a CPD from a VNF, it is not possible to identify from which VNFD this CPD has to be extracted as two VNFDs may use the same CPDId for different purposes. Replacing associatedCpdId which referen...In the current GS, if a SAPD is re-exposing a CPD from a VNF, it is not possible to identify from which VNFD this CPD has to be extracted as two VNFDs may use the same CPDId for different purposes. Replacing associatedCpdId which references VnfExtCpd or PnfExtCpd or Sapd, by associatedCpd which includes CpdInConstituentElement removes the ambiguity. VnfExtCpd or PnfExtCpd or Sapd is referenced by constituentCpdId attribute of CpdInConstituentElement.v3.5.1ramanathanramanathanhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/164SOL005 NSDManagement-API Subscriptions NFVO_DUPLICATION==0 is used in both te...2021-02-23T19:05:20ZvignaudSOL005 NSDManagement-API Subscriptions NFVO_DUPLICATION==0 is used in both test cases.In both use case :
`Create duplicated NSD Management subscription with NFVO not creating duplicated subscriptions`
and
`Create duplicated NSD Management subscription with NFVO creating duplicated subscriptions`
Seems to use NFVO_DU...In both use case :
`Create duplicated NSD Management subscription with NFVO not creating duplicated subscriptions`
and
`Create duplicated NSD Management subscription with NFVO creating duplicated subscriptions`
Seems to use NFVO_DUPLICATION==0 for skipping the test.https://forge.etsi.org/rep/nfv/SOL006/-/issues/23Development changes for branch dev-v3.4.12020-10-01T06:42:30ZppreeDevelopment changes for branch dev-v3.4.1https://forge.etsi.org/rep/nfv/api-tests/-/issues/96Implement continuous integration with code validation2020-01-10T11:56:04ZMichele CarignaniImplement continuous integration with code validationPossible steps of the CI
* robot dry run
* robot linting https://pypi.org/project/robotframework-lint/
* automated generation of docx contributions (tentative)
* generate list of all keywords in the project (to see if they can be consoli...Possible steps of the CI
* robot dry run
* robot linting https://pypi.org/project/robotframework-lint/
* automated generation of docx contributions (tentative)
* generate list of all keywords in the project (to see if they can be consolidated)https://forge.etsi.org/rep/nfv/api-tests/-/issues/95UnicodeDecodeError: 'utf8' in Upload NSD Content as plain text file in asynch...2020-01-07T09:47:17ZbaloghtUnicodeDecodeError: 'utf8' in Upload NSD Content as plain text file in asynchronous mode test caseTried to run Upload NSD Content as plain text file in asynchronous mode test case but I have got an error:
UnicodeDecodeError: 'utf8' codec can't decode bytes in position 10-11: invalid continuation bytes.
The used NSD package is worki...Tried to run Upload NSD Content as plain text file in asynchronous mode test case but I have got an error:
UnicodeDecodeError: 'utf8' codec can't decode bytes in position 10-11: invalid continuation bytes.
The used NSD package is working properly so the problem is in the test case I think. Is it passed earlier?https://forge.etsi.org/rep/nfv/api-tests/-/issues/86Unable to generate 404 in all operations in LCM2019-06-18T15:57:34ZElian KrajaUnable to generate 404 in all operations in LCMIn all operations (instantiate, scale, operate ...) the Test Case related to the 404 is not able to trigger that error. URI may need to change.In all operations (instantiate, scale, operate ...) the Test Case related to the 404 is not able to trigger that error. URI may need to change.