Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

curl -k -X PUT https://dcae-pm-mapper:8443/delivery/<filename> -H 'X-DMAAP-DR-META:{"productName": "AcmeNode","vendorName": "Acme","lastEpochMicrosec": "1538478000000","sourceName": "oteNB5309","startEpochMicrosec": "1538478900000","timeZoneOffset": "UTC+05:00","location": "ftpes://127.0.0.1:22/ftp/rop/A20161224.1045-1100.bin.gz","compression": "gzip","fileFormatType": "org.3GPP.32.435#measCollec","fileFormatVersion": "V9"}' -H "Content-Type:application/xml" --data-binary @<filename> -H 'X-ONAP-RequestID: 12345' -H 'X-DMAAP-DR-PUBLISH-ID: 12345'


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

Image Modified

output.json

...

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
namekpipolicyinstance.json
height250
View file
namekpipolicytype.json
height250
View file
namedeploykpipolicy.json
height250

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"]'