Page History

...

1. Action point follow-up
   1. Illia Halych review the official simu page (pythonsdk wrapper)
      1. done, no example for Honolulu, to be completed in Istanbul
   2. Morgan Richomme refine the information about the conditions of the resiliency tests of worker restart -
      1. See Honolulu topic
   3. Lasse Kaihlavirta Offline discussions with Lasse about AAI CSIT
      1. Done
   4. Krzysztof Kuzmicki Next week proposal about what we can do with robot
      1. Postponed to next week
   5. Krzysztof Kuzmicki INT-1907 - browser_setup.robot does not provide proper teardown Open  no teardown for browser-based checks - high consumption of resources at the end
      1. used by VID test, workaround to be confirmed
   6. Maybe we need more information about DMaaP simulator use and to write it better in the simulator doc → Reported by Lasse Kaihlavirta

      1. Globally we are not well structured on the simulator, on the release note of version X we should list all the versions of the simulators we used for the validation. It shall be done by the use case teams that developed a simu and:or the integration team. The difficulty ois to get the full view on the simulators, some are hidden in repositories, some are unmaintained,...# action Morgan Richomme review Integration simu and release versions if possible + update doc accordingly

   7. Need of consolidation of versioning of images of simulators used in CSIT  → Reported by Lasse Kaihlavirta
      1. sure it is a bit messy...and impossible to maintain, integration can cleanup time to time..but the best way for functional tests => bring functional tests including simu in their own repo. And if the simu can be used more widely create a dedicate repo under integration/simulators..
2. Admin
   1. INFO.yaml updated needed (NS repo have no yaml + status of the project)
      1. strange INFO.yaml is needed to create the repo => to be xchecked. Morgan Richomme indicates to Thomas Kulik that it will be done with the next INFO update (needed as at least 2 committers announced they will stop after Honolulu)
   2. thanks to Pawel and Marcin for their contributions and all the best for the next challenges
3. Honolulu
   1. status:board review https://jira.onap.org/secure/RapidBoard.jspa?rapidView=229
   2. Remaining work on tests
      1. pnf_macro => OK on daily guilin, what do we do regarding CI integration

         1. kudos to Michał Jagiełło  - first pythonsdk tests with simulator - let's wait for the merge of Dan fix for SDNC-1515, if OK #action Morgan Richomme add pnf-macro to CI

         2. stil SO bugs preventing Lukasz Rajewski to complete his test .. deja-vu?
         3. #action Lukasz Rajewski properly tag SO bugs to reference them as blocking in Integration blicking table
      2. tern: test run in CI
         
         1. test results available (launched manually) => https://logs.onap.org/onap-integration/weekly/onap_weekly_pod4_master/2021-04/19_18-36/security/tern/index.html
         2. next CI run shall be good..wait and see

      3. stability/resiliency tests

         1. I started the first resiliency tests: TEST-308 - [Resiliency] Evaluate ONAP behavior on k8s worker node restart In Progress , replay done, mail sent to the community (network issue?)
            

            1. behavor different on Nokia (pod stuck for ever in Terminating state when stopping a working) and Samsung RKE2 cluster, continue discussion on the ticket Bartek Grzybowski  indicates that we shall be careful especially with statefulset, it coudl explain some issues
            2. #action morgan retry and wait for the 5 minutes (Eviction timeout) then investigate on the networking issue

         2. stability tests

            1. SDC tests: 72h 5 parallel on boarding started on the 20th of April..wait and see...
               1. First tests were all OK but duration ontinuously increases. No error rate is high. Wait for the end of the tests to get the graphs.
               2. #action Morgan Richomme grant access to Christophe Closset to check the status of SDC/DB
            2. instantiation tests to be planned after onboarding tests

      4. consolidation of versions

         1. better exception catching + integration of the GUI => still action Morgan

      5. removal of the submodule: done

   3. documentation update started but not finished => https://gerrit.onap.org/r/c/integration/+/120236
   4. release testsuite 1.8.0 to be done?
      1. next week if no objection
   5. simulators: whuch dockers are available in nexus today? could we clarify the build chain?
      1. see previous topic
4. Istanbul
   1. New Jira board created: https://jira.onap.org/secure/RapidBoard.jspa?rapidView=233
   2. discussion on future tests
      1. follow up integration AAI tests in CSIT
      2. CDS in CSIT?
5. AoB
   1. Andreas Geissler mentioned that his CI chains were affected by the non availability of an ansible image used in the runner => could be a problem, need to release also such images somewhere to avoid such issues #action Morgan Richomme check ansible image availability for chained-ci (2.7.13)
      1. issue also on Orange chains last week (build chain of ansible image was broken, chain fixed)
   2. Christophe Closset raises a question on python2.7 in jenkins CI and in robot. Partly addressed by the initiative of robot refactoring. note xtesting dockers also still using python2.7 due to dependency to python-utils that has not evolved for a long time.

•  Morgan Richomme review Integration simu and release versions if possible + update doc accordingly
•  Lukasz Rajewski properly tag SO bugs to reference them as blocking in Integration blicking table
•  if SDNC-1515 merged and pnf-simu OK in honoluluMorgan Richomme add pnf-macro to CI
•  Morgan Richomme grant access to Christophe Closset to check the status of SDC/DB
•   Morgan Richomme retry and wait for the 5 minutes (Eviction timeout) then investigate on the networking issue
•  Morgan Richomme check ansible image availability for chained-ci

...