Introduction

...

 High level Design / Architecture

OVSDB Manager 

               Cloud controller can configure Wi-Fi parameters in gateway, extender or  CPE using OVSDB & Manager entities. OVSDB is a database server that executes in RDK-B CPE. Any update of parameters in this database by cloud controller is notified to OneWifi process by OVSDB manager entity over RBUS. OneWifi process validates the parameter or set of parameters and applies the configuration in WiFi driver or baseband. If successfully applied, OneWifi also notifies OVSDB manager about the successful completion so that the database tables are updated with the right state of WiFi subsystem of the CPE.

OneWiFi Interface Mapping

Identified task list

• Need to learn how OpenSync work with OneWiFi - Communication is through DM/RBUS, not wifi hal. May need to refer Comcast device.

• Need to compile OpenSync for OneWifi (some kconfig should be enabled)

• Need to know how to start OpenSync through OneWiFi

• Need to know OVSDB tables of OpenSync collaborate with OVSDB tables of OneWiFi(wifi.db)

• Bringup OVSDB manager for synchronization

• Wi-Fi interface alignment with Netgear wifi dongle and  Make sure existing wifi functionality won't be disturbed.

• Netgear driver support with 2.0 USB port

• Conversion of Linux bridge into OVS bridge(brlan0) - OVSAgent is now part of rootfs but not operational

• Update dnsmasq configuration for OpenSync backhaul AP feature (wifi2, wifi3)

• Enable IP_GRE as kernel module

• Home AP bringup in RPI GW

• Backhaul AP bringup in RPI GW

• Make sure that GRE tunnel is created for backhaul communication and it is stable (Need to be tested with Extender)

• Need to make sure that onewifi existing functionality is not breaking

Check point

• Need to confirm that rdk-wifi-hal is aligned for OpenSync [Already we have OpenSync in Comcast onewifi(driver based) enabled device]

Dependencies

• Dongle's minimal support for 2AP and 1 STA.

• If Netgear dongle is not providing such support, need to find new WiFi dongle.

• Device provisioning in Plume Inventory (require Plume's support)

• ovsdb manager/OVSM acts as medium between onewifi webconfig subdoc  and plume controller
• Opensync have run-time dependencies with ovsdb-server & openvswitch(ovsdb-server start up is part of ovsagent . currently, this server is not running in rpi).

Considerations

Start the integration activity either in dunfell or kirkstone feature branch

• if we go with dunfell, we may need to put extra effort for kirkstone based build

• dunfell may be supported for next few releases.

• if we want to go with dunfell based build, its better to start with 64bit build

Validation

• Check opensync service / Opensync process will be run by meshagent DM parameter

• Check opensync managers

• Check Manager table for Online status

• Associate RPI4 extender with RPI4 gateway

• check ovsdb and wifi db table updation if any action taken in plume NOC / RDK WebUI

Flow Diagram/Pseudo Code

Sequence Diagrams

...