\r
- Download the PM Mapper blueprint onto the pod, this can be found in:\r
\r
- https://gerrit.onap.org/r/gitweb?p=dcaegen2/services/pm-mapper.git;a=blob_plain;f=dpo/blueprints/k8s-pm-mapper.yaml;h=b331e41222377b8fbf7b68b4f5fff5ba5998da16;hb=refs/heads/dublin\r
+ https://git.onap.org/dcaegen2/services/pm-mapper/tree/dpo/blueprints/k8s-pm-mapper.yaml\r
\r
- Create inputs.yaml\r
\r
:delim: ;\r
:header: Property , Sample Value , Description , Required\r
\r
- 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\r
- aaf_password ; <dcae_password> ; This is the password for the given user e.g. The <dcae_password> is dcae@dcae.onap.org's password. ; Yes\r
+ client_id ; dcae@dcae.onap.org ; In the Dublin release information about the AAF user must be provided to enable publishing to authenticated topics. ; Yes\r
+ client_password ; <dcae_password> ; This is the password for the given user e.g. The <dcae_password> is dcae@dcae.onap.org's password. ; Yes\r
enable_http ; true ; By default, the PM-Mapper will only allow inbound queries over HTTPS. However, it is possible to configure it to enable HTTP also. ; No\r
tag_version ; nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.pm-mapper:1.0.1 ; The tag of the Docker image will be used when deploying the PM-Mapper. ; No\r
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. ; No\r
\r
.. code-block:: yaml\r
\r
- aaf_username: dcae@dcae.onap.org\r
- aaf_password: <dcae_password>\r
+ client_id: dcae@dcae.onap.org\r
+ client_password: <dcae_password>\r
enable_http: false\r
- tag_version: nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.pm-mapper:1.0.1\r
+ tag_version: nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.pm-mapper:latest\r
pm-mapper-filter: {"filters": []}\r
\r
\r
.. code-block:: bash\r
\r
cfy install --blueprint-id pm-mapper --deployment-id pm-mapper -i inputs.yaml k8s-pm-mapper.yaml\r
-\r
Logging\r
=======\r
\r
-The log file is located under /var/log/ONAP/dcaegen2/services/pm-mapper/pm-mapper_output.log.\r
+There are two separate log files in the PM Mapper container.\r
+\r
+The main log file is located under /var/log/ONAP/dcaegen2/services/pm-mapper/pm-mapper_output.log.\r
+\r
+The human readable log file which contains less information is located under /var/log/ONAP/dcaegen2/services/pm-mapper/pm-mapper_output_readable.log.\r
+\r
+Log Level\r
+"""""""""\r
+\r
+The PM Mapper log level is set to INFO by default. This can be changed in the running container by editing the logLevel variable in the logback.xml file located under /opt/app/pm-mapper/etc/logback.xml. Changes to this file will be picked up every 30 seconds.\r