Alin, My suggestion would be to hold off on finalizing the documentation until we squash all the pending bugs. Looks like we are getting there.
Thanks, -- Nithin On Feb 4, 2017, at 12:21 AM, Alin Serdean <aserd...@cloudbasesolutions.com<mailto:aserd...@cloudbasesolutions.com>> wrote: Hard dependancy on default internal port (AllowManagementOS) has been removed. Software checksums are part of the windows datapath. Disconnecting/Connecting the VIF is no longer required. Unit tests are enabled and passing for some time now... The option to create a MSI has been added. Signed-off-by: Alin Gabriel Serdean <aserd...@cloudbasesolutions.com<mailto:aserd...@cloudbasesolutions.com>> --- Documentation/intro/install/windows.rst | 50 +++++++++------------------------ 1 file changed, 13 insertions(+), 37 deletions(-) diff --git a/Documentation/intro/install/windows.rst b/Documentation/intro/install/windows.rst index caa9f40..1e7707f 100644 --- a/Documentation/intro/install/windows.rst +++ b/Documentation/intro/install/windows.rst @@ -117,21 +117,6 @@ The following explains the steps in some detail. under Bash. The remainder, prefixed by ``>``, are PowerShell commands and must be run in PowerShell. -Install Requirements --------------------- - -* Share network adaptors - - We require that you don't disable the "Allow management operating system to - share this network adapter" under 'Virtual Switch Properties' > 'Connection - type: External network', in the HyperV virtual network switch configuration. - -* Checksum Offloads - - While there is some support for checksum/segmentation offloads in software, - this is still a work in progress. Till the support is complete we recommend - disabling TX/RX offloads for both the VM's as well as the HyperV. - Bootstrapping ------------- @@ -287,16 +272,15 @@ Enforcement' during boot. The following commands can be used: You may have to restart the machine for the settings to take effect. In the Virtual Switch Manager configuration you can enable the Open vSwitch -Extension on an existing switch or create a new switch. If you are using an -existing switch, make sure to enable the "Allow Management OS" option for VXLAN -to work (covered later). +Extension on an existing switch or create a new switch. The command to create a new switch named 'OVS-Extended-Switch' using a physical NIC named 'Ethernet 1' is: .. code-block:: ps1con - PS > New-VMSwitch "OVS-Extended-Switch" -NetAdapterName "Ethernet 1" + PS > New-VMSwitch "OVS-Extended-Switch" -NetAdapterName "Ethernet 1" ` + -AllowManagementOS $false .. note:: @@ -517,22 +501,17 @@ assign a 'OVS port name' which is a unique name across all VIFs on this Hyper-V. The next step is to add the VIF to the ovsdb using its 'OVS port name' as key. -First, assign a unique 'OVS port name' to the VIF. The VIF needs to have been -disconnected from the Hyper-V switch before assigning a 'OVS port name' to it. -In the example below, we assign a 'OVS port name' called ``ovs-port-a`` to a -VIF on a VM ``VM1``. By using index 0 for ``$vnic``, the first VIF of the VM -is being addressed. After assigning the name ``ovs-port-a``, the VIF is -connected back to the Hyper-V switch with name ``OVS-HV-Switch``, which is -assumed to be the Hyper-V switch with OVS extension enabled.: +First, assign a unique 'OVS port name' to the VIF. In the example below, we +assign a 'OVS port name' called ``ovs-port-a`` to a VIF on a VM ``VM1``. By +using index 0 for ``$vnic``, the first VIF of the VM is being addressed. We +assume that OVS extension is enabled on the Hyper-V vSwitch to which the VIF is +connected: .. code-block:: ps1con PS > import-module .\datapath-windows\misc\OVS.psm1 PS > $vnic = Get-VMNetworkAdapter <Name of the VM> - PS > Disconnect-VMNetworkAdapter -VMNetworkAdapter $vnic[0] PS > $vnic[0] | Set-VMNetworkAdapterOVSPort -OVSPortName ovs-port-a - PS > Connect-VMNetworkAdapter -VMNetworkAdapter $vnic[0] \ - -SwitchName OVS-Extended-Switch Next, add the VIFs to ``br-int``: @@ -556,8 +535,6 @@ Dumping the ports should show the additional ports that were just added: ovs-vsctl show 4cd86499-74df-48bd-a64d-8d115b12a9f2 Bridge br-pif - Port "vEthernet (external)" - Interface "vEthernet (external)" Port "Ethernet0" Interface "Ethernet0" Port br-pif @@ -677,9 +654,9 @@ Re-Add the VIF ports with the VLAN tag: Add tunnels ~~~~~~~~~~~ -The Windows Open vSwitch implementation support VXLAN and STT tunnels. To add -tunnels. For example, first add the tunnel port between 172.168.201.101 <-> -172.168.201.102: +Let us add tunnels between two endpoints. +For example, first add the tunnel port between +172.168.201.101 <-> 172.168.201.102: .. code-block:: doscon @@ -791,9 +768,8 @@ his development repository in github and triggering a new build. TODO ---- -* Investigate the working of sFlow on Windows and re-enable the unit tests. +* Investigate the working of sFlow on Windows. * Investigate and add the feature to provide QoS. -* Sign the driver & create an MSI for installing the different OpenvSwitch - components on Windows. +* Sign the driver -- 2.10.2.windows.1 _______________________________________________ dev mailing list d...@openvswitch.org<mailto:d...@openvswitch.org> https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddev&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=-xl6DPE_Y3uQD-mpZD7osBo2iL4s3jwdmSjTlGgjlsQ&m=SQCZQhfAP01Ac1gx1213M5gpQgJc2OXdAhqaoDBopQo&s=71jTIFCZuFRonV_WWZpJgAHQdssF6w3XfCC3Js39lFM&e= _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
