Versions Compared

Key

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

Date

Attendees

Recording:

Agenda

  • Status updatePast work on CM Handling with use of SDNR DB (Elastic Search / Maria DB?)
  • Discussion of CM Flow 


Notes:

Update: Priyank, Vishal, Murali are meeting regularly. Vishal team to deploy the latest CPS codebase to have full CM update implementation.

CM Flow: Shankar created sequence flow diagram for CM Update. Great discussion from team to update and improve accuracy of flow.

  • Discussion - OSC SMO project has changed from O1/VES handling to O2, Cloud and Service orchestration
  • SDNR has internal SDNRDB database (ElasticSearch) which is used for SDNR actions. This needs to be updated when there is a VES CM Update notification.
  • Feedback from Martin on CM flow - represented here as Target implementations even if not implemented currently in Montreal plan
    1) Cloud orchestration (e.g. ORMO) should be the interface to set up topology in RAN-Sim
    2) RANSim NF registration to SDNR via self-mount is ok, but target should be to use PNF Registratio
    3) When NF connection is established in SDNR, current implementation is to manually invoke CPSDMI API to register cmHandle. This can be automated with code in CPSDMI


Update flow is in See Config Management (CM) Sequence Flow - Developer Wiki - Confluence (onap.org)


-- notes from previous mtgs --

VES message example: See CPS-1434: VES Message to update CPS DB 

...