New projects proposal are posted here. These projects need to be reviewed and approved by TSC.
Some of the Use Cases, Functional and non functional requirements are carried over from previous releases as they required multiple releases to be implemented.
SDC, SO, SDN-C,OOF,ExternalAPI, UUI, ESR,Modeling,MultiVIM/Cloud, VFC, Modeling, DCAE, Policy, Holmes,
Consistent ID of a cloud region
...
AAI: TO
DCAE: TO
ExtAPI: TO
Multi-VIM: Test support
...
SDC: Partially committed based on Chinamobile/ZTE/Vodafone contribution
SO: Committed based on the contributions from CMCC, ZTE and VDF for the main flows
SDN-C/CCSDK : Committed based on contributions from Huawei and ZTE
VF-C: Committed
Modeling: Committed
Usecase-UI: Committed
Holmes: Committed based on Huawei and ZTE contribution
Multi-VIM/Cloud: Committed based on VMware contribution
Policy: Committed base on Huawei contribution
ExtAPI: Committed as long as a serviceOrder is created, either for service creation or modification with full service characteristics and values. ExtAPI can not read service characteristic and service state from AAI which does not expose those informations.
...
Dev/Test privided by Chinamobile, Vodafone, Huawei,
Work done but test is blocked by VID/SO blockers - integration blockers
Y
Status
colour
Green
title
Green
Issue mentioned in the M3 Scorecard has been cleared. Pair-wise testing with APPC was successful. Need to test closed loop when latest Policy containers will be available
Test blocked by VID/SO blockers - integration blockers
Y
Status
colour
Green
title
Green
Y
All: Test Only
N/A - part of regression tests
N/A - part of regression tests
HPA Testing confirmed by INTEL
vCPE (Heat)
Integration Team
HPA
1
Status
colour
Green
Y
Status
colour
Yellow
title
YELLOW
Test blocked by VID/SO blockers - integration blockers
Y
Status
colour
Green
title
Green
Y
All: Test Only
N/A - part of regression tests
N/A - part of regression tests
HPA Testing confirmed by INTEL
CCVPN Use Case (Dublin) High priority:1, SD-WAN Multi-site to Multi-site service creation; 2, Service change: add or delete a site;3, close loop intelligent surveillance
Multi-sites creation function will be partially implemented.
(Has risks on implementation of coding and testing in SDC) - integration blockers
Y
Status
colour
Green
Some bugs related to multi-site creation function in SO will be fixed by next week.
This function is also at high priority in the integration test and the integration team in CCVPN team will spare all the efforts to support this function.
SDC: Partially committed based on Chinamobile/ZTE/Vodafone/Fujitsu contribution
SO: Committed based on the contributions from CMCC, ZTE and VDF for the main flows
SDN-C/CCSDK : Committed based on contributions from Huawei and ZTE
VF-C: Committed
Modeling: Committed
Usecase-UI: Committed
Holmes: Committed based on Huawei and ZTE contribution
Multi-VIM/Cloud: Committed based on VMware contribution
Policy: Committed base on Huawei contribution
ExtAPI: Committed as long as a serviceOrder is created, either for service creation or modification with full service characteristics and values. ExtAPI can not read service characteristic and service state from AAI which does not expose those informations.
Dev/Test provided by Chinamobile, Vodafone, Huawei,
AAI: (using 5G use case PNF discovery and re-registration: TO
DCAE: C
ExtAPI: C
SDC: TO
SO (using 5G use case PNF discovery and re-registration): TO
Policy: TO
CLAMP: TO
SDNC: C
Modeling: design
DCAE: Committed based on contribution from Huawei, TechM and Nokia
ExternalAPI: Committed
SO: 5G PNF Committed based on the contributions from Nokia /Huawei
SDNC: Committed based on contributions from BBS team
Modeling: contributions from Swisscom/Huawei/Nokia
AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability
Nokia, Swisscom, Huawei, TechM
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.
Functional Requirements
M1 Scorecard:
Green: The functional requirement will be fully implemented and tested
Yellow: The functional requirement will be partially implemented. It is possible to identify capabilities for this functional requirement that can be tested (phasing approach).
Red: The functional requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy
Tableenhancer
numberOfFixedRows
1
numberOfFixedColumns
4
decimalMark
. (point)
Functional Requirement
Owner
Project Impacted
Priority
M1 Scorecard
TSC M1 Approval
M3 Scorecard
M3 TSC Approval
M4 Scorecard
TSC M4 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)
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)
SDC: Committed based on contribution from VF, Huawei and iconectiv
Vodafone, iconectiv, huawei
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.
Non-Functional Requirements
M1 Scorecard:
Green: The non-functional requirement will be fully implemented and tested
Yellow: The non-functional requirement will be partially implemented. It is possible to identify capabilities for this non-functional requirement can be tested (phasing approach).
Red: The non-functional requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy
Tableenhancer
numberOfFixedRows
1
numberOfFixedColumns
4
decimalMark
. (point)
Non Functional Requirement
Owner
Project Impacted
Priority
M1 Scorecard
TSC M1
Approval
M3 Scorecard
M3 TSC Approval
M4 Scorecard
TSC M4 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)
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)
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
ONLY DCAE component. No other projects securing the xNF comms.
Need review at TSC
Status
colour
Green
Y
Slide presented on PTL Call (1/14/2019)
DCAEGEN2-1101 - DCAE enhancements to support certificate authentication for HTTPS. All HTTPS connections from xNFs go to DCAE so no other projects need to be updated.
DCAEGEN2-978 - DCAE replaces clear text password with hash.
DCAE - Committed based on Nokia's contribution
Controller part (SDNC) committed from Ericsson, see 5G UC.
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
SO (using 5G use case PNF discovery and re-registration): TO (to be confirmed)
Policy: TO
CLAMP: TO
SDNC: C
Modeling: design
DCAE: Committed based on contribution from Huawei, TechM and Nokia
ExternalAPI: Committed
SO: Committed based on the contributions from Nokia /Huawei?
SDNC: Committed based on contributions from BBS team
Modeling: contributions from Swisscom/Huawei/Nokia
AAI: assuming schema/model changes only contributed by community. Also depends on AAI modelling SME availability
...
Nokia, Swisscom, Huawei
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.
Functional Requirements
M1 Scorecard:
Green: The functional requirement will be fully implemented and tested
Yellow: The functional requirement will be partially implemented. It is possible to identify capabilities for this functional requirement that can be tested (phasing approach).
Red: The functional requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy
...
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
...
SDC & SO: Partially committed (based on solution and TechM contribution)
Policy: Partially committed - TechM resources but scope must be worked out by M2
This project has been split so that a portion of it can be accomplished in Dublin. The model driven portion of the project is represented on this line and has been committed to with a unrequired stretch goal for DCAE
...
DCAE: Partial Committed
CLAMP: Committed
Policy: Committed
...
DCAE: One requirement cannot be committed due to resource constraint, and it is a needed requirement
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.
Non-Functional Requirements
M1 Scorecard:
Green: The non-functional requirement will be fully implemented and tested
Yellow: The non-functional requirement will be partially implemented. It is possible to identify capabilities for this non-functional requirement can be tested (phasing approach).
Red: The non-functional requirement can not be partially delivered, min. requirements can not be met in order to define a testing strategy
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.
Development Stretch Goal for Dublin. No particular Integration Testing required. Portal container at RC0 will be the final version to be tested
Y
Status
colour
Green
Y
Status
colour
Green
Implementation and documentation of the Angular upgrade that is scoped in Dublin is complete. Further, new screen changes are being planned to E release (as the Angular upgrade is a huge XL sized effort)
Y
Jira
server
ONAP JIRA
serverId
425b2b0a-557c-3c0c-b515-579789cceedb
key
PORTAL-345
Jira
server
ONAP JIRA
serverId
425b2b0a-557c-3c0c-b515-579789cceedb
key
PORTAL-330
Portal
XL
Code:
PORTAL
TO:
Policy, VID
PORTAL (C)
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.
Dublin POC / Experimentation
POC Definition - (In Progress)
Tableenhancer
numberOfFixedRows
1
numberOfFixedColumns
4
decimalMark
. (point)
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
Functional Requirement
Self Serve Control Loop (Closed Loop Subcommittee)