...
- results not bad. Remaining test errors due to DCAE changes but a patch is in gate - no results due to error below.
- The Makupsafe issue (jinja2 upstream dependency) is also responsible for the istanbul k8s installation issue
...
- deployment OK but all smoke tests failing due to Makupsafe
...
...
...
- 5G Slicing automation follow up
- All patches of Maciej Lisowski merged
- Question from Ahila P on simulators sent by mail. For the moment 2 of the 3 simulators are in the wiki. Action morgan push simu to the repo (the repo already exists)
- kubescape => demo next week
- Load test on AAI (using gatling) => action Morgan Richomme resync Michał Jagiełło /William Reehil / Christophe AUZIZEAU
- kafka (testing refactoring) => Refactoring of tests due to kafka refactoring, answer sent by mail to Fiachra Corcoran
...
- Morgan Richomme and Sylvain Desbureaux are stepping down
- end of contributions: end of March 2022
- end of Orange platform: end of Jakarta release (with minimal support)
- Azure / NH won't be touched (gating will work, staging, ...) but resources to be identified to manage them...
- Lab status
- onap-k8s issue - there is an another issue after the dependency library new version release
- Orange lab - some issues with connection during random tests
still blocks master gatingJira server ONAP Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key AAI-3450
- user-98b79 http://scancode.onap.eu/
- logging currently using GitHub account (consider using LF ID)
- needs to be discussed with seccom where the scan policies should be stored
- prepare a demo with two Integration projects:
- integration/docker/onap-java11 · Gerrit Code Review
- integration/docker/onap-python · Gerrit Code ReviewAdd images into scancode during
docker-verify
Jenkis job and run pipeline for them. We could analyse results and present that during one of the incoming PTL meetings
- INT-2021 - Automate 5G Slicing use case in CI OTWARTY update
- Create a demo · Gerrit Code Review (onap.org) repo directory to keep there scripts and migrate Manual Configurations - Developer Wiki - Confluence (onap.org) into markdown files there to be able to keep history and review changes
- Lab status
- Orange lab down
- DT still down
- Gating is OK, but since today some A&AI issues observed
- basic_cnf_macro test
- E2E network slicing use case
- INT-2064 - Automate 5G Slicing use case in CI - Manual configuration step 1 - SDC OTWARTY
- INT-2065 - Automate 5G Slicing use case in CI - Manual configuration step 2 - UUI Configuration OTWARTY
- INT-2066 - Automate 5G Slicing use case in CI - Manual configuration step 3 - MSB Configuration OTWARTY
- INT-2067 - Automate 5G Slicing use case in CI - Manual configuration step 4 - SO OTWARTY
- INT-2068 - Automate 5G Slicing use case in CI - Manual configuration step 5 - OOF Configuration OTWARTY
- INT-2069 - Automate 5G Slicing use case in CI - Manual configuration step 6 - Policy Creation Steps OTWARTY
- INT-2070 - Automate 5G Slicing use case in CI - Manual configuration step 7 - AAI Configuration OTWARTY
- INT-2071 - Automate 5G Slicing use case in CI - Manual configuration step 8 - ConfigDB OTWARTY
- INT-2072 - Automate 5G Slicing use case in CI - Manual configuration step 9 - SDNC OTWARTY
- INT-2073 - Automate 5G Slicing use case in CI - prepare a demo repo section OTWARTY
...
- at the beginning Integration team needs to take a look on the first phase: Manual Configurations - Developer Wiki - Confluence (onap.org) - preparing an ONAP for instantiation
- several steps - for sure some missing gaps in ONAP SDK
- There is a plan to create a scenario in pythonsdk-tests repo for that use case
- [INT-2021] Automate 5G Slicing use case in CI - ONAP JIRA ticket which is going to be used to plan a work
- Automate use case 5G Slicing in CI - Developer Wiki - Confluence (onap.org) ← links shared by Ahila P
...
Today morning Trivy was ran on ONAP daily master
Code Block | ||
---|---|---|
| ||
Pods
onap-cli-757c76f546-zfd4m in vulnerable!
onap-message-router-0 in vulnerable!
onap-sdnrdb-coordinating-only-6f6d6b887b-kzr9x in vulnerable!
onap-sdnrdb-master-0 in vulnerable!
onap-sdnrdb-master-1 in vulnerable!
onap-sdnrdb-master-2 in vulnerable!
onap-vfc-huawei-vnfm-driver-57fddd8bc7-nqn7b in vulnerable!
onap-vnfsdk-56d9fb886f-sk4s4 in vulnerable!
Images:
nexus3.onap.org:10001/onap/cli:6.0.1 -> onap-cli-757c76f546-zfd4m
nexus3.onap.org:10001/onap/dmaap/dmaap-mr:1.3.0 -> onap-message-router-0
docker.nexus.azure.onap.eu/bitnami/elasticsearch:7.9.3 -> onap-sdnrdb-coordinating-only-6f6d6b887b-kzr9x, onap-sdnrdb-master-X
nexus3.onap.org:10001/onap/vfc/nfvo/svnfm/huawei:1.3.9 -> onap-vfc-huawei-vnfm-driver-57fddd8bc7-nqn7b
nexus3.onap.org:10001/onap/vnfsdk/refrepo:1.6.3 -> onap-vnfsdk-56d9fb886f-sk4s4 |
...
- Disable portal tests Krzysztof Kuzmicki
- user-98b79 starts http://scancode.onap.eu/ . Thanks!
- Lab status
- Better results, but due to Nexus restart and no images all tests failed
- cds-resource-resolution is still failing... looks the instance is created before tests is executed
- Integration risks for Jakarta Jakarta Risks - Developer Wiki - Confluence (onap.org)
- Main risks are resources: labs and humans
- Nexus restart https://lists.onap.org/g/onap-discuss/message/23758 should we restart the images creation?
- Yes, after Jenkins and Nexus are back again jobs below need to be rerun
- https://jenkins.onap.org/view/integration/job/integration-xtesting-healthcheck-docker-merge-master/
- https://jenkins.onap.org/view/integration/job/integration-xtesting-security-docker-merge-master/
- https://jenkins.onap.org/view/integration/job/integration-xtesting-infra-healthcheck-docker-merge-master/
- https://jenkins.onap.org/view/integration/job/integration-xtesting-smoke-usecases-pythonsdk-docker-merge-master/
- https://jenkins.onap.org/view/integration/job/integration-xtesting-smoke-usecases-robot-docker-merge-master/
- https://jenkins.onap.org/view/integration/job/integration-xtesting-smoke-usecases-robot-py3-docker-merge-master/
- Yes, after Jenkins and Nexus are back again jobs below need to be rerun
- Nexus doesn't work - tests doesn't work....
- LF ticket created - Theme Extension - Linux Foundation JIRA
- gatig tests works due to Azure cache - images are not downloaded from nexus during each execution
- When it worked we had several tests issues
- needed to check if we don't use same kubeconfig on many tests pipelines
- that can create conflicts because one test tries to create an instance of existing resource
- needed to check if we don't use same kubeconfig on many tests pipelines
- Kubescape tests
- could be useful but won't replace already existing tests
- root pods check based just on the kubernetes resource definition (pod, deployment, statefulset etc.) and not check if the root user is disabled on the image
- could be possible to add them into pipeline soon
- could be useful but won't replace already existing tests
...
- there are currently 3 Azure labs
- 2 gatings and 1 integration lab with ONAP
- needs to ask TSC if it's possible to add one more to run daily tests - outside of any company infrastructure (currently Orange, Nokia, DT)
- we could run daily on the 1 integration lab machine, but there is a risk we won't have a working lab if during daily execution ONAP creation fails
...
- it's not required and will take a lot of time and resources, leave it as it is
...