Versions Compared

Old Version 6

changes.mady.by.user Priyank Maheshwari

Saved on

compared with

New Version 7

changes.mady.by.user Priyank Maheshwari

Saved on

Key

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

...

#

Issue

Notes 

Decision

1Do we persist the incoming CM Data AVC Event in our database ?

2Which model to be used for the data in the cache ?

3Who will upload the model ? will it be done using our model-loader way ?

4How will the data be uploaded which will later be updated ?

5What happens once the data is updated ? Is cps-core responsible to send out the updated events ? 

6Frequency of VES message , which determines the frequency of Data AVC events.

7Which datastore to be used in CPS?


Overview

  • What is happening now ? 


PlantUML Render Macro
titleSON_CPS_EXISTING
@startuml "Existing CPS SON Use Case"

participant VES_COLLECTOR
participant DMI_PLUGIN
participant NCMP
participant KAFKA

VES_COLLECTOR -> DMI_PLUGIN : Ves Standard Message
DMI_PLUGIN -> DMI_PLUGIN : Reads and Transforms VES Msg to DMI Data AVC Cloud Event
DMI_PLUGIN -> NCMP : DMI Data AVC Event
NCMP -> KAFKA : NCMP just forwards the DMI Data AVC to cm-events topic
@enduml


  • What we want to achieve ?


PlantUML Render Macro
titleSON_CPS_TARGET
@startuml "Existing CPS SON Use Case"

participant VES_COLLECTOR
participant DMI_PLUGIN
participant NCMP
participant CPS_CORE
participant KAFKA

VES_COLLECTOR -> DMI_PLUGIN : Ves Standard Message
DMI_PLUGIN -> DMI_PLUGIN : Reads and Transforms VES Msg to DMI Data AVC Cloud Event
DMI_PLUGIN -> NCMP : DMI Data AVC Event
NCMP -> NCMP : Parses DMI Data AVC Event
NCMP -> CPS_CORE : delegates the "Replace" operation to CPS-CORE
CPS_CORE -> CPS_CORE : Performs the PATCH operation and updates the existing data
NCMP -> KAFKA : NCMP forwards the DMI Data AVC to cm-events topic
@enduml