...
curl <dcaegen2-dcae-healthcheck> and check if pm-mapper is in 'ready' state.
Expand title See example $ curl 10.42.181.66 | jq
{
"type": "summary",
"count": 12,
"ready": 11,
"items": [
{
"name": "dev-dcaegen2-dcae-pm-mapper",
"ready": 1,
"unavailable": 0
},
{
"name": "dev-dcaegen2-dcae-config-binding-service",
"ready": 1,
"unavailable": 0
},
{
"name": "dev-dcaegen2-dcae-inventory-api",
"ready": 1,
"unavailable": 0
},
{
"name": "dev-dcaegen2-dcae-servicechange-handler",
"ready": 0,
"unavailable": 1
},
{
"name": "dev-dcaegen2-dcae-deployment-handler",
"ready": 1,
"unavailable": 0
},
{
"name": "dev-dcaegen2-dcae-policy-handler",
"ready": 1,
"unavailable": 0
},
{
"name": "dep-dcae-ves-collector",
"ready": 1,
"unavailable": 0
},
{
"name": "dep-dcae-tca-analytics",
"ready": 1,
"unavailable": 0
},
{
"name": "dep-dcae-prh",
"ready": 1,
"unavailable": 0
},
{
"name": "dep-dcae-hv-ves-collector",
"ready": 1,
"unavailable": 0
},
{
"name": "dep-dcae-datafile-collector",
"ready": 1,
"unavailable": 0
},
{
"name": "dep-dcae-snmptrap-collector",
"ready": 1,
"unavailable": 0
}
]
}
...
Verification
To verify that the PM Mapper is working as it should, we can publish a 3GPP XML file to the PM Mapper, and verify that the output on Message Router is:
- Valid VES
- The counters in the VES match what we expect based on our filtering.
To publish a file to the PM Mapper we can use the following example curl. Where <filename> Must begin with A or C and the file extension must be .xml.
| Code Block |
|---|
curl -k -X PUT https://dcae-pm-mapper:8443/delivery/<filename> -H 'X-DMAAP-DR-META:{"productName": "Acme","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' |
| Code Block |
|---|
curl -k https://message-router:3905/events/org.onap.dmaap.mr.PM_MAPPER |
...
Configuration
Configuration of the service consists of generating an inputs file which will be used as part of the Cloudify install. The PM-Mapper blueprints were designed with sane defaults for the majority of the fields.
Below you will find some examples of fields which can be configured, and some of the fields which must be configured.
In the Dublin release information about the AAF user must be provided to enable publishing to authenticated topics. An Inputs file with this information included can look like:
Code Block aaf_username: dcae@dcae.onap.org aaf_password: <dcae_password>
where
<dcae_password>is replaced with a real password.By default, the PM-Mapper will only allow inbound queries over HTTPS, however its possible to configure it to enable HTTP also. This configuration can look like:
Code Block enable_http: true
The default behavior of the PM-Mapper is to map all measType in the received PM XML files, however, it's possible to provide filtering configuration which will reduce the VES event to the counters that the designer has expressed interest in. An example of this configuration:
Code Block pm-mapper-filter: {"filters":[{"pmDefVsn":"targetVersion","nfType":"targetNodeType","vendor":"targetVendor","measTypes":["targetMeasType"]}]}In this provided example a VES event containing the "targetMeasType" will only be generated and published if the following conditions are true:
- The
- vendor of the node sending the file is "
- targetVendor"
- The
- type of the node sending the file is "
- targetNodeType"
Additional Information on the filter model can be found here.
By default the latest Docker Images will be used when deploying the PM-Mapper, however, this attribute can also be configured like:
Code Block tag_version: nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.pm-mapper:<version>
where version is as desired.