- 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 Legacy server System 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 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-3450
- Former user (Deleted) 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
- Ahila P Network slicing automation
- 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
- 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
- List of log4j vulnerability impacted pods in ONAP
Today morning Trivy was ran on ONAP daily master
Code Block language text 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
- There are more and more critical issue found, but these are just for cve-2021-44228
...