From 77378982fde84326045c9eb998b47f6f7ad88ebb Mon Sep 17 00:00:00 2001 From: Jean-Yves Geury Date: Wed, 22 Apr 2020 22:43:35 +0200 Subject: [PATCH] bbs-ep documentation updates for DCAEGEN2-2105 - installation documentation MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Updates for bbs-ep installation from blueprint repository. Note : Also updated : • The “DCAE R6 BBS-EventProcessor Service (BBS Usecase)” documentation in https://wiki.onap.org/pages/viewpage.action?pageId=76875749 • The “installation.rst” file in https://gerrit.onap.org/r/c/dcaegen2/+/106464/2/docs/sections/services/bbs-event-processor/installation.rst Issue-ID: DCAEGEN2-2105 Signed-off-by: Geury Change-Id: Ief0a0f63b6281eef17cd53c877969a9b7a0e80ba --- components/bbs-event-processor/README.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/components/bbs-event-processor/README.md b/components/bbs-event-processor/README.md index 14ecc8ce..2a6fec01 100644 --- a/components/bbs-event-processor/README.md +++ b/components/bbs-event-processor/README.md @@ -16,27 +16,26 @@ use case architecture. Through RestConf-Collector or VES-Collector, these events (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. I +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. ## Installation and Removal BBS-ep is delivered as a Spring-Boot application ready to be deployed in Docker (via docker-compose). -For Dublin release, it will be a DCAE component that can dynamically be deployed via Cloudify blueprint installation. +BBS-ep can be dynamically deployed in DCAE’s Cloudify environment via its blueprint deployment artifact. + Steps to deploy are shown below - Transfer blueprint component file in DCAE bootstrap POD under /blueprints directory. Blueprint can be found in - -- Transfer blueprint component inputs file in DCAE bootstrap POD under / directory. Blueprint inputs file can be found in - + - Enter the Bootstrap POD - Validate blueprint - cfy blueprints validate /blueprints/k8s-bbs-event-processor.yaml-template + cfy blueprints validate /blueprints/k8s-bbs-event-processor.yaml - Upload validated blueprint - cfy blueprints upload -b bbs-ep /blueprints/k8s-bbs-event-processor.yaml-template + cfy blueprints upload -b bbs-ep /blueprints/k8s-bbs-event-processor.yaml - Create deployment - cfy deployments create -b bbs-ep -i /bbs-event-processor-input.yaml bbs-ep + cfy deployments create -b bbs-ep -i /blueprints/k8s-bbs-event-processor.yaml bbs-ep - Deploy blueprint cfy executions start -d bbs-ep install -- 2.16.6