...
...
...
...
...
...
Table of Contents
1. Overview
DCAE project provides intelligence for ONAP to support automation (via open-loop and CL) by performing network data collections, analytics & correlation and trigger actionable rootcause events.
...
- Complete DCAE transformation to Helm
- Common Template Enhancement for dcaegen2-services-common (filebeat removal + general add-on capabilities)
- Continue removal of Consul dependency & application config standardization via configmap
- MOD Support for Helm chart generation/distribution
- Deprecate Cloudify and related Handlers from ONAP deployment
- Integration Testsuite migration to use helm chart
- Support TSC approved ONAP Usecases and Features (details documented here - DCAE R10 Jakarta M2 Release Planning)
- TSC/SECCOM Global requirements
- STDIO complaince for Heartbeat and SNMPTRap MS
- TSC/SECCOM Best Practice
- Integration base image alignment for VES/RESTConf/SliceAnalysis MS
- Reducing DCAE backlogs + security fixes
Following new services will be delivered as POC in R10
- ML MS (REQ-1074)
- Repository : https://git.onap.org/dcaegen2/services/tree/components/ml-prediction-ms (introduced as new subproject under existing repo)
- ML MS (REQ-1074)
Refer DCAE R10 Jakarta M2 Release PlanningPlanning#Scope for more details
Following Platfrom components are deprecated and no longer part of DCAE deployment
- Cloudify
- Dashboard
- ServiceChange Handler
- Policy-Handler
- Deployment-Handler
- InventoryAPI
- ConfigBindingService*
3. New or modified interfaces
...
- PMSH - Adds new API support for Subscription/Filters/Measurement group management (this will be consumed by Policy)
- Slice Analysis - API to provide resource availability for existing slice/subslice. OOF is consumer of the API and will use this data to determine reusability of slice. - NSI/NSSI Selection based on resource occupancy levels; SliceAnalysis will also subscribe to AAI notification to support User-intent triggered CL flow for Bandwidth assessment
Deprecated interfaces
- Cloudify API (used for LCM of DCAE MS)
- InventoryAPI (used for saving/retreving DCAE blueprints)
- DeploymentHandler API (used by CLAMP for triggering MS deployment)
4. Interface naming
DCAE R10 Jakarta M2 Release PlanningPlanning#APIOutgoingDependencies
DCAE R10 Jakarta M2 Release PlanningPlanning#APIIncomingDependencies
5. Reference to the interfaces
DCAE R10 Jakarta M2 Release PlanningPlanning#APIOutgoingDependencies
Existing platform API's - https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/offeredapis.html
...
VES Collector Performance Test
PM-Mapper performance baseline
Datafile Collector (DFC) performance baseline results
HV-VES Performance Test
7. Involved use cases, architectural capabilities or functional requirements
- Usecases - DCAE R10 Jakarta M2 Release PlanningPlanning#JakartaUsecaseswithDCAEimpact
- Features - DCAE R10 Jakarta M2 Release PlanningPlanning#JakartaFeatureswithDCAEImpact
8. Platform Maturity Targets
...
Global Requirement and Best Practices - DCAE R10 Jakarta M2 Release PlanningPlanning#BestPractices/GLOBALRequirements
9. Listing of new or impacted models used by the project (for information only)
...