Versions Compared

Old Version 231

changes.mady.by.user Morgan Richomme

Saved on

compared with

New Version 232

changes.mady.by.user Morgan Richomme

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

  1. Action point follow-up
    1. AP1 Illia Halych : ask OOM for the right place to host helm chart
      1. unformal exchange. For CDS helm charts are stored intestsuite/cds/mock-* until we coudl move the helm charts to a helm registry
    2. AP2 Andreas Geissler add warning in doc for backup and restore
      1. patch done
    3. AP3 Morgan Richomme contact TSC regarding B&R task force and possible scenario for Honolulu
      1. done, mail sent, Catherine Lefevre answered and agreed on shortmid term plans
    4. AP4 Morgan Richomme test basic-pnf (macro) on daily master before integrating thsi use case in CI
      1. done, test issues reported to Michał Jagiełło  and added in
        Jira
        serverONAP JIRA
        serverId425b2b0a-557c-3c0c-b515-579789cceedb
        keyINT-1822
  2. Admin
    1. congratulation to the team for the S3P..now it will be cool to fix the issues in Master/Gating (smile)
    2. windriver re-installation: to be planned after honolulu => answer sent to Intel team
    3. Azure Staging lab reinstalled
      1. #acrion Morgan Richomme  send a mail to the community to indicate that staging azure is back (guilin maintenance release as master is broken)
  3. Honolulu
    1. Troubleshooting campaign status: Image AddedINT-1883 - Reccurent various errors in smoke tests In Progress
      1. several issues found
        1. SDC races => including offset to move to pseudo sequential seems to reduces the number of SDC issues. Still one where ceritification seems to take to much time => possibility to add a workaround in the test to retry and/or delay the creation/certification
          1. #action Morgan Richomme amend pythonsdk_tests to include the workaround
        2. VID 500 due to the presence of a "U" char in random password (which explains why we did not have always the error...à - deobuscated by VID even if not obfuscated using jetty library interprating U as unicode char breaking everything. Problem found and fixed by Krzysztof Opasiak => last gating seems reasonably better
        3. SO error (so-bpmn stuck) was alsready observed time to time in guilin, so it is not a new problem...it explains why sometimes an instantiation takes 3 minutes sometimes 20, a jIRA had been created on this aspect
          Jira
          serverONAP JIRA
          serverId425b2b0a-557c-3c0c-b515-579789cceedb
          keySO-3419
        4. rebase/remerge in gate in progress...gates will burn over the next days...but it means that master chains should be back and usable
    2. Automated tests
      1. demo Apex pdp Policy Santosh bayas  Prudence Au
        1. test done on Bell labs, adaptation needed to be intgrated in CI (config in a dedicated file not leveraging CM information)..
          1. #Action Santosh bayas  identify inputs to see if parameters are missing + publish robot code in testsuite for review
      2. CDS regression test (session with Jozsef Csongvai  planned on thursday to give a try on Orange lab and see how we can integrate in CI - helm chart finally with docker file in mock repositories)
        1. mock in gates
        2. troubleshooting planned on thursday
      3. DCAEmod, 5Gbulkpm evolution (Krzysztof Kuzmicki ) → Morgan Richomme 
        1. Could we move this point to next week when bulkpm over HTTPS server will be finished and DCAEMOD in daily CI ?
        2. #action Morgan Richomme Krzysztof Kuzmicki check why we have a path difference between execution in the robot pod and in the xtesting docker
      4. pythonsdk (pnf, clamp, .., removal of the submodule, patch to allow test replay)
      5. tern integration in CI Alexander Mazuruk  Morgan Richomme - how to test/troubleshoot ansible par
        1. user-98b79 provides follow up in the MR https://gitlab.com/Orange-OpenSource/lfn/onap/xtesting-onap/-/merge_requests/37
          1. #action Morgan Richomme reriew MR for the integration of tern in ci-weekly
          2. #agreed moved weekly reinstallation on Friday next week
    3. S3P tests
      1. back on B&R mail to the community => only resilience tests to be planned for Honolulu
      2. stability => target?
        1. wait for master stabilization
        2. Figures to be decided: 5 // onboarding during 48, 20 // instantiation during 48?
      3. feed back on first test executed with litmus
        1. k8s chaos monkey framework
        2. it was possible to anote onap component and generate chaos..coudl be used for resiliency testing to check that components are recovering
    4. use cases
      1. who knows the list of Honolulu use cases?..
        1. Lukasz Rajewski  shared the link with the Honolulu Release Requirements
        2. no requests received so far
        3. no documentation changes seen
        4. #action Morgan Richomme contact use case owner to collect the possible needs and remind the need to update teh doc
  4. Istambul => for information to be discussed next week
    1. Move Robot pod out of ONAP cluster (including robot)
      1. certificate and robot pod to be executed in onap-testing cluster
    2. CI dashboard: improved dashboard to identify regression over time (see xls graphs) - muti platforms?
    3.  PythonSDK
      1. which tests? what is poorly covered?
        1. vFWCL? scaleout?
        2. NBI
        3. basic loop (basic_clamp extended)
    4. Add a retry capability in CI? other rules (if onap-helm or onap-k8s Fail "too much" => do not execute E2E tests to save CI time?)
    5. Robot refactoring: target (slot planned after the meeting if we are short in time)
      1. #action Morgan Richomme  Krzysztof Kuzmicki  create Epic and tasks to detail expectations on robot pod refactoring (alpine, split web/robot, python3, execution from outside the cluster, use python baseline image,....)
  5. AoB
  •  AP1: Morgan Richomme  amend pythonsdk_tests to include the workaround
  •  AP2: Santosh bayas  identify inputs to see if parameters are missing + publish robot code in testsuite for review
  •  AP3: Morgan Richomme  Krzysztof Kuzmicki  check why we have a path difference between execution in the robot pod and in the xtesting docker
  •  AP4: Morgan Richomme  review MR from user-98b79 for the integration of tern in ci-weekly
  •  AP5: Morgan Richomme  contact use case owner to collect the possible needs and remind the need to update the doc
  •  AP6: Morgan Richomme  Krzysztof Kuzmicki  create Epic and tasks to detail expectations on robot pod refactoring (alpine, split web/robot, python3, execution from outside the cluster, use python baseline image,....)

  1. Action point follow-up
    1. AP1: Andreas Geissler check if doc of the official use cases are excplictely referencing the robot pod
      1. not done yet
    2. AP2:  Morgan Richomme  include Nokia pod in onap-integration web site
      1. done => http://testresults.opnfv.org/onap-integration/
    3. AP3: all help reviewing the OOM patches to give Integration feedback
      1. in progress see next section
  2. Admin
  3. Honolulu
    1. pythonsdk
      1. smoke test issues (basic_vnf, basic_cnf) 10'

...