...
New projects proposal are posted here. These projects need to be reviewed and approved by TSC.
...
The Requirements extracted from SP lists of priorities for Casablanca are covered either by the Use Case, the functional requirements, the non functional requirement or within a project scope of work.
Table of Contents |
---|
Use CasesCases
Use Case | Owner | Projects or functional requirements Impacted for Casablanca | Link(s) to High Level Design (HLD) /Low Level Design (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, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc) | Company Engagement | Notes | M4 Status |
---|---|---|---|---|---|---|---|---|---|---|---|
vFW | AT&T | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | ||||||
vDNS | AT&T | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | ||||||
VoLTE | China Mobile | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | ||||||
vCPE | Kang Xi | HPA | All: Test Only | N/A - part of regression tests | N/A - part of regression tests | ||||||
CCVPN |
SO,OOF, SDNC,UUI, integration Stretch goal: SDC, DCAE, external API. |
NOTE: No project should be code impacted by this use case. | Materials Lin Meng. Material Jianguo Zeng | All; Test |
Contingent that Use Case owner are able to add resources on impacted projects and Integration agreement
SO, Portal, External API, APPC, DCAE
HPA
**NOTE: OSAM uses the PNF capability similar to 5G use case. No new development efforts were identified to support OSAM using PNF
VNFRQTS (include PNFs)
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
...
Projects Impacted
for Casablanca
...
Priority
(from SP perspective)
Dependency (from/to) another project(s)
...
...
VNFSDK (minor), SDC (minor), Policy, OOF (minor), SO (minor)
VNFRQTS
...
Orange: 2
ATT: 2
China Telecom: 2
China Mobile: 1
Verizon: 2
Vodafone: 2
...
Policy: on SDC
OOF: on AAI, Policy
...
Code: Policy, OOF, VNFSDK
...
Policy: Partially
OOF: Committed
VNFSDK: Committed
Policy: Resources
...
...
SDC, SO, VID, SDNC, APPC, VNFSDK, OOF, VF-C
VNFRQTS
...
Orange: 1
ATT: 1
China Telecom: 2
China Mobile: 2
Verizon: 1
Vodafone: 2
...
VID: on OOF, SO
SDC: on SO
...
VID: Not committed
APPC: Not committed
SDC: committed based on Amdocs contribution
SDN-C: committed
OOF: Not Committed
...
VID: requires additional design information
APPC: Not enough details on requirements, plus limited resources
OOF: Resources to be worked out
...
...
SO, APPC, VF-C, CLAMP, DCAE, Policy, OOM, VID, SDN-C, A&AI, Multi-VIM/Cloud, OOF
VNFRQTS,SDC
...
Orange: 1
ATT: 1
China Telecom: 1
China Mobile: 1
Verizon: 3
Vodafone: 1
...
CLAMP: depend on Policy
VID: on SO
APPC: on SO
Policy: on SO
OOF: on MultiCloud, Policy
...
VID: XS
CLAMP: M
AAI: XS
OOF: S
Code: SO, APPC, CLAMP, DCAE, Policy, OOM, VID, SDN-C, A&AI, Multi-VIM/Cloud, OOF
...
CLAMP: Committed with risks (see dependency)
VID: Committed
APPC: Partially Committed
Policy: Committed with risks (TBD)
AAI:
Committed
OOF: Partially committed
SDN-C: committed
DCAE: Not committed
...
APPC: Only committing to requirement to retrieve configuration data from AAI; Support for Controller Type currently a stretch goal until requirement are more defined
OOF: Limited resources; if R2 homing workflows need to be enhanced.
SDC: waiting on controller type decision
DCAE: From requirement, appears TO impact; need clarification as DCAE is noted as code impact.
...
...
SDC, SO, DCAE, SDN-C, App-C, A&AI, CDT, Modeling, VID, OOF
VNFRQTS
...
Orange: 2
ATT: 1
China Telecom: 3
China Mobile: 1
Verizon: 1
Vodafone: 2
VID: on SO
DCAE: on DMAAP-DR, OOM
...
VID: S
AAI: XS? need clarification on what's expected
OOF: need clarification on requirements for RAN VNF Homing
DCAE: XL
...
Code: VID
Test Only: SDC
Code : DCAE
VID: Not Committed
APPC: Not Committed
AAI: Not Committed
OOF: Partially Committed
SDNC: committed
DCAE: Partially Committed (New service committed based on Ericsson/Nokia)
...
VID: Additional information required
APPC: Per review of slides, does not appear to be anything specific for APPC in Casablanca. Items mentioned are more longer term, roadmap items
AAI: Expecting this to be modelling/schema updates only but unclear. Need additional information and analysis by AAI SMEs
OOF: Additional information required on policies required for RAN VNF Homing
DCAE: No Edge deployment support for R3. DDS-VES and new analytic platform not committed
...
...
Orange: 2
ATT: 2
China Telecom: 1
China Mobile: 3
Verizon: 3
Vodafone: 3
OOF: M
code change: OOF
...
CCSDK: committed
SDN-C: committed
OOF: Partially committed
DCAE: Not Committed
OOF: Limited resources
DCAE: Additional information required to assess impact
...
...
Orange: 3
ATT: 3
China Telecom: 1
China Mobile: 2
Verizon: 2
Vodafone: 3
...
Centralized Representation
and Consistent ID of Cloud Regions
...
...
SO,VID,SDNC,OOF,VFC,
UUI,MultiCloud, DCAE,
DMaaP, Integration
...
Orange: 1
ATT: 2
China Telecom: 2
China Mobile: 3
Verizon: 1
Vodafone: 1
...
VID: on SO
SO/OOF/VFC: MultiCloud
...
VID: S
MultiCloud: S
VFC:S
...
SO,VID,SDNC,OOF,VFC,
UUI,MultiCloud, Integration
Test: DCAE, DMaaP
...
VID: Not Committed
OOF: Committed
SDNC: Not committed
DCAE: Not committed
MultiCloud: Committed
VF-C :Committed
SDNC: Limited resources
DCAE: Not enough details on requirements.
...
...
Edge Scoping MVP for Casablanca - ONAP Enhancements
...
Orange: 3
ATT: 3
China Telecom: 3
China Mobile: 3
Verizon: 2
Vodafone: 1
OOF: on MultiCloud, AAI
...
AAI: XS? need clarification on what's expected
OOF: M
...
OOF: Committed
Multi-Cloud: Committed
DCAE: Not committed
Code: SO,OOF, SDNC,UUI Stretch goal: SDC, DCAE, external API, CCSDK, HOLMES, POLICY | SO:committed, OOF:committed (Huawei resources as required). UUI:committed Integration: committed SDNC: (Huawei resources as required). Stretch goal: DCAE : Not committed(Huawei &CMCC plan to contribute) SDC: Not committed External API:(VDF & huawei plan to contribute) CCSDK: (Huawei resources as required). HOLMES: (Huawei & ZTE to contribute) POLICY: (Huawei & CMCC to contribute) | if projects not committed is just in strech goal, then we will dev based on exist features, may impact some usibiligy, but won't impact the final result. DCAE : From discussion with Xin Miao (Huawei), this usecase requires new RESTCONF collector to be added into DCAE.This cannot be committed for R3 due to pending requirement clarification and architectural alignment besides resourcing constraint. | China Mobile, Vodafone, Huawei, ZTE | Contingent that Use Case owner are able to add resources on impacted projects and Integration agreement. Refer to this link for CCVPN closed loop related support in R3. |
POC Demo planned for ONS at Amsterdam | ||||||||||||
OSAM/PNF | SO, Portal, External API, APPC, DCAE HPA **NOTE: OSAM uses the PNF capability similar to 5G use case. No new development efforts were identified to support OSAM using PNF VNFRQTS (include PNFs) | OSAM Material | All: Test Only | ATT, Turk Telecom, Swisscom | Contingent that Use Case owner are able to add resources on impacted projects and Integration agreement |
Not M4 Gating No Component development required for this usecase in Casablanca Integration testing delayed due to resource contraint. Defer to Dublin |
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
Functional Requirements | Owner | Projects Impacted for Casablanca | Link(s) to High Level Design (HLD) /Low Level Design (LLD) (if any) | Priority (from SP perspective) | 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, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc) | Company Engagement | Notes | M4 Status | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
HPA | VNFSDK (minor) | HPA Enhancements (For Casablanca Release) | Orange: 2 ATT: 2 China Telecom: 2 China Mobile: 1 Verizon: 2 Vodafone: 2 | VNFSDK: none SDC: VNFSDK, VNFD model Policy: SDC OOF: SO, Policy, AAI AAI: Multi-CLoud | VNFSDK: M SDC:XS Policy: M OOF: S SO: S AAi: S/M Multi-Cloud: M | VNFSDK (C) | Policy: Committed based on Intel providing resources OOF: Committed VNFSDK: Committed SDC: committed based on Intel contribution. SO: committed AAI: committed based on Intel resources. Multi-Cloud: committed | Intel |
All code has been or will be submitted
Unresolved dependency on SDC - two bug fixes required. Update: Oct 18: the bugs on SDC have been addressed | |||||||||||||||||||||||
Change Management - Flexible designer/orchestrator | SDC, SO, VID | Link to Slide | Orange: 1 ATT: 1 China Telecom: 2 China Mobile: 2 Verizon: 1 Vodafone: 2 | VID: on SO SDC: on SO | SDC:XL VID: M | Code: SO,VID,SDC | VID: Not committed (Note: VID part is "nice to have" - no dependency on VID from other projects) SDC: committed based on Amdocs contribution SO : Committed (with support from ATT resources) | VID: requires additional resources | AT&T, Amdocs | |||||||||||||||||||||||
Change Management - traffic migration | SDNC, APPC, VNFSDK | Link to Slide | Orange: 1 ATT: 1 China Telecom: 2 China Mobile: 2 Verizon: 1 Vodafone: 2 | Code: SDNC, APPC | SDN-C: committed APPC: Not committed Orange: Committed | APPC: Not enough details on requirements, plus limited resources | AT&T, Orange, Intel | |||||||||||||||||||||||||
Change Management - 5G PNF software upgrade | SO, A&AI, Ansible/EC - test only support; SDNC/CCSDK- dev to incorporate 5G PNFs | Link to Slide | Orange: 1 ATT: 1 China Telecom: 2 China Mobile: 2 Verizon: 1 Vodafone: 2 | SDN-C: Committed | AT&T, China Mobile, Huawei | |||||||||||||||||||||||||||
Change Management - CM scheduler | OOF, VID VID - Nice to have - the functionality can still be delivered with OOF only (scheduler would need to be invoked through CLI) | Link to Slide | Orange: 1 ATT: 1 China Telecom: 2 China Mobile: 2 Verizon: 1 Vodafone: 2 | VID on OOF | VID: S | Code: OOF, VID | OOF: Committed VID: Not committed (this can still be delivered with OOF) | VID: requires additional resources | AT&T | |||||||||||||||||||||||
Scaling Closed Loop Scaling (High Priority) | Policy, CLAMP, SO, DCAE | Link to Slides | Orange: 1 ATT: 1 China Telecom: 1 China Mobile: 1 Verizon: 3 Vodafone: 1 | CLAMP: on Policy Policy: on SO | CLAMP: M | Code: SO, CLAMP, Policy Test: DCAE | CLAMP: Committed with risks (dependency on Policy) Policy: Committed with risks (TBD) SO: Committed DCAE: Committed | AT&T |
All code has been or will be submitted | |||||||||||||||||||||||
Scaling Beijing Improvements (High Priority) | Scott Blandford | APPC, SDNC, SO, AAI, VID | VID: on SO APPC: on SO | VID: XS AAI: XS | Code: APPC, SDNC, SO, AAI | AAI: Committed APPC: Committed SDNC: Committed SO: Committed VID: Committed | AT&T |
All code has been or will be submitted (VID is having issues with test environment) | ||||||||||||||||||||||||
Scaling Controller_Topic_ID (Medium Priority) | Scott Blandford | SO | Code: SO | SO: Committed | AT&T |
All code has been or will be submitted | ||||||||||||||||||||||||||
Scaling Homing and Capacity Check (Low Priority) | Scott Blandford | Multi-VIM, OOF, SDNC, SO | OOF: on Multicloud and Policy | OOF: S | Code: OOF, SO, SDNC, Multi-VIM | OOF: Partially Committed | OOF: Resource issue if R2 solution needs to be extended for new policy constraints. | AT&T |
| |||||||||||||||||||||||
5G/PNF Plug and Play | SDC, SO, SDN-C, A&AI, CDT, Modeling, VID, DCAE, DMaaP | Link to Slide | Orange: 2 ATT: 1 China Telecom: 3 China Mobile: 1 Verizon: 1 Vodafone: 2 | VID: on SO | VID: S AAI: XS? need clarification on what's expected OOF: No impact | Code: VID Test Only: SDC Code : DCAE | VID: Committed based on Nokia's contribution SDNC: committed SO: Committed (with resources from Nokia) SDC: support based on current sdc capabilities from Beijing. APPC: No impact AAI: No code change, only modeling changes OOF: No impact DCAE: committed DMaaP: committed | APPC: Per review of slides, does not appear to be anything specific for APPC in Casablanca. Items mentioned are more longer term, roadmap items AAI: Expecting this to be modelling/schema updates only but unclear. Need additional information and analysis by AAI SMEs OOF: Additional information required on policies required for PNF placement DCAE: Committed based on Nokia's contribution on PRH | AT&T, Nokia, |
Code has been developed and submitted.
SO Code Merge. Health Checks for PRH done in DCAE.
E2E.Test cases need to be updated (for integration & testing) after1st run of whole flow. Sunny Day scenarios to be prepared (for testing). | ||||||||||||||||||||||
5G/PNF Software Version Reporting | CCSDK, SDN-C | Link to Slide | CCSDK: committed SDN-C: committed | AT&T |
A&AI and SDC support has been developed.
Usage in the 5G Software Upgrade Use Case is pushed to Dublin | |||||||||||||||||||||||||||
5G/PNF Lifecycle Management Support (Restart, Suspend of PNF) | SDN-C/SDN-R. Controller support for operations. SDNC (SDNR) dev to incorporate 5G PNFs | Link to Slide | OOF: Supports Change Management Scheduling SDN-C: Committed | Will address this via Change Management | AT&T, China Mobile, Huawei |
SDN-C Interfaces need investigation. Want to make sure SDN-C is supporting Ansible. | ||||||||||||||||||||||||||
5G/performance Analysis and Optimization High Volume and RT Data Collection of PM | DCAE, DMaaP, | Link to Slide | Orange: 2 ATT: 2 China Telecom: 1 China Mobile: 3 Verizon: 3 Vodafone: 3 | DCAE: on DMAAP (native Kafka support) | OOF: M DCAE: L | code change: OOF Code : DCAE | CCSDK: committed SDN-C: committed OOF: No Impact DCAE: Committed (based on Nokia contribution) with dependency risk | OOF: Limited resources | AT&T, Nokia, | DCAE: Edge deployment support for R3, DDS-VES and new analytic platform (flink) not committed due to resource constraint |
Code is developed & Submitted. | |||||||||||||||||||||
5G/performance Analysis and Optimization Bulk PM | DCAE, DMaaP | Link to Slide | DCAE: on DMAAP-DR | DCAE:L | code change: DMaaP Code change: DCAE | DCAE: DataFileCollector- Committed (based on Ericsson Contribution) with dependency risk PMMapper - Partial Commit (Based on Ericsson contribution) + dependency risk – Not a hard requirement | DCAE: Dependency on DMAAP-DR + PMMapper (Stretch goal) | AT&T, Ericsson |
DMaaP Data Router
File collector available but with a few pending tasks Update form Vimal on Oct 4: File collector on track.
PM Mapper postponed to Dublin at M3 | |||||||||||||||||||||||
5G/performance Analysis and Optimization Optimization Framework Enhancements (Placement, Formulation, Solving) | OOF | Link to Slide | OOF: M | code change: OOF | OOF: Committed to SON | AT&T, Nokia, Reliance Jio |
All code has been submitted | |||||||||||||||||||||||||
Withdrawn from Casablanca release by the requirement owner | Orange: 3 ATT: 3 China Telecom: 1 China Mobile: 2 Verizon: 2 Vodafone: 3 | |||||||||||||||||||||||||||||||
Centralized Representation and Consistent ID of Cloud Regions, Plan B, Phase 1: Centralized Representation of Cloud Regions | SO, Integration | Centralized Representation and Consistent Identification of Cloud Regions In ONAP | Orange: 1 ATT: 2 China Telecom: 2 China Mobile: 3 Verizon: 1 Vodafone: 1 | code : SO, Integration | SO: committed based on Intel's contribution Integration: committed | To align MVP, propose alternative action plan B: break this requirement into 3 phases. Phase 1 is to centralize the representation of cloud regions; Phase 2 is to apply consistent ID across all related ONAP projects. Phase 3 is to correlate and align dcaeLocation to AAI's cloud region. This phase requires further discussion, hence not listed here. Note on "Intel's contribution": This is the synergy effort with HPA, no further special changes needed here. hence this can be deemed as a dependency on HPA's impact on SO. | SO: will be ready to test soon. Integration: Not started yet. | |||||||||||||||||||||||||
Centralized Representation and Consistent ID of Cloud Regions, Plan B, Phase 2: Consistent ID of Cloud Regions | SO,VID,SDNC,OOF,VFC, UUI,MultiCloud. | Centralized Representation and Consistent Identification of Cloud Regions In ONAP | Orange: 1 ATT: 2 China Telecom: 2 China Mobile: 3 Verizon: 1 Vodafone: 1 | VID/SDNC: on SO SO/OOF/VFC: MultiCloud | VID: XS MultiCloud: S VFC:S | code : SO,VID,SDNC,OOF,VFC, UUI,MultiCloud | SO: not committed VID: Not Committed SDNC: Not committed OOF: Committed MultiCloud:Committed VF-C :Committed UUI: committed | SDNC: Limited resources VID: requires additional resources | MultiCloud: Ready to test VFC: not started yet UUI: not started yet | |||||||||||||||||||||||
Edge Automation Through ONAP (EA) | A&AI, Multi-Cloud, OOF, SO | Orange: 3 ATT: 3 China Telecom: 3 China Mobile: 3 Verizon: 2 Vodafone: 1 | OOF: on MultiCloud & SO Multi-Cloud: on A&AI | SO: XS AAI: XS OOF: M Multi-Cloud: M-L | Code: OOF, Multi-Cloud, A&AI, SO Test: Integration (vFW use case) | Casablanca MVP:
| M4 on target in relevant projects Integration Test Plan in Progress: HPA & Cloud Agnostic Intent - R3 Test Plan (In Progress) | |||||||||||||||||||||||||
Edge Automation Through ONAP (EA) | Multi-Cloud | Orange: 3 ATT: 3 China Telecom: 3 China Mobile: 3 Verizon: 2 Vodafone: 1 | Multi-Cloud: M-L | Code: Multi-Cloud | Casablanca MVP:
| M4 on target in relevant projects Start Small MVP "Node metrics and HPA metrics from Grafana dash board" No plan for integration testing. |
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
Non Functional Requirements | Owner | Sub-category | Project Impacted for Casablanca | Link(s) to High Level Design (HLD) /Low Level Design (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, then what are the gaps per impacted project (people/FTEs; HLD/LLD; etc) | Company Engagement | Notes | M4 Status |
---|---|---|---|---|---|---|---|---|---|---|---|---|
S3P |
| Likely ALL depending upon TSC determination of new level requirements per category | Usability: New API’s adhere to Versioning strategy Versioning & API Documentation Recommendations Manageability: Adherence to ONAP Logging Spec v1.2 (implementation of the spec will occur in Dublin - Logging Dublin Scope) | Portal: on AAF, MUSIC, OOM VID, Policy, SDC, AAI: on Portal | Portal: XL | Portal: Code | Portal: Not Committed APPC: Partial DCAE: Partial SDC: committed VID: Partial (depends on Portal) AAI: Partial | APPC: Please refer to M1 Planning template for details DCAE: Refer to DCAE R3 M1 Release Planning#PlatformMaturity for details AAI: Please refer to AAI R3 Platform Maturity | Portal: IBM (only forAngularupgrade - shown interest, but not committed yet) | Portal: 1) Looking for resources who can help with adhering logging standards, API versioning and kubernetes deployment of Portal dockers. 2) Furthermore, Portal requires a security expert in addressing angular upgrade to address the Nexus-IQ reported vulnerability (the angular upgrade its self is XL t-shirt size task). | ||
Security | Note: This does not cover what is in S3P. However, based on that it is expected to have a certificate or use CADI to get certificates to enable secure communication Pluggable authentication and Authorization (Use of CADI and ?):
Secure communication toxNFs(Security for 5G Use cases). DCAE, APPC, VFC? VNF requirements. (Secure Communication to Network Functions)
Vnf package security following SOL 004: SDC, VNFreqs, VNF SDC | CADI/AAF Integration: | Portal: on AAF Test coverage (js): (1) js Sonar plug-ins activation (2) min. 3 additional containers per application => Jenkins enhancements (3) Maven build to be updated DMaaP on AAF DCAE on AAF, OOM,DMAAP OOF on AAF | Portal (CADI): M DCAE: XL SDC: L Test coverage (js): All: M/L | Portal: Code SDC: code VID: Code | Portal: Not Committed APPC: Partial OOF: Partial DCAE: Not Committed SDC: Partial VID: Partial (depends on Portal) AAI: Partial |
...
AAI: Expecting this to be modelling/schema updates only but unclear. Need additional information and analysis by AAI SMEs
DCAE: Need clarification on DCAE impact
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.
Abbreviations:
- Edge Automation through ONAP - EA
Non Functional Requirements
- Performance
- Stability
- Resiliency
- Security (see below)
- Scalability
- Manageability
- Usability
Likely ALL depending upon TSC determination of new level requirements per category
Usability: New API’s adhere to Versioning strategy
Manageability: Adherence to ONAP Logging Spec v1.2
Portal: on AAF, MUSIC, OOM
VID, Policy, SDC, AAI: on Portal
Portal: Not Committed
APPC: Partial
DCAE:Partial
APPC: Please refer to M1 Planning template for details DCAE: Refer to DCAE R3 M1 Release Planning#PlatformMaturity |
Note: This does not cover what is in S3P. Howeverbasedon that it is expected to have a certificate or use CADI to get certificates to enable secure communication
Pluggable authentication and Authorization (Use of CADI and ?):
- JAVA projects to use CADI client and enforcement point
- Non-JAVA projects:Waituntilthereismulti-language.
- All projects either need to have certificates (for secure communication) (based on a common trust store of AAF). The certificate distribution can be part of deployment mechanism and will be further detailed.
Secure communication toxNFs(Security for 5G Use cases). DCAE, APPC, VFC? VNF requirements. (Secure Communication to Network Functions)
- TLS and/or SSH for netconf (APP-C, SDN-C, CCSDK)
- HTTPS security for VES (DCAE) (with certificates, slowly deprecating username/pasword)
- Description of how the xNFs will get their certificates (VNFreqs).
Vnf package security following SOL 004: SDC, VNFreqs, VNF SDC
table for open issues/question with current proposal OOF: Please see OOF Casablanca M1 Release Planning Template SDC: because of the size of the sdc source code we will be able to reach only 10% unit test coverage on the Javascript. VNF package security missing information. AAI: Please refer to AAI R3 Platform Maturity | Portal: Looking for resources who understand the AAF based certificate management to upgrade using CADI client in Portal. OOF: Need more clarity on AAF support for python projects in Casablanca | |||||||||||||||||||||||
Upgrade (from Beijing to Casablanca) | All: XL | APPC: Not Committed CLAMP: Not Committed DCAE: Not Committed SDC: not commited VID: Not Committed AAI: Not committed | APPC, CLAMP, Portal, SDC, DCAE, VID, AAI: Lack of resources require additional information (does it include rollback, retrofit, no impact on run-time, etc)? | |||||||||||||||||||||
Architecture Alignment |
|
| DCAE on DMAAP (for DR) | DCAE:XL | DCAE:Partial Commit (New service committed based on Ericsson/Nokia) SDC: partial MultiVIM: Committed External API: Committed SO: Partially committed A&AI: partially committed CCSDK: committed | DCAE: DDS-VES and new analytic platform (FLINK) not committed due to resource. xNF-DCAE authentication not committed due to open issue listed under security. SDC: policy designer not planned for Casablanca, ETSI compliance only sol004 is planed. PNF suport will be done ontop of the existing capabilities. RTC stretch goal. DCAE-DS committed. Flow designer committed. ExtAPI: Interlude is a stretch goal SO: "decomposition" committed; "service instantiation" stretch goal A&AI: abstract topology sync-up committed | Reviewed and accepted at M3 reviews | |||||||||||||||||
HEAT support | HEAT-based ONAP deployment support should be dropped once OOM-based ONAP deployment's issues are fully identified and resolved. Recommendation from TSC: keep supporting HEAT in Casablanca for testing and integration purposes. However, HEAT won't be a gating item at Release Sign-Off. | Portal: on OOM | Portal: S SDC:S | Portal: Code SDC: code | Portal: Not Committed APPC: Will support Heat partially OOF: Support HEAT for testing SDC:committed VID: Partially | Portal: See Risk #4 | Portal: Switching CSIT jobs from using HEAT based to OOM based requires resources who can understand the current setup. | |||||||||||||||||
Internationalization language support | Tao Shen |
|
Design language/internationalization component in Portal and provideserviceapistopartnering apps like Policy, VID, SDC, AAI Note: This will need to go through the whole process (Architecture review,...) to understand whatthesdk will be providing and dependenciesonother ONAP project (Portal, SDC,...) As per Lingli and Tao from chinamobile, this is reviewed and approved by Arch Team. | UsecaseUI: on Portal | Portal: L | Portal: Code | Portal: Partial APPC: Not Committed CLAMP: Not Committed SDC: Not committed VID: Not committed | Portal: Limited resources | Portal: AT&T, ChinaMobile | Portal: Policy, VID, SDC, AAI can choose to use this Internationalization feature based on their capacity. Only UsecaseUI team is committed to develop and use this feature for now in Casablanca. |
Due to lack of resource, this is postpone to Dublin Release | |||||||||||||
Testing |
| Most UI projects with javascript. Recommendation from TSC: This is related to Code Coverage: recommendation is to keep 50% Code Coverage for Casablanca including JavaScript. (In Beijing Release code coverage was only covering Java and Python code, not javascript) | Linux Foundation Unit test and CSIT coverage framework, Policy, VID, SDC, AAI: on Portal, DCAE (for JavaScript coverage) | Portal: XL SDC:S VID:S | Code: portal, SDC, VID | Portal: Partial (no Javascript) APPC: Partial, Java code will maintain 50%, no commitment for Javascript CLAMP: Partial, Java code will maintain 50%, no commitment for Javascript DCAE:Partial (except javascript) SDC: maintain 50% coverage for java and python add 10% coverage for UI(java script) VID: maintain 50% coverage for java add 10% coverage for UI (java script) AAI: Partial, Java code will maintain 50%, add 10% coverage for sparky (javascript) | Portal, APPC, CLAMP, DCAE: See Risk #1 | Portal: AT&T, IBM, TechM | ||||||||||||||||
modeling | Hui Deng | SDC: needs to support composite pattern in R3 SDC/SO/A&AI needs to support Service Order, Service Catalogue, service scaling Modeling runtime needs to be supported by A&AI in release 3 | SDC:not committed SO A&AI - changes to the run-time schema require significant refactoring in all of AAI's client applications. That refactoring might be planned and addressed in R4; for R3, perhaps mapping existing runtime schema to new model definitions can suffice? | SDC: late submission to the requirements for Casablanca, not clear on what are the requirements from sdc. |
CADI/AAF Integration:
Portal: on AAF
Test coverage (js):
(1) js Sonar plug-ins activation
(2) min. 3 additional containers per application
=> Jenkins enhancements
(3) Maven build to be updated
DMaaP on AAF
DCAE on AAF, OOM,DMAAP
OOF on AAF
Portal (CADI): M
DCAE: XL
Test coverage (js):
All: M/L
Portal: Not Committed
APPC: Partial
OOF: Partial
DCAE: Not Committed
APPC: Please refer to M1 Planning template for details
DCAE: Refer to DCAE R3 M1 Release Planning#PlatformMaturity for details
OOF: Please see OOF Casablanca M1 Release Planning Template
Portal: Looking for resources who understand the AAF based certificate management to upgrade using CADI client in Portal.
OOF: Need more clarity on AAF support for python projects in Casablanca
APPC: Not Committed
CLAMP: Not Committed
DCAE: Not Committed
Architecture Alignment
- API improvement
- Realtimestreaming
- K8S Support (for VNFs)
View file | ||||
---|---|---|---|---|
|
DCAE on DMAAP (for DR)
APPC: Under assessment
CLAMP: Under assessment
DCAE:Partial Commit (New service committed based on Ericsson/Nokia)
DCAE: DDS-VES and new analytic platform (FLINK) not committedduetoresource. xNF-DCAE authentication not committed due to open issue listed under security.
HEAT-based ONAP deployment support should be dropped once OOM-based ONAP deployment's issues are fully identified and resolved.
Recommendation from TSC: keep supporting HEAT in Casablanca for testing and integration purposes. However, HEAT won't be a gating item at Release Sign-Off.
Portal: Not Committed
APPC: Will support Heat partially
OOF: Support HEAT for testing
- User Experience
View file | ||||
---|---|---|---|---|
|
Design language/internationalization component in Portal and provideserviceapistopartnering apps like Policy, VID, SDC, AAI
Note: This will need to go through the whole process (Architecture review,...) to understand whatthesdk will be providing and dependenciesonother ONAP project (Portal, SDC,...)
As per Lingli and Tao from chinamobile, this is reviewed and approved by Arch Team.
Portal: Partial
APPC: Not Committed
CLAMP: Not Committed
- Enable JavaScript Unit tests
- CSIT tests
Most UI projects with javascript.
Recommendation from TSC: This is related to Code Coverage: recommendation is to keep 50% Code Coverage for Casablanca including JavaScript. (In Beijing Release code coverage was only covering Java and Python code)
Portal: XL
SDC:S
VID:S
Code: portal, SDC, VID
Portal: Partial (no Javascript)
APPC: Partial, Java code will maintain 50%, no commitment for Javascript
CLAMP: Partial, Java code will maintain 50%, no commitment for Javascript
DCAE:Partial (except javascript)
SDC: maintain 50% coverage for java and python
add 10% coverage for UI(java script)
VID: maintain 50% coverage for java
add 10% coverage for UI (java script)
T-Shirt Size: Ballpark estimation for assessing the development/testing activities performed by the project team; not the integration team
...