| Use Case | JIRA link (REQ) One issue per requirement. Instructions | Owner(s) | TSC Ranking | M1 Scorecard | TSC M1 Approval Recommendation | M2/M3 Scorecard | TSC M2/M3 Approval | M4 Scorecard | TSC M4 Approval | RC0 Scorecard | TSC RC0 Approval | Link(s) to HLD/LLD if any | Dependency (from/to) another project(s) | T-Shirt Size  | Project's Impact: Test Only (TO), Code (C) | Committed (C)/ Partially Committed (P) or not (N) per impacted project
| If Partially or not committed, what are the project gaps (FTE, reqs, etc) | Integration Lead(s) | Company Engagement | Notes |
|---|
| Third Party Operational Domain Manager |  REQ-17 - Third Party Operational Domain Manager In Progress
| | RANK #0 | | YES | | YES | | YES | GREEN | No information from Test Lead in the wiki 2: Frankfurt Release Integration Testing Status | Third-party Operational Domain Manager |
| S | SDC (C) SO (TO) AAI (TO) | Changes being done in local setup SDC: Committed based on Telstra contribution [TSC]: What does it mean? No SDC contribution to the ONAP Community. [Atif]:Changes were temporarily done locally, when the ElAlto branch wasn't cut and we couldn't commit to master | Will commit after review discussion with SDC PTL
[TSC]:What's the status? PTL OK? [Atif] PTL is OK. Code commit started. | | Telstra | Complete company commitment for delivery of Frankfurt Scope for this use case |
| Service Resolver Features | | Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | REQ-13 |
|---|
|
| rene.robert@orange.com | RANK #4 | | NO |
|
|
|
|
|
| Service Resolver |
|
| SDC (C), SO (C), AAI (TO) | No SO decision | MISSING INFO | MISSING INFO | Orange |
|
| CMPv2 CA Plugin for AAF | | Jira |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | REQ-140 |
|---|
|
| | RANK #3 | | YES | The new approved committers resolved the risk for not getting the code committed into the project. The approval of a new targeted solution from ‘ArchCom’ results in no dependency on AAF CertMan, thus our previous major risks for delay has been resolved. This new design has resulted in a larger contribution than intially planned, which introduces a new risk of delay due to not sufficient time.
| YES
| M4 Exception request. Full functionality postponed to RC0 due to late M2/M3 milestone achievement in relation to AAF issues. Main parts of functionality delivered. First E2E test successfully done.
Exception agreed with Integration PTL (Morgan) Pending agreement with AAF team (John, Jonathan)
| YES | 09.04.2020 update: OOM integration still not finalized. OOM experts (Sylvain and Krzysztof) are working with Nokia and E/// to finalize OOM contribution. Contribution which left can also be considered as integration effort as only OOM repo is going to be updated. AAF part is over.
02.04.2020 update: OOM integration is almost over. First manual installation on Nokia lab was ok with some workarounds in different charts, but there is a problem in other charts that blocks success verification on Orange lab.
26.03.2020 update: Still one week is required to finalize this requirement. E2E (client↔server↔CMPv2 server) functionality delivered. Two tasks left - AAF's new microservice-OOM integration (AAF-1083) and secure communication between CertService's client and CertService (AAF-1084).
| No information from Test Lead in the wiki 2: Frankfurt Release Integration Testing Status
April 9: Damian Nowak says that code is complete. Will update integration test status April 15: Tracked as #43 on Frankfurt Release Integration Testing Status (same item as for REQ-76) |
|
| XL - | AAF (C) Integration (C) | AAF: (C) Integration:(C) | See notes | | AT&T Ericsson Nokia
| Note: Nokia and Ericsson volunteered to work this. As PTL, I approved the path forward (create Client, build plugin, etc) but was unable to create actual REQ. Please consider this working item until them. (update : | Jira |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | REQ-140 |
|---|
|
created, at the moment we do not expect multiple release impacts but it has to be further checked) ALSO... This MAY be a multi-release effort, which will not affect normal Operations in anyway, if CMPv2 isn't completed within Frankfurt. |
CCVPN: E-LINE Service over OTN NNI | | Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | REQ-141 |
|---|
|
| LIN MENG | RANK #2 | | YES | Note: Functional impacts and API changes in the related modules have been reported and documented. To be more specific : API changes in A&AI and SDN-C are committed and merged. OOF: Swagger API document is provided; coding has be started by last week. U-UI has no API change, resource are in the coding phase now;
| YES | Note: - Code in impacted modules has been merged.
- Documentation has been submitted.
- Ready for integration test.
| YES | For AAI, UUI & OOF integration test are completed using snapshot version and waiting for released version of UUI and OOF for testing with Frankfurt version. SDN-C testing hasn't been finished yet. | Recommended for a GO? Tracked as #12.1, 12.2 on Frankfurt Release Integration Testing Status | E-LINE over OTN Inter-Domain Links - Proposal |
| XL (Multiple releases) | TO: SO; C: U-UI, A&AI, OOF, SDN-C | U-UI committed by ChinaMobile; A&AI committed by Huawei; OOF committed by Huawei; SDN-C committed by Huawei |
| | China Mobile, Huawei |
|
End to End Layer 1 Service Management. Modeling the Optical Service | | Jira |
|---|
| server | ONAP JIRA |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | REQ-37 |
|---|
|
| | RANK #3 | CCSDK PTL has confirmed he can deliver it | YES
| Functional requirements & corresponding APIs have been documented across: A&AI, SDNC, CCSDK - merge in progress SO - coding phase UUI - coding phase | YES | Code has been merged for following modules: A&AI, SDNC, UUI Documentation has been merged SO code changes are currently under discussion & might require design change causing delay or reducing scope of use-case. (Risk identified under Frankfurt risks) 3/11 update: SO changes have been resubmitted & is under review. Have preliminary agreement from PTL (seshu). All other impacted modules has been merged. 3/18 update: Previous resubmission has been merged. Some small fixes are submitted and ready for merge. 3/25 update: Ready for integration test.
| YES
| Integration test cases have been executed across SO, SDNC, A&AI, UUI components based on available version Waiting on official F release version for verification | Recommended for a GO? Tracked as #12.1 on Frankfurt Release Integration Testing Status | Multi-domain Optical Network Services | CCVPN use-case alignment | XL (Multiple releases) | TO: SDC, ExtAPI C: UUI, SO, A&AI, SDN-C, CCSDK | SO - C A&AI - C SDN-C - C UUI - C CCSDK-C SDC - TO ExtAPI - TO Code will be committed by Fujitsu
| Have gained PTL agreement & JIRA epics have been created under UUI, SO, SDNC, A&AI, CCSDK | Xin Miao | AT&T Orange Fujitsu | Working with CCVPN team to align towards common modelling for OTN |
Deploying Distributed External functions
| | Jira |
|---|
| server | ONAP JIRA |
|---|
| serverId | 425b2b0a-557c-3c0c-b515-579789cceedb |
|---|
| key | REQ-195 |
|---|
|
| | RANK #0
| | YES | | YES | |
|
|
|
| Depends on development progress of Multi-Cloud K8S work. (K8S based Cloud region support (Continue from R4)) | XL (Multiple releases) | TO: Multi-Cloud | Intel will contribute to this. There is no code development and it is for testing the work being done in MC project. |
| | Intel, Aarna, TM |
|
