Versions Compared

Old Version 5

changes.mady.by.user Z-Reshmi K R

Saved on

compared with

New Version 6

changes.mady.by.user Z-Reshmi K R

Saved on

Key

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

...

draw.io Diagram
bordertrue
diagramNameRDK VLAN Bridge Manager - Module Diagram
simpleViewerfalse
width
linksauto
tbstyletop
lboxtrue
diagramWidth333
revision34

Architecture

  1. OVSDB and WebPA can receive data from the Cloud in any format but they MUST translate this data into the DML syntax exposed by RDK VLAN & Bridging Manager and transmit this data to that module via the Bus.
  2. RDK VLAN & Bridging Manager stores a custom data model that allows for all OVS functionality (e.g. OpenFlow), as well as generic bridging/VLAN termination functionality.
    1. Basic bridge and VLAN configuration MUST be generic enough (where possible) such that it is not tied to any one particular implementation. 
    2. Some features (e.g. OpenFlow) will only be implementable using OVS, and therefore will not feature an equivalent Linux Utilities implementation.
  3. RDK VLAN & Bridging Manager's Southbound API can be used to translate configuration data into specific OVS or Linux Utilities commands, depending on the platform requirements.
    1. In some cases, OVS Bridging will have to be supported alongside Linux VLAN configuration. 
    2. In other cases, platforms may choose between a full OVS implementation or a full Linux Utilities implementation.
  4. In this design, the CPE bridge/VLAN configuration is decoupled from backend management services as well as from low-level utilities. This allows RDK-B to be more flexible in how it is managed from the cloud, and how it operates on a platform.

...