| | 180 | |
| | 181 | ==== (9/29) ==== |
| | 182 | A quick survey for distributed controllers brought up several examples: |
| | 183 | * Onix: A Distributed SDN control platform, which synchronizes controllers with a Network Information Base (NIB), which stores network state. Relies on a DHT + local storage. Oriented towards reliability, scalability, stability, and generalization. |
| | 184 | * !HyperFlow: A NOX application that allows multiple controllers to coordinate by subscribing to each other and distributing events that change controller state. Relies on WheelFS, a FUSE-based distributed filesystem. |
| | 185 | * Helios: A distributed controller by NEC. Cannot find a white-paper for this one. |
| | 186 | |
| | 187 | !HyperFlow is what this (attempted) controller seems to resemble the most. However, the point to make is that this controller should not be just another implementation of one of these controllers, or their characteristics. The model for the currently existing distributed controller seems to assume that of multiple controllers that all run the same application, and to allow that one application to scale. This contrasts from the distribution of functions across multiple controllers e.g. having each controller run a different application to "vertically" distribute the load (Vertical - splitting of a network stack into several pieces as opposed to the duplication of the same stack across multiple controllers). |
| | 188 | |
| | 189 | |
