...
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
Jira Legacy | ||||||
---|---|---|---|---|---|---|
|
ONAP-based Analytics as a Service Details:
- What does ONAP-based Analytics Service encompass?
- Support analytics-as-a-service in the cloud-regions that have K8S site orchestrator.
- Use same analytics framework to have analytics even in ONAP-Central.
- Two packages - Standard package and inferencing package.
- Use existing analytics applications - TCA to prove this framework.
- As a stretch - Showcase one ML based applications
- Training application
- Inferencing application
- How to Develop?
- Use PNDA as a base
- Create/adapt Helm charts
- Ensure that no HEAT based deployment is necessary.
- Use components that are needed for normal analytics as well ML based analytics (Apache Spark latest stable release, HDFS, OpenTSDB, Kafka, Avro schema etc..)
- Use some PNDA specific packages - Deployment manager as one example.
- Develop new software components
- that allow distribution of analytics applications to various analytics instances
- that allow onboarding new analytics applications and models.
- that integrates with CLAMP framework (if needed)
- Impacted ComponentsONAP Projects
- DCAE, CLAMP, A&AI (TBD), Multi-VIM/Cloud (TBD)
- How to Test?
TCA (Changes - Convert this as a spark application)
New Machine learning models for KPI (packet loss) prediction (New use case)
...