From patchwork Sat Feb 4 08:21:14 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Alin Serdean X-Patchwork-Id: 724018 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from mail.linuxfoundation.org (mail.linuxfoundation.org [140.211.169.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 3vFmt83jmQz9s75 for ; Sat, 4 Feb 2017 19:21:52 +1100 (AEDT) Received: from mail.linux-foundation.org (localhost [127.0.0.1]) by mail.linuxfoundation.org (Postfix) with ESMTP id 71407910; Sat, 4 Feb 2017 08:21:19 +0000 (UTC) X-Original-To: dev@openvswitch.org Delivered-To: ovs-dev@mail.linuxfoundation.org Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id AF71C5A7 for ; Sat, 4 Feb 2017 08:21:17 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail.cloudbasesolutions.com (mail.cloudbasesolutions.com [91.232.152.5]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 9ACF4135 for ; Sat, 4 Feb 2017 08:21:16 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.cloudbasesolutions.com (Postfix) with ESMTP id B7C63408BD for ; Sat, 4 Feb 2017 10:21:15 +0200 (EET) X-Virus-Scanned: amavisd-new at cloudbasesolutions.com Received: from mail.cloudbasesolutions.com ([127.0.0.1]) by localhost (mail.cloudbasesolutions.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w9dhocf_PMAk for ; Sat, 4 Feb 2017 10:21:15 +0200 (EET) Received: from mail.cloudbasesolutions.com (unknown [10.77.78.3]) by mail.cloudbasesolutions.com (Postfix) with ESMTP id 3319640275 for ; Sat, 4 Feb 2017 10:21:15 +0200 (EET) Received: from CBSEX1.cloudbase.local ([10.77.78.3]) by CBSEX1.cloudbase.local ([10.77.78.3]) with mapi id 14.03.0319.002; Sat, 4 Feb 2017 09:21:14 +0100 From: Alin Serdean To: "dev@openvswitch.org" Thread-Topic: [PATCH 1/4] doc-windows: Remove obsolete documentation Thread-Index: AQHSfr+mS0BPjEm23EqIkCduhVUFCA== Date: Sat, 4 Feb 2017 08:21:14 +0000 Message-ID: <20170204082101.17928-1-aserdean@cloudbasesolutions.com> Accept-Language: en-US, it-IT Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.77.78.1] MIME-Version: 1.0 X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: [ovs-dev] [PATCH 1/4] doc-windows: Remove obsolete documentation X-BeenThere: ovs-dev@openvswitch.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: ovs-dev-bounces@openvswitch.org Errors-To: ovs-dev-bounces@openvswitch.org 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 --- 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 - 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