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
Use Case | JIRA link (REQ) One issue per requirement. | Owner(s) | Projects or functional requirements impacted for this release | 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 | SDC | TSC: Missing information (see red and blue cells) Atif - updated the missing information in red and blue cells | 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 | SDC, SO, Policy | 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 | AAF Integration | 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 | A&AI, SDN-C, OOF, U-UI, SO | TSC: All Info provided. Has it been reviewed by the impacted PTLs? | 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 | SDC, SO, AAI SDN-C, Modeling, UUI | TSC:See red cells Need commitments from company/PTL | 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? | Reviewing with PTLs | Xin Miao | AT&T Orange Fujitsu | Working with CCVPN team to align towards common modelling for OTN | ||||
Distributed Analytics use case on K8S regions | Multi-Cloud | See Red cells Still Arch | Depends on development progress of Multi-Cloud K8S work. | XL (Multiple releases) | TO | C TSC: Which company will develop this? Has it been reviewed with PTL? | MISSING INFORMATION | 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 requireing architecture review
Requirement | JIRA link (REQ) One issue per requirement. | Owner | Project Impacted | 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 | CLAMP DCAE POLICY | 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 | |||||||
All Control Loop Policy Models should be TOSCA Compliant Operational, Guard Policies | CLAMP POLICY | 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 | DCAE POLICY | 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 | CLAMP POLICY | 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 | ||||||||
Integration of CDS as Actor in Control Loops | CLAMP POLICY CDS | TSC: ALL Info provided. GO to be part of the TSC prioritizationa | 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 | DOC Integration | 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 | SO SDNC OOF POLICY | TSC: See red cell. What's the side effect if no company will develop SDNC, SO? | M | SO - C SDNC - C OOF - C POLICY - C | POLICY - C OOF - C Need commitments from SDNC and SO TSC: Which companies will cover this - per component? | AT&T, Intel | |||||||||
Modeling: Enhanced Nested and Shared Service Information Model - 5G / E2E Network Slicing modeling | SDC SO OOF AAI Modeling | TSC: See red cell. | NETWORK SLICING in R6 Frankfurt | L | SDC-C AAI-C External API | Company commitment per component | MISSING INFORMATION | CMCC Amdocs AT&T Wiprc Huawei | |||||||
5G / OOF SON Enhancement | DCAE Policy Controller OOF Runtime DB | TSC: See red cell. | 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 Company commitment per component | Swaminathan Seetharaman | Wipro AT&T | RAN-Simulator will be submitted as part of Demo VNFs repository DCAE: Son-handler update; committed based on Wipro support | ||||||
5G / Run-time data persistency (RunTime DB / CM): VES Model relations, VES CM model (CM Notify). | A&AI Controller SDC RunTime DB (new component) DCAE | TSC: See red cell. | 5G CONFIGURATION (RunTime DB) | 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 Company commitment per component | Sandeep Shah | Nokia AT&T | Will be a new component, presented at Architecture S/C. | ||||||
Modeling: GeoLocation Model (and standards harmonization) | Modeling work only | Modeling | TSC: No development? Company Commitment or is it a Modeling subcommittee activity? | 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 | SDC VID SO CDS VNFRQTS Integration Modeling | TSC: See red cell. | 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) committed by Ericsson & Huawei (SO) | Ericsson Huawei | ||||||||
PNF / Enable Schema Update once PNF software is updated | Modeling SDC Integration VNFRQTS | TSC: See red cell. | PNF software upgrade in R6 Frankfurt | M | SDC: C Integration: C VNFRQTS: DO | SDC: C Integration: C committed by Ericsson | Ericsson | ||||||||
LCM API Evolution | Development in R6 will be part of REQ-84 | 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 | SO SDNC Integration | TSC: See red cell. | PNF software upgrade in R6 Frankfurt | LCM API Evolution | M | SO: C SDNC: C Integration:C | SO: C SDNC: C Integration:C Company commitment per component | Huawei | |||||||
PNF / PNF Software Upgrade with EM with Netconf | yaoguang wang | SO CDS Integration | TSC: See red cell. | 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 Company commitment per component | Enbo Wang | Huawei | |||||
Modeling: 5G / ORAN & 3GPP Standards Harmonization | Modeling SDN-C DCEA | TSC: See red cell. | MOBILITY STANDARDS HARMONIZATION WITH ONAP | M | SDNC: C DCAE: C | SDN-C: C DCAE: C SDN-C (A1 adaptor) committed by Ericsson Company commitment per component | Dongho Kim Marge Hillis Vimal Begwani | AT&T Nokia Ericsson | DCAE: Impact for adopting new VES domain; Committed based on Nokia support. | ||||||
5G / License Management | VNFREQ, after UCs agreed SDC(*) Modeling ( *) No code or test impact expected in R6 as an outcome of the proposed UC | TSC: No development? Company Commitment or is it a Modeling subcommittee activity? | LICENSING MANAGEMENT | SDC | M | No code or test impact expected in R6 | N/A | AT&T Nokia Ericsson Orange | |||||||
5G / Bulk PM / PM Control | SO DCAE Integration | TSC: See red cell. => Requested information about company commitment has 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 | DCAE Integration | TSC: See red cell. | 5G Bulk PM in Frankfurt/R6 | AAF (REQ-140) | S | DCAE: C | DCAE: C Company commitment is Nokia? | Nokia | DCAE: Committed based on Nokia support | |||||
5G / PM dictionary | SDC: GAB Config file DCAE: VES Event Reg Spec | TSC: See red cell. | FM META DATA & PM DICTIONARY in R6 Frankfurt | S | SDC: Update GAB Config File (no S/W update) DCAE: DO | SDC - C DCAE - C Company commitment per component | 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 | SO CDS Modeling Integration | TSC: See red cell. | 5G Network Resource Model (NRM) Configuration in R6 Frankfurt | M | SO: C CDS: C Modeling: DO Integration: C | SO: C CDS: C Modeling: P Integration: C Company commitment per component | yaoguang wang | Huawei | ||||||
5G / 5G Service Modeling: Modeling (exploratory) work for creating a 5G Service | Modeling Work Only (No REQ) | Modeling | TSC: No development? Company Commitment or is it a Modeling subcommittee activity? | 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 | DCAE SO VID | TSC: See red cell. | PNF PLUG and PLAY in R6 Frankfurt | AAF (REQ-140) | M | DCAE: C SO: C VID: C | DCAE: C SO: C VID: C Company commitment per component | Nokia | DCAE: SDK Dmaap lib refactor; committed based on Nokia support | |||||
PNF / Configuration with NETCONF/ Secure Communication between xNFs and ONAP | SDNC Integration | TSC: See red cell. => Requested information about company commitment has 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 | VNF-SDK Integration | TSC: See red cell. | PNF/VNF PREONBOARDING / ONBOARDING in R6 Frankfurt | S | VNFSDK: C Integration: TO | VNFSDK: C Integration: TO Company commitment per component | Nokia Ericsson | ||||||||
Modeling: Runtime instance model based on A&AI reverse engineering | Modeling only. No new implementation requirements | TSC: See red cells | Reverse-engineering AAI data model to Papyrus information model | AAI | S | AAI: C (one bug fix remaining in UML generation tooling) | Company commitment per component | MISSING IFNORMATION | AT&T Ericsson Huawei Orange | ||||||
Modeling: documentation of policy and allotted resource model | Modeling Work Only | Kevin Scaggs | Modeling only. No new implementation requirements | TSC: No development? Company Commitment or is it a Modeling subcommittee activity? | Policy SDC | M | AT&T | ||||||||
Scaling Extensions | APPC CCSDK | 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 | APPC Integration | 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 | Integration | 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 | PORTAL | 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 | PORTAL | 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 | SDC Modeling SO VFC OOF Integration | 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 | SDC Modelling | TSC: No development? Company Commitment or is it a Modeling subcommittee activity? | L | |||||||||||
Vertical Industry Oriented On-demand 5G Slice Service (this is merged with Network Slicing use case, and has become E2E Network Slicing) | LIN MENG | Modeling, U-UI, SO, DCAE | TSC: NO GO From Archi. Next Step? | China Mobile, Tencent, Huawei | Merged with Network Slicing use case | ||||||||||
E2E Network Slicing | SO, AAI, OOF, SDN-C, EXT-API, U-UI, Policy, DCAE, Modeling | TSC: NO GO From Archi. Next Step? | NETWORK SLICING in R6 Frankfurt | SDC | XL | SO - C OOF - C SDN-C - C AAI - C EXT-API - C UUI - C DCAE - C POLICY - TO | SO - C OOF - C SDN-C - C AAI - N EXT-API - C UUI - C DCAE - C POLICY - C | Wipro, AT&T, Amdocs, China Mobile, Huawei, Tencent | |||||||
Remove Python2 dependencies | David McBride | ALL projects using Python | 1- NEED Company to commit - MUST HAVE | M | |||||||||||
Multicloud K8s Support (Continuation from R4) | MultiCloud K8s SO SDC | See red cells | K8S based Cloud region support (Continue from R4) | Multi-Cloud : C | Company commitment per component | MISSING Information | Intel Aarna Tech Mahindra | ||||||||
K8s CDS Support | Multicloud K8s CDS Integration | 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 | Multicloud K8s, AAI/ESR, Policy, OOF, SO, SDC | TSC: ALL Info provided. GO to be part of the TSC prioritization | 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 | Multicloud K8s | See red cells | Multicloud K8s | S - M | MULTICLOUD: C | Multicloud K8s Company commitment per component | MISSING INFORMATION | Intel | |||||||
VSP Compliance and Validation Check within SDC - Phase 2 | SDC | See red cells Requirements introduced after Sept 27th | VSP Compliance and Validation Check within SDC | SDC: C | Company commitment per component (Prabhu: Reviewed the design with SDC PTL and Vodafone already committed the code in SDC and code review is in progress) | Prabhu Balan | Vodafone | ||||||||
OVP Testing and Certification Support Within SDC | SDC VTP | See red cells Requirements introduced after Sept 27th | OVP Testing and Certification Support Within SDC (Frankfurt) | SDC - C VTP - C | SDC - Vodafone VTP-iconectiv | ||||||||||
SECCOM Code coverage – increase to 60% | All projects | Feasibility to be reviewed Some teams got a waiver from previous release | |||||||||||||
SECCOM Containers configured per secure recommendation | All projects using containers | Candidate for TSC MUST HAVE | |||||||||||||
SECCOM Java 11 and 13 migration from v8 | All projects using java | Feasibility to be reviewed | |||||||||||||
SECCOM CII badging – meet targeted Silver and Gold requirements | All projects | Feasibility to be reviewed | |||||||||||||
SECCOM Complete the OJSI backlog | All relevant projects having an entry in OJSI | Feasibility to be reviewed | |||||||||||||
SECCOM HTTPS communication vs. HTTP | All relevant projects still using http communication instead of https | Candidate for TSC MUST HAVE | |||||||||||||
SECCOM Password removal from OOM HELM charts | All relevant projects | Candidate for TSC MUST HAVE | |||||||||||||
SECCOM Communication Matrix | All projects | Feasibility to be reviewed | |||||||||||||
SECCOM Containers and Kubernetes secure configuration recommendation | All projects using containers | Feasibility to be reviewed | |||||||||||||
SECCOM Coverity integration by end of Frankfurt | All projects | Feasibility to be reviewed with LF IT | |||||||||||||
SECCOM Ingress controller | All projects | Feasibility to be reviewed | |||||||||||||
SECCOM ISTIO POC – limited ONAP deployment scope | AAF + TBC | Shall we move this req to POC? | |||||||||||||
SECCOM Secure communication for 5G – AAF contribution – CMPv2 protocol trial usage | Hampus Tjäder | AAF | What's the difference with the Use Case. Shall we only consider this req | ||||||||||||
SECCOM Perform Software Composition Analysis - Vulnerability tables | All projects | Candidate for TSC MUST HAVE |
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
POC Definition - (In Progress)
Type | Requirement | Owner | Project Impacted | 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 |
---|---|---|---|---|---|---|---|---|---|---|
Acumos - DCAE Integration | DCAE | 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.