- Action point follow-up
- Michał Jagiełło pnf_macro add processing for pnf_macro to wait for a clean startup of the simulator (currently time based, and it seems that it takes more time than expected)
- Not done
- Morgan Richomme cleanup basic_clamp and re-run it on a daily master
- Done
- Michał Jagiełło complete basic_vm_macro
- In progress, issue in SDNC:
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key SDNC-1515
- In progress, issue in SDNC:
- Morgan Richomme create wiki page to reference the GUI endpoints to be tested
- Done Honolulu UIs
- all review the wiki page and add the links of the GUI you are using
- Morgan Richomme create a wiki page to improve the process on test integration in CSIT and/or CI from third parties
- all review/complete the wiki on process to integrate new external tests in CSIT or CI
- Morgan Richomme initiate an official page on simulator
- Krzysztof Kuzmicki complete the official simulator page with NS illustration
- To be Done
- Bartek Grzybowski review the official simu page (list of usable simu)
- Done
- Illia Halych review the official simu page (pythonsdk wrapper)
- To be Done
- Michał Jagiełło pnf_macro add processing for pnf_macro to wait for a clean startup of the simulator (currently time based, and it seems that it takes more time than expected)
- Admin
- Illia Halych officially new Integration commiter, welcome !
- No update on xtesting docker release
- LF IT backend , not possible to move logs, no cleanup mechanism (manual cleanup needed)
- Honolulu
- status:board review https://jira.onap.org/secure/RapidBoard.jspa?rapidView=229&selectedIssue=INT-1842
- action #all review your Jira ticket move to instanbul or close
- Daily Honolulu CI/CD chain created
- Remaining work on tests
basic_clamp: integrated in CI, several successful runs, but improvements needed to manage exceptions (Policy/DCAE/CLamp) => https://gerrit.onap.org/r/c/testsuite/pythonsdk-tests/+/120234
basic_vm_macro (replace vfw_macro): in progress still some issues on the daily honolulu
pnf_macro => add mechanism to have a better control of the pnf simu launch (timer is not enough) => # action Michal
refactoring of 5gbulkpm => #action Krzysztof => test done this afternoon => merged
tern: test declared in CI, but issue => # action morgan & Alexander
stability tests
I started the first resiliency tests: TEST-308 - [Resiliency] Evaluate ONAP behavior on k8s worker node restart
- Other labs are experiencing different issues
- Nokia => pod remain in stuck
- #action Daniel, Andreas create a JIRA ticket for each resiliency test
- #action morgan create a wiki page to consolidate resiliencey tests
- Other labs are experiencing different issues
stability I planned to regive a try to Natacha's suite as soon as the other tests are OK
- to be tried asap: if enough resources => weekly Honolulu to be launched on Wednesday
consolidation of versions: I was waiting for the come back of Pawel but as far as I understood, you will move to othe r challenges soon.. :) so I need to review that
better exception catching
integration of the GUI part to generate an html reporting (for the moment I usually replay manually the tests, get the results and apply the GUI processing manually)
removal of the submodule: test in progress (seems there was an import in the simu step), once done we could review our docker build (to remove the developer mode) but we shall not forget to adapt xtesting-onap according ly (/Src/onaptests/src/onaptests => /usr/lib/python3.8/sites-available/onaptests
CDS / CSIT => will not have the resource to do it for Honolulu => move to Istanbul
GUI tests: wait for completion of the Wiki page and see if enough bandwidth => move to instanbul
- documentation update started
- honolulu branching done
- release testsuite 1.8.0 to be done
- status:board review https://jira.onap.org/secure/RapidBoard.jspa?rapidView=229&selectedIssue=INT-1842
- Istanbul
- requests from new project (OOF, AAI) "on how to bring new tests to integration" => How to help projects to integrate their tests in Integration?
- run robot tests out of onap namespace: How to run the tests out of the ONAP cluster?
- AoB
- Action point follow-up
- Morgan Richomme action morgan initiate Illia Halych committer promotion procedure
- done
- Morgan RichommeMichał Jagiełło develop basic_vm_macro and basic_cbf_macro
- basic_vm ready to be tested, basic_cnf shall be very closed
- Morgan Richommecontact Lasse Kaihlavirta to see if CDS regression could be integrated in CSIT
- done, no bandwidth available, Jira created
- Morgan RichommeAndreas Geisslerlist UI and create a healthcheck test to check the availability of the UI
- done, see next section
- Morgan Richomme action morgan initiate Illia Halych committer promotion procedure
- Admin
- Committer promotion: formal vote initiated Committer Promotion Request for Integration Illia Halych
- vote in progress, please committer vote before the end of the week
- testing docker discussion (formating, unexpected removal of daily build dockers,..)
- 2 tickets created on LF
- "fresh" xtesting dockers disappear time to time on the nexus https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-21812
- "impossible to release because the tag format of the snapshot docker does not respect some rules" => https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-21710
- xtesting dockers are rebuilt daily based on the branches (guilin/master end of branches of all the components embedded in the docker), CI or end users cannot guess the format imposed by the LF rules (used for components e.g. 6.0-STAGING-20210315T185806Z)
- 2 tickets created on LF
- Committer promotion: formal vote initiated Committer Promotion Request for Integration Illia Halych
...