summaryrefslogtreecommitdiffstats
path: root/docs/sections/services/mapper/installation.rst
diff options
context:
space:
mode:
authorVENKATESH KUMAR <vv770d@att.com>2020-11-12 15:00:02 -0500
committerVENKATESH KUMAR <vv770d@att.com>2020-11-12 22:30:51 -0500
commite21c848562599340a99fc216bdaae97686d92a72 (patch)
tree65a3446cccde840220e3e2be2b53ee16d0bad7b4 /docs/sections/services/mapper/installation.rst
parent2cf33d0d1cecad5a309d428aa44f7740ca48032e (diff)
DCAE doc cleanup warnings
Change-Id: I39daca57d4754abe0db56a7f85e7274a5f45ad74 Signed-off-by: VENKATESH KUMAR <vv770d@att.com> Issue-ID: DCAEGEN2-2141 Signed-off-by: VENKATESH KUMAR <vv770d@att.com>
Diffstat (limited to 'docs/sections/services/mapper/installation.rst')
-rw-r--r--docs/sections/services/mapper/installation.rst9
1 files changed, 3 insertions, 6 deletions
diff --git a/docs/sections/services/mapper/installation.rst b/docs/sections/services/mapper/installation.rst
index 2add9d92..da0bcdc1 100644
--- a/docs/sections/services/mapper/installation.rst
+++ b/docs/sections/services/mapper/installation.rst
@@ -17,7 +17,7 @@ VES-Mapper can be deployed individually though it will throw errors if it can't
VES-Mapper blueprint is available @
https://git.onap.org/dcaegen2/services/mapper/tree/UniversalVesAdapter/dpo/blueprints/k8s-vesmapper.yaml-template.yaml?h=elalto
-VES-Mapper docker image is available in Nexus repo @ `nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.mapper.vesadapter.universalvesadaptor:1.0.1 <nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.mapper.vesadapter.universalvesadaptor:1.0.1>`_
+VES-Mapper docker image is available in Nexus repo @ `nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.mapper.vesadapter.universalvesadaptor:latest <nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.mapper.vesadapter.universalvesadaptor:latest>`_
@@ -27,11 +27,8 @@ VES-Mapper docker image is available in Nexus repo @ `nexus3.onap.org:10001/onap
*a. Verify DMaaP configurations in the blueprint as per setup*
Dmaap Configuration consists of subscribe url to fetch notifications from the respective collector and publish url to publish ves event.
-
-
-``streams_publishes`` and ``streams_subscribes`` points to the publishing topic and subscribe topic respectively.
-
-update these ``urls`` as per your DMaaP configurations in the blueprint.
+
+``streams_publishes`` and ``streams_subscribes`` point to the publishing topic and subscribe topic respectively. Update these ``urls`` as per your DMaaP configurations in the blueprint.
*b. Verify the Smooks mapping configuration in the blueprint as per the usecase. Blueprint contains default mapping for each supported collector ( SNMP Collector and RESTConf collector currently) which may serve the purpose for the usecase. The ``mapping-files`` in ``collectors`` contains the contents of the mapping file.