NFV - Network Functions Virtualisation issueshttps://forge.etsi.org/rep/groups/nfv/-/issues2021-10-28T05:16:04Zhttps://forge.etsi.org/rep/nfv/SOL006/-/issues/38IFA014ed351_Dependencies IE description improvement2021-10-28T05:16:04ZppreeIFA014ed351_Dependencies IE description improvementNFVIFA(20)000480r2_IFA014ed351_Dependencies_IE_description_improvementNFVIFA(20)000480r2_IFA014ed351_Dependencies_IE_description_improvementv3.5.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/39IFA011ed351_segmentationType definition to subport level.2021-10-28T05:16:41ZppreeIFA011ed351_segmentationType definition to subport level.Follows NFVIFA(20)000387r1: IFA011ed351_Fix_Typos in clause 7-1-6 sync_to_IFA015_work
to correct segmentationType definition to subport level.Follows NFVIFA(20)000387r1: IFA011ed351_Fix_Typos in clause 7-1-6 sync_to_IFA015_work
to correct segmentationType definition to subport level.v3.5.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/40IFA011ed351 Add missing Dependencies IE definition2021-10-28T05:14:51ZppreeIFA011ed351 Add missing Dependencies IE definitionNFVIFA(20)000482r1: IFA011ed351 Add missing Dependencies IE definitionNFVIFA(20)000482r1: IFA011ed351 Add missing Dependencies IE definitionv3.5.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/41IFA011ed351 updates related to the use of VIPs2021-10-28T05:14:28ZppreeIFA011ed351 updates related to the use of VIPsFollows NFVIFA(20)000599r1
for changes VipCpd:
reference to intVirtualLinkDesc and a flag “dedicatedIPAddress” added.
reference to VnfExtCp attribute removed
And a additional fix in referencing vdu-cpdFollows NFVIFA(20)000599r1
for changes VipCpd:
reference to intVirtualLinkDesc and a flag “dedicatedIPAddress” added.
reference to VnfExtCp attribute removed
And a additional fix in referencing vdu-cpdv3.5.1ppreeppreehttps://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/43IFA011ed351 updates scaling descriptors related to use of VIPs2021-10-28T05:14:00ZppreeIFA011ed351 updates scaling descriptors related to use of VIPsFollows NFVIFA(20)000614r7: IFA011ed351 updates of scaling descriptors related to the use of VIPsFollows NFVIFA(20)000614r7: IFA011ed351 updates of scaling descriptors related to the use of VIPsv3.5.1ppreeppreehttps://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/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/api-tests/-/issues/186Unsupported function tested in test case VNFLifecycleManagementAPI Subscripti...2021-06-28T13:36:44ZyaoyuyUnsupported function tested in test case VNFLifecycleManagementAPI Subscriptions SOL003 v2.6.1According to the specicfication file, the parameters supported by the GET method on subscriptions are filter and nextpage_opaque_marker.<br>
However, the attribute selector like exclude_fileds,exlude_default is also tested in Subscriptio...According to the specicfication file, the parameters supported by the GET method on subscriptions are filter and nextpage_opaque_marker.<br>
However, the attribute selector like exclude_fileds,exlude_default is also tested in Subscriptions tests.<br>
Test cases are GET subscriptions with all_fields attribute selector, GET subscriptions with exclude_default attribute selector,GET subscriptions with fields attribute selector,GET subscriptions with exclude_fields attribute selector.
Is this part missing in the specification file or the test cases should be removed?
https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/02.06.01_60/gs_NFV-SOL003v020601p.pdf (Table 5.4.18.3.2-1: URI query parameters supported by the GET method on this resource)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/187Missing set suite variable in keyword in vnfpackagemanagement keyword at mult...2021-09-21T16:43:57ZsinghadiMissing set suite variable in keyword in vnfpackagemanagement keyword at multiple check position```
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
GET ${apiRoot}/${apiName}/${apiVersion}/vnf_packages/${vnfPkgZipVNFD}/vnfd
Check HTTP Response Status Code Is ...```
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"${AUTHORIZATION_HEADER}":"${AUTHORIZATION_TOKEN}"}
GET ${apiRoot}/${apiName}/${apiVersion}/vnf_packages/${vnfPkgZipVNFD}/vnfd
Check HTTP Response Status Code Is 200
```https://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/api-tests/-/issues/189[VNFPackageManagement-API.IndividualVNFPackage] The 'descriptor_id' is fetche...2021-09-28T10:41:41Zbanerjeesu[VNFPackageManagement-API.IndividualVNFPackage] The 'descriptor_id' is fetched as None, causing validation failureFile: SOL005/VNFPackageManagement-API/VNFPackageManagementKeywords.robot
Line: around 200
---
```
Fetch Information from SOL001 descriptor file
Import Variables ${CURDIR}/descriptors/SOL001/VNFD/vnfd_SOL001.yaml
${descriptor_...File: SOL005/VNFPackageManagement-API/VNFPackageManagementKeywords.robot
Line: around 200
---
```
Fetch Information from SOL001 descriptor file
Import Variables ${CURDIR}/descriptors/SOL001/VNFD/vnfd_SOL001.yaml
${descriptor_id}= Get Variable Value ${topology_template.node_templates.properties.descriptor_id}
${provider}= Get Variable Value ${topology_template.node_templates.properties.provider}
${product_name}= Get Variable Value ${topology_template.node_templates.properties.product_name}
${software_version}= Get Variable Value ${topology_template.node_templates.properties.software_version}
${descriptor_version}= Get Variable Value ${topology_template.node_templates.properties.descriptor_version}
```
---
${topology_template.node_templates.properties.descriptor_id} evaluates to None, as the file SOL005/VNFPackageManagement-API/descriptors/SOL001/VNFD/vnfd_SOL001.yaml does not have 'properties' under 'topology_template.node_templates'. And this is pretty much true for all the variables listed above, provider, product_name, ... so on.
Are the descriptor files (e.g. SOL001/VNFD/vnfd_SOL001.yaml) provided in the plugtest source for reference purposes only?2.7.1https://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/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/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/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/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/api-tests/-/issues/190Wrong Problem Details JSON Object set in Keywords Check HTTP Response Body Js...2021-10-05T10:15:18ZyaoyuyWrong Problem Details JSON Object set in Keywords Check HTTP Response Body Json Schema Is ProblemDetails SOL005 VNFPackageManagementAPI v2.6.1When check HTTP Response Body Json Schema Is ProblemDetails
the problem details json object should be application/problem+json according to the RFC7807
but now the value is application/json
https://datatracker.ietf.org/doc/html/rfc7807When check HTTP Response Body Json Schema Is ProblemDetails
the problem details json object should be application/problem+json according to the RFC7807
but now the value is application/json
https://datatracker.ietf.org/doc/html/rfc7807https://forge.etsi.org/rep/nfv/SOL009/-/issues/2OpenAPI wiki page - "models" session in "UI" links and "schemas" session in "...2022-05-28T07:54:10ZVlademir BrusseOpenAPI wiki page - "models" session in "UI" links and "schemas" session in "Editor" links.All APIs in the OpenAPIs wiki page have:
- UI links – there is a “models” section in OpenAPIs swagger UI pages, this section does not exist in other APIs
- Editor links – there is a “schemas” section in OpenAPIS swagger Editor pages,...All APIs in the OpenAPIs wiki page have:
- UI links – there is a “models” section in OpenAPIs swagger UI pages, this section does not exist in other APIs
- Editor links – there is a “schemas” section in OpenAPIS swagger Editor pages, this section does not exist in other APIs
These issues were reported before, I think in v3.3.1, as these sections are not showed in other APIs there is a need to make them as a standard, the sections need to be removed in SOL009 or included in the other APIs.Giacomo BerniniGiacomo Bernini