> On 16 Mar 2015, at 02:41, Ben Pfaff <b...@nicira.com> wrote: > > On Mon, Mar 16, 2015 at 12:33:09AM +0000, Alessandro Pilotti wrote: >> As discussed on IRC, here's the Windows MSI installer project that we’d like >> to >> submit for upstream inclusion: >> >> https://github.com/cloudbase/ovs-windows-installer >> >> The included README.rst provides information on how to generate the MSI and >> I’ll also be happy to answer any question and review. >> >> In terms of location of the code, we could IMO either include the installer >> as >> a separate project on https://github.com/openvswitch or as a subfolder under >> the https://github.com/openvswitch/ovs project itself. >> My vote is for the first option, but if you guys prefer the second I’ll be >> happy to send the full patchset on the ML for review. > > Thanks for writing this and publishing it! > > One factor in deciding whether this should be part of the OVS tree or > part of a separate tree is how closely coupled it is with the rest of > the OVS tree. If it's likely that changes to OVS (new files or > whatever) would require changes in the installer, then that makes me > tend to believe that the installer should be part of the OVS tree, > because then it becomes possible to fix up the installer in the same > commit that changes OVS. That is one reason that it is nice to have, > for example, the Debian and Red Hat packaging in the OVS tree. What are > your thoughts on that issue? (I have not looked at the installer tree.) > > Thanks, > > Ben.
We kept the coupling between the installer and the OVS projects as loose as possible. For example the installer build makes no assumptions on the content of the CLI binaries folder (ovs-vsctl.exe, etc), it just takes whatever the OVS build process generated and includes the binaries in the installer. The only real coupling is in the fact that we expect to have one kernel driver and two Windows services (daemons): ovs-vswitchd and ovsdb-server. This means that changes to the project are required in case a new daemon or driver is going to be added, but I expect this to be a very rare scenario. Alessandro _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
