| 75 | | |
| | 75 | ==== (9/10): ==== |
| | 76 | Beginning of creating a basis for controllers that can be connected together. Tentatively calling the controllers that are going to be part of the hierarchy "units", as in, "units of control". |
| | 77 | |
| | 78 | This involved taking `OFChannelHandler` and creating something similar to it, for connections from (down-links to) other controllers. At first represented connections from units as their own implementations, then figured this was problematic if the packets from the controllers are to be handled by the modules. This means it makes sense to represent the connections from other controllers as `OFSwitchImpl`s. |
| | 79 | |
| | 80 | Two new mock-OFProtocol types were created for inter-unit messaging. |
| | 81 | |
| | 82 | * OFUnitServiceRequest: request for list of services from unit |
| | 83 | * OFUnitServiceReply: relevant service information |
| | 84 | |
| | 85 | The service reply will probably communicate a service type (topology, network storage, etc.) and a location to find it, such as port on a datapath where a NAS is located (if network storage). This is basically a way for the network to advertise location of services to topology-aware elements, as opposed to a server attached to a network doing the adverts for hosts. |
| | 86 | |
