NFV - Network Functions Virtualisation issueshttps://forge.etsi.org/rep/groups/nfv/-/issues2021-10-28T05:14:51Zhttps://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/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/45IFA011ed361_removal of deprecated element in vnf.2021-12-13T07:41:18ZppreeIFA011ed361_removal of deprecated element in vnf.delete supportMandatory attribute marked deprecated in v3.3.1 from VirtualNetworkInterfaceRequirements information elementdelete supportMandatory attribute marked deprecated in v3.3.1 from VirtualNetworkInterfaceRequirements information elementv3.6.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL009/-/issues/4Query params should not be defined as global parameters in SOL009_params.yaml.2022-01-19T11:54:19ZVlademir BrusseQuery params should not be defined as global parameters in SOL009_params.yaml.SOL009 is using the same parameters in the file SOL009_params.yaml of the GET methods for all interfaces, but the query parameters can be different for each GET method.
Giacomo answered the following:
“The only open point remains the u...SOL009 is using the same parameters in the file SOL009_params.yaml of the GET methods for all interfaces, but the query parameters can be different for each GET method.
Giacomo answered the following:
“The only open point remains the use of query parameters, for which you are right in some cases they should not be defined as global parameters in SOL009_params.yaml.
Given the fact this issue requires a thorough review of all the OpenAPIs, and most of all that the misalignment with the spec only involves the description field of the query parameters for the various operations, I'd suggest to implement this work for next version of OpenAPIs (i.e. ed361).”Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL002-SOL003/-/issues/3Query params should not be defined as global parameters in SOL002SOL003_param...2022-01-25T10:10:17ZVlademir BrusseQuery params should not be defined as global parameters in SOL002SOL003_params.yaml.SOL002 and SOL003 are using the same parameters in the file SOL002SOL003_params.yaml of the GET methods for all interfaces, but the query parameters can be different for each GET method.
Giacomo answered the following:
“The only open po...SOL002 and SOL003 are using the same parameters in the file SOL002SOL003_params.yaml of the GET methods for all interfaces, but the query parameters can be different for each GET method.
Giacomo answered the following:
“The only open point remains the use of query parameters, for which you are right in some cases they should not be defined as global parameters in SOL002SOL003_params.yaml.
Given the fact this issue requires a thorough review of all the OpenAPIs, and most of all that the misalignment with the spec only involves the description field of the query parameters for the various operations, I'd suggest to implement this work for next version of OpenAPIs (i.e. ed361).”Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL005/-/issues/21Query params should not be defined as global parameters in SOL005_params.yaml2022-01-31T08:24:12ZVlademir BrusseQuery params should not be defined as global parameters in SOL005_params.yamlSOL005 is using the same parameters in the file SOL005_params.yaml of the GET methods for all interfaces including "NS Lifecycle Management" and "NS Performance Management" interfaces, for example, but the parameters for both are differe...SOL005 is using the same parameters in the file SOL005_params.yaml of the GET methods for all interfaces including "NS Lifecycle Management" and "NS Performance Management" interfaces, for example, but the parameters for both are different and can be different for others.
Giacomo answered the following:
“The only open point remains the use of query parameters, for which you are right in some cases they should not be defined as global parameters in SOL005_params.yaml.
Given the fact this issue requires a thorough review of all the OpenAPIs, and most of all that the misalignment with the spec only involves the description field of the query parameters for the various operations, I'd suggest to implement this work for next version of OpenAPIs (i.e. ed361).”Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL009/-/issues/3OpenAPI wiki page - NFVManoConfigurationAndInformationManagement-API of v3.5....2022-01-31T11:10:58ZVlademir BrusseOpenAPI wiki page - NFVManoConfigurationAndInformationManagement-API of v3.5.1 showing several errors on "Editor" page.In the "NFVManoConfigurationAndInformationManagement-API" of SOL009 v3.5.1 it is showing several errors when rendering the swagger "Editor" page on Chrome browser.
The use of "oneOf" should be investigated here since in v3.3.1 does not ...In the "NFVManoConfigurationAndInformationManagement-API" of SOL009 v3.5.1 it is showing several errors when rendering the swagger "Editor" page on Chrome browser.
The use of "oneOf" should be investigated here since in v3.3.1 does not have this issue. If so, we need a solution for that.
Structural error at paths./peer_entities.post.requestBody
should have required property '$ref'
missingProperty: $ref
Jump to line 18171
Structural error at paths./peer_entities.post.requestBody
should match exactly one schema in oneOf
Jump to line 18171
...
Giacomo answered that "this is because some data types inside this API have "type" as attribute names, which is also an OpenAPI keyword. So it is a kind of warning that the editor page tool gives to signal it. Not sure how to be avoided to be honest, as we cannot change the attribute name "type" otherwise it will not be compliant with SOL specs."Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/SOL006/-/issues/46IFA011ed361_Fixing IpAddressAssignment flag2022-05-10T04:44:52ZppreeIFA011ed361_Fixing IpAddressAssignment flagv3.6.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/47IFA011ed361 Adding externallyManaged attribute to VnfVirtualLinkDesc2022-05-10T04:45:13ZppreeIFA011ed361 Adding externallyManaged attribute to VnfVirtualLinkDescv3.6.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/49IFA011ed361_FEAT03 Add missing minNumberofPreservedInstances attribute to Nfv...2022-05-10T04:46:11ZppreeIFA011ed361_FEAT03 Add missing minNumberofPreservedInstances attribute to NfviMaintenanceInfo IEv3.6.1ppreeppreehttps://forge.etsi.org/rep/nfv/SOL006/-/issues/48IFA011ed361-Add standardized interface requirements to VirtualNetworkInterfac...2022-05-10T04:46:25ZppreeIFA011ed361-Add standardized interface requirements to VirtualNetworkInterfaceRequirementsv3.6.1ppreeppreehttps://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 Berninihttps://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/SOL005/-/issues/22Cannot specify default NS instantiation level of InstantiateNsRequest and Cha...2022-08-04T16:59:04ZPietro PiscioneCannot specify default NS instantiation level of InstantiateNsRequest and ChangeVnfFlavourData data typesOn Note 5 of InstantiateNsRequest data type is stated that "[..] If none of the two parameters (nsInstantiationLevelId or targetNsScaleLevelInfo) are present, the default NS instantiation level as declared in the NSD shall be used."
It ...On Note 5 of InstantiateNsRequest data type is stated that "[..] If none of the two parameters (nsInstantiationLevelId or targetNsScaleLevelInfo) are present, the default NS instantiation level as declared in the NSD shall be used."
It is not clear where the default NS instantiation level attribute should be placed.
Same issue for ChangeVnfFlavourData data type.https://forge.etsi.org/rep/nfv/SOL005/-/issues/24Attribute dependency issue in VnfInstanceData and NestedNsInstanceData data t...2022-08-04T16:59:29ZPietro PiscioneAttribute dependency issue in VnfInstanceData and NestedNsInstanceData data typesAccording Note 1 of the VnfInstanceData 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 Ope...According Note 1 of the VnfInstanceData 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.
The same issue affects the NestedNsInstanceData data type.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.https://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/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/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 Bernini