Versions Compared

Key

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

...

  • Onboarding (design)
    • The mS owner identifies the input and output stream in spec file. The actual topic/feed and access credentials are
  • Runtime
    • Plugins (Dmaap and K8SPlugin)
      • These are cloudify plugins bootstrapped into DCAE Cloudify Manager during platform instantiation. The plugins provides interface/function to implement specific function. The plugins are referenced based on node type in the blueprint (deployment artifact for DCAE MS).
    • DMaap Bus Controller (DBCL)
      • DMaap Bus Controller provides API to serve new feed and topic creation requests
    • ConfigBindingService
      • DCAE Platform Component providing standardized API for DCAE Microservice to retrieve configuration including Dmaap topic/feed configuration dynamically provisioned.
    • Consul KV
      • Key-Value store where all service component configuration are stored during deployment.

<Flow/sequence diagram to be added>


PlantUML Macro
titleSequenceFlowForDmaapPlugin
@startuml
title DMAAP plugin sequence flow
box  "DCAE Onboarding"
actor MS_Developer as a1 #green 
participant "Bp-gen" as a2
entity DCAE_MS_Blueprint as a3 #blue
end box 
box "DCAE-DMAAP Runtime" #f4c69f

participant "Dashboard" as c0
participant "Cloudify \n(K8S & DMaaP\n plugin)" as c

participant "DMAAP BC" as c1
participant "DMAAP" as c2
entity "TOPIC/FEED"  as c3

database Consul as c4
participant "DCAE MS" as c5
end box

autonumber

a1 -> a2 : Creates component\n spec specifying \n publish/subscribes\n streams (topic/feed) 
a2 -> a3 : Generates cloudify \nblueprint
a3 -> a1
a1 -> c0 : "Blueprint upload\n and deploy"
c0 -> c : "dcae.nodes.Containerized\nServiceComponentUsingDmaap"
c -> c1 : "invokes buscontroller api\n type=ccsdk.nodes.Feed\nccsdk.nodes.Topic\n"
c1 -> c1 : check AAF role/namespace
c1 <-> c2 : Provisions new feed/topic
c2 <-> c3
c1 -> c : returns topic/feed along\n with aaf credential
c -> c4 : KV store updated \n for corresponding service
c5 -> c4 : retrieves dmaap \n configuration using \ncbs api
c5 -> c3 : Publish/subscribes to topic/feed
@enduml

EL-Alto Usecase

The 5G Bulk PM components, namely DataFile Collector and PM-Mapper were deployed using Dmaap Plugin integration for El-Alto .<usecase reference to be added>as prototype to validate the secure & dynamic feed/topic provisioning feature.

The complete flow for the usecase 5G Bulk PM flow can be referred here - 5G - Bulk PM (Casablanca carry-over items).

This usecase enabled validation of both DMaap Message-router and Data-Router case for both publisher and subscriber MS.

DataFile Collector : Subscribe from MR topic, publish files into DR feed

PM-Mapper : Subscribes from DR Feed; publish into MR topic

Demo

Scope

  • Review blueprint configuration for DFC
  • Deployment for DFC (via dashboard)
  • Validation of new feed created
  • Review blueprint configuration for PM-Mapper
  • Deployment of PM-Mapper (via dashboard)
  • Validation of new feed/topic created
  • Sample data flow

...