summaryrefslogtreecommitdiff
path: root/windows/ovs-windows-installer/CustomActions.wxs
Commit message (Collapse)AuthorAgeFilesLines
* MSI: Use platform specific netcfg locationAlin Gabriel Serdean2018-01-051-2/+7
| | | | | | | | | | | | We use the command `netcfg` to install the Windows datapath. Since we have both 32 and 64 bit installers available point it to the platform specific binary. Found while testing. Signed-off-by: Alin Gabriel Serdean <aserdean@ovn.org> Acked-by: Ben Pfaff <blp@ovn.org>
* msi: add ovs-vswitchd trigger infoAlin Serdean2017-02-271-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | This patch changes the service ovs-vswitchd from "auto" execution to "demand" start. This patch also introduces a custom action for the ovs-vswitchd service in which the following command will be executed before the service startup: sc triggerinfo ovs-vswitchd \ start/strcustom/6066F867-7CA1-4418-85FD-36E3F9C0600C/VmmsWmiEventProvider The above command is a service trigger available since Windows 7. More on the topic: https://msdn.microsoft.com/en-us/library/windows/desktop/dd405513%28v=vs.85%29.aspx In out case we will wait until Microsoft-Windows-Hyper-V-VMMS has triggered that the WMI provider: VmmsWmiEventProvider has started. The change is needed because the network service inside VMMS starts slower than ovs-vswitchd, which will cause a race condition because we check if the OVS extension is enabled on a single switch. Signed-off-by: Alin Gabriel Serdean <aserdean@cloudbasesolutions.com> Acked-by: Sairam Venugopal <vsairam@vmware.com> Signed-off-by: Gurucharan Shetty <guru@ovn.org>
* This commit adds the windows installer to the OVS tree.Alin Gabriel Serdean2015-06-071-0/+67
Requirements are the following: Visual Studio Community 2013 WiX Toolset 3.9 Microsoft_VC120_CRT_x86.msm More detailed information on the requirements and build instructions can be found under: https://github.com/cloudbase/ovs-windows-installer/blob/master/README.rst To run and make the installer issue the following: ./boot.sh ./configure CC=./build-aux/cccl LD="`which link`" \ LIBS="-lws2_32 -liphlpapi" --prefix="C:/openvswitch/usr" \ --localstatedir="C:/openvswitch/var" --sysconfdir="C:/openvswitch/etc" \ --with-pthread="C:/pthread" --with-vstudiotarget="Release" make clean && make -j16 windows_installer To uninstall one could use the following Powershell commandlets: $app = Get-WmiObject -Class Win32_Product | Where-Object ` { $_.Name -match "Open Vswitch" } $app.Uninstall() Signed-off-by: Alin Gabriel Serdean <aserdean@cloudbasesolutions.com> Co-authored-by: Alessandro Pilotti <apilotti@cloudbasesolutions.com> Signed-off-by: Alessandro Pilotti <apilotti@cloudbasesolutions.com> Signed-off-by: Gurucharan Shetty <gshetty@nicira.com>