aboutsummaryrefslogtreecommitdiffstats
path: root/src/onaptests/steps/simulator
AgeCommit message (Collapse)AuthorFilesLines
2021-06-16[TEST] Create "pnf-macro-test-simulator" resourcesMichal Jagiello1-1/+1
Resolve conflicting "pnf-simulator" resource creation. Replate it with "pnf-macro-test-simulator" Issue-ID: TEST-341 Signed-off-by: Michal Jagiello <michal.jagiello@t-mobile.pl> Change-Id: Icb54cab9b9f8a5e09e657faea96f9ce9bc79acef
2021-05-28[TEST] Use nf-simulator/vesclientMichal Jagiello1-2/+2
Pnf-simulator created "mongo" service and deployment what causes errors. With the nf-simulator/vesclinet we could create mogno service with custom name Issue-ID: TEST-341 Signed-off-by: Michal Jagiello <michal.jagiello@t-mobile.pl> Change-Id: Iafde4be988d44291a56c649a1902319bbeeb050c
2021-05-18[TEST] Patch ip values in pnf-simulator eventMichal Jagiello1-0/+4
Issue-ID: INT-1894 Signed-off-by: Michal Jagiello <michal.jagiello@t-mobile.pl> Change-Id: I59b141fce25581b0fd92fcc3e2857148b7002c2b
2021-05-12Merge "[TEST] Catch k8s connection exceptions"Morgan Richomme1-18/+25
2021-05-11[TEST] Catch ConnectionError exception during pnf simulator startupMichal Jagiello1-1/+1
When PNF simulator starts up a series of requests are sent but if ConnectionError is raised then tests is interrupted and no report is generated Issue-ID: TEST-337 Signed-off-by: Michal Jagiello <michal.jagiello@t-mobile.pl> Change-Id: I5dbdfa3b7d5a2c16b3ecc00ae4ab46ac3bb5443f
2021-05-11[TEST] Catch k8s connection exceptionsMichal Jagiello1-18/+25
In two steps: ExposeCDSBlueprintprocessorNodePortStep and PnfSimulatorCnfRegisterStep we uses kubernetes Python library to prepare environment or check the status of pod instantiation. If connection with k8s api gateway can't be established an exception is raised and no test report is created. Add try...except block to catch connection error and finish test gently Issue-ID: TEST-336 Signed-off-by: Michal Jagiello <michal.jagiello@t-mobile.pl> Change-Id: I1993bec4c886d77645e1a60e0f3d169abeb4e8bd
2021-04-21Wait for pnf simulatorMichal Jagiello1-56/+30
Add VSP for PNF Issue-ID: TEST-280 Signed-off-by: Michal Jagiello <michal.jagiello@t-mobile.pl> Change-Id: If2476f5f9f9fc8d4c14c5dd398a8a659e7fe3e9a
2021-04-07Merge "Remove masspnfsimulator as a git submodule."Bartek Grzybowski5-241/+0
2021-04-07Remove masspnfsimulator as a git submodule.Illia Halych5-241/+0
Removed both submodule and the old pnf directory Issue-ID: INT-1882 Signed-off-by: Illia Halych <illia.halych@t-mobile.pl> Change-Id: Ie439a0dea9aff7efc743822ec5ea5715f4af241e
2021-03-18[PNF] Extend timer before sending request to simulatormorganrol1-1/+1
Tests done on daily Guilin shows that the simulator takes some seconds to start, so we shoudl not send immediately the regsitration request to the simu A retry mechanism could be implemented meanwhile the extension of the timer seems to be enough Issue-ID: INT-1822 Signed-off-by: morganrol <morgan.richomme@orange.com> Change-Id: I648f3d3401206b79190b431d35f83c506788bfaa
2021-01-25PNF simulator CNF instantiation and registation stepsMichal Jagiello2-0/+145
Use CNF of PNF simulator in pnf_macro scenario Issue-ID: INT-1822 Signed-off-by: Michal Jagiello <michal.jagiello@t-mobile.pl> Change-Id: Id7f70b45219a36b7fc70921a1438b0cbe57a1756
2021-01-12Fix steps time measurementMichal Jagiello1-0/+1
Substeps execution time is not stored with the right time of step execution Issue-ID: TEST-292 Signed-off-by: Michal Jagiello <michal.jagiello@t-mobile.pl> Change-Id: I58e2aecb1f3cfb1a2bf78a438fc3d508ecf83cc1
2020-12-16PNF macro instantiationMichal Jagiello2-3/+6
Issue-ID: TEST-280 Change-Id: I6d18b90c3f4c66ddf8c9a4ebe3de7182481e331f Signed-off-by: Michal Jagiello <michal.jagiello@t-mobile.pl>
2020-12-16Update masspnf simulator repository pathBartek Grzybowski1-1/+1
Masspnf simulator has been moved to it's own repository. Change-Id: I6360b478bb853eabf57ddad199e36180c5a8f2e9 Issue-ID: TEST-278 Signed-off-by: Bartek Grzybowski <b.grzybowski@partner.samsung.com>
2020-12-14Add PNF simulator execution and cleanup as a BaseStepEli Halych5-0/+237
1. The simulator is the masspnfsim from integration project. Added as a git submodule. 2. The flow: build image, bootstrap simulator, run simulator, stop simulator, remove simulator, remove image (only simulator). 3. Additionally trigger (sending a message to VES) is handled in pnf/utils.py. To send a request to VES, vesip in settings.PNF_VES_CONFIG should be set to the one accessible from simulator container. Default one (172.17.0.1) communicates with the machine the simulator runs at. 4. commonEventHeader's fields can be overridden in settings.py (here sourceName, reportingEntityName) Issue-ID: TEST-278 Signed-off-by: Eli Halych <illia.halych@t-mobile.pl> Change-Id: Id77dc8c517a30458abd81f2aadc416204be522b5