...
| Project Name | OOM | Notes | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Health CheckOK | PASS | Integration-staging-oom-daily | ||||||||||||||||||||||||||||||
SO ↔ SDNC | Pass | PASS | Integration-staging-oom-daily VNF-API Pass vFW Usecase deployed on OOM | |||||||||||||||||||||||||||||
| SO ↔ AAI | PassPASS | Integration team could proceed with the test vFW Usecase deployed on OOM | SO ↔ LOG (ELK) | in-Progress | | Jira | | ||||||||||||||||||||||||||
| server | ONAP JIRA | |||||||||||||||||||||||||||||||
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb | key | SO-1110-staging-oom-daily||||||||||||||||||||||||||||||
SO ↔ Multi cloud | PassPASS | Carried on by SO team, using staging-oom Basic sets of API calls appear to work ok. Some issues filed related to AAI update API calls:
(note: above testing is limited to SO using infra_workload api of multicloud. Tested on OOF pod - vFW Create/Query/Delete have been performed successfully in the OOF pod. Solved issues:
Jira | server | ONAP JIRA | columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution | serverId | 425b2b0a-557c-3c0c-b515-579789cceedb | key | SO-1142 | ||||||||||||||||||||||
| SO ↔ VFC (deploy) | Pass | SO ↔ SDC | Pass | |||||||||||||||||||||||||||||
| SO ↔ OOF | Pass | Resolved: 10/16 Tried updated OOM charts for Music/OOF - still seeing issues with pods initializing, have OOF team members troubleshooting 10/17 OOF pods are now coming up using a workaround for aaf-sms issue, however healthcheck is not passing, OOF team members are investigating. We are planning on sending some homing request from SO to OOF later in the day, once this issue is fixed and OOF is configured. 10/19 OOF team has resolved blocker and setup simulators to interface with OSDF. This should enable SO to test SO/OOF interface. Testing Resumes and will be updated today with results. Resolved: 10/22 I was able to send a homing request for vFW from SO and receive a homing solution from OOF. Moving pairwise to pass. Since OOF (OSDF) is mocking communication with policy/HAS/AAI etc. testing of a real solution will resume in integration test when OOF is completely functional. Tested in OOF project of pod-onap-01 Solved Issues:
Issues In Progress:
| ||||||||||||||||||||||||||||||
| PASS | Integration-staging-oom-daily (VFC Pair Wise Testing for Frankfurt Release) | |||||||||||||||||||||||||||||||
| SO ↔ SDC | PASS | Integration-staging-oom-daily | ||||||||||||||||||||||||||||||
| SO ↔ OOF | NA | Nothing new in Dublin | ||||||||||||||||||||||||||||||
| SO ↔ VID | PASS | Integration-staging-oom-daily | ||||||||||||||||||||||||||||||
| PRH ↔ SO, via DMaap | In-Progress | Needs | SO ↔ VID | Pass | VNF API - Pass vFW Usecase deployed on OOM |