NFV - Network Functions Virtualisation issueshttps://forge.etsi.org/rep/groups/nfv/-/issues2019-12-11T02:30:16Zhttps://forge.etsi.org/rep/nfv/SOL006/-/issues/5Implement IFA011 MegaCR FEAT15 VNF Snapshot2019-12-11T02:30:16ZjethanandaniImplement IFA011 MegaCR FEAT15 VNF SnapshotThis issue is to track changes for implementing [IFA011_MegaCR_FEAT15_VNF_Snapshot](/uploads/72dcf09b5ccab65a356e1e438ea64c52/IFA011_MegaCR_FEAT15_VNF_Snapshot)This issue is to track changes for implementing [IFA011_MegaCR_FEAT15_VNF_Snapshot](/uploads/72dcf09b5ccab65a356e1e438ea64c52/IFA011_MegaCR_FEAT15_VNF_Snapshot)jethanandanijethanandanihttps://forge.etsi.org/rep/nfv/SOL006/-/issues/4Implement NFVIFA(18)000600r2 - Remove element groups2019-12-09T19:44:51ZjethanandaniImplement NFVIFA(18)000600r2 - Remove element groupsjethanandanijethanandanihttps://forge.etsi.org/rep/nfv/SOL006/-/issues/3Implement NFVIFA(18)000562r2_IFA011ed251_nicIoRequirements2019-12-09T19:48:29ZjethanandaniImplement NFVIFA(18)000562r2_IFA011ed251_nicIoRequirements2.6.1 and 2.7.1 version of SOL006 does not implement [NFVIFA_18_000562r2_IFA011ed251_nicIoRequirements](/uploads/62a949108fb9f589a977ab878ed2fcd5/NFVIFA_18_000562r2_IFA011ed251_nicIoRequirements). This issue has been opened to track that...2.6.1 and 2.7.1 version of SOL006 does not implement [NFVIFA_18_000562r2_IFA011ed251_nicIoRequirements](/uploads/62a949108fb9f589a977ab878ed2fcd5/NFVIFA_18_000562r2_IFA011ed251_nicIoRequirements). This issue has been opened to track that issue.jethanandanijethanandanihttps://forge.etsi.org/rep/nfv/SOL006/-/issues/2Implement IFA011Ed251 CR NFVIFA(18)000381r1 - Enhance the virtual storage mod...2020-02-12T01:01:05ZjethanandaniImplement IFA011Ed251 CR NFVIFA(18)000381r1 - Enhance the virtual storage modelling in VNFDThe current model does not support IFA011ed251 CR NFVIFA(18)000381r1, [Enhance_the_virtual_storage_modelling_in_VNFD](/uploads/f81e167f0cf79e8158b0149d317d78ed/Enhance_the_virtual_storage_modelling_in_VNFD)The current model does not support IFA011ed251 CR NFVIFA(18)000381r1, [Enhance_the_virtual_storage_modelling_in_VNFD](/uploads/f81e167f0cf79e8158b0149d317d78ed/Enhance_the_virtual_storage_modelling_in_VNFD)jethanandanijethanandanihttps://forge.etsi.org/rep/nfv/SOL006/-/issues/1Sequencing rules in SOL006 LCM scripts2020-02-12T00:59:31ZjethanandaniSequencing rules in SOL006 LCM scriptsThe following action point needs to be addressed as part of SOL006.
SOL95-AP5 - Clarify whether SOL006 should specify the sequencing rules between scripts triggered on internal and external events.
In ETSI GS NFV-IFA 011, the definiti...The following action point needs to be addressed as part of SOL006.
SOL95-AP5 - Clarify whether SOL006 should specify the sequencing rules between scripts triggered on internal and external events.
In ETSI GS NFV-IFA 011, the definition of the "LifeCycleManagementScript" information element of the VNFD associates scripts with events, where an event can be an external or an internal stimulus.
In SOL001, external stimuli are mapped to TOSCA operations corresponding to the VNF LCM operations defined in ETSI GS NFV-IFA 007 and internal stimuli are mapped to preamble and postamble of these TOSCA operations. If an LCM script is associated to a TOSCA operation that represents a preamble or a postamble to a VNF LCM operation, the script is executed before or after the execution of the VNF LCM operation implementation, respectively.
It looks like there are actually two issues w.r.t. how SOL006 implements IFA011 concepts.
1. The first issue is that SOL006 defines a single event type internal-lifecycle-management-script-event the specification of which – in the common-definitions.yang module) seems to exclude external stimuli.
2. The second issue (which is the one originally targeted by the action point) is that SOL006 does not specify the order of execution between LCM scripts attached to an external stimuli et LCM scripts attached to an internal stimuli. This issue can’t be fixed without fixing the 1st one.jethanandanijethanandanihttps://forge.etsi.org/rep/nfv/api-tests/-/issues/91Checking Location header on Operation Tasks should be removed2020-11-19T15:16:14ZElian KrajaChecking Location header on Operation Tasks should be removedLine 22 in VNFLifeCycleManagementAPI/CancelOperationTask.robot
` Should Contain ${headers} Location`
should be removed since it is not required.
The same operation should be done on the other LCM Operations TASKLine 22 in VNFLifeCycleManagementAPI/CancelOperationTask.robot
` Should Contain ${headers} Location`
should be removed since it is not required.
The same operation should be done on the other LCM Operations TASKhttps://forge.etsi.org/rep/nfv/api-tests/-/issues/90[GENERIC] Content-Type when errors occur should be application/problem+json2021-10-05T10:15:18ZElian Kraja[GENERIC] Content-Type when errors occur should be application/problem+jsonAs per 4.3.5.2 General mechanism when an error occurs the Content-Type shall be set to "application/problem+json"As per 4.3.5.2 General mechanism when an error occurs the Content-Type shall be set to "application/problem+json"https://forge.etsi.org/rep/nfv/api-tests/-/issues/89Header Location shhould not be checked in Individual VNF LCM operation occurr...2021-06-03T08:49:18ZElian KrajaHeader Location shhould not be checked in Individual VNF LCM operation occurrenceIn the operations of Retry, rollback etc, on the POST method the check on Location header should be removed.In the operations of Retry, rollback etc, on the POST method the check on Location header should be removed.https://forge.etsi.org/rep/nfv/api-tests/-/issues/88Update requirements.txt is needed2019-06-27T07:23:38ZElian KrajaUpdate requirements.txt is neededLine 8: `robotframework-jsonlibrary==0.2` should become `robotframework-jsonlibrary` and the extention file for the jsonlibrary should be removed since the patch is not more necessaryLine 8: `robotframework-jsonlibrary==0.2` should become `robotframework-jsonlibrary` and the extention file for the jsonlibrary should be removed since the patch is not more necessaryElian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/87Update on Subscriptions in SOL005/VNFPackageManagement-API when duplications ...2019-06-27T07:23:59ZElian KrajaUpdate on Subscriptions in SOL005/VNFPackageManagement-API when duplications are testedKeyword `Send Post Request for Duplicated VNF Package Subscription` should not check the fact that the NFVO is able or not to handle duplication of the subscriptions, since the behaviour based on the result is checked on the next steps o...Keyword `Send Post Request for Duplicated VNF Package Subscription` should not check the fact that the NFVO is able or not to handle duplication of the subscriptions, since the behaviour based on the result is checked on the next steps of the main keyword.Elian KrajaElian Krajahttps://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.https://forge.etsi.org/rep/nfv/api-tests/-/issues/85Wrong URI in SOL002/VNFIndicator-API/VNFIndicators.robot2020-10-26T06:13:39ZElian KrajaWrong URI in SOL002/VNFIndicator-API/VNFIndicators.robotLine 209 should contain a wrong URI
i.e.: `Get ${apiRoot}/${apiName}/${apiVersion}/indicator`Line 209 should contain a wrong URI
i.e.: `Get ${apiRoot}/${apiName}/${apiVersion}/indicator`Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/84Keyword "Check resource instantiated" in SOL003/VNFLifeCycleManagement-API sh...2020-11-19T14:48:27ZElian KrajaKeyword "Check resource instantiated" in SOL003/VNFLifeCycleManagement-API should be parametrizedThe keyword "Check resource instantiated" checks always the same variable ${vnfInstance} even when the task is trying to use another one
I.e.: Instantiate a vnfInstance Conflict in InstantiateVNFTask.robot is trying to instantiate a vnf...The keyword "Check resource instantiated" checks always the same variable ${vnfInstance} even when the task is trying to use another one
I.e.: Instantiate a vnfInstance Conflict in InstantiateVNFTask.robot is trying to instantiate a vnf with ID ${instantiatedVnfInstanceId}, but in the SETUP part, the "Check resource instantiated" performs a check on instance id ${vnfInstance}https://forge.etsi.org/rep/nfv/api-tests/-/issues/83Missing schema in SOL003/VNFLifeCycleManagement-API2021-06-03T08:49:18ZElian KrajaMissing schema in SOL003/VNFLifeCycleManagement-APINo such file or directory: 'schemas//VnfLcmOpOcc.schema.json'No such file or directory: 'schemas//VnfLcmOpOcc.schema.json'https://forge.etsi.org/rep/nfv/api-tests/-/issues/82ETag should not be checked on PATCH Operations2020-11-18T18:58:30ZElian KrajaETag should not be checked on PATCH OperationsIn the PATCH operations, it should be avoided the check of the ETag, since the operation will be asynchronous. In fact, a 202 Accepted is returned and as reported in the spec (Table 5.4.3.3.4-2 of SOL003):
`The request was accepted for ...In the PATCH operations, it should be avoided the check of the ETag, since the operation will be asynchronous. In fact, a 202 Accepted is returned and as reported in the spec (Table 5.4.3.3.4-2 of SOL003):
`The request was accepted for processing, but the processing has not been completed.`
FILE: SOL003/VNFLifecycleManagement-API/IndividualVNFInstance.robothttps://forge.etsi.org/rep/nfv/api-tests/-/issues/81Keyword "Check Postcondition VNF Package Subscription Is Set" should be checked2019-06-27T07:24:10ZElian KrajaKeyword "Check Postcondition VNF Package Subscription Is Set" should be checkedKEYWORD BuiltIn . Run Keyword If Should Not Be Equal As Strings, ${location}, Location, GET, ${apiRoot}/${apiName}/${apiVersion}/subscriptions/${response['body']['id']}
Runs the given keyword with the given arguments, if condition is tr...KEYWORD BuiltIn . Run Keyword If Should Not Be Equal As Strings, ${location}, Location, GET, ${apiRoot}/${apiName}/${apiVersion}/subscriptions/${response['body']['id']}
Runs the given keyword with the given arguments, if condition is true.
Start / End / Elapsed: 20190604 12:57:00.774 / 20190604 12:57:00.775 / 00:00:00.001
12:57:00.775 FAIL Evaluating expression 'Should Not Be Equal As Strings' failed: SyntaxError: invalid syntax (<string>, line 1)Giacomo BerniniGiacomo Berninihttps://forge.etsi.org/rep/nfv/api-tests/-/issues/80Typo in IndividualVNFPackages2019-06-27T07:24:15ZElian KrajaTypo in IndividualVNFPackagesIl line 19, validation should be done on variable ${vnfPkgInfo}
FILE: SOL005/VNFPackageManagemt-API/IndividualVNFPackage.robotIl line 19, validation should be done on variable ${vnfPkgInfo}
FILE: SOL005/VNFPackageManagemt-API/IndividualVNFPackage.robotElian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/79Typos on Subscriptions.robot o n NSD-Management-API2019-06-27T07:24:48ZElian KrajaTypos on Subscriptions.robot o n NSD-Management-APISubscriptions.robot
1. Line 23 NsdmSubscription should be NsdmSubscriptions
2. Line 57 PmSubscription should be NsdmSubscriptionSubscriptions.robot
1. Line 23 NsdmSubscription should be NsdmSubscriptions
2. Line 57 PmSubscription should be NsdmSubscriptionElian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/78Error loading json in PNFContent2019-06-27T07:24:53ZElian KrajaError loading json in PNFContentIn order to correctly load jsons, should be used the `Get File` keyword instead of `Get Binary File`In order to correctly load jsons, should be used the `Get File` keyword instead of `Get Binary File`Elian KrajaElian Krajahttps://forge.etsi.org/rep/nfv/api-tests/-/issues/77[GENERIC] REST library not supporting multipart payload.2021-06-03T08:49:18ZElian Kraja[GENERIC] REST library not supporting multipart payload.When a csar or zip file are supposed to be a payload of a POST or a PUT, the REST library fails.
In order to avoid this, the RequestLibrary should be used instead of RESTWhen a csar or zip file are supposed to be a payload of a POST or a PUT, the REST library fails.
In order to avoid this, the RequestLibrary should be used instead of REST