NFV - Network Functions Virtualisation issueshttps://forge.etsi.org/rep/groups/nfv/-/issues2020-06-12T13:12:06Zhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/100Assignment of response variable @ vs $ in VnfLcmMntOperationKeywords and NSLC...2020-06-12T13:12:06Zraducccradu@luxoft.comAssignment of response variable @ vs $ in VnfLcmMntOperationKeywords and NSLCMOperationKeywordsPlease check the correct assignment of response variable in keywords robot files.
https://forge.etsi.org/rep/nfv/api-tests/blob/2.6.1-fix-plu/SOL003/VNFLifecycleManagement-API/VnfLcmMntOperationKeywords.robot
Set Global Variable @{r...Please check the correct assignment of response variable in keywords robot files.
https://forge.etsi.org/rep/nfv/api-tests/blob/2.6.1-fix-plu/SOL003/VNFLifecycleManagement-API/VnfLcmMntOperationKeywords.robot
Set Global Variable @{response} ${outputResponse}
vs
Set Global Variable ${response} ${outputResponse}
Both forms are used in keyword files which misleads an NFVO solution.https://forge.etsi.org/rep/nfv/api-tests/-/issues/99Typo in file name for Terminate VNF Work Flow2020-05-26T13:37:52ZMichele CarignaniTypo in file name for Terminate VNF Work FlowIn
https://forge.etsi.org/rep/nfv/api-tests/blob/2.6.1.0.02/SOL003/VNFLifecycleManagement-API/TerminatelVNFWorkflow.robot
the file name shall be
TerminateVNFWorkflow.robotIn
https://forge.etsi.org/rep/nfv/api-tests/blob/2.6.1.0.02/SOL003/VNFLifecycleManagement-API/TerminatelVNFWorkflow.robot
the file name shall be
TerminateVNFWorkflow.robotGiacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/api-tests/-/issues/98Empty VnfIdentifierCreationNotification.schema.json2021-06-03T08:49:18ZMichele CarignaniEmpty VnfIdentifierCreationNotification.schema.jsonThe following schema file is empty:
https://forge.etsi.org/rep/nfv/api-tests/blob/master/SOL002/VNFLifecycleManagement-API/schemas/VnfIdentifierCreationNotification.schema.json
The definition should be at:
https://forge.etsi.org/rep/n...The following schema file is empty:
https://forge.etsi.org/rep/nfv/api-tests/blob/master/SOL002/VNFLifecycleManagement-API/schemas/VnfIdentifierCreationNotification.schema.json
The definition should be at:
https://forge.etsi.org/rep/nfv/SOL002-SOL003/blob/v2.4.1/src/definitions/SOL002SOL003VNFLifecycleManagement_def.yaml#L704https://forge.etsi.org/rep/nfv/api-tests/-/issues/97Empty vnfLcmOperationOccurrenceNotification.schema.json2021-02-09T08:17:28ZMichele CarignaniEmpty vnfLcmOperationOccurrenceNotification.schema.jsonThe following schema file is empty:
https://forge.etsi.org/rep/nfv/api-tests/blob/master/SOL003/VNFLifecycleManagement-API/schemas/vnfLcmOperationOccurrenceNotification.schema.json
The definition should be the one available at:
https...The following schema file is empty:
https://forge.etsi.org/rep/nfv/api-tests/blob/master/SOL003/VNFLifecycleManagement-API/schemas/vnfLcmOperationOccurrenceNotification.schema.json
The definition should be the one available at:
https://forge.etsi.org/rep/nfv/SOL002-SOL003/blob/v2.4.1/src/SOL002/VNFLifecycleManagementNotification/definitions/VNFLifecycleManagementNotification_def.yamlhttps://forge.etsi.org/rep/nfv/SOL006/-/issues/19SOL006ed331 FEAT10 IFA014 Augment anti-affinity scope2020-03-02T17:03:25ZjethanandaniSOL006ed331 FEAT10 IFA014 Augment anti-affinity scopeThis issue tracks the implementation of FEAT10.This issue tracks the implementation of FEAT10.v3.3.1jethanandanijethanandanihttps://forge.etsi.org/rep/nfv/SOL006/-/issues/18SOL006 - Mirror of NFVSOL(20)000027 for v2.8.12020-02-11T16:50:35ZjethanandaniSOL006 - Mirror of NFVSOL(20)000027 for v2.8.1This is a mirror of the CR NFVSOL(20)000027 that changed affinityOrAntiAffinityGroupId in VNFD and NSD from a list to a leaf-list. That CR is being tracked as part of nfv/SOL006#17.
In YANG, list consists of multiple attributes, while l...This is a mirror of the CR NFVSOL(20)000027 that changed affinityOrAntiAffinityGroupId in VNFD and NSD from a list to a leaf-list. That CR is being tracked as part of nfv/SOL006#17.
In YANG, list consists of multiple attributes, while leaf-list consists of a single item or is scalar. Since affinityOrAntiAffinityGroupId is a scalar list of ids, it should be a leaf-list, not a list.v2.8.1jethanandanijethanandanihttps://forge.etsi.org/rep/nfv/SOL006/-/issues/17affintyOrAntiAffinityGroupId should be leaf-list, not a list.2020-01-23T21:23:51ZjethanandaniaffintyOrAntiAffinityGroupId should be leaf-list, not a list.In IFA011 affinityOrAntiAffinityGroupId in VduProfile and VirtualLinkProfile is currently modeled as a list. It should be modeled as a leaf-list, as it is a scalar list of ids.
Similar is the case with IFA014.
This issue will track the...In IFA011 affinityOrAntiAffinityGroupId in VduProfile and VirtualLinkProfile is currently modeled as a list. It should be modeled as a leaf-list, as it is a scalar list of ids.
Similar is the case with IFA014.
This issue will track the fixes for it.v3.3.1jethanandanijethanandanihttps://forge.etsi.org/rep/nfv/SOL006/-/issues/16nfv/SOL006#12 does not implement FEAT03 NFVI MOD correctly2020-02-11T21:37:49Zjethanandaninfv/SOL006#12 does not implement FEAT03 NFVI MOD correctlynfv/SOL006#12 and MR nfv/SOL006!69 did not implement FEAT03 NFVI MOD correctly.
nfviMaintenanceInfo was added to LocalAffinityOrAntiAffinityRule for IFA011 or VNFD. However, SOL006 had a common definition for LocalAffinityOrAntiAffinit...nfv/SOL006#12 and MR nfv/SOL006!69 did not implement FEAT03 NFVI MOD correctly.
nfviMaintenanceInfo was added to LocalAffinityOrAntiAffinityRule for IFA011 or VNFD. However, SOL006 had a common definition for LocalAffinityOrAntiAffinityRule for VNFD and NSD. Therefore nfviMaintenanceInfo does NOT belong in the common definition and should be added only in the case of VNFD.
This issue will track removing of nfviMaintenanceInfo from the common definition to VNFD only and update the corresponding examples.v3.3.1jethanandanijethanandanihttps://forge.etsi.org/rep/nfv/SOL006/-/issues/15SOL006ed331 FEAT16 - SAL2020-02-11T21:40:11ZjethanandaniSOL006ed331 FEAT16 - SALThis issue is to track the implementation of FEAT16 - SAL.This issue is to track the implementation of FEAT16 - SAL.v3.3.1jethanandanijethanandanihttps://forge.etsi.org/rep/nfv/SOL006/-/issues/14Mirror nfv/SOL006!13 for v2.8.12020-02-11T21:42:36ZjethanandaniMirror nfv/SOL006!13 for v2.8.1The issue applies to v2.8.1 also.The issue applies to v2.8.1 also.v2.8.1jethanandanijethanandanihttps://forge.etsi.org/rep/nfv/SOL006/-/issues/13Implement CR NFVIFA(18)0001051 - IFA014ed321 Rel3 Mirror NsVirtualLinkDesc2020-01-23T21:21:39ZjethanandaniImplement CR NFVIFA(18)0001051 - IFA014ed321 Rel3 Mirror NsVirtualLinkDescThis CR proposed to remove several attributes that are no longer in use by NsVirtualLinkDesc. While provider and version were removed, the definition still consists of security (securityParameters) that has been defined in SOL007 and the...This CR proposed to remove several attributes that are no longer in use by NsVirtualLinkDesc. While provider and version were removed, the definition still consists of security (securityParameters) that has been defined in SOL007 and there is no plan to define a virtual link level security.
This issue will be used to track the removal of that attribute.v3.3.1jethanandanijethanandanihttps://forge.etsi.org/rep/nfv/api-tests/-/issues/94Wrong parameter name in GET Network Service Descriptors Information with attr...2021-06-03T08:49:18ZbaloghtWrong parameter name in GET Network Service Descriptors Information with attribute-based filter test caseSOL005/NSDManagement-API/environment/NSDescriptors.robot
```
GET Network Service Descriptors Information with attribute-based filter
[Documentation] Test ID: 5.3.1.1.2
... Test title: GET Network Service Descriptors Informa...SOL005/NSDManagement-API/environment/NSDescriptors.robot
```
GET Network Service Descriptors Information with attribute-based filter
[Documentation] Test ID: 5.3.1.1.2
... Test title: GET Network Service Descriptors Information with attribute-based filter
... Test objective: The objective is to test the retrieval of Network Service Descriptors information using attribute-based filter, perform a JSON schema validation of the collected data structure, and verify that the retrieved information matches the issued attribute-based filter
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO.
... Reference: section 5.4.2.3.2 - SOL005 v2.4.1
... Config ID: Config_prod_NFVO
... Applicability: none
... Post-Conditions: none
GET Network Service Descriptors Information with attribute-based filter
Check HTTP Response Status Code Is 200
Check HTTP Response Body Json Schema Is NsdInfos
Check HTTP Response Body NsdInfos Matches the requested attribute-based filter
```
SOL005/NSDManagement-API/environment/NSDManagementKeywords.robot
```
GET Network Service Descriptors Information with attribute-based filter
Log The GET method queries multiple NS descriptors using Attribute-based filtering parameters
Set Headers {"Accept": "${ACCEPT_JSON}"}
Run Keyword If ${AUTH_USAGE} == 1 Set Headers {"Authorization": "${AUTHORIZATION}"}
GET ${apiRoot}/${apiName}/${apiVersion}/ns_descriptors?${POS_FIELDS}
${output}= Output response
Set Suite Variable ${response} ${output}
```
SOL005/NSDManagement-API/environment/nsDescriptors.txt
```
*** Variables ***
${POS_FIELDS} name=nsdOnboardingState
```
From the standard:
All attribute names that appear in the NsdInfo and in data types referenced from
it shall be supported in attribute-based filtering parameters.
In the Definition of the NsdInfo data type there is no name attribute, it should be nsdName.https://forge.etsi.org/rep/nfv/api-tests/-/issues/93Wrong HTTP Response Status Code in Get all Network Service Descriptors Inform...2021-02-12T08:57:46ZbaloghtWrong HTTP Response Status Code in Get all Network Service Descriptors Information with malformed authorization token test case```
Get all Network Service Descriptors Information with malformed authorization token
[Documentation] Test ID: 5.3.1.1.4
... Test title: Get all Network Service Descriptors Information with malformed authorization token
...```
Get all Network Service Descriptors Information with malformed authorization token
[Documentation] Test ID: 5.3.1.1.4
... Test title: Get all Network Service Descriptors Information with malformed authorization token
... Test objective: The objective is to test that the retrieval of Network Service Descriptors Information fails when using malformed authorization token
... Pre-conditions: One or more Network Service Descriptors are onboarded in the NFVO.
... Reference: section 4.5.3.3, 5.4.2.3.2 - SOL005 v2.4.1
... Config ID: Config_prod_NFVO
... Applicability: The NFVO requires the usage of access tokens for authorizing the API requests.
... Post-Conditions: none
Get all Network Service Descriptors Information with malformed authorization token
Check HTTP Response Status Code Is 400
```
The HTTP Response Status Code should be 401, the provided token is not authorized but it seems valid.https://forge.etsi.org/rep/nfv/api-tests/-/issues/92Wrong parameter name in NsdInfo.schema.json2021-02-08T16:10:53ZbaloghtWrong parameter name in NsdInfo.schema.jsonIn SOL005/NSDManagement-API/schemas/NsdInfo.schema.json there is a typo in onboardingFailureDetails:
```json
"onboardingFailureDetails": {
"description": "The definition of the general \"ProblemDetails\" data structure from IETF R...In SOL005/NSDManagement-API/schemas/NsdInfo.schema.json there is a typo in onboardingFailureDetails:
```json
"onboardingFailureDetails": {
"description": "The definition of the general \"ProblemDetails\" data structure from IETF RFC 7807 [19] is reproduced in this structure. Compared to the general framework defined in IETF RFC 7807 [19], the \"status\" and \"detail\" attributes are mandated to be included by the present document, to ensure that the response contains additional textual information about an error. IETF RFC 7807 [19] foresees extensibility of the \"ProblemDetails\" type. It is possible that particular APIs in the present document, or particular implementations, define extensions to define additional attributes that provide more information about the error. The description column only provides some explanation of the meaning to Facilitate understanding of the design. For a full description, see IETF RFC 7807 [19].\n",
"type": "object",
"required": [
"statussss",
"detail"
],
```
I think statussss should be status.https://forge.etsi.org/rep/nfv/SOL006/-/issues/12SOL006ed331 FEAT03 - NFVI MOD2020-02-11T16:59:24ZjethanandaniSOL006ed331 FEAT03 - NFVI MODThis issue tracks the implementation of FEAT03 - NFVI MOD.This issue tracks the implementation of FEAT03 - NFVI MOD.v3.3.1jethanandanijethanandanihttps://forge.etsi.org/rep/nfv/SOL006/-/issues/11Implement IFA014 MegaCR FEAT05 - Add priority to NSD2020-06-08T19:19:20ZjethanandaniImplement IFA014 MegaCR FEAT05 - Add priority to NSDFEAT05 enables adding priority to NS Deployment Flavour to enable resource allocation for things like Network Slicing.FEAT05 enables adding priority to NS Deployment Flavour to enable resource allocation for things like Network Slicing.v3.3.1jethanandanijethanandanihttps://forge.etsi.org/rep/nfv/SOL006/-/issues/10Implement NFVIFA(19)000154: FEAT02 IFA011 Review declare LCM coordination int...2019-12-19T20:55:34ZjethanandaniImplement NFVIFA(19)000154: FEAT02 IFA011 Review declare LCM coordination interface in VnfInterfaceDetailsThe IFA CR adds another enum type for vnfInterfaceName under VnfInterfaceDetails. This issue is opened to track the addition of that enum.The IFA CR adds another enum type for vnfInterfaceName under VnfInterfaceDetails. This issue is opened to track the addition of that enum.v3.3.1jethanandanijethanandanihttps://forge.etsi.org/rep/nfv/SOL006/-/issues/9Fix the change in NFVIFA(18)00503 that changed the layerProtocol attribute fr...2019-12-19T20:53:23ZjethanandaniFix the change in NFVIFA(18)00503 that changed the layerProtocol attribute from 1 to 1..N.SOL006 has implemented the IFA CR above. However, the cardinality of layerProtocol is 1..N, not 0..N as implemented in SOL006.
To correct it SOL006 needs to add 'min-elements 1' under layerProtocol.SOL006 has implemented the IFA CR above. However, the cardinality of layerProtocol is 1..N, not 0..N as implemented in SOL006.
To correct it SOL006 needs to add 'min-elements 1' under layerProtocol.v2.8.1jethanandanijethanandanihttps://forge.etsi.org/rep/nfv/SOL006/-/issues/8Add LifeCycleManagementScript events for external events that are new in rele...2019-12-19T20:50:39ZjethanandaniAdd LifeCycleManagementScript events for external events that are new in release 3.nfv/SOL006#5 and nfv/SOL006#7 added new internal events for LifeCycleManagementScript events. This issue is opened to track the addition of corresponding external events.nfv/SOL006#5 and nfv/SOL006#7 added new internal events for LifeCycleManagementScript events. This issue is opened to track the addition of corresponding external events.v2.8.1jethanandanijethanandanihttps://forge.etsi.org/rep/nfv/SOL006/-/issues/7Implement NFVIFA(19)000061r3: FEAT02 IFA011 MegaCR2019-12-19T20:48:17ZjethanandaniImplement NFVIFA(19)000061r3: FEAT02 IFA011 MegaCRThis CR implements [NFVIFA_19_000061r3__FEAT02_IFA011_MegaCR](/uploads/13adf590b21c350bf9d2828f555f7138/NFVIFA_19_000061r3__FEAT02_IFA011_MegaCR) Vnf Software ModificationThis CR implements [NFVIFA_19_000061r3__FEAT02_IFA011_MegaCR](/uploads/13adf590b21c350bf9d2828f555f7138/NFVIFA_19_000061r3__FEAT02_IFA011_MegaCR) Vnf Software Modificationjethanandanijethanandani