DCAE R6 VESMapper (BBS Usecase)

Overview

VES-Mapper microservice of DCAE can help to collect telemetry data / events / alerts from VNFs and collectors of DCAE and convert them into VES compliant events. It supports both VES-5.4 and VES-7.0 specifications.

Based on the configuration, the VES-Mapper subscribes to non-VES notifications published on the DMaaP. By using mapping files, the mapper converts the received notifications into VES events and publish them back on DMaaP on the configured topic. It uses a Java framework called Smooks (smooks.org) for the mapping files.

In case of BroadBand Service (BBS), VES-Mapper will receive the PNF registration notifications from DMaaP that are published by RestConf Collector, convert them into VES-7.0 events and publish them back on DMaaP for PNF registration handler service to pick them.

Blueprint/model/image

• VES-Mapper blueprint is available @
  https://gerrit.onap.org/r/gitweb?p=dcaegen2/services/mapper.git;a=blob;f=UniversalVesAdapter/dpo/blueprints/k8s-vesmapper.yaml-template.yaml;h=refs/head/master

• VES-Mapper docker image is available in Nexus repo @ nexus3.onap.org:10001/onap/org.onap.dcaegen2.services.mapper.vesadapter.universalvesadaptor:1.0.0-SNAPSHOT

Deployment Prerequisite/dependencies

VES-Mapper can be deployed individually though it will throw errors if it can not reach to DMaaP instance's APIs. To functionally test the mapper, only DMaaP is needed.

Deployment Steps

• Transfer blueprint file in DCAE bootstrap POD under /blueprints directory

• Log-in to the DCAE bootstrap POD's main container

To Deploy::

1. Validate blueprint

   cfy blueprints validate /blueprints/k8s-vesmapper.yaml-template.yaml

   
   
   

2. Upload validated blueprint

   cfy blueprints upload -b ves-mapper /blueprints/k8s-vesmapper.yaml-template.yaml

   
   
   

3. Create Cloudify Deployment

   cfy deployments create -b ves-mapper ves-mapper

   
   
   

4. Deploy component

   
   
   

To Undeploy::

1. Uninstall component

   
   
   

2. Delete blueprint

   
   
   

Validation

1. Check that VES-Mapper POD is created and it is in running state
   
   
   

   
   
   

2. Check the logs. Here are some important log statements that could be looked for.

   
   
   

Functional testing of VES-Mapper individually

1. Send a PNF registration notification on behalf of RestConf Collector by calling DMaaP API

   rcc_noti.json

2. Invoke DMaaP API to fetch message on the topic unauthenticated.VES_PNFREG_OUTPUT . VES-Mapper should have published converted VES event on this topic.

   
   Converted VES event

3. VES-Mapper logs