Page History

Overview

BBE-ep is responsible for handling two types of events for the BBS use case.

First are PNF re-registration internal events published by PRH. BBS-ep must process these internal events to understand if they

actually constitute ONT(CPE) relocation events. In the relocation case, it publishes an event towards unauthenticated.DCAE_CL_OUTPUT

DMaaP topic to trigger further Policy actions related to BBS use case.

Second type of events are CPE authentication events originally published by the Edge SDN M&C component of BBS use case architecture.

Through RestConf-Collector or VES-Collector, these events are consumed by BBS-ep and they are forwared towards unauthenticated.DCAE_CL_OUTPUT

DMaaP topic to trigger further Policy actions related to BBS use case.

BBE-ep periodically polls for the two events. Polling interval is configurable and can be changed dynamically from Consul. Its implementation

is based on Reactive Streams (Reactor library), so it is fully asynchronous and non-blocking.

Blueprint/model/image

Note: Provide links to gerrit/nexus artifacts

Deployment Prerequisite/dependencies

Deployment Steps

Β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/master
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=36e69cf64bee3b46ee2e1b95f1a16380b7046482;hb=refs/heads/master

Docker image 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

BBS-ep requires DMaaP and A&AI to be functional in ONAP.

It consumes/publishes messages from DMaaP and it also fetches (never updates) information from A&AI related to the BBS use-case logic.

Deployment Steps

To deploy

• Transfer blueprint component file in DCAE bootstrap POD under /blueprints directory
• Transfer blueprint component inputs file in DCAE bootstrap POD under / directory
• Log-in to the DCAE bootstrap POD's main container

• Validate blueprint

  
  

  Code Block
  language bash theme Midnight title Validate Blueprint linenumbers true
  cfy blueprints validate /blueprints/k8s-bbs-event-processor.yaml-template

  
  

• Upload validated blueprint
  
  

  Code Block
  language bash theme Midnight title Upload validated blueprint linenumbers true
  cfy blueprints upload -b bbs-ep /blueprints/k8s-bbs-event-processor.yaml-template

• Create Cloudify Deployment

  
  

  Code Block
  language bash theme Midnight title Create Cloudify deployment linenumbers true
  cfy deployments create -b bbs-ep -i /bbs-event-processor-input.yaml bbs-ep

  
  

• Deploy component
  
  

  Code Block
  language bash theme Midnight title Deploy component linenumbers true
  cfy executions start -d bbs-ep install

  
  

To undeploy

• Uninstall running component and delete deployment
  
  

  Code Block
  language bash theme Midnight title Uninstall component linenumbers true
  cfy uninstall bbs-ep

  
  

• Delete blueprint
  
  

  Code Block
  language bash theme Midnight title Delete blueprint linenumbers true
  root@cluster-admin:~# kubectl -n onap get pods | grep -i bbs dep-bbs-event-processor-6b6df75d94-g7jw8 2/2 Running 0 1d

  
  

Validation

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

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

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.

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

...