...
- High-Volume VES collector microservice (under 5G/performance analysis and optimization)
- File collector microservice (under 5G/performance analysis and optimization) **Dependency Has dependency on DMaaP project for BusController delivery DataRouter delivery
- PM Mapper microservice (under 5G/performance analysis and optimization) **Dependency Has dependency on DMaaP project for DataRouter delivery (Stretch Goal, not currently committed for Casablanca))
- Standalone TCA microservice
...
In addition, DCAE team will work on following enhancement as Stretch Goal (not currently committed for Casablanca due to resource constraint / external dependencies /unclear requirement )
- (S3P:security) Buscontroller integration for dynamic topic provisioning and AAF based role setting. **Dependency Has dependency on DMaaP project for BusController delivery
- (S3P:Performance) Performance optimization
- VESCollector
- TCA (new TCA service independent of CDAP will be contributed for R3).
- VES
6.0upgrade support (Updated 07/31/18 - VES 7.0.1 will be supported in R3 and will replace 6.0 originally planned)- Primarily VES Collector updates for new domains and transformation
(Security requirement for mutual TLS needs further clarification)
- Primarily VES Collector updates for new domains and transformation
- DCAE onboarding tool (dcae_cli) enhancement and environment support
- (S3P: Maintainability) Logging format compliance
- (S3P: Resiliency) MultiMutli-site support **Dependency Has dependency on OOM Team
- (S3P: Security) Securing api/interface and authorization via AAF (Need further clarification/support from Security/AAF team - 1) CADI library not available for Python 2) Consistent solution for AAF integration not identified (security proposal has many items WIP) 3) Process of AAF certificate distribution in K8S for components not defined and esp for components interfacing with external to ONAP)
- Following R2 items (descoped due to time/resource constraint) will be continued to enhanced for platform integration/S3P needs
...
DCAE will support the following functional requirements listed on the Casablanca Release Requirements page:
- 5G/PNF
Partial Commit - Support for new collector and services for processing highvolume RAN measurement and bulk data file processing - Scaling
Scaling - Test only (No additional development expected from DCAE to support this requirement)
- 5G/PNF
...
Deliverable Name | Deliverable Description |
---|---|
Component spec | All ms added into DCAE should provide meta data representation of the component itself; will be used to generate models in SDC and blueprint generation |
blueprints | Executable/SourceCode |
plugins | SourceCode |
cli | SourceCode/Tool/Documentation |
deployment-handler | SourceCode/Docker image |
servicechange-handler | SourceCode/Docker image |
inventory-api | SourceCode/Docker image |
policy-handler | SourceCode/Docker image |
configbinding | SourceCode/Docker image |
ves | SourceCode/Docker image |
snmptrap | SourceCode/Docker image |
tca | SourceCode/jar/Docker image |
...
Sub-components are repositories and are consolidated in a single centralized place. Edit the Resouce and Repositories in the centralized page.
...
In addition to existing platform/service component, following new components are targeted for R3
Deliverable | Repository | Maven Group ID | Components Description |
data-file-collector | dcaegen2/collectors/datafile | org.onap.dcaegen2.collectors.datafile | Data File collector |
hv-ves- |
collector | dcaegen2/collectors/hv-ves | org.onap.dcaegen2.collectors.hv-ves | High Volume VES Collector |
pm- |
mapper | dcaegen2/services/pm-mapper | org.onap.dcaegen2.services.pm-mapper | Mapper to process files from DR and transform to VES |
tca- |
gen2 | dcaegen2/analytics/tca- |
gen2 | org.onap.dcaegen2.analytics.tca- |
gen2 | Standalone(SA) TCA |
Architecture
High level architecture diagram
...
Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
---|---|---|---|---|
Performance | 1 | 2(stretch) |
| |
Stability | 2 | 2 |
| |
Resiliency | 2 | 2 |
| |
Security | 1 | 1 Recommendation for Casablanca is Level 2; however, Level 2 requirements are unclear and cannot be committed to. Securing api/interface and authorization via AAF (Stretch Goal, not currently committed for Casablanca due to following 1) CADI library not available for Python 2) Consistent solution for AAF integration not identified (security proposal has many items WIP) 3) Process of AAF certificate distribution in K8S for components not defined and esp for components interfacing with external to ONAP) Buscontroller integration for dynamic topic provisioning and AAF based role setting. **Dependency on DMaaP project for BusController delivery (Stretch Goal, not currently committed for Casablanca) |
| |
Scalability | 1 | 1 Mutli-site support **Dependency on OOM Team (Stretch Goal, not currently committed for Casablanca) |
| |
Manageability | 1 | 1 Recommendation for Casablanca is Level 2; however, Level 2 requirements are unclear (independent upgrade) and cannot be committed to. |
| |
Usability | 1 | 1 Recommendation for Casablanca is Level 2; however, Level 2 requirements are unclear (related to tutorial documentation) and cannot be committed to. |
|
...
Risk identified | Mitigation Plan | Contingency Plan |
---|---|---|
To fill out | To fill out |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
...