Shared libraries on Windows could be implemented as DLLs (Dynamic Link Libraries) with some custom support for versioning. This means also that updates of new versions of the DLLs should controlled by a custom installer.
-----Original Message----- From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Thomas Graf Sent: Thursday, January 15, 2015 7:19 AM To: Gurucharan Shetty Cc: dev; YAMAMOTO Takashi Subject: Re: [ovs-dev] OVN architecture 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://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_ > >> >> openstack_neutron_tree_stable_juno_neutron_plugins_ofagent&d=AwI > >> >> GaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExL > >> >> XY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=BOjy7uXWvQ7_zay-Yzf-Z2zPIMCBc5 > >> >> NiTCjTNxYAdYU&s=bQdLaLSSbfeFOSxAm6ke5xfCzrQA39wkiG0g_ZcR04U&e= > >> > > >> > 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 https://urldefense.proofpoint.com/v2/url?u=http-3A__openvswitch.org_mailman_listinfo_dev&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=BOjy7uXWvQ7_zay-Yzf-Z2zPIMCBc5NiTCjTNxYAdYU&s=UyabyhKPWJeZTHnkqZ2RX5jEpNn_edhyd3ljIMS0sN4&e= _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
