You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Introduction
Architecture
- 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.
- 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.
- Basic bridge and VLAN configuration MUST be generic enough (where possible) such that it is not tied to any one particular implementation.
- Some features (e.g. OpenFlow) will only be implementable using OVS, and therefore will not feature an equivalent Linux Utilities implementation.
- 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.
- In some cases, OVS Bridging will have to be supported alongside Linux VLAN configuration.
- In other cases, platforms may choose between a full OVS implementation or a full Linux Utilities implementation.
- 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.
![](/download/thumbnails/169451135/RDKVLanBridge%20Manager.png?version=1&modificationDate=1632482271000&api=v2)