[ovs-git] [openvswitch/ovs] 7a9830: msi: add ovs-vswitchd trigger info

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/openvswitch/ovs
  Commit: 7a983037025d93745699296bda5fb92367822343
      https://github.com/openvswitch/ovs/commit/7a983037025d93745699296bda5fb92367822343
  Author: Alin Serdean <aserdean at cloudbasesolutions.com>
  Date:   2017-02-27 (Mon, 27 Feb 2017)

  Changed paths:
    M windows/ovs-windows-installer/CustomActions.wxs
    M windows/ovs-windows-installer/Product.wxs

  Log Message:
  -----------
  msi: add ovs-vswitchd trigger info

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 at cloudbasesolutions.com>
Acked-by: Sairam Venugopal <vsairam at vmware.com>
Signed-off-by: Gurucharan Shetty <guru at ovn.org>