Page Comparison

1. Project Overview

...

DCAE components are classified between platform and service components.  DCAE Platform refers to the set of controller components which manages deployment and LCM of DCAE service components. The DCAE services components includes all the microservices - collectors, analytics and event processor which supports active data-flows and processing as required by ONAP usecases.
The  The architecture of DCAE targets flexible, micros-service oriented, model based component design and deployment. DCAE also offers support for multi-site collection and analytics operations which are essential for large ONAP deployments. .

Under new DCAE transformation project, DCAE platform components will be replaced by cloud native functions supported via sidecar/init containers through Helm deployment.

2. New component capabilities for

...

Isanbul, i.e. the functional enhancements

DCAE Focus for R8 is on following

...

...

• Progress on DCAE Architecture transformation to migrate to Helm
  • Common Template Enhancement 
    • CMPv2 Certificate
    • Policy Sidecar
    • PG credentials management through K8S secret
    • ConfigMap Support
    • DMaap Config Support (dynamic)
  • Helm charts migration for all other DCAE services
    • Bulk PM flow - DataFile, PM-Mapper, PMSH
    • E2E Slicing - KPI-MS, Slice-Analysis, DL Handlers (Feeder, Admin, DES)
    • Son-Handler, Heartbeat, VES-Mapper, RESTCOnf, SNMPTrap, BBS-Ep
  • Remove Consul dependency - application config standardization for Helm deployed components  (Prototype for VES/HV-VES)
    • Helm charts generation through MOD  (POC)
    • ONAP Internal Helm Registry support

• TSC/SECCOM Global requirements
• Reducing DCAE backlogs  + security fixes

Refer DCAE R9 M2 Release Planning#Scope for more details

Following new services will be delivered in R8 

...

• Repository : https://git.onap.org/dcaegen2/services/tree/components/kpi-computation-ms (introduced as new subproject under existing repo)

...

Image Added

Following Platfrom components are marked for archival post Istanbul; they will be RO only.

• Dashboard
• ServiceChange Handler
• Policy-Handler
• Deployment-Handler
• InventoryAPI

Image Added

3. New or modified interfaces

New External interfaces

• PMSH - Adds API support for Subscription/Filters/Measurement group management; this will be invoked by CLAMP. https://gerrit.onap.org/r/adminc/repos/dcaegen2/platform/ves-openapi-manager  (New repo)
• DCAE-service-policy-Sync (REQ-479)
  • Repository :  https://git.onap.org/dcaegen2/deployments/tree/dcae-services-policy-sync  (introduced a new subproject/module under existing repo)

In Honolulu, POC for new MOD Front-End and Back-end components will continue  - DCAEGEN2-2313 (this would eventually replace NiFI based UI/processor in subsequent ONAP release)

Image Removed

3. New or modified interfaces

Architecture diagram - DCAE R9 M2 Release Planning#Highlevelarchitecturediagram

New External interfaces

• None for H release

Modified interfaces

• VES Collector (7.2.1 VES support)

If they are modified, are the backwards compatible?

• VESCollector - Yes

4. Interface naming

...

• +/121898
• Slice Analysis -  API to provide details of remaining capacity available for queried slice. OOF is consumer of the API and will use this data to determine reusability of slice. - NSI/NSSI Selection based on resource occupancy levels

Modified interfaces

• NA

4. Interface naming

DCAE R9 M2 Release Planning#APIOutgoingDependencies

5. Reference to the interfaces

DCAE R9 M2 Release Planning#APIOutgoingDependencies

Existing platform API's - https://docs.onap.org/projects/onap-dcaegen2/en/latest/sections/offeredapis.html

...

• VES-Collector
• HV-VES (High Volume VES)
• PRH (PNF Registration Handler)
• DFC (DataFile Collector)
• 3GPP PM Mapper
• PM Subscription Handler
• DCAE SDK
• RESTConf - https://git.onap.org/dcaegen2/collectors/restconf/tree/swagger_restconfcollector.yaml
• des-swagger.json
• PMSH
• Slice-Analysis MS 

Deprecation Notice: Following Platform API's will be deprecated immediately after Istanbul. For Istanbul release - no new enhancement/updates are planned for these component (Istanbul deployment will continue using Honolulu version). 

• Deployment-Handler

...

• Inventory API
• DCAE Dashboard - https://git.onap.org/ccsdk/dashboard/tree/ccsdk-app-os/src/main/resources/swagger.json

6. What are the system limits

Relies on k8s for loadbalancing and scaling. DCAE platform handles the control flow and do not carry the data/event; DCAE service components can be scaled and support state management through external DB and/or K8S state management.

As DCAE collectors are extensively used in all ONAP usecase, performace testing has been done on below collectors

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 R9 M2 Release Planning#HonoluluUsecaseswithDCAEimpactPlanning#IstanbulUsecaseswithDCAEimpact
• Features - DCAE R9 M2 Release Planning#HonoluluFeatureswithDCAEImpactM2Release Planning#IstanbulFeatureswithDCAEImpact

8. Platform Maturity Targets

DCAE R9 M2 Release Planning#PlatformMaturity.1Istanbul Release Platform Maturity

Global Requirement and Best Practices Practices - DCAE R9 M2 Release Planning#BestPracticeCandidatesDCAE R9 M2 Release Planning#GlobalRequirementsPlanning#BestPractices/GLOBALRequirements

9. Listing of new or impacted models used by the project (for information only)

VES Mode updates tracked under REQ-433 - ONAP/3GPP & O-RAN Alignment-Standards Defined Notifications over VES (Honolulu)No model changes