- Action point follow-up
- Admin
- testsuite 1.6.1 released successfully
- 1.6.2 to be planned (lots of work on policy by Brian and Marco)
- testsuite 1.6.1 released successfully
- integration java 11 docker not generated in ONAP : https://nexus3.onap.org/#browse/search/docker=attributes.docker.imageName%3Donap%2Fintegration*:c60bc6b9612f47d368c19be6ea730120
- work for xtesting dockers in progress
- new repository for onap_tests to be planned (consuming python_onap_sdk for Guilin)
- issue on windriver lab/ bad configuration with python client confirmed by Steven
- new committers - coordinator is ..coordinating (request under review)
- RC1 postponed - RC0 still missing ESR, CDS
- Frankfurt
- Use Case status
- Lab lab status
- windriver SB-00 weird out of memory on 1 node. Seems that recovery was fine..
- wiki page follow-up: 2: Frankfurt Release Integration Testing Status
- vCPE descoped (neither Brian nor Bartek have resources for Frankfurt)
- bulk PNF annonced completed but blocking JIRA open..
- First attempt to integrate vcpe_tosca in CI (but onapcli needed)
- Lab lab status
- CI status
- Use Case status
- Guilin
- still time to complete the page => vote on priorities next week? => Epic => JIRA
- good to have some visibility on your possible commitment (Marco already indicated that he will have less time)
- AoB
(16:39:52) collab-meetbot: Meeting ended Wed May 6 14:39:51 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
(16:39:52) collab-meetbot: Minutes: http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2020/onap-int.2020-05-06-14.27.html
(16:39:52) collab-meetbot: Minutes (text): http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2020/onap-int.2020-05-06-14.27.txt
(16:39:52) collab-meetbot: Log: http://ircbot.wl.linuxfoundation.org/meetings/onap-int/2020/onap-int.2020-05-06-14.27.log.html
- Action point follow-up
- Admin
- Request for committer promotion sent to TSC for Andreas, Pawel and Krzysztof
- weird error detected with testsuite-1.6.0
- the code was old (Dublin)
- however the self release process was OK, the references provided were correct
- the recent daily tag was dealing with old code, test on the last daily tag was OK
- 1.6.0-STAGING-latest always OK
- 1.6.0 regenerated but looks still old... (1.4.3) => ticket to LF https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-19593
- Request to send daily results in Nexus in progress https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-19494
- Request to generate docker for non Java projects (without recreating a bash script within the jjb directories) also in progress https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-19533
- windriver CI / gitlab block due to an misconfiguration
- The requests from the python client are very long (compared to CLI)
- there are some attempts using private endpoints before using the right one.
- Flavor check takes for instance less than 1 minutes for the 16 VM supposed to host the k8s nodes, it takes more than 1 h in windriver..
- Use Case status
- Lab lab status
- windriver SB-00 installed since last week
- wiki page follow-up: 2: Frankfurt Release Integration Testing Status
- Lab lab status
- Frankfurt
- CI status
- infra-healthcheck: https://gerrit.onap.org/r/c/oom/+/106586
- dmaap timeout occurs once in a while:
- healthcheck
- only multicloud (WIP) in onap health
- note if security fixes merged by Music => trigger OOF errors, sync needed
- smoke tests
- pnf registrate is now working in the CI chains: thanks to Krzysztof Ku?mickiKuzmicki !
- basic tests are also working (still using deprecated VNF API but at least basic onboarding/distribution/instantiation is suceessfully from outside the cluster) thanks to Andreas Geissler
- security: 2 tests expected to be OK for M4
- public endpoint: only music patch ready but resync with OOF needed
- 10 rooted pods remaining (2 AAI/ESR, CCDSK, MUSIC, MSB (fixed but not merged yet))
- infra-healthcheck: https://gerrit.onap.org/r/c/oom/+/106586
- CI status
...