...
Configuration of the service consists of generating an inputs file (YAML) 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.
| Property | Sample Value | Description | Required |
|---|---|---|---|
| aaf_username | dcae@dcae.onap.org | In the Dublin release information about the AAF user must be provided to enable publishing to authenticated topics. | Yes |
| aaf_password | <dcae_password> | This is the password for the given user e.g. Replace The <dcae_password> with is dcae@dcae.onap.org's password. | Yes |
| enable_http | true | By default, the PM-Mapper will only allow inbound queries over HTTPS. However, however its it is possible to configure it to enable HTTP also. | No |
| tag_version | nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.pm-mapper:<version> | By default the latest Docker Images will be used when deploying the PM-Mapper. Replace <version> with the desired Docker image version. | No |
| pm-mapper-filter | {"filters": [{"pmDefVsn":"targetVersion", "nfType":"targetNodeType", "vendor":"targetVendor", "measTypes":["targetMeasType"]}]} | 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. In this provided example a VES event containing the "targetMeasType" will only be generated and published if the following conditions are true:
Additional Information on the filter model can be found here. | No |
...