From patchwork Wed Sep 23 00:45:31 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Alin Serdean X-Patchwork-Id: 521519 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from archives.nicira.com (unknown [IPv6:2600:3c00::f03c:91ff:fe6e:bdf7]) by ozlabs.org (Postfix) with ESMTP id 4BEF114010F for ; Wed, 23 Sep 2015 10:46:12 +1000 (AEST) Received: from archives.nicira.com (localhost [127.0.0.1]) by archives.nicira.com (Postfix) with ESMTP id 5342010760; Tue, 22 Sep 2015 17:46:11 -0700 (PDT) X-Original-To: dev@openvswitch.org Delivered-To: dev@openvswitch.org Received: from mx3v1.cudamail.com (mx3.cudamail.com [64.34.241.5]) by archives.nicira.com (Postfix) with ESMTPS id CE1121070F for ; Tue, 22 Sep 2015 17:46:09 -0700 (PDT) Received: from bar3.cudamail.com (bar1 [192.168.15.1]) by mx3v1.cudamail.com (Postfix) with ESMTP id 95AD0618C1D for ; Tue, 22 Sep 2015 18:46:05 -0600 (MDT) X-ASG-Debug-ID: 1442969160-03dd7b044508bf0001-byXFYA Received: from mx3-pf3.cudamail.com ([192.168.14.3]) by bar3.cudamail.com with ESMTP id eAhIzIvdA38rqz6x (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 22 Sep 2015 18:46:01 -0600 (MDT) X-Barracuda-Envelope-From: aserdean@cloudbasesolutions.com X-Barracuda-RBL-Trusted-Forwarder: 192.168.14.3 Received: from unknown (HELO cbssmtp1.cloudbase.local) (91.232.152.5) by mx3-pf3.cudamail.com with SMTP; 23 Sep 2015 00:45:54 -0000 Received-SPF: pass (mx3-pf3.cudamail.com: SPF record at cloudbasesolutions.com designates 91.232.152.5 as permitted sender) X-Barracuda-Apparent-Source-IP: 91.232.152.5 X-Barracuda-RBL-IP: 91.232.152.5 Received: from localhost (localhost [127.0.0.1]) by cbssmtp1.cloudbase.local (Postfix) with ESMTP id CC1404217F for ; Wed, 23 Sep 2015 03:45:53 +0300 (EEST) X-Virus-Scanned: amavisd-new at cloudbasesolutions.com Received: from cbssmtp1.cloudbase.local ([127.0.0.1]) by localhost (cbssmtp1.cloudbase.local [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UEsDY6CNhpgT for ; Wed, 23 Sep 2015 03:45:33 +0300 (EEST) Received: from CBSEX1.cloudbase.local (unknown [10.77.78.3]) by cbssmtp1.cloudbase.local (Postfix) with ESMTP id 62CF94213B for ; Wed, 23 Sep 2015 03:45:33 +0300 (EEST) Received: from CBSEX1.cloudbase.local ([10.77.78.3]) by CBSEX1.cloudbase.local ([10.77.78.3]) with mapi id 14.03.0224.002; Wed, 23 Sep 2015 02:45:33 +0200 X-CudaMail-Envelope-Sender: aserdean@cloudbasesolutions.com From: Alin Serdean To: "dev@openvswitch.org" X-CudaMail-MID: CM-V3-921070201 X-CudaMail-DTE: 092215 X-CudaMail-Originating-IP: 91.232.152.5 Thread-Topic: [PATCH] datapath-windows: Update documentation X-ASG-Orig-Subj: [##CM-V3-921070201##][PATCH] datapath-windows: Update documentation Thread-Index: AQHQ9ZkmU4AGAq+iq0yX6HHXFRzT3g== Date: Wed, 23 Sep 2015 00:45:31 +0000 Message-ID: <1442969144-12564-1-git-send-email-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-GBUdb-Analysis: 0, 91.232.152.5, Ugly c=0.279065 p=-0.466667 Source Normal X-MessageSniffer-Rules: 0-0-0-11302-c X-Barracuda-Connect: UNKNOWN[192.168.14.3] X-Barracuda-Start-Time: 1442969161 X-Barracuda-Encrypted: DHE-RSA-AES256-SHA X-Barracuda-URL: https://web.cudamail.com:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at cudamail.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.10 X-Barracuda-Spam-Status: No, SCORE=0.10 using per-user scores of TAG_LEVEL=3.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=3.0 tests=RDNS_NONE X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.22806 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.10 RDNS_NONE Delivered to trusted network by a host with no rDNS Subject: [ovs-dev] [PATCH] datapath-windows: Update documentation X-BeenThere: dev@openvswitch.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@openvswitch.org Sender: "dev" Commit ID:7845b70384d75bd7d753648cb547be5c6c75ddca changed the hardcoded names of 'internal' and 'external.1'. This patch updates the documentation to accomodate the patches. Signed-off-by: Alin Gabriel Serdean Acked-by: Nithin Raju --- This patch is intended for branch-2.4 as well --- INSTALL.Windows.md | 71 ++++++++++++++++++++++++++++++++++++------------------ 1 file changed, 47 insertions(+), 24 deletions(-) diff --git a/INSTALL.Windows.md b/INSTALL.Windows.md index 6d870ed..2119842 100644 --- a/INSTALL.Windows.md +++ b/INSTALL.Windows.md @@ -263,21 +263,43 @@ ovs-vswitchd by running 'ovs-appctl exit'.) 07> Add the physical NIC and the internal port to br-pif. -In OVS for Hyper-V, we use 'external' as a special name to refer to the -physical NICs connected to the Hyper-V switch. An index is added to this -special name to refer to the particular physical NIC. Eg. 'external.1' refers -to the first physical NIC on the Hyper-V switch. +In OVS for Hyper-V, we use the name of the adapter on top of which the Hyper-V +virtual switch was created, as a special name to refer to the physical NICs +connected to the Hyper-V switch. I.e. let us suppose we created the Hyper-V +virtual switch on top of the adapter named 'Ethernet0'. In OVS for Hyper-V, we +use that name('Ethernet0') as a special name to refer to that adapter. Note: Currently, we assume that the Hyper-V switch on which OVS extension is enabled has a single physical NIC connected to it. -Interal port is the virtual adapter created on the Hyper-V switch using the +Internal port is the virtual adapter created on the Hyper-V switch using the 'AllowManagementOS' setting. This has already been setup while creating the -switch using the instructions above. In OVS for Hyper-V, we use a 'internal' -as a special name to refer to that adapter. +switch using the instructions above. In OVS for Hyper-V, we use a the name of +that specific adapter as a special name to refer to that adapter. By default it +is created under the following rule "vEthernet ()". - % ovs-vsctl add-port br-pif external.1 - % ovs-vsctl add-port br-pif internal +As a whole example, if we issue the following in a powershell console: +PS C:\package\binaries> Get-NetAdapter | select Name,MacAddress,InterfaceDescription + +Name MacAddress InterfaceDescription +---- ---------- -------------------- +Ethernet1 00-0C-29-94-05-65 Intel(R) PRO/1000 MT Network Connection +vEthernet (external) 00-0C-29-94-05-5B Hyper-V Virtual Ethernet Adapter #2 +Ethernet0 00-0C-29-94-05-5B Intel(R) PRO/1000 MT Network Connection #2 + +PS C:\package\binaries> Get-VMSwitch + +Name SwitchType NetAdapterInterfaceDescription +---- ---------- ------------------------------ +external External Intel(R) PRO/1000 MT Network Connection #2 + + +We can see that we have a switch(external) created upon adapter name 'Ethernet0' +with an internal port under name 'vEthernet (external)'. Thus resulting into the +following ovs-vsctl commands + + % ovs-vsctl add-port br-pif Ethernet0 + % ovs-vsctl add-port br-pif "vEthernet (external)" * Dumping the ports should show the additional ports that were just added. Sample output shows up as follows: @@ -286,22 +308,23 @@ as a special name to refer to that adapter. system@ovs-system: lookups: hit:0 missed:0 lost:0 flows: 0 - port 4: internal (internal) <<< 'AllowManagementOS' adapter on - Hyper-V switch + port 4: vEthernet (external) (internal) <<< 'AllowManagementOS' + adapter on + Hyper-V switch port 2: br-pif (internal) - port 1: br-int (internal - port 3: external.1 <<< Physical NIC + port 1: br-int (internal) + port 3: Ethernet0 <<< Physical NIC % ovs-vsctl show a56ec7b5-5b1f-49ec-a795-79f6eb63228b Bridge br-pif - Port internal - Interface internal + Port "vEthernet (external)" + Interface "vEthernet (external)" Port br-pif Interface br-pif type: internal - Port "external.1" - Interface "external.1" + Port "Ethernet0" + Interface "Ethernet0" Bridge br-int Port br-int Interface br-int @@ -342,19 +365,19 @@ with OVS extension enabled. system@ovs-system: lookups: hit:0 missed:0 lost:0 flows: 0 - port 4: internal (internal) + port 4: vEthernet (external) (internal) port 5: ovs-port-a port 2: br-pif (internal) port 1: br-int (internal - port 3: external.1 + port 3: Ethernet0 % ovs-vsctl show 4cd86499-74df-48bd-a64d-8d115b12a9f2 Bridge br-pif - Port internal - Interface internal - Port "external.1" - Interface "external.1" + Port "vEthernet (external)" + Interface "vEthernet (external)" + Port "Ethernet0" + Interface "Ethernet0" Port br-pif Interface br-pif type: internal @@ -410,7 +433,7 @@ prior to adding tunnels. % ovs-vsctl set Interface tun-2 options:in_key=flow % ovs-vsctl set Interface tun-2 options:out_key=flow - Where port-type is the string stt or vxlan + Where port-type is the string stt or vxlan Requirements