Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Βlueprint component file can be found in

  https://gerrit.onap.org/r/gitweb?p=dcaegen2/services.git;a=blob_plain;f=components/bbs-event-processor/dpo/blueprints/k8s-bbs-event-processor.yaml-template;hb=refs/heads/masterdublin
Blueprint inputs file can be found in
  https://gerrit.onap.org/r/gitweb?p=dcaegen2/services.git;a=blob_plain;f=components/bbs-event-processor/dpo/blueprints/bbs-event-processor-input.yaml;h=f503eb823160aa7d2aae763d322818227f0f00b7;hb=refs/heads/masterdublin

Docker image metadata for component can be found in

  https://nexus3.onap.org/repository/docker.snapshot/v2/onap/org.onap.dcaegen2.services.components.bbs-event-processor/manifests/1.0.0-SNAPSHOT

Deployment Prerequisite/dependencies

...

  • Uninstall running component and delete deployment

    Code Block
    languagebash
    themeMidnight
    titleUninstall component
    linenumberstrue
    cfy uninstall bbs-ep


  • Delete blueprint

    Code Block
    languagebash
    themeMidnight
    titleDelete blueprint
    linenumberstrue
    cfy blueprints delete bbs-ep
    

Deployment steps for VES-Mapper

  • VES-Mapper blueprint is available @
    https://gerrit.onap.org/r/gitweb?p=dcaegen2/services/mapper.git;a=blob_plain;f=UniversalVesAdapter/dpo/blueprints/k8s-vesmapper.yaml-template.yaml
  • 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
      cfy executions start -d ves-mapper install
  • To un-deploy::
    1. Uninstall component
      cfy uninstall ves-mapper
    2. Delete blueprint
      cfy blueprints delete ves-mapper

Initial Validation

After deployment, we can check if BBS-ep POD is running correctly

Code Block
languagebash
themeMidnight
titleVerify BBS-ep is running
linenumberstrue
root@cluster-admin:~# kubectl -n onap get pods | grep -i bbs
dep-bbs-event-processor-6b6df75d94-g7jw8                          2/2       Running            0          1d

And then check the logs to see if it can connect to DMaaP, polling for events. Even in the absence of events, we can at least verify that there is nothing to consume for both PNF re-registration messages and CPE authentication messages.


Initial Validation

After deployment, we can check if BBS-ep POD is running correctly

Code Block
languagebash
themeMidnight
titleVerify BBS-ep is running
linenumberstrue
root@cluster-admin:~# kubectl -n onap get pods | grep -i bbs
dep-bbs-event-processor-6b6df75d94-g7jw8    
Code Block
languagebash
themeMidnight
titleVerify BBS-ep can poll DMaaP
linenumberstrue
kubectl -n onap logs dep-bbs-event-processor-6b6df75d94-g7jw8 -c bbs-event-processor


2019-04-10 09:37:58.151  INFO 1 --- [pipeline-thrd-4] o.o.b.e.p.p.ReRegistrationPipeline       : Process next Re-Registration events
2019-04-10 09:37:58.152  INFO 1 --- [pipeline-thrd-1] o.o.b.e.p.p.CpeAuthenticationPipeline    : Process next CPE Authentication events
2019-04-10 09:38:07.680  INFO 1 --- [tor-http-nio-10] o.o.b.e.p.p.CpeAuthenticationPipeline    : Nothing to consume from DMaaP
2019-04-10 09:38:07.681  INFO 1 --- [tor-http-nio-10] o.o.b.e.p.p.CpeAuthenticationPipeline    : CPE Authentication processing pipeline has been completed
2019-04-10 09:38:07.681  INFO 1 --- [tor-http-nio-10] o.o.b.e.p.p.ReRegistrationPipeline       : Nothing to consume from DMaaP
2019-04-10 09:38:07.681  INFO 1 --- [tor-http-nio-10] o.o.b.e.p.p.ReRegistrationPipeline   2/2    : PNF Re-Registration processingRunning pipeline has been completed
2019-04-10 09:38:28.151  INFO 1 --- [pipeline-thrd-4] o.o.b.e.p.p.ReRegistrationPipeline  0      : Process next Re-Registration events

Initial Validation for VES-Mapper

After Cloudify deployment,

...

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

...

 1d


And then check the logs to see if it can connect to DMaaP, polling for events. Even in the absence of events, we can at least verify that there is nothing to consume for both PNF re-registration messages and CPE authentication messages.

Code Block
languagebash
themeMidnight
titleVerify BBS-ep can poll DMaaP
linenumberstrue
kubectl -n onap logs dep-bbs-event-processor-6b6df75d94-g7jw8 -c bbs-event-processor


2019-04-10 09:37:58.151  INFO 1 --- [pipeline-thrd-4] o.o.b.e.p.p.ReRegistrationPipeline       : Process next Re-Registration events
2019-04-10 09:37:58.152  INFO 1 --- [pipeline-thrd-1] o.o.b.e.p.p.CpeAuthenticationPipeline    : Process next CPE Authentication events
2019-04-10 09:38:07.680  INFO 1 --- [tor-http-nio-10] o.o.b.e.p.p.CpeAuthenticationPipeline    : Nothing to consume from DMaaP
2019-04-10 09:38:07.681  INFO 1 --- [tor-http-nio-10] o.o.b.e.p.p.CpeAuthenticationPipeline    : CPE Authentication processing pipeline has been completed
2019-04-10 09:38:07.681  INFO 1 --- [tor-http-nio-10] o.o.b.e.p.p.ReRegistrationPipeline       : Nothing to consume from DMaaP
2019-04-10 09:38:07.681  INFO 1 --- [tor-http-nio-10] o.o.b.e.p.p.ReRegistrationPipeline       : PNF Re-Registration processing pipeline has been completed
2019-04-10 09:38:28.151  INFO 1 --- [pipeline-thrd-4] o.o.b.e.p.p.ReRegistrationPipeline       : Process next Re-Registration events

...



Feed test data

To perform functional tests for BBS-ep, we must first populate test data to A&AI. This can be done by running the following Postman collection along with the required input file.

...

Code Block
languagebash
themeMidnight
titlePublished event
linenumberstrue
[
"{\"closedLoopEventClient\":\"DCAE.BBS_event_processor_mSInstance\",\"policyVersion\":\"1.0.0.5\",\"policyName\":\"CPE_Authentication\",\"policyScope\":\"policyScope\",\"target_type\":\"VM\",\"AAI\":{\"cpe.old-authentication-state\":\"outOfService\",\"cpe.new-authentication-state\":\"inService\",\"cpe.swVersion\":\"1.2.3\",\"service-information.hsia-cfs-service-instance-id\":\"1923eaa8-8ab7-49ef-b4c2-e185efbbe832\"},\"closedLoopAlarmStart\":1556102531,\"closedLoopEventStatus\":\"ONSET\",\"closedLoopControlName\":\"controlName\",\"version\":\"1.0.2\",\"target\":\"vserver.vserver-name\",\"requestID\":\"205f5550-37a0-4be7-be63-effefe181b37\",\"from\":\"DCAE-bbs-event-processor\"}"
]

Functional testing of VES-Mapper individually

  1. Send a PNF registration notification on behalf of RestConf Collector by calling DMaaP API
    1. curl -v -k -H 'Content-Type:application/json' -POST http://message-router.onap.svc.cluster.local:3904/events/unauthenticated.DCAE_RCC_OUTPUT -d @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.

...

\"from\":\"DCAE-bbs-event-processor\"}"
]