[ovs-discuss] Controller to Switch distance (milli-second) limits
Dear Members- I am working on a topology where the Controller is separated from its OVS instances by over 30 milliseconds. I imagine that the performance of the Controller will begin to degrade as its distance to OVS instances increases since the Controller will be waiting longer and that would consume more resources on the Controller. I spend some time searching this topic but did not find anything. Can someone point me to an indepth discussion of this topic? Also, I am new to this mailing list. I tried to look in the archives first and I did not see an easy way to search them -- the archives are available as downloadable text files (one file per month). I would have to download the files and then search through them individually. Am I missing an easier way to search? Thank you, Ravi ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Controller to Switch distance (milli-second) limits
On Sun, Apr 01, 2018 at 08:45:05AM -0400, ravimalhot . wrote: > I am working on a topology where the Controller is separated from its OVS > instances by over 30 milliseconds. I imagine that the performance of the > Controller will begin to degrade as its distance to OVS instances increases > since the Controller will be waiting longer and that would consume more > resources on the Controller. I spend some time searching this topic but did > not find anything. Can someone point me to an indepth discussion of this > topic? I don't know of an in-depth discussion. I'll point out, though, that the architecture of the controller makes a great difference. If the controller is reactive, that is, if it sets up flows in reaction to traffic (received via packet-ins), then it will be affected much more by the RTT to the switch than if it is proactive. > Also, I am new to this mailing list. I tried to look in the archives first > and I did not see an easy way to search them -- the archives are available > as downloadable text files (one file per month). I would have to download > the files and then search through them individually. Am I missing an easier > way to search? You can use Google or another search engine to search, if you specify "site:openvswitch.org". Works quite well. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] [openvswitch 2.9.0] testsuite: 787 1011 1932 1933 1934 1935 1936 1937 1941 1943 failed
On Sun, Mar 25, 2018 at 10:30:44PM +0100, Stuart Cardall wrote: > Test results for 2.9.0 under Alpine Linux (fails mainly from the > ovsdb-server replication sections). > > Anything I can do to help test - please let me know. Thanks for the report. The failure of test 787 is hard to explain. I don't have a good idea on that one. Sometimes, some of our tests have intermittent failures due to timing, which is undesirable but difficult to eliminate. It doesn't look like that should be one of those, though. 1011 was just a bug in the testsuite. I sent out a patch: https://patchwork.ozlabs.org/patch/894033/ I believe that the remaining tests fail because busybox "diff" is not POSIX compliant. To verify that, would you mind installing GNU diffutils and rerunning those tests? If that fixes the problem, then we will have to decide whether it is better to document GNU diffutils as a dependency for running the tests, or to skip those tests if diff is incompatible, or to modify the testsuite to cope with noncompliant diff. Thanks, Ben. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] [openvswitch 2.9.0] testsuite: 787 1011 1932 1933 1934 1935 1936 1937 1941 1943 failed
The majority of the failures were due to Busybox's diff. With the patch & _without_ diffutils: ## - ## ## Test results. ## ## - ## ERROR: 2104 tests were run, 9 failed unexpectedly. 319 tests were skipped. ## -- ## ## testsuite.log was created. ## ## -- ## Please send `tests/testsuite.log' and all information you think might help: To: Subject: [openvswitch 2.9.0] testsuite: 787 1932 1933 1934 1935 1936 1937 1941 1943 failed === with the patch & _with_ diffutils as a $checkdepends only test 787 failed: ## - ## ## Test results. ## ## - ## ERROR: 2104 tests were run, 1 failed unexpectedly. 319 tests were skipped. ## -- ## ## testsuite.log was created. ## ## -- ## Please send `tests/testsuite.log' and all information you think might help: To: Subject: [openvswitch 2.9.0] testsuite: 787 failed === Stuart. On 04/01/2018 06:10 PM, Ben Pfaff wrote: > On Sun, Mar 25, 2018 at 10:30:44PM +0100, Stuart Cardall wrote: >> Test results for 2.9.0 under Alpine Linux (fails mainly from the >> ovsdb-server replication sections). >> >> Anything I can do to help test - please let me know. > Thanks for the report. > > The failure of test 787 is hard to explain. I don't have a good idea on > that one. Sometimes, some of our tests have intermittent failures due > to timing, which is undesirable but difficult to eliminate. It doesn't > look like that should be one of those, though. > > 1011 was just a bug in the testsuite. I sent out a patch: > https://patchwork.ozlabs.org/patch/894033/ > > I believe that the remaining tests fail because busybox "diff" is not > POSIX compliant. To verify that, would you mind installing GNU > diffutils and rerunning those tests? If that fixes the problem, then we > will have to decide whether it is better to document GNU diffutils as a > dependency for running the tests, or to skip those tests if diff is > incompatible, or to modify the testsuite to cope with noncompliant diff. > > Thanks, > > Ben. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] Configuring OVS as a gateway
hello, I want to configure an OVS to connect two subnets of the network together as follows (as a gateway), h1 (192.168.20.1) -(192.168.20.10) (eth1)Openvswitch (eth0)( 10.0.0.1/16) Its bridge(br1) is connected to eth0 and the Ip address of eth0 is assigned to br1. Could you help me to configure the host and the openvswitch to help the host to connect to the other part of the network? Thank you ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
[ovs-discuss] Error in "Make" after patching OVS
Dear all, I patched OVS successfully but when I issue "make" command it gives following error: taimur@ubuntuibm:~/openvswitch-2.6.0$ make make all-recursive make[1]: Entering directory `/home/taimur/openvswitch-2.6.0' Making all in datapath make[2]: Entering directory `/home/taimur/openvswitch-2.6.0/datapath' Making all in linux make[3]: Entering directory `/home/taimur/openvswitch-2.6.0/datapath/linux' make -C /lib/modules/4.4.0-31-generic/build M=/home/taimur/openvswitch-2.6.0/datapath/linux modules make[4]: Entering directory `/usr/src/linux-headers-4.4.0-31-generic' CC [M] /home/taimur/openvswitch-2.6.0/datapath/linux/actions.o In file included from /home/taimur/openvswitch-2.6.0/datapath/linux/actions.c:24:0: /home/taimur/openvswitch-2.6.0/datapath/linux/compat/include/linux/openvswitch.h:443:2: error: unknown type name ‘ovs_be16’ ovs_be16 rwnd; ^ make[5]: *** [/home/taimur/openvswitch-2.6.0/datapath/linux/actions.o] Error 1 make[4]: *** [_module_/home/taimur/openvswitch-2.6.0/datapath/linux] Error 2 make[4]: Leaving directory `/usr/src/linux-headers-4.4.0-31-generic' make[3]: *** [default] Error 2 make[3]: Leaving directory `/home/taimur/openvswitch-2.6.0/datapath/linux' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/home/taimur/openvswitch-2.6.0/datapath' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/taimur/openvswitch-2.6.0' make: *** [all] Error 2 Could any body help on this? Thanks! Best regards, Taimur Hafeez ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Setting TCP rwnd value in Open vSwitch
Dear Volkan,
Could you please tell *version* of OVS on which you applied
*"tcp_rwnd.diff"* patch? Thanks in advance!
On Fri, Mar 23, 2018 at 5:11 PM, Taimur Hafeez
wrote:
> I applied the patch but it I am unable to do it properly. For this reason,
> i am sharing environment on which i tried along with the terminal output.
> Also i tried various other commands of patching but unfortunately all in
> vain. Could you please what version of OVS and ubuntu you used for this
> patch? Please guide through this. Thankyou!
>
> Environment 1:
>
> OVS version 2.3.90
> Linux sdnhubvm 4.4.0-97-generic #120-14.04.1-Ubuntu SMP
>
> Environment 2:
> OVS version 2.8.1
> Linux ubuntu ibm 4.13.0-36-generic #40- Ubuntu SMP
>
>
> **My comment==Environment 1 Ubuntu terminal
> log*
> ubuntu@sdnhubvm:~/openvswitch$ patch -t < tcp_rwnd.diff
> can't find file to patch at input line 5
> Perhaps you should have used the -p or --strip option?
> The text leading up to this was:
> --
> |diff --git a/datapath/linux/compat/include/linux/openvswitch.h
> b/datapath/linux/compat/include/linux/openvswitch.h
> |index 12260d8..dd84b04 100644
> |--- a/datapath/linux/compat/include/linux/openvswitch.h
> |+++ b/datapath/linux/compat/include/linux/openvswitch.h
> --
> No file to patch. Skipping patch.
> 2 out of 2 hunks ignored
> can't find file to patch at input line 33
> Perhaps you should have used the -p or --strip option?
> The text leading up to this was:
> --
> |diff --git a/include/openvswitch/flow.h b/include/openvswitch/flow.h
> |index df80dfe..64da205 100644
> |--- a/include/openvswitch/flow.h
> |+++ b/include/openvswitch/flow.h
> --
> No file to patch. Skipping patch.
> 2 out of 2 hunks ignored
> can't find file to patch at input line 57
> Perhaps you should have used the -p or --strip option?
> The text leading up to this was:
> --
> |diff --git a/include/openvswitch/ofp-actions.h
> b/include/openvswitch/ofp-actions.h
> |index 74e9dcc..a7512e5 100644
> |--- a/include/openvswitch/ofp-actions.h
> |+++ b/include/openvswitch/ofp-actions.h
> --
> No file to patch. Skipping patch.
> 2 out of 2 hunks ignored
> can't find file to patch at input line 87
> Perhaps you should have used the -p or --strip option?
> The text leading up to this was:
> --
> |diff --git a/lib/odp-execute.c b/lib/odp-execute.c
> |index 65a6fcd..b052f1c 100644
> |--- a/lib/odp-execute.c
> |+++ b/lib/odp-execute.c
> --
> No file to patch. Skipping patch.
> 2 out of 2 hunks ignored
> can't find file to patch at input line 122
> Perhaps you should have used the -p or --strip option?
> The text leading up to this was:
> --
> |diff --git a/lib/odp-util.c b/lib/odp-util.c
> |index 626a82c..a124d6e 100644
> |--- a/lib/odp-util.c
> |+++ b/lib/odp-util.c
> --
> No file to patch. Skipping patch.
> patch: malformed patch at line 192: {
>
>
> -
>
>
> On Fri, Mar 23, 2018 at 5:07 PM, Taimur Hafeez
> wrote:
>
>> I applied the patch but it I am unable to do it properly. For this
>> reason, i am sharing environment on which i tried along with the terminal
>> output. Also i tried various other commands of patching but unfortunately
>> all in vain. Could you please what version of OVS and ubuntu you used for
>> this patch? Please guide through this. Thankyou!
>>
>> Environment 1:
>>
>> OVS version 2.3.90
>> Linux sdnhubvm 4.4.0-97-generic #120-14.04.1-Ubuntu SMP
>>
>> Environment 2:
>> OVS version 2.8.1
>> Linux ubuntu ibm 4.13.0-36-generic #40- Ubuntu SMP
>>
>>
>> **My comment==Environment 1 Ubuntu terminal
>> log*
>> ubuntu@sdnhubvm:~/openvswitch$ patch -t < tcp_rwnd.diff
>> can't find file to patch at input line 5
>> Perhaps you should have used the -p or --strip option?
>> The text leading up to this was:
>> --
>> |diff --git a/datapath/linux/compat/include/linux/openvswitch.h
>> b/datapath/linux/compat/include/linux/openvswitch.h
>> |index 12260d8..dd84b04 100644
>> |--- a/datapath/linux/compat/include/linux/openvswitch.h
>> |+++ b/datapath/linux/compat/include/linux/openvswitch.h
>> --
>> No file to patch. Skipping patch.
>> 2 out of 2 hunks ignored
>> can't find file to patch at input line 33
>> Perhaps you should have used the -p or --strip option?
>> The text leading up to this was:
>> --
>> |diff --git a/include/openvswitch/flow.h b/include/openvswitch/flow.h
>> |index df80dfe..64da205 100644
>> |--- a/include/openvswitch/flow.h
>> |+++ b/include/openvswitch/flow.h
>> --
>> No file to patch. Skipping patch.
>> 2 out of 2 hunks ignored
>> can't find file to patch at input line 57
>> Perhaps you should have used the -p or --strip op
