You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
Introduction
RDKVLAN&BridgeManager is a component that interfaces directly with the RDK Bus.
It is responsible for:
- Supporting bridges and VLAN interfaces
- Storing configuration and statistical data for bridges and VLAN interfaces
- Creating/deleting the bridges or interfaces
- And communicating the status of the bridges or interfaces with other RDK Managers
The following diagram shows how RDKVLAN&BridgeManager sits in the RDK-B architecture as well as its internal processes:
eyJleHRTcnZJbnRlZ1R5cGUiOiIiLCJnQ2xpZW50SWQiOiIiLCJjcmVhdG9yTmFtZSI6IlotUmVzaG1pIEsgUiIsIm91dHB1dFR5cGUiOiJibG9jayIsImxhc3RNb2RpZmllck5hbWUiOiJaLVJlc2htaSBLIFIiLCJsYW5ndWFnZSI6ImVuIiwidWlDb25maWciOiJ7fSIsImRpYWdyYW1EaXNwbGF5TmFtZSI6IiIsInNGaWxlSWQiOiIiLCJhdHRJZCI6IjE2OTQ1MjU2NCIsImRpYWdyYW1OYW1lIjoiUkRLIFZMQU4gQnJpZGdlIE1hbmFnZXIgLSBNb2R1bGUgRGlhZ3JhbSIsImFzcGVjdCI6IiIsImxpbmtzIjoiYXV0byIsImNlb05hbWUiOiJSZGtWbGFuQnJpZGdlTWFuYWdlciIsInRic3R5bGUiOiJ0b3AiLCJjYW5Db21tZW50IjpmYWxzZSwiZGlhZ3JhbVVybCI6IiIsImNzdkZpbGVVcmwiOiIiLCJib3JkZXIiOnRydWUsIm1heFNjYWxlIjoiMSIsIm93bmluZ1BhZ2VJZCI6MTY5NDUxMTM1LCJlZGl0YWJsZSI6ZmFsc2UsImNlb0lkIjoxNjk0NTI1NzAsInBhZ2VJZCI6IiIsImxib3giOnRydWUsInNlcnZlckNvbmZpZyI6eyJlbWFpbHByZXZpZXciOiIxIn0sIm9kcml2ZUlkIjoiIiwicmV2aXNpb24iOjEsIm1hY3JvSWQiOiI4YmNjMDc4ZC0wNTMzLTQ0N2UtOWE3ZC1kMGM2ZDY4YjA5YmQiLCJwcmV2aWV3TmFtZSI6IlJESyBWTEFOIEJyaWRnZSBNYW5hZ2VyIC0gTW9kdWxlIERpYWdyYW0ucG5nIiwibGljZW5zZVN0YXR1cyI6Ik9LIiwic2VydmljZSI6IiIsImlzVGVtcGxhdGUiOiIiLCJ3aWR0aCI6IjM0NiIsInNpbXBsZVZpZXdlciI6ZmFsc2UsImxhc3RNb2RpZmllZCI6MTYzMzAwNDU0NjAwMCwiZXhjZWVkUGFnZVdpZHRoIjpmYWxzZSwib0NsaWVudElkIjoiIn0=
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.