You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Overview

KPI-computation-service is component that can to do calucaltion based on PM data, and expose KPI result.
The features include:
    Subscribe original PM data from DMaaP
    Do KPI computation based on KPI formula which can be got from config policies and the formula can be configued dynamically.
    Publish KPI results on DMaaP
    Receive request for specific KPI computation (future scope) on specific ‘objects’ (e.g., S-NSSAI, Service)

Architecture Diagram

KPI flows:

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 MS will support for periodical KPI Computation. Period may be specified by a requestor optionally, if nothing is specified, KPI computation MS will continue computation until an explicit stop trigger is received.
4. The KPI result which genertate by kpi computation will be published to DMaaP.

Artifact

KPI ms can be dynamically deployed in DCAE’s Cloudify environment via its blueprint deployment artifact.

Βlueprint component file can be found in:

    https://git.onap.org/dcaegen2/platform/blueprints/tree/blueprints/k8s-kpi-ms.yaml


Deployment Prerequisite/dependencies

  1. DCAE and DMaaP pods should be up and running. 

  2. Make sure that cfy is installed and configured to work with the Cloudify deployment.

Deployment Steps

a)Execute bash on the bootstrap Kubernetes pod.

 

b)Download the kpi blueprint and save to /blueprints directory.

c)Run Cloudify to install the kpi ms      

      cfy blueprints upload -b kpi-ms k8s-kpi-ms.yaml      cfy deployments create -b kpi-ms kpi-ms         cfy executions start -d kpi-ms install

Validation

Functional tests       

(Specify/refer to functional test cases built around this service)

Automated Testsetup

(reference to automated test suites)

Known Limitations

(Refer to open/deferred jiras)

Future Enhancement Planned



Note: Refer to ONAP/RTD release note documentation wherever applicable

           

  • No labels