...
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:
| Panel |
|---|
|
|
| title | inputs.yaml |
|---|
aaf_username: dcae@dcae.onap.org
aaf_password: <dcae_password> |
|
where <dcae_password> is replaced with the appropriate 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:
The default behavior of By default the latest Docker Images will be used when deploying 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:, however, this attribute can also be configured like:
| Panel |
|---|
|
|
| title | inputs.yaml |
|---|
tag_version: nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.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 |
|---|
| language | yml |
|---|
| theme | Emacs |
|---|
| title | inputs.yaml |
|---|
|
tag_version: nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.pm-mapper:<version> |
...
where version is as desired.
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:
| Panel |
|---|
|
| 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.
