...
Priority | M1 Scorecard | TSC M1 Approval | Functional 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) | 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) | Company Engagement | Notes | M4 Status | |||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2 |
| YYes with Condition: Need to confirm testing resource to Yang Xu and what the Integration Team will be able to test #Action - Bin/Yang to sync-up | Consistent ID of a Cloud Region (Dublin) | Bin Yang | SDNC & APPC , VID, SO, UUI, VFC, OOF | Consistent ID of a Cloud Region (Dublin) | APPC(TO, code already exists), SDN-C: test support only | SO: Support testing effort, changes are likely in. VFC:Committed UUI:Committed VID: Committed based on ATT resources | AT&T China Mobile | ||||||||||||
2 |
| Y | Continuation of HPA (Dublin) | Alexander Vul | VNFSDK, SDC, SO, VF-C, OOF, AAI, Policy, Multi-Cloud | Continuation of HPA (Dublin) | SDC - Jira bugs open, OL001 compatibility requirements addressed. | AAI: TO SO: Code Hardening, Expansion of use-case support, testing | AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability | Intel ARM(???) | Development t resources from ARM are required to test HPA support on ARM hardware | ||||||||||
2 |
| Y | Scaling Use Case (Dublin) | Scott Blandford | Main focus on DCAE/CLAMP & Policy | Scaling Use Case (Dublin) | DCAE: TO | CLAMP: Committed (Based on TechM resource commitment) Policy: Committed (Based on TechM Resource Commitment) | |||||||||||||
0 |
| Y | K8S based Cloud Region Support | Multi-Cloud, AAI, SDC, SO | K8S based Cloud Region Support | AAI: TO | SDC & SO: Committed based on Intel/VMWare contribution AAI: Partially committed | AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability | Intel, VMWare | Testing confirmed by INTEL | |||||||||||
3 |
POC for Dublin under Multi-Cloud umbrella | Y #action for Srini/Marco/Yang - identify another repo than demo | Distributed Analytics as a Service (Dublin Summary) - Edge Automation | Multi-Cloud, Demo | Distributed Analytics as a Service (Dublin Summary) - Edge Automation | MultiVIM/Cloud: partially committed based on VMware's contribution | VMware, Intel | Testing confirmed by INTEL | |||||||||||||
2 |
SO Only Testing confirmed by CM Team (AT&T) | Y with Condition: Limited to SO Scope #action - Ajay/Seshu/Ryan to meet and provide low level requirements | Change Management Dublin Extensions - Flexible designer/orchestrator | SO, VID | Change Management Dublin Extensions | SO (C), VID (C) | SO: Committed (AT&T) VID: pending final decision from Nokia (stretch goal) | AT&T Nokia | |||||||||||||
2 |
Testing confirmed by AT&T | Y | Change Management Dublin Extensions - Traffic Migration | APPC, OOF | Change Management Dublin Extensions | APPC (C), OOF (C), A&AI (TO) | APPC: Committed (Orange) OOF: Committed (Orange) | Orange | |||||||||||||
2 |
Testing confirmed by AT&T | Y | Change Management Dublin Extensions - Schedule Optimization | OOF | Change Management Dublin Extensions | OOF (C), Policy (TO) | OOF: Committed (AT&T) | AT&T | |||||||||||||
3 |
Testing confirmed by AT&T | Y | Model Driven Control Loop Design (Close Loop sub-committee) | DCAE, CLAMP, Policy | Model driven Control Loop Design | DCAE: AT&T Committed CLAMP: Committed Policy: Committed | AT&T commits to finding the required resources | AT&T, Nokia | |||||||||||||
3 |
SO Only Testing confirmed by SO Team | Y with Condition: Limited to SO Scope | Modularity | SO, SDC, VFC, APPC, SDNC | SDC: Not committed APPC: Not committed SO: Committed based on the code from R3 SDNC: Not committed VFC: Partially committed | SDC: no resources, not enough info APPC: no resources SDNC: no resources VFC: optimize DB microservice CDS project will provide Resource assignment functionality | |||||||||||||||
3 |
ETSI Alignment SOOL003 plug-in to SO | Y | ETSI Alignment SO plugin to support SOL003 to connect to an external VNFM | SO, SDC, AAI, | https://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Architecture%20Requirements-pa3.pptx?version=1&modificationDate=1544650581000&api=v2 | SDC: Partially committed (based on Ericsson contribution) SO: Committed (SOL003) based on contribution from Nokia and Ericsson AAI: Not Committed | SDC: no resources .AAI: no resources (detailed impact to be discussed) Action Byuong | ||||||||||||||
3 |
ETSI Alignment. SOL005 plug-in to SO | N | ETSI Alignment SO plugin to support SOL005 to connect to an external NFVO | SO, SDC, AA, External API, VFC (underdiscussion) | SO: SOL005 under dicusion with Verizon | ||||||||||||||||
4 |
Architecture did not approve | N | OSAM/PNF | ??? | ??? | ||||||||||||||||
4 |
| N | TOSCA Task Force | ??? | https://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Architecture%20Requirements-pa3.pptx?version=1&modificationDate=1544650581000&api=v2 | OOF: Policy Tosca model API and ONAP CLI integration | Intel | ||||||||||||||
4 |
| N | Alloted Network Function | ??? | ??? | ||||||||||||||||
3 |
| Y #Action- Need to confirm testing resource | Phase 1 - VSP Compliance Check | SDC CLI/VNFSDK | VSP Compliance Check within SDC (Dublin) | SDC: Committed based on contribution from VF, Huawei and iconectiv | Vodafone, iconectiv, huawei |
...
Priority | M1 Scorecard | TSC M1 Approval | Non Functional 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) | 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) | Company Engagement | Notes | M4 Status | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 |
| Yes with Condition: It does not include Ability to instantiate the entire service with API (VID) | Improve our E2E Process Automation | SO |
https://wiki.onap.org/download/attachments/48529726/ONAP-E2E-Automation-v3.pptx?api=v2 | AAI AAF DMaaP Policy PNF use case (5G) | XL | Code: APPC (CDS) TO: | SDC: CCSDK: SO: OOM: Testsuite: Documentation: AAI: TO | AT&T | ||||||||||||||||||||||||||||||||||
1 |
Container optimization : on –going (eg SDNC) | Testing Strategy https://lists.onap.org/g/onap-tsc/message/4605 Project teams to document the change in image size from Casablanca to Dublin as part of the changes they are making | S3P - Footprint Optimization (Integration with Alpine) | OOM + ALL | SDC: N CCSDK, CLAMP: Committed Multi-VIM/loud: committed Policy: committed DCAE: Not committed | SDC: no resources DCAE: Resource constraint | ||||||||||||||||||||||||||||||||||||||
1 |
Component/memory optimization: Ongoing Assessment | Testing Strategy https://lists.onap.org/g/onap-tsc/message/4605 Project teams to document the change in image size from Casablanca to Dublin as part of the changes they are making | OOM + ALL | SDC: N CCSDK, CLAMP: Committed Multi-VIM/loud: committed Policy: committed DCAE: Not committed | SDC: no resources DCAE: Resource constraint | |||||||||||||||||||||||||||||||||||||||
1 |
Global optimization (e.g. shared DB) - stretch goal=shared PostgreSQL; shared MariaDB | Testing Strategy https://lists.onap.org/g/onap-tsc/message/4605 Project teams to document the change in image size from Casablanca to Dublin as part of the changes they are making | OOM + ALL | SDC: N CCSDK, CLAMP: Committed Multi-VIM/loud: committed Policy: committed DCAE: Not committed | SDC: no resources DCAE: Resource constraint | |||||||||||||||||||||||||||||||||||||||
1 |
Manual PH1 | Yes with limited scope: Manual PH1 | CI/CD | OOM + Integration (Infrastructure) |
| Integration Logging OOM + ALL (helm charts) | L | no except devops/scripts in oom/integration | OOM: Linux Foundation (C) Orange (C) Bell (C) Amdocs (C) Logging: Bell (C) Amdocs (C) Integration: | Amdocs Orange Linux Foundation Bell Huawei | ||||||||||||||||||||||||||||||||||
1 |
| Yes | Document as You Code | ALL | Tracked in JIRA - Label: Documentation | |||||||||||||||||||||||||||||||||||||||
1 |
| Yes with Conditions #Action - provide findings on the PTL call | Security by Design | Security Subcommittee | ALL | |||||||||||||||||||||||||||||||||||||||
1 |
| Yes #Action on TSC | Modeling M3 Checklist enhancement | Modeling Subcommittee | SO, SDC, VFC, APPC, VNFSDK | Proposed M3 Checklist modeling updates discussion | VFC: Committed | |||||||||||||||||||||||||||||||||||||
1 |
| #Action - Need to be discussed on the PTL Call Phasing approach: #0 conf change only #1 upgrade with no data schema change #2 upgrade with data schema change | S3P - Provide Upgrade Capabilities | OOM + ALL | Dublin Release Platform Maturity | In Dublin will establish plan & basis for platform release upgrade strategy to be implemented in following release. | ||||||||||||||||||||||||||||||||||||||
1 |
| Y | Move Helm Chart (OOM) at project level | OOM + ALL | During the PTL meeting on 12/17 -it was agreed that No enforcement to make it happen for all project in Dublin release, but expectation to to completed within El Alto release. This could potentially be a S3P items. 6 projects have been identified for trial: Logging, Policy, APPC, CLAMP, AAI and ONAP CLI | |||||||||||||||||||||||||||||||||||||||
1 |
| Y | oParent Integration to fix vulnerabilities | Security Subcommittee | Integration +ALL | Modeling: TO | AAI, DCAE, DMaaP, Holmes, Logging, Modeling, MSB, Multi-Cloud, ONAP CLI, UUI, Policy, Portal, SO, VFC, VNFSDK, AAF,CLAMP, MUSIC: Already Integrated ExtApi, VID: Committed SDC: Not Committed CCSDK/SDNC, OOM, APPC, OOM: No | CCSDK/SDNC, APPC: dependency on ODL OOF (HAS, OSDF): python, not Java SDC: No resource OOM: No java code | ||||||||||||||||||||||||||||||||||||
1 |
| Yes with Conditions Based on PTL call (2/4), procedures to be provided to PTLs | CIST running OOM | PTLs | Infrastructure capacity | |||||||||||||||||||||||||||||||||||||||
2 |
| S3P- Geo-Redundancy | OOM (introduction of CNI)/MUSIC capabilities leveraged by initial ONAP Components i.e. OOF, Portal, SDC | Platform Maturity Resiliency Requirements | ||||||||||||||||||||||||||||||||||||||||
2 |
| Yes with Conditions: Need to confirm testing resource to Yang Xu and what they will be able to test by 2/4 otherwise this item will be descoped | SOL 004 (VNF Package Security) | Samuli Kuusela | SDC, VNFSDK | SDC:
| SDC: Partially committed (based on Ericsson contribution) | |||||||||||||||||||||||||||||||||||||
3 |
| Yes with Conditions: #action - Stephen/SECCOM to follow-up on testing | xNF communication security enhancements | AAF, DCAE, Controllers | Slide presented on PTL Call (1/14/2019) | DCAE - Committed based on Nokia's contribution
| ||||||||||||||||||||||||||||||||||||||
4 |
| No | S3P - Service Mesh (ISTIO) | Security & Architecture Subcommittees | ALL except MSB or performed at K8S level (OOM); Poc of ISTIO plug-in to AAF not resourced | https://wiki.onap.org/download/attachments/45293323/2018-12%20Virt%20F2F%20-%20%20Dublin%20Architecture%20Requirements-pa3.pptx?version=1&modificationDate=1544650581000&api=v2 | ||||||||||||||||||||||||||||||||||||||
4 |
| No | S3P Manageability - Logging Capabilities | see yellow/red in in progress log, aaf cli, consul, contrib, dcae, dmaap, nbi, oof, sdnc, so, uui, vid, vnfsdk, vvp good aai, appc, clamp, esr, multicloud, policy, pomba, portal, sdc, vfc | Library: In progress portal/sdk and possible so library adjustment
Infrastructure: dmaap is adding containers, need to work with other teams in red
as part of overall
| Log OOM Portal SO AAI | OOM (c) LOG (c) Portal (c) SO (c) AAI (c) Multicloud(c) | LOG/POMBA OOM | Amdocs AT&T Bell Hauwei Intel | |||||||||||||||||||||||||||||||||||
3 |
| Yes with Conditions: Need to confirm testing resource to Yang Xu and what they will be able to test - to be concluded on 2/4 | Locale/Internationalization language support | Portal, UsecaseUI | Internationalization language support | Portal, UsecaseUI | L | Code: | UsecaseUI (C) | |||||||||||||||||||||||||||||||||||
3 |
| Yes with Condition: Stretch Goal | Angular 6 Upgrade of ONAP Portal and SDK | Portal |
| Portal | XL | Code: PORTAL TO: Policy, VID | PORTAL (C) |
...