This group is locked. No changes can be made to the group while it is locked.
Re: [openflowplugin-dev] [controller-dev] Openflow Protocol Library
i would like to summarize our thoughts behind OF Protocol Library architecture and react to given suggestions.
In the current architecture one of the main responsibility of southboundI agree. But it is not defined how southbound protocol plugin has to implement this functionality - if it must be implemented directly or if the plugin can use other component (or library) to achieve this.
Other responsibilities of the protocol plugin ( discovery/inventory service, dataWith right API design connection handling could be exposed to the plugin and the plugin could still control things like acceptance on session, capability negotiation and other funcionalities. However, base pieces of this functionality could be in library.
In the proposed design of protocol library, I think pipeline processing andThe location of code and functionality in OF protocol library vs. southbound plugin does not prevent creating comprehensive solution, but this functionality is not southbound protocol plugin specific. With right API design, the plugin could use or customize it to its specific needs.
Component 6 (OF 1.3 CoDec) can be a static library on the similarBy implementing this architecture model in the protocol library it allows library to be used also outside of the controller without the need to extract logic from the southbound protocol plugin.