The page is intended to summarize all the requirements for Frankfurt Release.
These requirements will be prioritized by the TSC to realistically fit within the Frankfurt Release Timeline.
The Release Scope should be finalized during the M1 Release Planning milestone at the xxx.
TSC Prioritization (Ranking)
- RANK #0 – Special GO - fully covered by involved companies
- RANK #1 – GO “Must Have”
- RANK #2 - GO “Continuity of previous releases”
- RANK #3 – GO if PTLs are OK since the impacted applications are less “stretched”
- RANK #4 – NO GO – Mostly new requirements/features/projects
Requirements Milestones Summary
See also Documenting Release Requirements in JIRA
Epic Link | Fix For Versions (all) | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
Frankfurt Release | Guilin Release | Honolulu Release | Istanbul Release | Jakarta Release | Kohn Release | London Release | Montreal Release | New Delhi Release | Istanbul Maintenance Release 1 | Unscheduled | T: | |
5G / OOF SON Enhancement | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 |
5G / ORAN & 3GPP Standards Harmonization | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 |
5G OOF SON use case requirements for Guilin release | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 |
5G Service Modeling in R8 | 0 | 0 | 15 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 17 |
5G SON use case enhancements for Istanbul release | 0 | 0 | 0 | 13 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 13 |
5G SON use case enhancements for Jakarta release | 0 | 0 | 0 | 0 | 14 | 0 | 0 | 0 | 0 | 0 | 0 | 14 |
5G SON use case enhancements for Kohn release | 0 | 0 | 0 | 0 | 0 | 14 | 0 | 0 | 0 | 0 | 0 | 14 |
5G SON use case enhancements for London release | 0 | 0 | 0 | 0 | 0 | 0 | 14 | 0 | 0 | 0 | 2 | 16 |
5G SON Usecase R8 | 0 | 0 | 16 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 18 |
A1 Adapter Extension & A1 Policy Management | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 |
A1 Policy Functions Extension - Istanbul | 0 | 0 | 0 | 12 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 12 |
A1 Policy Functions Extension - Jakarta | 0 | 0 | 0 | 0 | 12 | 0 | 0 | 0 | 0 | 0 | 0 | 12 |
A1 Policy Functions Extension - Kohn | 0 | 0 | 1 | 1 | 1 | 13 | 0 | 0 | 0 | 1 | 0 | 13 |
A1 Policy Functions Extension - London | 0 | 0 | 0 | 0 | 0 | 0 | 13 | 0 | 0 | 0 | 0 | 13 |
Add VSP Compliance and Verification Check feature Phase 2 | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 |
Akraino Distributed Analytics use case | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 |
All Control Loop Policy Models should be TOSCA Compliant | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 |
APPC Ansible automation with VNF-C LCM support | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 |
Architecture - modelling alignment | 7 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 7 |
ASD onboarding package IM / DM | 0 | 0 | 0 | 0 | 12 | 0 | 0 | 0 | 0 | 0 | 0 | 12 |
Bulk PM / PM Data Control Extension | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 |
Bulk PM / PM Data Control Improvements | 0 | 0 | 11 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 11 |
Bulk PM / PM Data Control Improvements | 0 | 0 | 0 | 12 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 12 |
Bulk PM / PM Data Control Improvements | 0 | 0 | 0 | 0 | 13 | 0 | 0 | 0 | 0 | 0 | 0 | 13 |
CCVPN-E-LINE Service over OTN NNI | 3 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 |
Total Unique Issues: | 196 | 22 | 248 | 184 | 189 | 107 | 187 | 1 | 1 | 1 | 84 | 1216 |
Use Cases
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.
Architecture:
- Pink - NO GO
- Purple - GO
- Green - Considered OK not requiring architecture review
- Black - Architecture not yet performed
Use Case | JIRA link (REQ) One issue per requirement. | Owner(s) | Priority | M1 Scorecard | TSC M1 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 gaps/ project (people/FTEs; HLD/LLD; etc) | Integration Lead | Company Engagement | Notes |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Third Party Operational Domain Manager | TSC: ALL Info provided. GO to be part of the TSC prioritization | Third-party Operational Domain Manager | S | SDC (C) SO (TO) AAI (TO) | Changes being done in local setup [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 | rene.robert@orange.com | TSC: NO GO From Archi. Next Step? | Service Resolver | SDC (C), SO (C), AAI (TO) | No SO decision | MISSING INFO | MISSING INFO | Orange | ||||||
CMPv2 CA Plugin for AAF | TSC: ALL Info provided. GO to be part of the TSC prioritization | 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-140Getting 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 | LIN MENG | TSC: ALL Info provided. GO to be part of the TSC prioritization | 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 | TSC: ALL Info provided. GO to be part of the TSC prioritization | Multi-domain Optical Network Services | CCVPN use-case alignment | XL (Multiple releases) | TO: SDC, ExtAPI C: UUI, SO, A&AI, SDN-C | SO - C A&AI - C SDN-C - C UUI - C SDC - TO ExtAPI - TO TSC: Which company will develop this? Code will be committed by Fujitsu | Have gained PTL agreement & JIRA epics have been created under SO, SDNC, A&AI | Xin Miao | AT&T Orange Fujitsu | Working with CCVPN team to align towards common modelling for OTN | ||||
Deploying Distributed External functions Stephen Terrill, as per the discussion on Architecture subcommittee review, I have changed the name of use case. I think there is no other feedback pending. If so, I request you to change the color to GO color (green). | TSC: NO GO From Archi. Next Step? Has it been discussed with the PTL? | 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 |
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.
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 | Priority | M1 Scorecard | TSC M1 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 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Self Serve Control Loops | TSC: ALL Info provided. GO to be part of the TSC prioritization | Self Serve Control Loops v2 | CLAMP | XL | CLAMP - C DCAE - C POLICY - C | CLAMP - C DCAE - C POLICY - C committed by AT&T | AT&T Ericsson | |||||||
All Control Loop Policy Models should be TOSCA Compliant Operational, Guard Policies | TSC: ALL Info provided. GO to be part of the TSC prioritization | 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 | TSC: ALL Info provided. GO to be part of the TSC prioritization | 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 | TSC: ALL Info provided. GO to be part of the TSC prioritization | 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 | TSC: ALL Info provided. GO to be part of the TSC prioritization | CDS actor support in Policy | 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 | TSC: See red cell | CLAMP, DCAE, POLICY | M | Documentation - DO Integration - TO | DOC - C POLICY - C DCAE - C CLAMP - C TSC: Which companies will cover this - per component? | Morgan Richomme | Bell Canada, AT&T, Orange | |||||||
Component Upgrades to new Policy Lifecycle API | TSC: GO to be part of the TSC prioritization for Policy, OOF ------------ What's the side effect if no company will develop SDNC, SO? Can still use legacy API - but those components will be removed in the G Release. So they must upgrade in the G-release. | M | SO - C SDNC - C OOF - C POLICY - C | POLICY - C (AT&T & Intel) OOF - C (Intel) Need commitments from SDNC and SO | AT&T, Intel | |||||||||
Modeling: Enhanced Nested and Shared Service Information Model - 5G / E2E Network Slicing modeling | TSC: ALL Info provided. Waiting feedback from the Architecture Team No commitment to cover ExtAPI | NETWORK SLICING PoC in R6 Frankfurt (Obsolete) | 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 | TSC: GO to be part of the TSC prioritization based on the assumptions that PTLs too are commmitting | OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt | L | POLICY - C OOF - C DCAE - C SDN-C - C Runtime DB - C Integration (Demo VNFs) - C | POLICY - C OOF - C DCAE - C SDN-C - C Runtime DB - C Integration (Demo VNFs) - C Policy, DCAE, Integration - Wipro commits OOF, Policy - AT&T commits SDN-C, Runtime DB - IBM commits | AT&T Wipro IBM | RAN-Simulator will be submitted as part of Demo VNFs repository | |||||||
5G / Run-time Data Persistency (RunTime Config DB) and VES Model relations, VES CM model (CM Notify). | TSC: GO to be part of the TSC prioritization based on the assumptions that PTLs too are commmitting | 5G CONFIGURATION (RunTime DB) | 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 | TSC: No development? Company Commitment or is it a Modeling subcommittee activity? Reqs posted after the deadline | 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 | TSC: See red cell. => Requested information about company commitment has been added (REMOVED RED from Commitment cell as discussed in 5G U/C S/C call - company commitment per component have been added) | 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 Schema Update once PNF software is updated | TSC: See red cell. => Requested information about company commitment has been added (REMOVED RED from Commitment cell as discussed in 5G U/C S/C call - company commitment per component have been added) | PNF software upgrade in R6 Frankfurt | M | SDC: C Integration: C VNFRQTS: DO | SDC: C Integration: C SDC, Integration and VNFRQTS are committed by Ericsson | Ericsson | ||||||||
LCM API Evolution | TSC: No development? Shall we merge with REQ-84? => No development in this REQ, ok to merge with REQ-84 if preferred | 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 | TSC: See red cell. (REMOVED RED from Commitment cell as discussed in 5G U/C S/C call - company commitment per component have been added) | 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 | yaoguang wang | TSC: See red cell. (REMOVED RED from Commitment cell as discussed in 5G U/C S/C call - company commitment per component have been added) | PNF software upgrade in R6 Frankfurt | 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 | |||||
Modeling: 5G / ORAN & 3GPP Standards Harmonization | TSC: See red cell. (REMOVED RED from Commitment cell since commitment per component have been added) | 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. | ||||||
5G / License Management | TSC: No development? Company Commitment or is it a Modeling subcommittee activity? 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. | 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 | TSC: See red cell. => Requested information about company commitment has been added. (REMOVED RED from Commitment cell as discussed in 5G U/C S/C call - company commitment per component have been added) | 5G Bulk PM in Frankfurt/R6 | CLAMP/Policy/CDS (REQ-33) | XL | SO: C DCAE: C Integration: C | SO: C DCAE: C Integration: C SO, DCAE and Integration committed by Ericsson | user-3784d | Ericsson | DCAE: Committed based on Ericsson support | |||||
5G / Bulk PM / Secure Communication between xNFs and ONAP | Pawel Baniewski | TSC: See red cell. (REMOVED RED from Commitment cell as discussed in 5G U/C S/C call - company commitment per component have been added) | 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 | TSC: See red cell. (REMOVED RED from Commitment cell as discussed in 5G U/C S/C call - company commitment per component have been added) | 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) | yaoguang wang | TSC: See red cell. (REMOVED RED from Commitment cell as discussed in 5G U/C S/C call - company commitment per component have been added) | 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) | TSC: No development? Company Commitment or is it a Modeling subcommittee activity? ANSWER: It is just modeling in R6. AT&T and Nokia commits to working with Modeling S/C work. | 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 | Benjamin Cheung | TSC: See red cell. (REMOVED RED from Commitment cell as discussed in 5G U/C S/C call - company commitment per component have been added) | 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 | |||||
PNF / Configuration with NETCONF/ Secure Communication between xNFs and ONAP | TSC: See red cell. => Requested information about company commitment has been added (REMOVED RED from Commitment cell as discussed in 5G U/C S/C call - company commitment per component have been added) | Configuration with NETCONF in Frankfurt/R6 | 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 | TSC: See red cell. (REMOVED RED from Commitment cell as discussed in 5G U/C S/C call - company commitment per component have been added) | 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 | Integration will only be for VNF-SDK work, there is not full E2E POB/OB integration in R6. | |||||||
Modeling: Runtime instance model based on A&AI reverse engineering | TSC: See red cells | Reverse-engineering AAI data model to Papyrus information model | AAI | S | 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 and allotted resource model | Modeling Work Only | Kevin Scaggs | TSC: No development? Company Commitment or is it a Modeling subcommittee activity? | Policy SDC | M | Modeling only. No new implementation requirements | AT&T | |||||||
Scaling Extensions | TSC: See red cell. | Scaling Use Case (Frankfurt) | APPC CCSDK/CDS SO | S-M | APPC - C CCSDK - TO SO - M | APPC - C CCSDK - C SO -M (Actor selection of CDS and APPC) Company commitment per component | Marco Platania | AT&T Nokia/Shanghai Nokia/Poland Tech Mahindra Orange | ||||||
APPC Ansible automation with VNF-C LCM support / CHM | TSC: ALL Info provided. GO to be part of the TSC prioritization | Change Management Frankfurt Extensions | APPC Integration | S | APPC: C Integration: C | APPC and Integration Commited by Orange | @Lukasz Rajewski | Orange AT&T | ||||||
vFW Traffic Distribution with Software Upgrade / CHM | TSC: ALL Info provided. GO to be part of the TSC prioritization | Change Management Frankfurt Extensions | Integration | XS | Integration: C | Integration Commited by Orange | @Lukasz Rajewski | Orange AT&T | ||||||
Portal Security Enhancements | Manoop Talasila | TSC: If partially committed - then please provide what will be the committed deliverables.? | MUSIC | L | Policy: C VID: C SDC: C | Portal partially committed by AT&T, IBM | 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 | Manoop Talasila | TSC: if no resource to support portal/sdk is it still viable? | XL | Policy: C VID: C SDC: 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 | ||||||
ETSI Alignment Support | TSC: If partially committed - then please provide what will be the committed deliverables.? | ETSI Alignment Support | XL | SDC: C SO: C VFC/ETSI Catalog: C Integration: C OOF: C | SDC (P) SO (C) VFC/ETSI Catalog (C) Integration (C) OOF (P) Company commitment per component | GAPs: OOF enhancement is requested for resource-level Homing. If not, there is a workaround. SDC is looking for resources | Andrew Fenner | Ericsson Verizon CMCC Samsung | ||||||
Architecture - Modelling Alignment | Stephen Terrill | TSC: No development? Company Commitment or is it a Modeling subcommittee activity? | 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) | LIN MENG | TSC: NO GO From Archi. Next Step? Swami (Oct 24): This use case has been merged to form the E2E Network Slicing use case | Modeling, U-UI, SO, DCAE | NA | China Mobile, Tencent, Huawei | Merged with E2E Network Slicing use case | ||||||||
E2E Network Slicing | TSC: NO GO From Archi. Next Step? Swami (Oct 24): Presented to ArchCom on Aug 22. In principle OK except for NSSMF architectural alignment with ONAP. However, this is not blocking as we can realize scenarios with external NSSMF for Frankfurt in the worst case. | E2E Network Slicing Use Case in R6 Frankfurt | SDC | XL | SDC - C SO - C OOF - C SDN-C - C UUI - C DCAE - C POLICY - TO AAI - C EXT-API - C VF-C - C Runtime DB - C (Stretch goals: EXT-API, VF-C, Runtime DB - to be checked and confirmed for impacts & commitments for Frankfurt) | (Commitments per component indicated in brackets) SDC, Modeling - C (Amdocs) SO - C (Wipro, China Mobile, Huawei) OOF - C (Wipro, China Mobile, Huawei) SDN-C - C (Wipro) UUI - C (China Mobile, Huawei) DCAE - C (China Mobile, Huawei) Policy - C (Wipro) AAI - C (Amdocs, Huawei) (Stretch goal) EXT-API -N (Stretch Goal) VF-C - C (Wipro) (Stretch Goal) Runtime DB - N (Stretch Goal) | Runtime DB, VF-C EXT-API and AAI are stretch goals. We will discuss with resp. PTLs on possible options, anyhow they are not blocking scope of this use case for Frankfurt. | Wipro, AT&T, Amdocs, China Mobile, Huawei, Tencent, ZTE | DCAE: Review pending; cannot be committed for Frankfurt as of 10/23 For EXT-API and Runtime DB, to check with the respective PTLs for possible resource commitments, accordingly will take a final call (not blocking for Frankfurt though) | |||||
Remove Python2 dependencies | David McBride | 1- NEED Company to commit - MUST HAVE | M | ALL projects using Python | ||||||||||
Multicloud K8s Support (Continuation from R4) | See red cells - Updated Company commitment per component | K8S based Cloud region support (Continue from R4) | Multi-Cloud : C | Code Multi-Cloud : Intel Testing of SO, Multicloud, SDC: Intel Catherine Lefèvre, Added information as requested. If it is fine with you, then i request you to change the color of this box | vFirewall: EdgeXFoundry Akraino ICN Distributed Analytics Catherine Lefèvre, Added information as requested. If it is fine with you, then i request you to change the color of this box | Intel Aarna Tech Mahindra | ||||||||
K8s CDS Support | TSC: ALL Info provided. GO to be part of the TSC prioritization | 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 | |||||||||
K8s HPA Support | TSC: ALL Info provided. GO to be part of the TSC prioritization | 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 | Marcus Williams | Intel | ||||||||
K8s Security and traffic controller | See red cells - Updated Company commitment per component | Multicloud K8s | S - M | MULTICLOUD: C | Intel commits to coding/testing in Multicloud Catherine Lefèvre, Added information as requested. If it is fine with you, then i request you to change the color of this box | Catherine Lefèvre, Added information as requested. If it is fine with you, then i request you to change the color of this box | Intel | |||||||
VSP Compliance and Validation Check within SDC - Phase 2 | See red cells Requirements introduced after Sept 27th [Prabhu]: Enriches flow already exists from Dublin. This is extended feature for Frankfurt | VSP Compliance and Validation Check within SDC | SDC: C | Company commitment per component ([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 | See red cells (susan: updated the red cells) Requirements introduced after Sept 27th (susan: project leads are reviewing) | OVP Testing and Certification Support Within SDC (Frankfurt) | SDC - C VTP - C | SDC-iconectiv VTP-iconectiv | Vodafone iconectiv | |||||||||
SECCOM Code coverage – increase to 60% | Feasibility to be reviewed Some teams got a waiver from previous release | All projects | ||||||||||||
SECCOM Containers configured per secure recommendation | Candidate for TSC MUST HAVE | All projects using containers | ||||||||||||
SECCOM Java 11 and 13 migration from v8 | Feasibility to be reviewed | All projects using java | ||||||||||||
SECCOM CII badging – meet targeted Silver and Gold requirements | Feasibility to be reviewed | All projects | ||||||||||||
SECCOM Complete the OJSI backlog | Feasibility to be reviewed | All relevant projects having an entry in OJSI | ||||||||||||
SECCOM HTTPS communication vs. HTTP | Candidate for TSC MUST HAVE | All relevant projects still using http communication instead of https | ||||||||||||
SECCOM Password removal from OOM HELM charts | Candidate for TSC MUST HAVE | All relevant projects | ||||||||||||
SECCOM Communication Matrix | Feasibility to be reviewed | All relevant projects | ||||||||||||
SECCOM Containers and Kubernetes secure configuration recommendation | Feasibility to be reviewed | All projects | ||||||||||||
SECCOM Coverity integration by end of Frankfurt | Feasibility to be reviewed with LF IT | All projects using containers | ||||||||||||
SECCOM Ingress controller | Feasibility to be reviewed | All projects | ||||||||||||
SECCOM ISTIO POC – limited ONAP deployment scope | Shall we move this req to POC? | All projects | ||||||||||||
SECCOM Secure communication for 5G – AAF contribution – CMPv2 protocol trial usage | Hampus Tjäder | What's the difference with the Use Case. Shall we only consider this req => The use case (REQ-140) is the primary requirement. This requirement can be considered as duplicate. | AAF + TBC | |||||||||||
SECCOM Perform Software Composition Analysis - Vulnerability tables | Candidate for TSC MUST HAVE | All projects |
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
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 | Acumos - DCAE Integration | M | DCAE - C | AT&T |
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.