The page is intended to summarize all the requirements for Frankfurt Release.
These requirements have been prioritized by the TSC to realistically fit within the Frankfurt Release Timeline.
The Release Scope should be finalized during the M1 Release Planning milestone on November 7th, 2019
TSC Prioritization (Ranking)
- RANK #0 – Special GO - quick wins, fully covered by involved companies
- RANK #1 – TSC Must Have – Mandatory for the release
- RANK #2 – Continuity - Items continued from previous releases
- RANK #3 – PTL Go – items that PTLs is OK to include since team has bandwidth
- RANK #4 – NO GO – items not approved for various reasons
Scorecard Key
Release 6 (Frankfurt) proposed use cases and functional requirements
M1 Scorecard:
- Green: Use Case will be fully implemented and tested
- Yellow: Use Case will be partially implemented. It is possible to identify capabilities for this use case that can be tested (phasing approach).
- Red: Use Case can not be partially delivered, min. requirements can not be met in order to define a testing strategy.
Other Milestones:
- Green: On Track
- Yellow: Use Case/Requirement not on track but could be mitigated by reducing the current scope and/or fix this issue prior M4. Risks identified and documented under Frankfurt Risks
- Red: Use Case/Requirement not on track and issue identified that will prevent from completing the development by M4. Use Case/Requirement should be moved to POC in alignment with the POC definition or de-scoped from the Frankfurt release.
Architecture:
- Pink - NO GO
- Purple - GO
- Green - Considered OK not requiring architecture review
- Black - Architecture not yet performed
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
| Use Case | JIRA link (REQ) One issue per requirement. | 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 |
| RANK #0 | GREEN | YES | GREEN | YES | GREEN | YES | GREEN | GO Tracked as #45 on 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 | REQ-13 - Getting issue details... STATUS | rene.robert@orange.com | RANK #4 | DESCOPED | NO | Service Resolver | SDC (C), SO (C), AAI (TO) | No SO decision | MISSING INFO | MISSING INFO | Orange | |||||||||
| CMPv2 CA Plugin for AAF | REQ-140 - Getting issue details... STATUS | RANK #3 | GREEN Confirmed by AAF PTL | YES | GREEN Update 1/24: 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 | YELLOW 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 | YELLOW 16.04.2020 && 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). | GO 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 : REQ-140 - Getting issue details... STATUS 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 | REQ-141 - Getting issue details... STATUS | LIN MENG | RANK #2 | GREEN | YES | GREEN 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 | GREEN Note:
| YES | YELLOW 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. | 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 | REQ-37 - Getting issue details... STATUS | RANK #3 | GREEN CCSDK PTL has confirmed he can deliver it | YES | GREEN Functional requirements & corresponding APIs have been documented across: A&AI, SDNC, CCSDK - merge in progress SO - coding phase UUI - coding phase | YES | GREEN 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 | GREEN 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 | 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 | REQ-195 - Getting issue details... STATUS | RANK #0 | GREEN | YES | GREEN | YES | DESCOPE | Depends on development progress of Multi-Cloud K8S work. | 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 |
- XS - <4 Man/Weeks;
- S - ~6 Man/Weeks;
- M - ~8 Man/Weeks;
- L - ~12 Man/Weeks;
- XL - > 12 Man/Weeks.
Requirements
M1 Scorecard:
- Green: The requirement will be fully implemented and tested
- Yellow: The requirement will be partially implemented. It is possible to identify capabilities for this functional requirement that can be tested (phasing approach).
- Red: The requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy
Architecture:
- Pink - NO GO
- Purple - GO
- Green- Considered OK not requiring architecture review
- Black - Architecture not yet performed
| Requirement | JIRA link (REQ) One issue per requirement. | Owner | TSC Ranking | M1 Scorecard | TSC M1 Approval Recommendations | M2/M3 Scorecard | M2/M3 TSC Approval | M4 Scorecard | M4 TSC Approval | RC0 Scorecard | RC0 TSC approval | Link(s) to HLD/LLD if any | Dependency (from/to) another project(s) | T-Shirt Size (XS, S, M, L, XL) | Project's Impact: Test Only (TO), Code (C), Documentation Only (DO) | Committed (C)/Partially Committed (P) or not (N) per Impacted projects | If Partially or not Committed, what are gaps/ project (people/FTEs; HLD/LLD; etc) | Integration Lead | Company Engagement | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
All Control Loop Policy Models should be TOSCA Compliant Operational, Guard Policies | REQ-21 - Getting issue details... STATUS | RANK #2 | GREEN | YES | GREEN | YES | GREEN | YES | GREEN | GO Track as #39 on Frankfurt Release Integration Testing Status | TOSCA Compliant Policy Types | SDC | M | CLAMP - C POLICY - C | CLAMP - C POLICY - C committed by AT&T & Ericsson | AT&T Ericsson | ||||
| Policy Update Notifications | REQ-25 - Getting issue details... STATUS | RANK #2 | GREEN | YES | GREEN | YES | GREEN | YES | GREEN | GO Track as #40 on Frankfurt Release Integration Testing Status | Policy Update Notifications | S | DCAE - C POLICY - C | DCAE - C POLICY - C committed by AT&T | AT&T Wipro | DCAE: Commitment based on Wipro | ||||
| CLAMP Deployment of Policies to PDP Groups | REQ-29 - Getting issue details... STATUS | RANK #3 | GREEN | YES | GREEN | YES | GREEN | YES | GREEN | GO Track as #41 on Frankfurt Release Integration Testing Status | CLAMP Deployment of Policies to PDP Groups | M | CLAMP - C POLICY- C | CLAMP - C POLICY - C committed by AT&T | AT&T Ericsson | |||||
| Integration of CDS as Actor in Control Loops | REQ-33 - Getting issue details... STATUS | RANK #3 | GREEN | YES | GREEN | YES | GREEN | YES | GREEN | GO Track as #42 on Frankfurt Release Integration Testing Status | CDS actor support in Policy | REQ-21 - Getting issue details... STATUS | L | CLAMP - C POLICY - C CDS - C Integration - C | CLAMP - C POLICY - C CDS - C Integration - C | Partial commitment from Bell Canada to support Policy+CDS integration. Partial commitment from Huawei to support | AT&T Bell Canada Ericsson Huawei Orange | |||
| Control Loop Tutorial Documentation | REQ-150 - Getting issue details... STATUS | RANK #3 | NO CODE IMPACT | YES | GREEN | YES | YELLOW Only Documentation No resources for Integration | YES | DE-SCOPED Limited resourcesSynchro with Sel-Serve Control-Loop | De-scoped, based on feedback from Eric Debeau | REQ-150 - Getting issue details... STATUS | CLAMP, DCAE, POLICY | M | Documentation - DO | DOC - C (Orange) POLICY - C (AT&T) DCAE - C (AT&T) CLAMP - C (AT&T) | No integration tests | Bell Canada, AT&T, Orange | |||
| Component Upgrades to new Policy Lifecycle API | REQ-162 - Getting issue details... STATUS | RANK #2 | GREEN | YES | GREEN | YES | GREEN | YES | GREEN | GO Track as #42 on Frankfurt Release Integration Testing Status | M | SDNC - C OOF - C POLICY - C | POLICY - C (AT&T & Intel) OOF - C (Intel) SDNC - C (AT&T) | AT&T, Intel | ||||||
| Modeling: Enhanced Nested and Shared Service Information Model - 5G / E2E Network Slicing modeling | REQ-60 - Getting issue details... STATUS | TSC: Replaced by new E2E Network Slicing Scope No commitment to cover ExtAPI | NETWORK SLICING PoC in R6 Frankfurt (Obsolete) | SDC Possibly dependent on REQ-162 - Getting issue details... STATUS | L | SDC-C AAI-C External API | Company commitment per component SDC - C (Amdocs) AAI - C (Amdocs) | *Note: Not sure integration lead is needed for modeling | CMCC Amdocs AT&T Wiprc Huawei | |||||||||||
| 5G / OOF SON Enhancement | REQ-154 - Getting issue details... STATUS | RANK #3 | GREEN CCSDK is not required | YES | GREEN | YES | GREEN | YES | GREEN | GO Track as #9 on Frankfurt Release Integration Testing Status | OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt | L | POLICY - C OOF - C DCAE - C SDN-C - C Integration (Demo VNFs) - C (See Notes) | POLICY - C OOF - C DCAE - C SDN-C - C
Integration (Demo VNFs) - C DCAE, Integration: - Wipro commits OOF, Policy: - AT&T commits SDN-C: IBM commits | AT&T Wipro IBM | RAN-Simulator submitted as part of simulators repo. Originally Runtime DB was also indicated as a potentially impacted component, however, it is not a part of Frankfurt release. So the necessary functionality for this use case (for Frankfurt) is continued to be realized using ConfigDB. | ||||
5G / Run-time Data Persistency (RunTime Config DB) and VES Model relations, VES CM model (CM Notify). | REQ-267 - Getting issue details... STATUS | RANK #3 | GREEN PTL has confirmed he can deliver CCSDK, SDN-C | YES | GREEN | YES | GREEN (see Project Wiki). Agreed to functionality in CC-SDK has been code-submitted. Reduced scope: No CM Notify VES event; No CIM/Yang. | YES | GREEN | GO Tracked as item 46: Frankfurt Release Integration Testing Status | CONFIGURATION & PERSISTENCY SERVICE | CM Notify VES Event (defined by Harmonized U/C) this U/C will actually use the CMNotify VES event and DCAE development to use the Event. | L | A&AI - TO SDC - TO Controller - C RunTime DB (new component) - C DCAE - C | A&AI - C SDC - C Controller - C RunTime DB (new component) - C DCAE - C Controller, RunTimeDB, - IBM commits SDC (TO) - AmDocs will commit DCAE - Nokia commits A&AI Testing - IBM will do testing. | Sandeep Shah | Nokia AT&T | Will be a new component, presented at Architecture S/C. | ||
| Modeling: GeoLocation Model (and standards harmonization) | Modeling work only | RANK #0 | NO CODE IMPACT | YES | GREEN | YES | DESCOPED | DESCOPED | PNF PLUG and PLAY in R6 Frankfurt | AAI | M | N/A | N/A | N/A | Ericsson Nokia | |||||
| PNF / PNF Software Upgrade using direct Netconf/Yang interface with PNF | REQ-84 - Getting issue details... STATUS | RANK #2 | GREEN SO impact clarified and agreed in SO weekly meeting. | YES | GREEN | YES | YELLOW Main function is merged. PNF upgrade procedure is working.
| YES | GREEN | GO Track as #23 on Frankfurt Release Integration Testing Status | PNF software upgrade in R6 Frankfurt | XL | SDC: C SO: C CDS: C VID: C Integration: C/DO VNFRQTS: DO | SDC: (C) SO: (C) CDS: (C) VID: (C) Integration: (C) Integration, SDC, SO, VID, CDS, and VNFRQTS are committed by Ericsson. SO is committed by Huawei | Ericsson Huawei | |||||
| PNF / Enable PNF software version at onboarding | REQ-88 - Getting issue details... STATUS | RANK #2 | GREEN Clarification: No impact on SO or VNF-SDK in R6. | YES | GREEN | YES | GREEN | YES | GREEN | Recommend GO Track as #24 on Frankfurt Release Integration Testing Status | M | SDC: C Integration: C VNFRQTS: DO | SDC: C Integration: C SDC, Integration and VNFRQTS are committed by Ericsson | Ericsson | ||||||
| LCM API Evolution | REQ-92 - Getting issue details... STATUS | TSC: Please merge with REQ-84 Oskar: Done, REQ-84 contains the R6 user stories related to this requirement. | https://wiki.onap.org/download/attachments/50202249/2019-07-02%20ONAP_R6_Controller_Evolution_LCM_APIs.pptx?api=v2 | N/A | Development in R6 will be part of REQ-84 | N/A | N/A | Ericsson | Main goals:
| |||||||||||
| PNF / Enhancement on PNF Software Upgrade with EM with Ansible | REQ-53 - Getting issue details... STATUS | RANK #2 | GREEN SO impact clarified and agreed in SO weekly meeting. | YES | GREEN | YES | GREEN | YES | GREEN | GO Track as #16 on Frankfurt Release Integration Testing Status | PNF software upgrade in R6 Frankfurt | LCM API Evolution | M | SO: C CCSDK: C Integration:C | SO: C CCSDK: C Integration:C Huawei commitment to SO,CCSDK,Integration | Huawei | ||||
| PNF / PNF Software Upgrade with EM with Netconf | REQ-96 - Getting issue details... STATUS | yaoguang wang | RANK #2 | GREEN SO impact clarified and agreed in SO weekly meeting. | YES | GREEN | YES | GREEN 03/11: Good progress so far. Based on good achievements of REQ-84 in SO and CDS, minor changes have been done. Test Status: Completed (see notes). | YES | GREEN | GO Track as #37 on Frankfurt Release Integration Testing Status | PNF software upgrade in R6 Frankfurt Notes: Test procedures and test results will be record soon in: PNF software upgrade with Netconf/Yang interface with EM | PNF Software Upgrade using direct Netconf/Yang interface with PNF | M | SO: C CDS: C Integration:C | SO: C CDS: C Integration:C Huawei commitment to SO, CDS, Integration | Enbo Wang | Huawei | ||
| 5G / ORAN & 3GPP Standards Harmonization | REQ-38 - Getting issue details... STATUS Modeling Only for Frankfurt | RANK #0 | GREEN | YES | PARTIAL GREEN green for A1 part (code merged) O1 enhancements moved to G release | YES | GREEN | YES | GREEN | GO Track as #22 on Frankfurt Release Integration Testing Status | MOBILITY STANDARDS HARMONIZATION WITH ONAP | M | SDNC: C DCAE: C | SDN-C: C DCAE: C SDN-C (A1 adaptor) committed by Ericsson & IBM DCAE committed by Nokia | Sandeep Shah (A1, O1) | AT&T Nokia Ericsson | DCAE: Impact for adopting new VES domain; Committed based on Nokia support. A1 Adapter implementation has been tested against A1 Mediator (1.0.0) | |||
| 5G / License Management | REQ-118 - Getting issue details... STATUS | RANK #0 ANSWER: There is no S/W development in R6. Company Commitment is commitment to work on Modeling & Architecture work for R6. Most of this U/C will be modeling development. | NO CODE IMPACT | YES | GREEN No API, No S/W | YES | GREEN | YES | GREEN | GO | LICENSING MANAGEMENT | SDC | M | Modeling: DO VNFRQTS, after UCs agreed: DO
( *) No code or test impact expected in R6 as an outcome of the proposed UCs | Nokia and Ericsson commit to: | N/A | AT&T Nokia Ericsson Orange | No development. Activity driven by Nokia and Ericsson is Use Case development. The UCs and modeling are done in synch. | ||
| 5G / Bulk PM / PM Control | REQ-129 - Getting issue details... STATUS | RANK #2 | GREEN SO impact clarified and agreed in SO weekly meeting. | YES | GREEN SO impact changed from C to TO. Instead added dependency to REQ-134 for SO PNF workflow enhancements. Also added REQ-25 as new dependency. Added AAI, CLAMP, Policy, SDNC and CCSDK as TO. | YES | YELLOW Main parts of use case delivered. A few user stories related to undeploying micro-service have been postponed. CLAMP cannot be used currently due to following bug that will not be fixed by M4 date: CLAMP-650 - Getting issue details... STATUS --- Mar 06 clarification: Proposing M4 with reduced scope rather than extension request:
| YES | GREEN | GO Track as #6 on Frankfurt Release Integration Testing Status | 5G Bulk PM in Frankfurt/R6 | REQ-25 REQ-33 REQ-134 | XL | DCAE: C Integration: C SO: TO AAI: TO CLAMP: TO Policy: TO SDNC: TO CCSDK: TO | All code and test committed by Ericsson for the listed projects. | Rajendra Jaiswal | Ericsson | DCAE: Committed based on Ericsson support | ||
| 5G / Bulk PM / Secure Communication between xNFs and ONAP | REQ-136 - Getting issue details... STATUS | Pawel Baniewski | RANK #2 | GREEN | YES | DESCOPED Currently marked yellow due to dependency to REQ-140. | 02/03 - Pawel recommends de-scoping | 5G Bulk PM in Frankfurt/R6 | AAF (REQ-140) | S | DCAE: C | DCAE: C Nokia Commits to DCAE: C Development | Nokia | DCAE: Committed based on Nokia support | ||||||
| 5G / PM dictionary | REQ-80 - Getting issue details... STATUS | RANK #2 | GREEN | YES | GREEN VES spec updated, reviewed and approved. Reconfiguration of SDC is in progress (JSON file change) | YES | GREEN | YES | GREEN No integration testing required for this requirement. Testing is only required at SC level | GO | FM META DATA & PM DICTIONARY in R6 Frankfurt | S | SDC: Update GAB Config File (no S/W update) DCAE: DOC DCAE: VES Event Reg Spec | SDC - C DCAE - C Nokia Commits to SDC, DCAE - C | Damian Nowak | AT&T Ericsson Nokia | DCAE: No code impact on VES reg yaml updates | |||
| 5G / 5G NRM Network Resource Model (Configuration Mgmt) | REQ-49 - Getting issue details... STATUS | yaoguang wang | RANK #3 | GREEN No commitment from SO lack of design, resource, etc Confirmation from yaoguang wang that the feature can be delivered even without SO. | YES | GREEN SO: requirements reviewed and approved. No additional API impacts. CDS: requirements approved. Parts of executor codes merged. | YES | GREEN | YES | GREEN | GO Track as #38 on Frankfurt Release Integration Testing Status | 5G Network Resource Model (NRM) Configuration in R6 Frankfurt | M | SO: C CDS: C Modeling: DOC Integration: C | SO: C CDS: C Modeling: P Integration: C Huawei commitment to SO, CDS, Integration | yaoguang wang | Huawei | |||
| 5G / 5G Service Modeling: Modeling (exploratory) work for creating a 5G Service | Modeling Work Only (No REQ) | RANK #0 ANSWER: It is just modeling in R6. AT&T and Nokia commits to working with Modeling S/C work. | NO CODE IMPACT | YES | GREEN | YES | GREEN | YES | GREEN | GO | 5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt | N/A | Modeling: C | Modeling: C | N/A (No integration or testing impact) | Nokia AT&T | Modeling work only | |||
| PNF / Plug and Play | REQ-134 - Getting issue details... STATUS | Benjamin Cheung | RANK #2 | GREEN Committed by SO PTL during the TSC call on 11/21 | YES | GREEN 02/03 - scope reduced by removing external cert work | YES | GREEN Mar 05 M4 on Reduced scope (see Wiki) | YES | YELLOW missing a release of SDNC component in version 1.8.1+ | GO Track as #5 on Frankfurt Release Integration Testing Status | PNF PLUG and PLAY in R6 Frankfurt | AAF (REQ-140) | M | DCAE: C SO: C VID: C | DCAE: C SO: C VID: C NOKIA Committed to DCAE, SO and VID Development | Nokia | DCAE: SDK Dmaap lib refactor; committed based on Nokia support 16.04: Currently released image for SO-BPMN (1.6.0 form27'th of March) is not working. Image from today 16.04 is sufficient and works. v2/onap/so/bpmn-infra/manifests/1.6.0-20200416T0645 | ||
| PNF / Configuration with NETCONF/ Secure Communication between xNFs and ONAP | REQ-76 - Getting issue details... STATUS | RANK #3 | GREEN | YES | GREEN | YES | YELLOW M4 Exception request: Full functionality postponed to RC0 due to late M2/M3 milestone achievement in relation to AAF issues. Exception discussed and agreed with SDNC and Integration PTLs. SO removed from test scope. | YES | YELLOW April 15 update: Updated integration item number April 9 update: OOM integration is still ongoing. Working with OOM experts and Nokia to finalize the contribution. See also RC0 update for REQ-140 (dependency). Mar 26 update: Estimating that one more week is needed to complete this feature. See SDNC-926 and REQ-140 for AAF dependency. Discussions with Integration and SDNC PTLs are ongoing. | GO Track as #43 on Frankfurt Release Integration Testing Status | Configuration with NETCONF in Frankfurt/R6 | Dependency on AAF (REQ-140) | M | SDNC: C Integration: C | SDNC: C Integration: C SDNC and Integration committed by Ericsson | Mariusz Sobucki | Ericsson | |||
| PNF / PNF pre-onboarding onboarding | REQ-135 - Getting issue details... STATUS | RANK #2 | GREEN | YES | GREEN | YES | GREEN Mar 05 Reduced scope. See Wiki | YES | YELLOW | GO Track as #8 on Frankfurt Release Integration Testing Status | PNF/VNF PREONBOARDING / ONBOARDING in R6 Frankfurt | S | VNFSDK: C Integration: TO | VNFSDK: C Integration: C Nokia Commits to VNFSDK and Integration - C | Nokia Ericsson | 16.04: New image has been released /onap/vnfsdk/refrepo:1.5.1
| ||||
| Modeling: Runtime instance model based on A&AI reverse engineering | Modeling Work Only REQ-170 - Getting issue details... STATUS | RANK #0 | NO CODE IMPACT | YES | GREEN | YES | GREEN | YES | GREEN | GO | Reverse-engineering AAI data model to Papyrus information model | AAI | S | AAI: No code changes, updating missing fields in schema AAI-2606 - Getting issue details... STATUS Modeling only. No new implementation requirements | AT&T commits to the bug fix | N/A, producing a model file only, not a use case | AT&T Ericsson Huawei Orange | |||
| Modeling: documentation of policy resource model | Modeling Work Only | Andy Mayer | RANK#0 | NO CODE IMPACT | YES | DESCOPEDPolicy resource model No-Go for Frankfurt R6. | Policy | M | Modeling only. No new implementation requirements | AT&T | ||||||||||
| Modeling: documentation of allotted resource model | Modeling Work Only | Andy Mayer | RANK #0 | NO CODE IMPACT | YES | GREEN | YES | GREEN | YES | GREEN | GO | SDC | M | Modeling only. No new implementation requirements | AT&T | |||||
| Scaling Extensions | REQ-42 - Getting issue details... STATUS | RANK #2 | GREEN | YES | GREEN | YES | GREEN | YES | GREEN | GO Track as #11 on Frankfurt Release Integration Testing Status | Scaling Use Case (Frankfurt) | APPC CCSDK/CDS SO | S-M | APPC - C CCSDK - TO SO - C | APPC - C CCSDK - C SO -C (Actor selection of CDS and APPC) APPC - Nokia Shanghai CCSDK - Tech Mahindra SO - Tech Mahindra | Marco Platania | AT&T Nokia/Shanghai Nokia/Poland Tech Mahindra Orange | |||
| APPC Ansible automation with VNF-C LCM support / CHM | REQ-191 - Getting issue details... STATUS | RANK #2 | GREEN | YES | GREEN | YES | GREEN | YES | GREEN | GO Track as #15 on Frankfurt Release Integration Testing Status | Change Management Frankfurt Extensions | APPC Integration | S | APPC: C Integration: C | APPC and Integration Commited by Orange | @Lukasz Rajewski | Orange AT&T | Implementation completed. Integration tests TBD on WindRivier lab jointly with REQ-187 - Getting issue details... STATUS | ||
| vFW Traffic Distribution with Software Upgrade / CHM | REQ-187 - Getting issue details... STATUS | RANK #2 | GREEN | YES | GREEN | YES | GREEN | YES | GREEN | GO Track as #15 on Frankfurt Release Integration Testing Status | Change Management Frankfurt Extensions | Integration | XS | Integration: C | Integration Commited by Orange | @Lukasz Rajewski | Orange AT&T | Implementation completed. Documentation still to be updated. Integration tests TBD on WindRivier lab jointly with REQ-191 - Getting issue details... STATUS | ||
| Portal Security Enhancements | REQ-64 - Getting issue details... STATUS | RANK #1 | YES | GREEN | YES | DE-SCOPED OJSI-190 waived. Portal team to publish vulnerability in Frankfurt release notes (PORTAL-863) | MUSIC | L | Policy: C VID: C SDC: C | Portal partially committed by AT&T, IBM SDC: C | Partially committed by Samsung (to support OJSI tickets) | Dominik Mizyn (for OJSI tickets) | AT&T Samsung IBM | |||||||
| Portal Technology Stack Upgrade and New reporting features | REQ-68 - Getting issue details... STATUS | Manoop Talasila | RANK #3 | YES | GREEN | YES | GREEN | YES | GREEN | GO Portal is ready with docker tag 3.2.0-STAGING-latest, however on-top of working to release the dockers as "3.2.0" final tag. | XL | Policy: C VID: C | Portal committed by AT&T, IBM | Partially committed by Samsung (to support Springboot upgrade on "portal" repo) Partially committed by IBM for test automation GAPS: No resources to support portal/sdk repo for Springboot upgrade. | Sireesh Chintamani (Overall Integration Lead) Sunder Tattavarada (for Angular upgrade) Dominik Mizyn (for Springboot upgrade on "portal" repo) Leimeng Shi (for reporting feature) | AT&T Samsung IBM | Implementation completed. Documentation still to be updated. Very close to release first version of docker images in staging to start the pairwise testing. | |||
| ETSI Alignment Support | REQ-101 - Getting issue details... STATUS | RANK #2 | GREEN SDC No more required | YES | GREEN | YES | GREEN | YES | GREEN | GO Track as #26 on Frankfurt Release Integration Testing Status | ETSI Alignment Support | XL | SO: C SOL003 Adapter: C SOL005 Adapter: C ETSI Catalog Mgr: C SOL002 Adapter: C | SO (C): committed by Ericsson and others with scale back scope ETSI Catalog Mgr (C): committed by CMCC SOL003 Adapter (C): committed by Ericsson with scale back scope SOL005 Adapter (C): committed by Verizon with scale back scope SOL002 Adapter (C): committed by Samsung with scale back scope | Andrew Fenner | Ericsson Verizon CMCC Samsung Intel | ||||
| Architecture - Modelling Alignment | REQ-110 - Getting issue details... STATUS | Stephen Terrill | TSC: Remove from the Frankfurt tracking. Ongoing discussions | L | SDC Modelling | |||||||||||||||
| Vertical Industry Oriented On-demand 5G Slice Service (this is merged with Network Slicing use case, and has become E2E Network Slicing) | REQ-146 - Getting issue details... STATUS | LIN MENG | TSC: This requirement is now merged with Network Slicing. No more individual tracking | Modeling, U-UI, SO, DCAE | NA | China Mobile, Tencent, Huawei | Merged with E2E Network Slicing use case | |||||||||||||
E2E Network Slicing There are two parts:
The above is a clarification consistent with previous archcom decisions, but detailing it more and is considered architecturally consistent given the scope (NSSMF outside ONAP). The following is not approved:
| RANK #3 TSC:
This should limit the impacts to SO and External API for Frankfurt | GREEN Based on revisited scope i.e. SO and ExtAPI, OOF and UUI ---------------- Lin Meng's comment (21st Nov): a) 15th &18th Nov: LinMeng's Mail sent to TSC explaining the "exception". b) 19th Nov: Steve's clarification of Arc decision in the first column. c) 20th Nov: Swami's Mail sent to TSC requesting OOF and UUI inclusion in scope (resource commitments and PTL agreements available) d) 21st Nov: LinMeng updated the columns for impacted modules, commitments based on the request sent to TSC , for TSC reference when in discussion Please help change the status to Green | YES considering #1 SO, ExtAPI UUI scope only #2 NSSMF is outside ONAP #3 OOF is exceptionally added and will be reviewed at M2 -------------------- Lin Meng (21st Nov) Confirmation: 1)Yes, we can deliver this feature for Frankfurt even without ExtAPI. 2) The impact in EXT-API for Frankfurt is only minimal impact, the resource has been identified and will be commited. Please help change the status to YES | GREEN (See Notes) | YES | GREEN (See Notes) | YES | GREEN Integration test is in progress. | GO Track as #10 on Frankfurt Release Integration Testing Status | E2E Network Slicing Use Case in R6 Frankfurt | SDC | XL | SO : C EXT-API : C POLICY : TO SDC : TO A&AI : TO U-UI : C OOF : C LinMeng updated on 21st Nov based on the request sent to TSC for including U-UI and OOF into scope, for TSC reference when in discussion | EXT-API : C (Huawei, Wipro) SO : C (Wipro, China Mobile, Huawei) POLICY : C (Wipro) SDC: C (China Mobile, Amdocs) A&AI : C (Huawei, Amdocs) U-UI : C (China Mobile) OOF : C (AT&T, Wipro) LinMeng updated on 21st Nov: Reply to TSC Concern: 1)Yes, we can deliver this feature for Frankfurt even without ExtAPI. 2) The impact in EXT-API for Frankfurt is only minimal impact, the resource has been identified and will be committed. | Wipro, Amdocs, China Mobile, Huawei, Tencent, AT&T, Verizon | Mar 4th, 2020:
Jan 15, 2020: SO, EXT-API, UUI and OOF are on track for the agreed scope, with respect to all aspects - APIs, functionality implementation, as well as resource commitments. | ||||
| Remove Python2 dependencies | REQ-174 - Getting issue details... STATUS | David McBride | RANK #1 | GREEN See feedbeck from PTL on the wiki except Stretch goals for SDC, VNFSDK to complete all in R6. Logging not committed for R6. | YES | Exceptions:
| YES | YELLOW All projects committed for the Frankfurt are OK except SDC and Multicloud Azure | YES | YELLOW All projects committed for the Frankfurt are OK except SDC and Multicloud Azure | GO | M | ALL projects using Python | |||||||
| K8s CDS Support | REQ-182 - Getting issue details... STATUS | RANK #3 | GREEN MultiCloud commitment confirmed | YES | GREEN | YES | GREEN | YES | GREEN | GO Track as #20 on Frankfurt Release Integration Testing Status | S-M | MULTICLOUD: C CDS: C Integration: C SO: TO SDC: TO | CDS commited by Orange and Samsung MULTICLOUD commited by Samsung, Orange and Intel Integration commited by Samsung, Orange and Intel | Orange Samsung Intel | Implementation inside ONAP components completed. Documentation and demonstration scripts still must be improved. First tests completed on integration lab of Samsung | |||||
| K8s HPA Support | REQ-183 - Getting issue details... STATUS | RANK #3 | GREEN | YES | GREEN | YES | DESCOPED Move to R7 | Multicloud K8s REQ-162 - Getting issue details... STATUS | S | MULTICLOUD: C OOF:TO Policy:TO AAI/ESR:TO SO: TO SDC: TO | Intel commits to coding in Multicloud and testing in OOF, Policy, AAI, SO, SDC | Intel | Moving this to POC - may not be done by R6 timeframe. | |||||||
| K8s Security and traffic controller | REQ-171 - Getting issue details... STATUS | RANK #3 | GREEN commitment from MultiCloud confirmed | YES | GREEN | YES | DESCOPED | Multicloud K8s | S - M | MULTICLOUD: C | Intel commits to coding/testing in Multicloud | Intel | ||||||||
| VSP Compliance and Validation Check within SDC - Phase 2 | REQ-203 - Getting issue details... STATUS | RANK #2 | GREEN | YES | GREEN | YES | GREEN | YES | GREEN | GO Track as #19 on Frankfurt Release Integration Testing Status | VSP Compliance and Validation Check within SDC | SDC: C | ([Prabhu]: SDC PTL reviewed the design and Vodafone already committed the code in SDC and code review is in progress) | Prabhu Balan | Vodafone | |||||
| OVP Testing and Certification Support Within SDC | REQ-208 - Getting issue details... STATUS | RANK #3 | GREEN | YES | DESCOPED the feature cannot be delivered in Frankfurt because of lack of resources in 2020 to complete integration testing | OVP Testing and Certification Support Within SDC (Frankfurt) | SDC - C VTP - C | SDC-iconectiv VTP-iconectiv | iconectiv | |||||||||||
| SECCOM Code coverage | REQ-207 - Getting issue details... STATUS | RANK #3 | GREEN See feedbeck from PTL on the wiki | YES | GREENWaiting for a feedback from PTLs - Jira tickets were opened to all projects. Preliminary feedback is on track. | Track | GREEN 131/155 repos above 50% code coverage. Discrepancies in coverage between Sonar and SonarCloud. Expect coverage to improve by RC0. | YES due to agreement that this req to be completed by RC0 | GREEN Projects with waivers
| GO | All projects | |||||||||
| SECCOM Containers configured per secure recommendation | REQ-215 - Getting issue details... STATUS | RANK #3 | GREEN | YES | GREENContinuing to follow up with PTLs. Will be gated by health check. Recommend approval. | Track | YELLOW Following up with PTLs. Some questions about the requirements in Chap.5 of the CIS Docker Benchmarks. | YES | GREEN | GO | All projects using containers | |||||||||
| SECCOM Java 11 migration from v8 | REQ-219 - Getting issue details... STATUS | RANK #3 | GREEN See feedbeck from PTL on the wiki. | YES | YELLOWWaiting for a feedback from some PTLs - Jira tickets were opened to all projects. Preliminary feedback is on track. | See REQ-219 for project status Discuss on PTL call | YELLOW Although majority of project plans to upgrade java in Guilin release, some of them already migrated in Frankfurt. | YES | GREEN Although majority of project plans to upgrade java in Guilin release, some of them already migrated in Frankfurt. | GO | All projects using java | |||||||||
| SECCOM CII badging – meet targeted Silver and Gold requirements | REQ-223 - Getting issue details... STATUS | RANK #3 | GREEN | YES | RED There has been no movement by the projects on the CII requirements for Frankfurt. | Discuss on PTL call | YELLOW | YES | DE-SCOPED Some projects have moved their CII answers to "Met" for the CII questions being focused on. More have indicated that they will do so in Guilin. | De-scoped by TSC on 5/28/20 Create new req for Guilin Deferred to RC2 Documentation only. No dependencies. Descoping requirement Frankfurt and moving to Guilin based on new SECCOM work effort. | All projects | |||||||||
| SECCOM Complete the OJSI backlog | REQ-227 - Getting issue details... STATUS | RANK #3 | GREEN excluding Logging Logging has open OJSI tickets but has been descoped from the release. Some of the tickets may not be closed easily but most of the most severe tickets is being worked on. | YES | YELLOW Not all of the tickets can be easily resolved due to AAF integration issues (i.e. in SO) but apart from that most of severe ticketes should be resolved till end of the release | YES | YELLOW Not all projects completed their OJSI backlog yet. All the details can be found in the Jira ticket (see open tickets that are blocking this requirement) See notes in March 12 TSC meeting agenda on compromise | YES | GREEN All OJSI tickets apart from 3 has been completed. SECCOM recommends to grant a waiver for 3 left OJSI tickets | GO | All relevant projects having an entry in OJSI | |||||||||
| SECCOM HTTPS communication vs. HTTP | REQ-231 - Getting issue details... STATUS | RANK #1 | GREEN except for Music (partial) and Holmes/Logging - no part of the release. See feedbeck from PTL on the wiki. | YES | GREEN Some projects tends to have issues with AAF integration to provide certificate but seems to be doable if issues in AAF are resolved | YES | YELLOW 17 HTTP ports still open. Detailed list can be provided by Morgan Richomme as he has the results that are updated every day | YES | YELLOW Only 30476 | Recommend approval | All relevant projects still using http communication instead of https | |||||||||
| SECCOM Password removal from OOM HELM charts | REQ-235 - Getting issue details... STATUS | RANK #1 | GREEN | YES | YELLOWThe amount of work is increasing as we discovered encrypted passwords and other cases where change in the components is required and we don't have the competency to make all of them (java script). We ask for help in some of the projects (only on the code part, OOM changes can be done on time) | YES | YELLOW Scope limited to mariadb-galera and components using mariadb-galera common chart or common instance. Most components ready/in-review components left: so - WIP policy - WIP CDS - merged | YES | GREEN All related patches merged. No more "secretpassword" for mariadb-galera. | GO | All relevant projects | |||||||||
| SECCOM Communication Matrix | REQ-239 - Getting issue details... STATUS | RANK #3 | GREEN DCAE will be the 'prototype' project/pilot with this release. Lesson Learnt will be shared to other projects. | YES - DCAE only | GREEN AS agreed first focus on external communication. | YES | GREEN Data collection for an external communication with scripts and support from DCAE. We propose to close it for Frankfurt with a note to continue the work in Guilin release. | YES | YELLOW | GO | All relevant projects | |||||||||
| SECCOM Containers and Kubernetes secure configuration recommendation | REQ-243 - Getting issue details... STATUS | RANK #3 | GREEN | YES | GREENWaiting for feedback from the Integration team | YES | GREEN Waiting for Integration team blocking K8S test results. | YES | GREEN | GO | All projects | |||||||||
| SECCOM Coverity integration by end of Frankfurt | REQ-247 - Getting issue details... STATUS | RANK #3 | GREEN | YES | DESCOPED Waiting for an update from fd.io on their experience as Artem is not available for this task. | Move to Guilin release. | All projects using containers | |||||||||||||
| SECCOM Ingress controller | REQ-251 - Getting issue details... STATUS | RANK #3 | GREEN | YES | GREEN Ingress is already configured for most of the components. Not all may be working properli (UI) but they all will be available through ingress | YES | GREEN All components accessible through ingress (nginx). | YES | GREEN | GO | All projects | |||||||||
| SECCOM Secure communication for 5G – AAF contribution – CMPv2 protocol trial usage | REQ-259 - Getting issue details... STATUS | Hampus Tjäder | RANK #3 | Please remove this requirement, it is a duplicate of REQ-140 - Getting issue details... STATUS | Need to understand why it is yellow | AAF + TBC | ||||||||||||||
| SECCOM Perform Software Composition Analysis - Vulnerability tables | REQ-263 - Getting issue details... STATUS | RANK #1 | GREEN except for Holmes/CLI and Logging - not part of R6 release See feedbeck from PTL on the wiki. | YES | DESCOPEWaiting for a feedback from PTLs. Script to automatically generate tickets is working. | OBE - de-scope | All projects | |||||||||||||
| Document current upgrade component strategy | David McBride | RANK #1 | YES | GREEN | YES | YELLOW This item should be completed by RC2. The following projects have not yet started this activity: APPC, CLAMP, Portal, Music, SO, VNFSDK, SDC | YES | DE-SCOPED | De-scoped by TSC on 5/28/20 Will be done by contractor during 2H20 GO |
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
- XS - <4 Man/Weeks;
- S - ~6 Man/Weeks;
- M - ~8 Man/Weeks;
- L - ~12 Man/Weeks;
- XL - > 12 Man/Weeks.
POC / Experimentation
SECCOM ISTIO POC – limited ONAP deployment scope
| Type | Requirement | Owner | Link(s) to HLD/LLD if any | Dependency (from/to) another project(s) | T-Shirt Size (XS, S, M, L, XL) | Project's Impact: Test Only (TO), Code (C) | Company Engagement | Notes | M4 Status | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| POC | SECCOM ISTIO POC – limited ONAP deployment scope | REQ-255 - Getting issue details... STATUS | ||||||||||||
| POC | Acumos - DCAE Integration | REQ-166 - Getting issue details... STATUS | GREEN | M | DCAE - C | AT&T Orange (Integration/UC support) | Met withEric Debeau/Orange team on 10/25 and they commited to support. | GREEN | ||||||
| POC | Self Service Control Loops | REQ-9 - Getting issue details... STATUS | XL | CLAMP - C DCAE - C Policy - C | AT&T | GREEN | ||||||||
| POC | Multicloud K8s Support (Continuation from R4) | REQ-178 - Getting issue details... STATUS |
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
- XS - <4 Man/Weeks;
- S - ~6 Man/Weeks;
- M - ~8 Man/Weeks;
- L - ~12 Man/Weeks;
- XL - > 12 Man/Weeks.