Page History

01 Jul 2020 

1. Action point follow-up
2. Admin
   1. windriver
      1. cleaning operation about to start... Windriver lab Frankfurt cleaning campaign
      2. resources for terraform based installation created
   2. robot-utils: repository is available => we could set a robot linter (not done on testsuite due to lots of errors but could be applied here)
3. Stable branches
   1. Frankfurt
      
      1. status
         1. CI follow-up
         2. use case: maintenance release will be needed for some use cases..
         3. most of the questions dealing with frankfurt issues are related to the installation( maria-galera resinstallation)
   2. El Alto
      1. CI run until beginning of May (switch to daily Frankfurt)
      2. Results wer OK and fixes (end of branches mainly deal with certificate issues) => no need to launch a full regression campaign all the more as, as all the use case owners are no more involved in ONAP it would be impossible to deal with the use cases.
4. Guilin
   1. new JIRA board: https://jira.onap.org/secure/RapidBoard.jspa?rapidView=221&selectedIssue=INT-1268
   2. new robot pod archi
      1. testsuite/oom helm chart to be moved back to OOM (proposal to have both in // during transition phase)
      2. leveraging on new architecture proposed by Daniel Rose (3 pods: 1 robot, 1 DB, 1 web server)
      3. shall follow OOM recommendations (cloud native, security,..)
      4. run the tests from inside the cluster/outside )> consequences
   3. Guilin Requirements dealing with VNF automation
      1. Requirements submitted by Lei Huang  ( Image AddedREQ-335 - Support for Test Topology Auto Design （NFV Testing Automatic Platform） To Do ,  Image AddedREQ-336 - Support for Test Environment Auto Deploy（NFV Testing Automatic Platform） To Do , Image AddedREQ-337 - Support for Test Task Auto Execution （NFV Testing Automatic Platform） To Do , Image AddedREQ-338 - Support for Test Result Auto Analysis & Certification （NFV Testing Automatic Platform） To Do
      2. Clarification needed to understand what is expected, how integration can help,..
   4. Pythonsdk 
      
      1. First release available on pypi: https://pypi.org/project/onapsdk/
      2. discussion on the possible scenarios to be created in https://git.onap.org/testsuite/pythonsdk-tests/
         1. first PoC proposed for scenarios: https://gitlab.com/Orange-OpenSource/lfn/onap/pythonsdk-tests
         2. place for discussion: https://etherpad.opnfv.org/p/onap_integration_onapsdk_scenarios
   5. new use cases
      1. first try on check certificates: dealing with nodport/internal/ingress => to be integrated in CI
      2. preonboarding, vcpe_tosca still in the loop
      3. Upstream cds tests are coming
      4. security test
         1. cleaning of the xfail lists on master?
         2. http enpoint => update: switch to nonssl? (Paweł Wieczorek )
         3. which threshold fro limits?
         4. check version according to SECCOM recommentations => ask SECCOm to move their list through a file in their repo to get a gerrit reference rather than a wiki page?
5. AoB

(19:15:07) collab-meetbot: Minutes: http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2020/integration_weekly_meeting_1_07_2020/onap-int-integration_weekly_meeting_1_07_2020.2020-07-01-16.38.html
(19:15:07) collab-meetbot: Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2020/integration_weekly_meeting_1_07_2020/onap-int-integration_weekly_meeting_1_07_2020.2020-07-01-16.38.txt
(19:15:07) collab-meetbot: Log: http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2020/integration_weekly_meeting_1_07_2020/onap-int-integration_weekly_meeting_1_07_2020.2020-07-01-16.38.log.html

24 Jun 2020 

• vF2F event, meeting canceled

17 Jun 2020 

1. Action point follow-up
2. Admin
   1. windriver
      1. cleaning operation end of June confirmed: Windriver lab Frankfurt cleaning campaign
      2. discussions on the integration needs (which project shall we keep..)
      3. new request for resources for terraform based installation
   2. robot-utils: self-release procedure tried but not successful, WIP if blocking => use the old method
   3. Any objection to archive oparent/cia?
3. Frankfurt
   
   1. status
      1. CI follow-up
      2. demo artifacts published today
      3. use case: maintenance release will be needed for some use cases..
4. Guilin
   1. Pythonsdk update  (Michał Jagiełło
      
      1. what's new (https://gitlab.com/Orange-OpenSource/lfn/onap/python-onapsdk)
      2. discussion on the possible scenarios to be created in https://git.onap.org/testsuite/pythonsdk-tests/
         1. place for discussion: https://etherpad.opnfv.org/p/onap_integration_onapsdk_scenarios
         2. smoke
            1. basic_vm (GR_API - VNF API is deprectaed now)
            2. freeradius_nbi
            3. clearwater vIMS
            4. basic_network
            5. basic_vm_cds
            6. basic_vm_closed_loop
            7. basic_cnf
            8. basic_cnf_closed_loop
            9. vfw_closedloop
            10. ....
         3. healthcheck
            1. basic_cds (upload CBA)
            2. basic policy
            3. ...
   2. new JIRA board: https://jira.onap.org/secure/RapidBoard.jspa?rapidView=221&selectedIssue=INT-1268
   3. new robot pod archi
      1. testsuite/oom helm chart to be moved back to OOM
      2. leveraging on new architecture proposed by Daniel Rose (3 pods: 1 robot, 1 DB, 1 web server)
   4. new use cases
      1. first try on check certificates (+ pres done for PTL)
      2. preonboarding, vcpe_tosca still in the loop
      3. Upstream cds tests are coming
      4. security test
         1. cleaning of the xfail lists on master?
         2. http enpoint => update: switch to nonssl? (Paweł Wieczorek )
         3. which threshold fro limits?
         4. check version according to SECCOM recommentations => ask SECCOm to move their list through a file in their repo to get a gerrit reference rather than a wiki page?
5. AoB

...