Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
...
This page describes the proposed architecture for the ONOS Web UI to support "federated ONOS". Right now it is just capturing initial thoughts...
| Warning |
|---|
After review, it was suggested that opening multiple web sockets from the UI (browser) was overcomplicating things. Since the subordinate clusters would need to be communicating with the uber cluster anyway, they should supply any data needed for UI visualization along the same channel. The UI should remain as a single web socket connection to the main controller/cluster. |
Web UI Connection Protocol
...
The UiWebSocket class would need to be enhanced to track the notion of whether the connection was MAIN or AUX. In this way, the UI resources / message handlers would be able to modify their behavior if needed.
Further Notes / Assumptions
- The topology view would work as it currently does, showing the "model" that is maintained at the Uber controller.
- In the Uber model, the clusters would appear as a single device – a "big switch".
- A "onos-federation-ui" application bundle (.oar file) would implement a topology overlay to:
- augment the detail panel when a "big-switch" device was selected, showing:
- additional data about the underlying topology
- a "display underlying topology" button
- pressing the button would launch a pop-up window, with the topology of the underlying network displayed**
- augment the detail panel when a "big-switch" device was selected, showing:
** This is where the auxiliary connection to the subordinate cluster would come in, to retrieve the "model" data.