On 01/15/15 at 07:04am, Gurucharan Shetty wrote: > On Thu, Jan 15, 2015 at 4:06 AM, Thomas Graf <tg...@noironetworks.com> wrote: > > On 01/15/15 at 03:36pm, YAMAMOTO Takashi wrote: > >> > On Thu, Jan 15, 2015 at 10:38:45AM +0900, YAMAMOTO Takashi wrote: > >> >> > ovn-controller > >> >> > -------------- > >> >> > >> >> neutron "ofagent" agent has a similar design to ovn-controller. > >> >> you might be able to reuse at least some of code if python+ryu > >> >> is acceptable. > >> >> > >> >> https://github.com/openstack/neutron/tree/stable/juno/neutron/plugins/ofagent > >> > > >> > I didn't know that there was an existing local controller. I'll learn > >> > something about the design. > >> > >> similar: > >> > >> - it's a local OpenFlow controller running on each nodes > >> > >> - it has ARP suppression feature implemented with packet-ins > >> (called "local arp responder" there) > >> > >> different: > >> > >> - ofagent doesn't have a layer equivalent to "OVN database". > >> it obtains the necessary info from its CMS (neutron) directly > > > > Another local controller to look at is the OpFlex OVS agent which runs > > locally as well and uses libopenvswitch and libofproto to talk OF/OVSDB > > to OVS. (I think OVN should be built on top of the now exposed shared > > libraries as well). > A point to be noted while taking a decision is that there is currently > no capability to build shared libraries on Windows platform.
Good point. I don't know enough about packaging on Windows to know whether fall back to static linking for Windows would impose any packaging/distribution problems. On Linux, the shared library dependency would simplify the packaging in Linux distributions. (A bug in OF code must be pushed to both OVS and OVN packages.) _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
