| Table of Contents |
|---|
...
1. KPI Computation MS will get PM data VES format from DMaaP
2. Other modules (e.g., SO/OOF/Slice Analysis MS) can also request KPI-MS for KPI calculation (Future scope beyond H-release).
3. KPI Computation will can be triggered once PM data received.
4. The KPI result which genertate by kpi computation will be published to DMaaP.KPI Computation do calculation ,generate KPI result, publish the result to Dmaap.
Current Status:
1. This ms provide a basic framework to support kpi computation, currently only support to do basic sum operation at present. more operation need to be extend in the future.
2. This ms only support to do calculation base on the real-time pm data from dmaap which published by pm-mapper.
3. This ms can support to get formula from cbs.
4. KPI Computation do calculation ,generate KPI result, publish the result to Dmaap.
Artifact
KPI ms can be dynamically deployed in DCAE’s Cloudify environment via its blueprint deployment artifact.
...
|
4. curl the topic on Message Router to retrieve kpi event:
curl -k https://message-router.onap.svc.cluster.local:3905/events/unauthenticated.DCAE_KPI_OUTPUT/c1/g1
...
The intention for kpi ms is to make this micro-service generic to be usable for other use cases also beyond E2E Network Slicing, and to add more capabilities., for R8 release, this ms will only support for periodical KPI Computationdo KPI Computation once pm data received, and support some basic computation, For example, the indicator "Downstream throughput for Single Network Slice Instance", It is obtained by downstream throughput provided by N3 interface from all UPFs to NG-RAN which are related to the single network slice instance, the ms will support the operation to sum all the downstream throughput from all the UPFs, and generate the kpi result. also other simple computation like this will be supported.
Future extension to enable more flexibility and greater reusability: support other modules (e.g., SO/OOF/Slice Analysis MS) can request KPI-MS for KPI calculation,;can do calculation based on the data not only from dmaap but also other service such as database etc; support more complex operation.
Creating KPI policy-type and policy-instance:
View file name kpipolicyinstance.json height 250
View file name kpipolicytype.json height 250
View file name deploykpipolicy.json height 250
| name | kpipolicyinstance.json |
|---|---|
| height | 250 |
| name | kpipolicytype.json |
|---|---|
| height | 250 |
| name | deploykpipolicy.json |
|---|---|
| height | 250 |
Earlier the kpi policy was given in the "application_config.yaml" file in the app-config folder as "kpi.policy" . Now for migrating the kpi policy to the policies module we are creating the new policy-type and the policy-instance and deploy the kpi policy. Then changes in the values.yaml file to fetch the policy with the "policy-id" with the help of policy sidecar container. Then get the kpi configs from the policies fetched and use in the computation of a Kpi.
Changes in values.yaml:
dcaePolicySyncImage: onap/org.onap.dcaegen2.deployments.dcae-services-policy-sync:1.0.1
policies:
policyID: |
'["com.Config_KPIMS_CONFIG_POLICY"]'