Versions Compared

Old Version 228

changes.mady.by.user Morgan Richomme

Saved on

compared with

New Version 229

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: 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'
        • 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 (Michal Jagiello 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
            serverONAP JIRA
            serverId425b2b0a-557c-3c0c-b515-579789cceedb
            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 Geissler 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

Actions

  • AP1 Illia Halych : ask OOM for the rright place to host helm chart
  • AP2 Andreas Geissler add warning in doc for backup and restore
  • AP3 Morgan Richomme contact TSC regarding B&R task force and possible scenario for Honolulu
  • AP4 Morgan Richomme test basic-pnf (macro) on daily master before integrating thsi use case in CI

  1. Action point follow-up
    1. no action point from last week (several docs)
    2. action point from the 17/02
      1. AP1: Morgan Richomme : contact vcpe tosca team to get their position in Honolulu (
        Jira
        serverONAP JIRA
        serverId425b2b0a-557c-3c0c-b515-579789cceedb
        keyTEST-239
        )
        1. done no feedback on the JIra
      2. AP2: user-98b79 : get the list of projects using the baseline images
        1. done
      3. AP3: Illia Halych amend https://gerrit.onap.org/r/c/testsuite/pythonsdk-tests/+/117192 for helm3 support
        1. done
      4. AP4: Morgan Richomme test basic_pnf on Orange daily master with onaptests:master
        1. not done PTO..but I can reaction myself;.
      5. AP5: Michał Jagiełło Morgan Richomme test carefully before submitting until we got a gate to do it...
        1. not really an action point but the advise is wise...be carefull after removing the submodules + change the xtesting installation (using standard python module not developer way...xtesting-onap shall follow)
      6. AP6: Krzysztof Kuzmicki prepare a 10 minutes demo on pnf-simu to nf-simu (explaning the graph shared by mail)
        1. done
      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..
        1. done
      8. AP8: Morgan Richomme contact Kenny Paul  for the status of the slack chan
        1. done it is a free chan, no idea how LF decides to pay for a non free chan..if community thinks that we shall be able to keep the history and then take a non free chan, it is possible to report it to the TSC
  2. Admin
    1. A1 policy enforcement created
      1. https://gerrit.linuxfoundation.org/infra/c/releng/info-master/+/66923
    2. nf repo created (Krzysztof Kuzmicki )
    3. M3 is over..JIRA review needed to know what is possible (support/test cases/) what shall be postponed...
      1. release cadence is new, some projects were surprised. No new code will be accepted in OOM gate. Lots of patches submitted...gating system under pressure..wait for merge to reach the RC0
  3. Honolulu (M3 is over..)
    1. CSIT issue with python2.7/Python3 (Lasse Kaihlavirta Morgan Richomme )
      1. fix submitted by user-98b79
      2. list of jenkins images  known in CSIT repo but not sure it is documented. Some issues due to python 2.7/3.5/3.6/3.7/3.8/3.9...lib dependency issues NB the seccom recommended version is the 3.9
    2. Refactoring of testsuite
      1. python2.7/micro service/root
      2. cert
      3. helm chart
      4. Lukasz Rajewski and Andreas Geissler suggest to put the effort on migrating to pythonsdk rather than maintaining the pod
      5. Morgan Richomme reminds that robot tests are run through pythonsdk, the question is linked to the robot pod not the ability to run robotframework test cases, which is always possible. Who is using the e2e scripts that trigger processing on the robot pod. Lasse Kaihlavirta indicates that some usecases (under upstreaming (A1)) are in this case. For Honolulu we may ask for a waiver and remove the pod in Istambul (is nobody is using it). Morgan Richomme sent a mail to the community  but no feedback so far. Scaleout and vFWCL still probably requires the pod, other usercases requires also the init offered by the bash scripts #action Andreas Geissler look in the doc which use cases explicitely make reference to the scripts in the official documentation
    3. status on CI/CD (delta guilin) (Morgan Richomme ) 
      1. New Nokia dualstack lab added in the pool of lab reporting results http://testresults.opnfv.org/onap/api/v1/results?last=5&case_name=full&pod=ci-dualstack-master-daily
        1. IPv4/IPv6 server, ONAP Master daily => results shared with the community in LF backend + Test DB
      2. shall we update http://testresults.opnfv.org/onap-integration/ ?
        1. Daniel Milaszkiewicz OK #action morgan add Nokia in http://testresults.opnfv.org/onap-integration/
      3. Master is currently not that bad: https://logs.onap.org/onap-integration/daily/onap_daily_pod4_master/03-01-2021_06-03/
        1. error due to internal cert executed in onap ns (shall be moved to an external ns)
        2. 1 error on enhanced policy => policy anticipated the OOM merge and already adapted the test, it shall be back OK once the new policy dockers woudl be merged
        3. 1 error in E2E due to SDC (exception not caught)
        4. lots of patch in OOM gate..if lots of errors it is not normal as the master is reasonably stable...
        5. #action all help reviewing the OOM patches to give Integration feedback
      4. Guilin is not good
        1. same CI errors in DT and Orange
        2. runnign the tests directly is usually good => issue in the way to launch the test in guilin
        3. "old" ansible version in the xtesting-onap branch
        4. tests in progress to use xtesting-onap master (assuming that the test version is provided by a env variable already) => no need of specific branch
      5. delta guilin/current master shared with the community
        1. https://docs.google.com/spreadsheets/d/1t3GNRtabdkVxG4ZAxqBJ-X7OO-Zv6xRwd8KrR52V9zU
        2. as usual some projects anticipate and provided features continuously (Policy, DCAE, NBI, OOF, OOM), some did not...which explains the gating bottlneck due to the M3
    4. security test update
      1. tern (Alexander Mazuruk user-98b79 )
        1. last results: https://logs.onap.org/onap-integration/daily/onap_weekly_pod4_master/02-25-2021_02-02/security/tern/
        2. patch submitted to fix some projects ..but they have no gating so manual test needed
          1. first patch submitted
          2. advantage, it will be easier to chase CVE if we can rely on baseline images
          3. issues with Python (and lib dependencies) but few components dealing with python
        3. next steps work on teh integration as a weekly job in xtesting-onap to run automatically tern everyweek
      2. versions still some issue in weekly chain + reporting to be integrated
        1. patch merged for the bug
        2. results of last week shared => https://logs.onap.org/onap-integration/daily/onap_weekly_pod4_master/02-25-2021_02-02/security/versions/versions/index.html
      3. core/internal nodeports tests can be long ..any idea how to parallelize
        1. wait for Paweł Wieczorek come back as same issue than for versions
    5. Backup & restore
      1. postponed to next week
    6. simu question on the availability of the E// pnf simu availability in nexus AJAY SINGH
      1. answer sent by mai, changes done broke the built chain => after 40 days the snampshot images are removed, as the image was not released and not rebuilt, expiration date was reached => need to fix the build or to release an old version (pretty sure that jenkins history is also cleaned..so probably not possible)
  4. AoB
  5. Action points for next meeting

...