| Requirement | JIRA link (REQ) One issue per requirement. Instructions | 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 | | | RANK #2 | | YES | | YES | | YES | | 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 | | | RANK #2 | | YES | | YES | | YES | | 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 | | | RANK #3 | | YES | | YES | | YES | | 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 | | | RANK #3 | | YES | | YES | | YES | | GO Track as #42 on Frankfurt Release Integration Testing Status | 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
CDS+CLAMP integration.
undefined undefined Bruno Sakoto Adil Mir Vidyashree Rama Gaurav Agrawal | | AT&T Bell Canada Ericsson Huawei Orange |
|
| Control Loop Tutorial Documentation | | | RANK #3 | | YES | | YES | 
Only Documentation No resources for Integration | YES | 
Limited resources Synchro with Sel-Serve Control-Loop | De-scoped, based on feedback from Eric Debeau | | CLAMP, DCAE, POLICY | M | Documentation - DO
| DOC - C (Orange) POLICY - C (AT&T) DCAE - C (AT&T) CLAMP - C (AT&T)
| | | Bell Canada, AT&T, Orange |
|
| Component Upgrades to new Policy Lifecycle API | | | RANK #2
| | YES | | YES | | YES | | 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 | | Swaminathan Seetharaman Shankaranarayanan Puzhavakath Narayanan | TSC: Replaced by new E2E Network Slicing Scope No commitment to cover ExtAPI |
|
|
|
|
|
|
|
| NETWORK SLICING PoC in R6 Frankfurt (Obsolete) | SDC Possibly dependent on  | 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 Borislav Glozman Swaminathan Seetharaman LIN MENG | CMCC Amdocs AT&T Wiprc Huawei |
|
| 5G / OOF SON Enhancement | | | RANK #3
| 
CCSDK is not required | YES | | YES | | YES | | GO Track as #9 on Frankfurt Release Integration Testing Status | OOF (SON) in R5 El Alto, OOF (SON) in R6 Frankfurt | Runtime DB Possibly dependent on (see Notes) | 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). | | | RANK #3 |
PTL has confirmed he can deliver CCSDK, SDN-C | YES
| | YES | 
(see Project Wiki). Agreed to functionality in CC-SDK has been code-submitted. Reduced scope: No CM Notify VES event; No CIM/Yang. | | | 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 | | YES | | YES | |
| |
| 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 | | | RANK #2 |
SO impact clarified and agreed in SO weekly meeting. | YES | | YES | YELLOW Main function is merged. PNF upgrade procedure is working. - No VID GUI, but upgrade work flow still can be triggered by CLI (via SO API).
- Custom upgrade workflow is not completed. But PNF upgrade still be done using SO hardcode workflow.
| YES | | 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 |
| Eric Moore | Ericsson Huawei |
|
| PNF / Enable PNF software version at onboarding | | | RANK #2 |
Clarification: No impact on SO or VNF-SDK in R6. | YES | | YES | | YES | | 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 | | | 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: - Support use of CDS for LCM actions
- Improved PNF LCM support
|
| PNF / Enhancement on PNF Software Upgrade with EM with Ansible | | | RANK #2 | 
SO impact clarified and agreed in SO weekly meeting. | YES | | YES | | YES | | 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 |
| Enbo Wang |
Huawei |
|
| PNF / PNF Software Upgrade with EM with Netconf | | yaoguang wang | RANK #2 |
SO impact clarified and agreed in SO weekly meeting. | YES | | YES | 
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 | | 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 | 
Modeling Only for Frankfurt | | RANK #0 | | YES | 
green for A1 part (code merged) O1 enhancements moved to G release | YES | | YES | | 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 |
| | 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 | | | 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. | | YES |
No API, No S/W | YES | | YES | | GO
| LICENSING MANAGEMENT | SDC | M | Modeling: DO VNFRQTS, after UCs agreed: DO
SDC(*)
( *) No code or test impact expected in R6 as an outcome of the proposed UCs | Nokia and Ericsson commit to:
Modeling: C
VNFRQTS: C |
| 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 | | | RANK #2 |
SO impact clarified and agreed in SO weekly meeting. | YES |
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 | 
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: 
--- Mar 06 clarification: Proposing M4 with reduced scope rather than extension request: - In R6, use of DCAE GUIs for micro-service deployment and configuration rather than CLAMP
| YES | | 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. |
| user-3784d | Ericsson | DCAE: Committed based on Ericsson support |
| 5G / Bulk PM / Secure Communication between xNFs and ONAP | | Pawel Baniewski | RANK #2 | | | 
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 | | | RANK #2 | | YES |
VES spec updated, reviewed and approved. Reconfiguration of SDC is in progress (JSON file change)
| YES | | YES |
No integration testing required for this requirement. Testing is only required at SC level | | 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 | RANK #3 |
No commitment from SO lack of design, resource, etc Confirmation from yaoguang wang that the feature can be delivered even without SO. | YES |
SO: requirements reviewed and approved. No additional API impacts. CDS: requirements approved. Parts of executor codes merged. | YES | | YES | | 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. | | YES | | YES | | YES | | 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 | | Benjamin Cheung | RANK #2 |
Committed by SO PTL during the TSC call on 11/21 | |
02/03 - scope reduced by removing external cert work | YES |
Mar 05 M4 on Reduced scope (see Wiki) | YES | 
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
→ There will be need to release new SO images
|
| PNF / Configuration with NETCONF/ Secure Communication between xNFs and ONAP | | | RANK #3 | | YES | | YES |
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 |
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 | | | RANK #2 | | YES | | YES |
Mar 05 Reduced scope. See Wiki | YES | | 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 - package integrity rules are present (SOL004 option 1) - need to have prepared automated test cases
- PNF SW update validation rules are present need to have prepared automated test cases
- Full integration automation of pre-onboarding and onboarding tests is ongoing
|
| Modeling: Runtime instance model based on A&AI reverse engineering | Modeling Work Only | | RANK #0 | | YES | | YES | | YES | | GO | Reverse-engineering AAI data model to Papyrus information model | AAI | S | AAI: No code changes, updating missing fields in schema 
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 | | YES | Policy 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 | | YES | | YES | | YES | | GO |
| SDC | M | Modeling only. No new implementation requirements |
|
|
| AT&T |
|
| Scaling Extensions | | | RANK #2 | | YES | | YES | | YES | | 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 | | | RANK #2 | | YES | | YES | | YES | | 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  |
| vFW Traffic Distribution with Software Upgrade / CHM | | | RANK #2 | | YES | | YES | | YES | | 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  |
| Portal Security Enhancements | | | RANK #1 |
Confirmation from Manoop Talasila that the feature can be delivered even without Policy. | YES | | YES |
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 | | Manoop Talasila | RANK #3 |
Confirmation from Manoop Talasila that the feature can be delivered even without Policy. | YES | | YES | | YES | | 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. | Angular Upgrade to latest version Performance and Optimization |
| 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 | | | RANK #2 |
SDC No more required | YES | | YES | | YES | | 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 | | 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) | | 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: - CSMF, NSMF in ONAP with external (core) NSSMF with a plug-in to SO is ArchCom approved.
That is SO and External API impacts.
- External CSMF with NSMF in ONAP with SO plug-in for core NSSM is Arch com approved
- Arch clarification:
- no NSSMF (potentially PoC only) in ONAP
- There are impacts to OOF; It will be based on the HAS functionality, but modifying the constrints
- AAI -> new schema (no code change).
- SDC -> test only
- Policy -> test only.
- UUI has the CSMF portal and NSMF portal.
- SO has new workflows to reprent the CSMF and NSMF and "NSSMF adapter"
- External API exposes the NSMF NB APIs and shares the API definition with UUI.
- For a example E2E slice. There is a NSI (E2E) - (1:1) - NSSI (E2E) – (NSSI (core) + NSSI (RAN).; howver for frankfurt, we assume that the NSSMF is outside ONAP, hence the "core NSSI handling" is "e2e".
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: - How the NSSMF is in ONAP
- Slice across two domains (i.e. core and ran)..
| | | RANK #3 TSC: - For the network slicing. The following is a Go from architecture
- SO plug-in to an External NSSMF (for core).
- CSMF and NSMF representation in ONAP, and also allowing CSMF external.
- What is not approved is NSSMF in ONAP; nor connecting two subslices together as that requires the NSSMF and that still needs quite some more discussion.
This should limit the impacts to SO and External API for Frankfurt |
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
| (See Notes) | YES |
(See Notes) | YES |
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: - Code in all impacted modules has been submitted.
- Documentation has been submitted.
- Ready for integration test.
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 | | David McBride | RANK #1 |
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: - Uncommitted projects
- DCAEGEN Cloudify
- SDC
| YES |
All projects committed for the Frankfurt are OK except SDC and Multicloud Azure | YES |
All projects committed for the Frankfurt are OK except SDC and Multicloud Azure | |
|
| M | ALL projects using Python |
|
|
|
|
|
| K8s CDS Support | | | RANK #3 |
MultiCloud commitment confirmed
| YES | | YES | | YES | | | Integration with CDS Change Management Frankfurt Extensions |
| 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 | | | RANK #3 | | YES | | YES |
Move to R7 |
|
|
| Extending HPA for K8S | Multicloud K8s
| 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 | | | RANK #3 |
commitment from MultiCloud confirmed | YES | | YES | |
|
|
|
| Multicloud K8s | S - M | MULTICLOUD: C | Intel commits to coding/testing in Multicloud
|
| | Intel |
|
| VSP Compliance and Validation Check within SDC - Phase 2 | | | RANK #2 | | YES | | YES | | YES | | 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 | | | RANK #3 | | YES |
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 | | | RANK #3 |
See feedbeck from PTL on the wiki | YES | Waiting for a feedback from PTLs - Jira tickets were opened to all projects. Preliminary feedback is on track.
| Track |
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 |
Projects with waivers - AAF (aaf-authz, Sidecar fproxy, Sidecar rproxy)
- Policy (policy-engine)
- Multicloud (multicloud-azure)
- OOF (optf-cmso)
| GO
|
|
|
| All projects |
|
|
|
|
|
| SECCOM Containers configured per secure recommendation | | | RANK #3 | | YES | Continuing to follow up with PTLs. Will be gated by health check. Recommend approval. | Track |
Following up with PTLs. Some questions about the requirements in Chap.5 of the CIS Docker Benchmarks. | YES | | GO |
|
|
| All projects using containers |
|
|
|
|
|
| SECCOM Java 11 migration from v8 | | | RANK #3 |
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 |
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 | | | RANK #3 | | YES | 
There has been no movement by the projects on the CII requirements for Frankfurt. | Discuss on PTL call | | YES | 
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 | | | RANK #3 |
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 | 
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 |
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
|
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 | | | RANK #1 | except for Music (partial) and Holmes/Logging - no part of the release. See feedbeck from PTL on the wiki. | YES |
Some projects tends to have issues with AAF integration to provide certificate but seems to be doable if issues in AAF are resolved | YES |
17 HTTP ports still open. Detailed list can be provided by Morgan Richomme as he has the results that are updated every day | YES |
Only 30476
(music-tomcat)
left
| Recommend approval |
|
|
| All relevant projects still using http communication instead of https |
|
|
|
|
|
| SECCOM Password removal from OOM HELM charts | | | RANK #1 |
| YES | The 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 |
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 |
All related patches merged. No more "secretpassword" for mariadb-galera. | GO |
|
|
| All relevant projects |
|
|
|
|
|
| SECCOM Communication Matrix | | | RANK #3 |
DCAE will be the 'prototype' project/pilot with this release. Lesson Learnt will be shared to other projects. | YES - DCAE only
|
AS agreed first focus on external communication. | YES |
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 | | GO |
|
|
| All relevant projects |
|
|
|
|
|
| SECCOM Containers and Kubernetes secure configuration recommendation | | | RANK #3 | | YES | Waiting for feedback from the Integration team | YES |
Waiting for Integration team blocking K8S test results. | YES | | GO |
|
|
| All projects |
|
|
|
|
|
| SECCOM Coverity integration by end of Frankfurt | | | RANK #3 | | YES |
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 | | | RANK #3 | | YES |
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 |
All components accessible through ingress (nginx). | YES | | GO |
|
|
| All projects |
|
|
|
|
|
| SECCOM Secure communication for 5G – AAF contribution – CMPv2 protocol trial usage | | Hampus Tjäder | RANK #3 | Please remove this requirement, it is a duplicate of | Need to understand why it is yellow |
|
|
|
|
|
|
|
|
| AAF + TBC |
|
|
|
|
|
| SECCOM Perform Software Composition Analysis - Vulnerability tables | | | RANK #1 | except for Holmes/CLI and Logging - not part of R6 release See feedbeck from PTL on the wiki. | YES |  Waiting for a feedback from PTLs.
Script to automatically generate tickets is working.
| Track OBE - de-scope |
|
|
|
|
|
|
| All projects |
|
|
|
|
|
| Document current upgrade component strategy |
| David McBride | RANK #1 |
except for Holmes/ Logging - not part of R6 release See feedbeck from PTL on the wiki. | YES | | YES |
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 by TSC on 5/28/20 Will be done by contractor during 2H20 GO |
|
|
|
|
|
|
|
|
|
REQ-17