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 (in unauthenticated.PNF_UPDATE DMaaP topic). 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 (in unauthenticated.CPE_AUTHENTICATION DMaaP topic) and they are forwarded 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.
BBS-ep is delivered as a Spring-Boot application ready to be deployed in Docker (via docker-compose).
BBS-ep can be dynamically deployed in DCAE’s Cloudify environment via its blueprint deployment artifact.
Blueprint can be found in
https://git.onap.org/dcaegen2/platform/blueprints/tree/blueprints/k8s-bbs-event-processor.yaml
Steps to deploy are shown below
To un-deploy BBS-ep, steps are shown below
For more details about the exact flows and where BBS-EP fits in the overall BBS flows, visit use case official documentation
BBS-ep is a sub-project of dcaegen2/services (inside components directory). To build just the BBS-ep component, run the following maven command from within components/bbs-event-processor directory
mvn clean install
Running with dev-mode of BBS-ep