Versions Compared

Old Version 1

changes.mady.by.user Michał Jagiełło

Saved on

compared with

New Version Current

changes.mady.by.user Michał Jagiełło

Saved on

Key

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

 

...

 

...

  • SECCOM: discussion about
    • Using integration images as the best practice (global requirement in the future)
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyINT-2000

    • support prometheus
      • Prometheus shouldn't be a part of ONAP because it's a just one of tools that could be used to collect metrics and shows dashboards
        • There is an idea to provide a Wiki with all the instructions how to deploy Prometheus, which dashboards should be included etc.
  • Lab status
  • Morgan Richomme stability tests issues
    • Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keySO-3791
    • after 35h test starts failing
  • Istanbul release RC
  • https://wiki.onap.org/questions

...

  • rouzaut Security tests
    • Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyINT-1995
  • Lukasz Rajewski Multicloud azure issues
  • Lab status
    • Failuers on both DT and Nokia labs
    • Due to Vexxhost migration a lot of tests failing - there were no docker images
  • Istanbul release
  • Robot gating
    • Plan to create a gating for robot tests - discussion with Sylvain Desbureaux needed if we could do that - gating is already heavy loaded

...

...

  • Action points
  • Admin
  •  Istanbul
    • review David's JIRA
      • weather board???
      • doc....
    • any news from the use case?
    • most of the projects released first version of new dockers..even so (smile)
    • Data creation project (Michal Chabiera python code / Piotr Stanior DT code / ..) - official doc clearly no more accurate - moved into next week agenda
    • Openstack/Kubernetes supported version, shall we precise, shall we plan tests (with which resources?)
    • Operation document ?
      • component update?
      • backup and restore ?
      • troubleshooting
      • ...
  • jakarta

...

...

  •  Introduction of Carriers Integration Leadership - define role/responsabilities based on Min. TSC scope + Team's wishes

#1 Ensure that the Gating is up and running and daily results are available and identify any blocker by raising JIRA ticket

...

#3 Help to include in CI Chains any new automated test developed by the ONAP Use Case/Requirement Integration Lead and/or any project team

  1. Admin
    1. INFO.yaml updated
  2. Istanbul
    1. Update on DCAE migration
    2. CDS tests in Istanbul
    3. update stability/resiliency
  3. AoB

...

  1. Action point follow-up
  2. Admin
    1. SECCOM reco / baseline images
      1. Patch created based on SECCOM reco
      2. Baseline images created (currently in gate) https://gerrit.onap.org/r/c/integration/docker/onap-java11/+/121545, https://gerrit.onap.org/r/c/integration/docker/onap-python/+/121544
    2. repo cleanup
      1. #action all cleanup the repo (integration/testsuite/Demo) and remove in master what is not used for istanbul/honolulu
    3. versioning
      1. xtesting images can be created now - 1.7.0 created for guilin..bad version 7.0.0 shall be created as well as 8.0.0 for honolulu (shall be possible now..)
        1. in progress....
      2. onapsdk => new version for guilin (7.6.0) and for honolulu (8.0.0)
        1. agreed => 2 versions needed #action michal create the 2 tags (7.6.0=8.0.0)
    4.  Future PTL: how to move forward: houston.pdf
  3. Honolulu
    1. integration of pnf_macro
      1. issue with mongo service when run in // with pnf-registrate, #action Krzysztof and Michal specify the service to be unique and linked to the use case
    2. stability integration in CI
      1. now included in weekly master chain
        1. currently limited to 24 because the system is breaking before 72h
        2. DB tuning in progress
        3. no more Maria DB issue, issues on ONAP side (SO or subsequent component for instantiation tests and data middleware for SDC)
    3. move back to pythonsdk xtesting version corresponding to the chain version (was master for all) => guilin backporting required
      1. that is why we need a "good" version for onapsdk..guilin is consuming guilin xtesting, honolulu/honlulu, master/master
    4. resiliency follow-up -teasing for next week presentation by Natacha Chéreau
      1. see you next week for a short presentation and a demo
  4. Istanbul
    1. discussions on CI/CD category:
      1. shall we split smoke into smoke (E2E test to validate the release) and use cases
      2. stability category added in honolulu, shall we add a resiliency category or put them all together
      3. postponed to next week
    2. onap-k8s update
      1. add the generation of a onap_versions.json to automate the container tracking
      2. onap_versions.json generated => shall be able to track the docker version changes on daily
    3. onapsdk main dev for Istanbul Michał Jagiełło
      1. #action michal send a mail to indicate main topic for onapsdk in istanbul
    4. dcae test update Krzysztof Kuzmicki
      1. postponed
    5. Epic for istanbul to be created
  5. AoB
    1. Thanks Lasse Kaihlavirta for the great work done since more than 2 years for integration project.

...

  1. Action point follow-up

    •  Lukasz Rajewski prepare a demo on test automation managed by Lukasz..why it could not be integrated in CI for the moment (reflexion for Istanbul)
    •  Morgan Richomme sent a mail to PTL on good practice. Reminder that no patch in gate oldes than x months is a criteria for milestones..it is clearly not respected.
    •  Lasse Kaihlavirta plan a 20' section for a full session 
  2. Admin
    1. committers
    2. baseline images
    3. repo cleanup
  3. Status on CSIT Lasse Kaihlavirta : CSIT status after Honolulu.pptx
    1. CPS = Showcase example, everything is fine
    2. CCSDK previous showcase, still requires distributtion of docker builds, not possible to rebuild locally
    3. DMaaP (dmaap/buscontroller moved), OPTF (optf/odf and optf/has already moved), SDNC (almost finished but still some failures) transition in progress
    4. AAI mumtitenancy done outside ONAP planned to be incoprorated into aai/resources and aai/traversal => use of scala+gatling (examples based on robot so far)
    5. Policy: CSIT moved to reir repositories but tests do not follow reco (test after merge, not project specific, jjb fully specific
    6. Still some active projects with old design (DCAEGEN2, Modeling, Multicloud, OOM-platform-cert-service, SO)
    7. Usecase #action Morgan Richomme dig a little bit to understand if it corresponds to active use cases
    8. VFC and VID do not seem really maintained
    9. VNFSDK: only images for frankfurt => not maintained
    10. CSIT tests disabled (aaf, appc, clamp, music)
    11. clamp moved to SDC => what does it mean from a CSIT perspective
  4. Demo vFW CNF Lukasz Rajewski Konrad Bańka
    1. slide deck: #action Lukasz Rajewski vFW CNF Use Case Demo
    2. use case partially automated but would require a KUD (test cannot use a ns of the existing k8s hosting ONAP)
    3. As the use case is maintained and includes regularly feature changes, it woudl be interesting to include it in CI..to show that it is red/green as part of the use cases (more than smoke tests)
    4. #action Morgan Richomme Konrad Bańka Lukasz Rajewski estimate what is missing for integration in CI
    5. Open question and where the status of the xNF shall be available for ONAP admin..not clear status of the service/vnf/module was available in VID, some test status was available in SDC but not sure to know where the info on the status of the xNF would be the more accurate #action Morgan Richomme send a mail to the community to get feedback on this xNF status page
  5. AoB

...

      1. all the INFO.yaml actions will be performed once
      2. PTL no candidate => escalation done to TSC
    2. xtesting docker release
      1. new way, need to twist the scripts but could be OK. Need to fix guilin CI chain first (issue due to new pbr value)
    3. baseline images: wait for seccom reco for istanbul
  2. Honolulu
    1. regression on multicloud-k8s / pnf-macro
      1. Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keyMULTICLOUD-1348
        issue due to helm format, no error with the helm charts sued for Lukasz's use case. Fix done, docker images must be regenerated
      2. action Lukasz Rajewski  prepare a demo on test automation managed by Lukasz..why it could not be integrated in CI for the moment (reflexion for Istanbul)
    2. master-weekly
      1. tern
        1. should be fully OK next week
        2. last results : https://logs.onap.org/onap-integration/weekly/onap_weekly_pod4_master/2021-05/07_22-21/security/tern/index.html
        3. Former user (Deleted) indicates that anothe resource from Saùmsung is working on the topic to improve the images. No feedback from the PTL.Morgan Richomme indicates that he reports the issue to PTL during PTL meeting. Not normal to have no feedback (e.g. CLI improvement patch in gate for a long time), David McBride sent a mail to Former user (Deleted)  #action  morgan sent a mail to PTL on good practice. Reminder that no patch in gate oldes than x months is a criteria for milestones..it is clearly not respected.
      2. stability tests
        1. update on MariaDB tuning => reduce the replica of non core components/removal of appc/... see stability_follow-up 2-2.pdf
          1. redimensioning is enough to avoid DB crash but recommendation to TSC to reduce replica for non core components 15 instances of Maria DB => 15x30 Go of additional RAM needed to avoid crash in load conditions...9 nodes cassandra...
          2. stability tests are now performed on each weekly => results are here: https://logs.onap.org/onap-integration/weekly/onap_weekly_pod4_master/2021-05/07_22-21/stability_tests/
        2. choice of the figures for weekly
          1. start with instantiation to avoid lots of models in SDC
          2. 10 instantiation in // during 24h (basic_vm / a la carte bpmn)
          3. then 5 onboarding in // during 24h
          4. needs to add basic_vm_macro if stability reached on first instantiation
        3. DB tuning
          1. suggestions from Samuel Liard  to modify Maria Db and Cassandra DB default configuration: https://gerrit.onap.org/r/c/oom/+/121229/10
          2. all integration committers are using teh default DB values on their lab, no specific tuning, only the nb of compoentns may be reduced (because not used)
    3. CSIT status after Honolulu (we may have to reserve some time for this so not necessarily today):  Integration (WIP)
      1. introduction to the status of CSIT at the end of Honolulu
      2. #action Lasse Kaihlavirta plan a 20' section for a full session

...

  1. Action point follow-up
    1. Morgan Richomme review Integration simu and release versions if possible + update doc accordingly
      1. not done yet..several issues on LF (SSO, Nexus, gerrit,..)
    2. Morgan Richomme create a JIRA for basic_vm_macro
      1. not needed last results with CCSDK fix look good
    3. Former user (Deleted) finalize push to LF back end
      1. test in progress on weekly master..config is good
    4. Morgan Richomme create resiliency chapter in doc and initiate Jira for confirmed issue (appears at least 2 times), restart of a controller still to be done to complete the test.
      1. done see next section
    5. Krzysztof Kuzmicki create a wiki page in Istanbul page for robot refactoring follow-up
    6. Krzysztof Kuzmicki create a wiki page in Istanbul page for DCAE migration
  2. Admin
    1. INFO.yaml updated needed (NS repo have no yaml + status of the project)
    2. Commiter Promotion Request for Bartosz Gardziejewski: results 10 Yes on 10
    3. Commiter Promotion Request for Alexander Mazuruk: results 4 Yes on 4
    4. PTL election: call for self nomination sent
      1. all operations on INFO.yaml will be done at the same time
      2. note Lasse Kaihlavirta indicated that he also will step down in 1 month
  3. Honolulu
    1. status:board review https://jira.onap.org/secure/RapidBoard.jspa?rapidView=229
      1. few JIRA still open # action all move or closed the JIRA in honolulu
    2. release testsuite 1.8.0 done
      1. just merged
    3. doc updated
      1. done
    4. Remaining work on tests
      1. macro issues Lukasz Rajewski

      2. stability/resiliency tests

        1. Maria DB galera troubleshooting

        2. honolulu_sign-off.pdf
        3. stability_follow-up.pdf
    5. Honolulu: Lessons Learned
      1. #action report your feedback on honolulu lesson learned
  4. Istanbul
    1. New Jira board created: https://jira.onap.org/secure/RapidBoard.jspa?rapidView=233
    2. brainstorm on new use cases for Istanbul open => https://etherpad.anuket.io/p/onap_integration_istanbul
      1. participants indicate their top 3 priorities for honolulu
  5. AoB

...

  1. Action point follow-up
    1. Morgan Richomme review Integration simu and release versions if possible + update doc accordingly
      1. not done, will be done after doc, stability and resiliency testing #reaction
    2. Lukasz Rajewski properly tag SO bugs to reference them as blocking in Integration blicking table
      1. SO bugs do not appear in Honolulu Integration Blocking Points => to be crosscheck with Lukasz Rajewski
    3. if SDNC-1515 merged and pnf-simu OK in honoluluMorgan Richomme add pnf-macro to CI
      1. honolulu daily shows that the basic_vm_macro issue is not really fully fixed => #action Morgan Richomme create a JIRA for basoc_vm_macro
    4. Morgan Richomme grant access to ChrisC to check the status of SDC/DB
      1. done see section on SDC stability test
    5. Morgan Richomme retry and wait for the 5 minutes (Eviction timeout) then investigate on the networking issue
      1. done, Jira completed
    6. Morgan Richomme check ansible image availability for chained-ci
      1. doneAndreas Geißler gave a new try, still issue but not related to teh image. open question: shall we also reference the image in the CI page of the release?
  2. Admin
    1. INFO.yaml updated needed (NS repo have no yaml + status of the project)
    2. Commiter Promotion Request for Bartosz Gardziejewski: please vote before end of the week. BTW if other committer proposal => feel free to suggest (to replace Pawel, Marcin and partly Thierry)
  3. Honolulu
    1. status:board review https://jira.onap.org/secure/RapidBoard.jspa?rapidView=229
    2. release testsuite 1.8.0 under built
      1. in progress https://gerrit.onap.org/r/c/testsuite/+/120960, once merged, submit a patch to OOM
    3. Remaining work on tests
      1. macro issues Lukasz Rajewski
        1. pnf-macro test to be done on master before integration in CI (working fine in guilin)
        2. basic_vm_macro good results on guilin but not so good on master/honolulu => JIRA created
          Jira Legacy
          serverSystem Jira
          serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
          keySDNC-1529
      2. tern: test run in CI but results not pushed yet to LF Backend => WIP to manage properly the push to lf backend. On last honolulu and master-weekly, artifacts were produced and pushed manually #action Former user (Deleted) finalize push to LF back end

      3. stability/resiliency tests

        1. Resiliency test

          1. worker node restart (thanks Bartek Grzybowski for the full analysis) => how do we follow, shall we create Jiras?
          2. test done, eviction looks good. some issues detected on some pods but not always trivial to reproduce may depend on the associated evicted pods. sometimes Init error, sometimes pod Running but exception..sometimes first eviction look good, but second seems to be fail... different cases referenced in Honolulu Resiliency and Backup and Restore test
          3. for SDC issue, the restart may be due to teh fact that the SDC is trying to recreate tables that already exist in cassandra
          4. #action Morgan Richomme create resiliency chapter in doc and initiate Jira for confirmed issue (appears at least 2 times), restart of a controller still to be done to complete the test.

        2. stability tests

          1. SDC tests: 72h 5 parallel on boarding INT-1912 - SDC Stability test: success rate drops after ~ 500 onboarding Open
          2. ChrisC reports that it was useful to detect new issues, especially the continuous time increasing that my be lead to teh DB and/or a middle ware layer (explicit exception seen)
          3. plan to integrate such test in weekly as part of benchmark test
          4. instantiation tests
            1. 48h 5 parallel basic_vm (initial issue on SDNC (fixed by restart) then regular timeout value then internal openstack issues INT-1918 - Stability tests: // instantiation Open
            2. more timeout than in guilin, need to be confirmed with a 1 test (no parallelization), mariadbgalera issue observed on some replica
            3. 72h 1 test basic_vm => problem with mariadb galera, results will not be as good as in guilin run
            4. issue with mariadbgalera after 24h (but tests run after the 48h tests..) once finished (thurday morning => reinstallation of honolulu weekly to reproduce the tests with the last dockers
            5. mariadb galera workaround reported by Bell to OOM, seems to improve the overall quality of gate but trigger an new issue on CDS. tradefoff between redundancy and efficiency not clear
    4. documentation update started but not finished => https://gerrit.onap.org/r/c/integration/+/120236
    5. estimation 2-3 days still needed to compelte the doc / release note + testsuite integration
  4. Istanbul
    1. New Jira board created: https://jira.onap.org/secure/RapidBoard.jspa?rapidView=233
    2. robot refacroting..it eems we have a plan (Krzysztof Kuzmicki )
    3. discussion by mail, #action Krzysztof Kuzmicki crerate a wiki page in Istanbul page
    4. migration of DCAE from cloudify to helm chart..first analysis by Krzysztof Kuzmicki , impacts to be planned on several tests
    5. discussion by mail, #action Krzysztof Kuzmicki crerate a wiki page in Istanbul page
    6. New CSIT (AAI, CDS,..)
    7. AAI is folowwing the SDC way (Maven based), for CDS it shoudl be possible to reuse what Lasse Kaihlavirta suggested. AAI team contacted SDC
    8. brainstorm on new use cases for Istanbul open => https://etherpad.anuket.io/p/onap_integration_istanbul
    9. all review the page, it is an etherpad..so do not refrain yourself..put everything you have in mind
  5. AoB
    1. Lasse Kaihlavirta closed the CSIT refactoring EPIC
    2. Lasse Kaihlavirta also disabled useless SO CSIT tests (with very old images) - the Jira was closed without action by Seshu Kumar Mudiganti so we remove some jobs as they are meaningless (test with casablanca images)
    3. Lasse Kaihlavirta add a browser cleanup on robot healthcheck (vid) to save resource, it will be integrated in 1.8.0

...

  1. Action point follow-up
    1. 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)
      1. Not done
    2. Morgan Richomme cleanup basic_clamp and re-run it on a daily master
      1. Done
    3. Michał Jagiełło complete basic_vm_macro
      1. In progress, issue in SDNC:
        Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keySDNC-1515
    4. Morgan Richomme create wiki page to reference the GUI endpoints to be tested
      1. Done Honolulu UIs
    5. all review the wiki page and add the links of the GUI you are using
    6. Morgan Richomme create a wiki page to improve the process on test integration in CSIT and/or CI from third parties
      1. Done How to help projects to integrate their tests in Integration?
    7. all review/complete the wiki on process to integrate new external tests in CSIT or CI
    8. Morgan Richomme initiate an official page on simulator
      1. Done https://docs.onap.org/projects/onap-integration/en/latest/integration-simulators.html
    9. Krzysztof Kuzmicki complete the official simulator page with NS illustration
      1. To be Done
    10. Bartek Grzybowski review the official simu page (list of usable simu)
      1. Done
    11. Illia Halych review the official simu page (pythonsdk wrapper)
      1. To be Done
  2. Admin
    1. Illia Halych officially new Integration commiter, welcome !
    2. No update on xtesting docker release
    3. LF IT backend , not possible to move logs, no cleanup mechanism (manual cleanup needed)
  1. Honolulu
    1. status:board review https://jira.onap.org/secure/RapidBoard.jspa?rapidView=229&selectedIssue=INT-1842
      1. action #all review your Jira ticket move to instanbul or close
    2. Daily Honolulu CI/CD chain created
      1. https://logs.onap.org/onap-integration/daily/onap_daily_pod4_honolulu/2021-04/
    3. Remaining work on tests

      1. 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

      2. basic_vm_macro (replace vfw_macro): in progress still some issues on the daily honolulu

      3. pnf_macro => add mechanism to have a better control of the pnf simu launch (timer is not enough) => # action Michal

      4. refactoring of 5gbulkpm => #action Krzysztof => test done this afternoon => merged

      5. tern: test declared in CI, but issue => # action morgan & Alexander

      6. stability tests

        1. I started the first resiliency tests: TEST-308 - [Resiliency] Evaluate ONAP behavior on k8s worker node restart

          1. Other labs are experiencing different issues
            1. Nokia => pod remain in stuck
            2. #action Daniel, Andreas create a JIRA ticket for each resiliency test
            3. #action morgan create a wiki page to consolidate resiliencey tests

        2. stability I planned to regive a try to Natacha's suite as soon as the other tests are OK

          1. to be tried asap: if enough resources => weekly Honolulu to be launched on Wednesday

      7. 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

        1. better exception catching

        2. 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)

      8. 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

        1. #action morgan review the patch dealing with sumbmodule removal +  cherry + adapt xtesting-onap

      9. CDS / CSIT => will not have the resource to do it for Honolulu => move to Istanbul

      10. GUI tests: wait for completion of the Wiki page and see if enough bandwidth => move to instanbul

    4. documentation update started
    5. honolulu branching done
    6. release testsuite 1.8.0 to be done
  2. Istanbul
    1. requests from new project (OOF, AAI) "on how to bring new tests to integration" => How to help projects to integrate their tests in Integration?
      1. Discussion on the support for AAI gatling tests. By default the multitenancy support is disabled and they require a keycloak third party
      2. first issue is the test env => we coudl imagine to have a daily scenario daily_master_multitenancy but we need to take care of the resources. Until we cannot rely on the windriver lab, it will be hard to create new scenarios...
      3. installation of keycloak shall be done in a tooling namespace through a helm chart => OOM
      4. Mohammad Hosnidokht indicated that gatling part is almost automated (docker verifying the roles)
      5. William Reehil indicated that it will probably break the other tests
      6. it is probably more relevant to start by creating a CSIT test (fonctional test) with AAI + keycloak rather than a daily.. 
      7. #action Morgan Richomme complete wiki instanbul page to track this scenario
    2. run robot tests out of onap namespace: How to run the tests out of the ONAP cluster?
  3. AoB
  •  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)
  •  Michał Jagiełło complete basic_vm_macro
  •  all review the wiki page and add the links of the GUI you are using
  •  all review/complete the wiki on process to integrate new external tests in CSIT or CI
  •  Krzysztof Kuzmicki complete the official simulator page with NS illustration
  •  Illia Halych review the official simu page (pythonsdk wrapper)
  •  all review your Jira ticket move to instanbul or close
  •  Morgan Richomme review the patch dealing with sumbmodule removal +  cherry + adapt xtesting-onap
  •  Morgan Richomme complete wiki instanbul page to track this scenario

...

  1. Action point follow-up
    1. Morgan Richomme action morgan initiate Illia Halych committer promotion procedure
      1. done
    2. Morgan RichommeMichał Jagiełło develop basic_vm_macro and basic_cbf_macro
      1. basic_vm ready to be tested, basic_cnf shall be very closed
    3. Morgan Richommecontact Lasse Kaihlavirta to see if CDS regression could be integrated in CSIT
      1. done, no bandwidth available, Jira created
    4. Morgan RichommeAndreas Geißlerlist UI and create a healthcheck test to check the availability of the UI
      1. done, see next section
  2. Admin
    1. Committer promotion: formal vote initiated Committer Promotion Request for Integration Illia Halych
      1. vote in progress, please committer vote before the end of the week
    2. testing docker discussion (formating, unexpected removal of daily build dockers,..)
      1. 2 tickets created on LF
        1. "fresh" xtesting dockers disappear time to time on the nexus https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-21812
        2. "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
        3. 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)

...

        • sequential versus parallel
          • tests planned to move to E2E sequential to avoid side effect due to parallelization. Parallel tests could be done on weekly...need to fist master and gating chains first.
      2. tests update (Michał Jagiełło 15' )
        1. pnf (macro flow)
          1. ready to be tested (logger fixed)
          2. #action morgan test basic-pnf on daily
        2. exceptions not caught
          1. patch provided
        3. basic_clamp
          1. almost there: last issue due to DCAE TCA, seems tehre is a regression on dcae due to python2.7 / Python3 =>
            Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyINT-1822
            . Wait for fix before retrying.
        4. wrapper
          1. OK, question on where to host the helm charts for the simulator (pnf and future one)
          2. #action contact OOM team => similar question than the for CDS mock objects
          3. it is possible to remove the submodule - just be carefull, once removed => possible to deploy onapsdk as a "standard module" no more as developer module => impact on xtesting-onap as the paces will be different
    2. Backup/restore Morgan Richomme 15' Backup_and_restore_discussion.pdf
      1. discussion on a realistic use case...
        1. backup and restore seems too optimistic
        2. consensus to work on the resiliency of the core component
        3. #action Andreas Geißler warning shall be added in the documentation, as aarna network is not really usable for a real backup/restore (more some examples to use velero)
        4. Companies that tried velero has issues due to teh fact that ONAP is not really cloud native
  2. AoB
    1. cmpv2 about to be moved from healthcheck to smoke
    2. Krzysztof Kuzmicki indicates that 5Gbulkpm will be updated ..may have some turbulences during the update

...

  1. Action point follow-up
    1. AP1: morgan_orange publish video and slideck on the how to
      1. done: Youtube video link, discussions in progress at LFN level to suggest how to publish such videos per community channel
    2. AP2: morgan_orange plan a new slot with praveen
      1. no feedback from praveen v , need to replan a slot
    3. AP3: morgan_orange send mail to suggest repo, and if OK => create teh repo
      1. mail sent to Konrad Bańka , wait for green light before creating the new repo
    4. AP4: morgan_orange anser to the mail for pnf-simu evolution and plan a formal agreement from committer next week
      1. see next section
    5. AP5: natacha add the _v to manage the settings path in order to retrieve the pythonsdk logs
      1. done but side effect due to the fact that the settings in master are in /Src/onaptests/src/onaptests and not under /usr/lib/python3.8 in xtesting
  2. Admin
    1. new ietf repo created, Bartek Grzybowski added JS linter, first upload in progress
    2. Guilin CI chain
      1. ~ OK http://testresults.opnfv.org/onap-integration/results/index-onap_daily_pod4_guilin-ONAP-oom.html
      2. Certificates CDS-UI expires in 3 days and VID in 29 days
      3. Error due to 500 from SDC
    3. Master chain
      1. pythonsdk tests broken during 2-3 days due to the introduction of onapsdk 7.4 (onapsdk custom exceptions were no more caught in onaptests)
      2. problem affecting all the gating chains
    4. Comments from Lukasz Rajewski on the slack channel => quid about the history, free account does not provide long retention period #action 8
  3. Honolulu
    1. Discussion on a recovery pipeline / resiliency tests (Marek Szwałkiewicz Morgan Richomme
      1. Epic created on Honolulu Resiliency and Backup and Restore test
        1. several tasks to perform tests
        2. Please do not hesitate to use the JIRA if you are performing such tests in your lab
    2. Discussion on CI/CD chain evolution (Morgan Richomme )honolulu_ci_evolution_08022021.pdf
      1. Krzysztof Kuzmicki indicates that dcae-mod shall be tested also through a new healthcheck test
      2. FWCL not possible to integrate in CI straightforward - preprovisionned resources needed, dependencies on installation (documented),
      3. Not sure if FW (macromode) will bring more than basic_VM + PNF and note sure Andreas Geißler will have resource to deal with it
      4. VCPE TOSCA (CLI) was not possible to run it on daily labs (running onwly on tester lab), improvements were planned in Guilin (seems to be done). #action 1
      5. #agreed No objection from the new categories and new tests for Honolulu branch
      6. for tern/scancode: watch out the versions of the OS, Debian9 is too old. #action 2
    3. Security
      1. versions: last update
        1. test created by Paweł Wieczorek
        2. waiver list introduced in Honolulu (patch merged)
        3. New GUI suggested more explicit that the json file: https://logs.onap.org/onap-integration/weekly/onap_weekly_pod4_master/02-11-2021_22-02/security/versions/versions/
          1. still lots of java 8 and python 2.7...
          2. very few projects seem to use the baseline images (that are up to date..)
    4.  Pythonsdk
      1. removal of the submodule?
      2. #agree remove the pnf submodule as soon as possible, be careful with the side effects on xtesting dockers / xtesting-onap ansible roles as we coudl move back from src/onaptests to /usr/lib/python3.8 path
      3. status on the wrapper (helm2/helm3)
        1. Illia Halych indicates that there is a client supporting helm2 and one supporting helm3 but not both
        2. #agree consider only helm3
        3. Add the statement in the README (as for the python min version 3.7 (same as pythonsdk)
        4. #action 3
      4. status on the tests basic_pnf, basic_clamp
        1. problem for basic_pnf seems to be fixed, patch merged on SDC
        2. see if the basic_pnf could be introduced in CI (test it first manually on daily weekly then add teh job xtesting-onap project that defines the CI chain) #action 4
      5. Improve reporting
        1. reporting may be misleading as it indictaes only the results of resource creation. We recently got an issue when deleting the resources => all the reporting is green even if there was an error during vfModule deletion. Michał Jagiełło submitted a patch to consider deletion in reporting #action 5
      6. Solution to limit issues on master gate (gating on pythonsdk?, versioning,..)
    5. pnf-simu > nf-simu: formal review
      1. #agreed
      2. demo to be planned next week #action6
  4. AoB
    1. Marcin Przybysz indicates that a discussion is needed on VID. Vid new UI is needed for PNF macromode tests but old UI is needed for vFWCL..how do we manage that
    2. Michał Jagiełło tried to setup the new VID uI (VID 7.0.2) but has issue, Marcin Przybysz indicates that some flags have to be tuned #action 7
  5. actions for next meeting
    1. AP1: Morgan Richomme : contact vcpe tosca team to get their position in Honolulu (
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyTEST-239
      )
    2. AP2: Former user (Deleted) : get the list of projects using the baseline images
    3. AP3: Illia Halych amend https://gerrit.onap.org/r/c/testsuite/pythonsdk-tests/+/117192 for helm3 support
    4. AP4: Morgan Richomme test basic_pnf on Orange daily master with onaptests:master
    5. AP5: Michał Jagiełło Morgan Richomme test carefully before submitting until we got a gate to do it...
    6. AP6: Krzysztof Kuzmicki prepare a 10 minutes demo on pnf-simu to nf-simu (explaning the graph shared by mail)
    7. AP7: Marcin Przybysz plan a demo of VID new UI, how to launch it, how it is used in PNF macromode + see with VID how we can manage tests that are using legacy VID..
    8. AP8: Morgan Richomme contact Kenny Paul  for the status of the slack chan

...

  1. Action point follow-up
  2. Admin
  3. Honolulu
    1. demo 5g-core-nf simu (praveen v ) 20'
    2. demo ORAN A1-based Closed Loop (Konrad Bańka ) 20' A1 Policy Enforcement PoCv1.pptx
    3. demo stability test launcher (Natacha Chéreau )10'
  4. AoB

(18:02:16) collab-meetbot: Meeting ended Wed Feb 10 17:02:15 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
(18:02:16) collab-meetbot: Minutes: http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2021/integration_weekly_meeting_10_2_2021/onap-int-integration_weekly_meeting_10_2_2021.2021-02-10-16.44.html
(18:02:16) collab-meetbot: Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2021/integration_weekly_meeting_10_2_2021/onap-int-integration_weekly_meeting_10_2_2021.2021-02-10-16.44.txt
(18:02:16) collab-meetbot: Log: http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2021/integration_weekly_meeting_10_2_2021/onap-int-integration_weekly_meeting_10_2_2021.2021-02-10-16.44.log.html

...

  1. Action point follow-up
  2. Admin
    1. new repo follow-up
  3. Honolulu
    1. demo PNF (Michał Jagiełło )
    2. discussion on simulators
    3. simulator wrapper in pythonsdk-tests (Illia Halych)
  4. Preparation vEvent
  5. AoB

(18:57:32) collab-meetbot: Minutes: http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2021/integration_weekly_meeting_27_01_2021/onap-int-integration_weekly_meeting_27_01_2021.2021-01-27-17.29.html
(18:57:32) collab-meetbot: Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2021/integration_weekly_meeting_27_01_2021/onap-int-integration_weekly_meeting_27_01_2021.2021-01-27-17.29.txt
(18:57:32) collab-meetbot: Log: http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2021/integration_weekly_meeting_27_01_2021/onap-int-integration_weekly_meeting_27_01_2021.2021-01-27-17.29.log.html

...

  1. Action point follow-up
  2. Admin
    1. new repo follow-up
    2. new Real time support channel: slack (already exists), publick rocket chat, mattermost, ....
  3. Honolulu
    1. demo PNF (Michał Jagiełło )
    2. discussion on simulators
    3. simulator wrapper in pythonsdk-tests (Illia Halych)
    4. CSIT redesign updates (Lasse Kaihlavirta)
    5. stability/resiliency testing (Natacha Chéreau )
    6. Update on Tern tests (Former user (Deleted) )
  4. Preparation vEvent
  5. AoB

(17:40:10) collab-meetbot: Minutes: http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2021/integration_weekly_meeting_20_01_2021/onap-int-integration_weekly_meeting_20_01_2021.2021-01-20-16.06.html
(17:40:10) collab-meetbot: Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2021/integration_weekly_meeting_20_01_2021/onap-int-integration_weekly_meeting_20_01_2021.2021-01-20-16.06.txt
(17:40:10) collab-meetbot: Log: http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2021/integration_weekly_meeting_20_01_2021/onap-int-integration_weekly_meeting_20_01_2021.2021-01-20-16.06.log.html

...

    1. demo tests DataFileCollector (Krzysztof Gajewski ) 10'
  2. Guilin Maintenance Release
  3. Preparation vEvent
  4. AoB

(16:26:02) collab-meetbot: Minutes: http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2021/integration_weekly_meeting_13_1_2021/onap-int-integration_weekly_meeting_13_1_2021.2021-01-13-14.51.html
(16:26:03) collab-meetbot: Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2021/integration_weekly_meeting_13_1_2021/onap-int-integration_weekly_meeting_13_1_2021.2021-01-13-14.51.txt
(16:26:03) collab-meetbot: Log: http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2021/integration_weekly_meeting_13_1_2021/onap-int-integration_weekly_meeting_13_1_2021.2021-01-13-14.51.log.html

...