Re: [ovs-discuss] OVS+DPDK QoS rate limit issue
> From: "王志克" > To: ovs-...@openvswitch.org, ovs-discuss@openvswitch.org > Sent: Wednesday, August 23, 2017 11:41:05 PM > Subject: [ovs-discuss] OVS+DPDK QoS rate limit issue > > > > Hi All, > > > > I am using OVS2.7.0 and DPDK 16.11, and testing rate limit function. > > > > I found that if the policing_rate is set very large, say 5Gbps, the rate is > limited dramatically to very low value, like 800Mbps. > > The command is as below: > > ovs-vsctl set interface port-7zel2so9sg ingress_policing_rate=500 > ingress_policing_burst=50 > > > > If we set the rate lower than 4Gbps, the rate is limited correctly. > > > > Test setup: > > Sender (DPDK pktGen) sends out about 10Gbps udp packet, with size about 1420 > IP size. > > The rate limit is set on VM vhost-user-client port. > > > > Any idea about this issue? Is that known issue? > > It seems 32-bit arithmetic is being used when converting the rate from kilobits per second to bytes per second. Could you give this patch a try? diff --git a/lib/netdev-dpdk.c b/lib/netdev-dpdk.c index 1aaf6f7e2..d6ed2c7b0 100644 --- a/lib/netdev-dpdk.c +++ b/lib/netdev-dpdk.c @@ -2229,8 +2229,8 @@ netdev_dpdk_policer_construct(uint32_t rate, uint32_t burst) rte_spinlock_init(&policer->policer_lock); /* rte_meter requires bytes so convert kbits rate and burst to bytes. */ - rate_bytes = rate * 1000/8; - burst_bytes = burst * 1000/8; + rate_bytes = rate * 1000ULL/8; + burst_bytes = burst * 1000ULL/8; policer->app_srtcm_params.cir = rate_bytes; policer->app_srtcm_params.cbs = burst_bytes; Regards, Lance Richardson > > Br, > > Wang Zhike > > ___ > discuss mailing list > disc...@openvswitch.org > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss > ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] [openvswitch 2.8.90] testsuite: 537 539 541 545 765 767 1966 1968 1975 1977 1984 1986 1993 1995 2001 2002 2003 2004 2006 2011 2013 2020 2022 2029 2031 2038 2040 2047 2049 2056 2058 2
> From: "Alin Serdean"
> To: b...@openvswitch.org, "Alin Balutoiu"
> Cc: "Terry Wilson" , "Lance Richardson"
> , "Russell Bryant"
> Sent: Monday, August 14, 2017 8:45:01 PM
> Subject: [openvswitch 2.8.90] testsuite: 537 539 541 545 765 767 1966 1968
> 1975 1977 1984 1986 1993 1995 2001 2002
> 2003 2004 2006 2011 2013 2020 2022 2029 2031 2038 2040 2047 2049 2056 2058
> 2065 2067 2074 2076 2083 2085 2092 2094
> 2101 2103 2110 2112 2119 2121 2128
>
> To:
>Subject: [openvswitch 2.8.90] testsuite: 537 539 541 545 765 767 1966 1968
>1975 1977 1984 1986 1993 1995 2001 2002 2003 2004 2006 2011 2013 2020
>2022 2029 2031 2038 2040 2047 2049 2056 2058 2065 2067 2074 2076 2083
>2085 2092 2094 2101 2103 2110 2112 2119 2121 2128 2130 2136 2138 2140
>2148 2151 2238 2244 2247 2250 failed
>
> After patch:
> https://github.com/openvswitch/ovs/commit/e7164d96bcbcf79044a93f6e7acc68f05d8e3945
> a lot of the python3 tests are failing.
>
> This is probably due to:
> +Traceback (most recent call last):
> + File "../.././appctl.py", line 75, in
> +main()
> + File "../.././appctl.py", line 60, in main
> +err_no, error, result = client.transact(args.command, args.argv)
> + File "c:\ovs\python\ovs\unixctl\client.py", line 39, in transact
> +error, reply = self._conn.transact_block(request)
> + File "c:\ovs\python\ovs\jsonrpc.py", line 326, in transact_block
> +error, reply = self.recv_block()
> + File "c:\ovs\python\ovs\jsonrpc.py", line 309, in recv_block
> +error, msg = self.recv()
> + File "c:\ovs\python\ovs\jsonrpc.py", line 273, in recv
> +data = data.decode('utf-8')
> +AttributeError: 'str' object has no attribute 'decode'
>
> Also using UTF-8 strings in Windows shells proves to be a bit of challenge.
>
> Me and @Alin Balutoiu are looking over changes needed on the Windows side as
> well.
>
> Since Python isn't quite my cup of tea I would like if you can oversee the
> patches that he will send out.
>
> Thanks,
> Alin.
>
Hi Alin,
It seems that for the Python3 non-windows, self.stream.recv() returns
socket.recv(),
which always has a type of "bytes". For the windows case, self.stream.recv()
returns
get_decoded_buffer(recvBuffer) from python/ovs/winutils.py, which does:
return bytes(recvBuffer).decode("utf-8")
So for the windows Python3 case, the type of the value returned by
self.stream.recv()
will always be "str".
I'm not sure why the windows case needs to do the utf-8 decode at the stream
layer,
but it would be nice if self.stream.recv() returned a consistent type that was
independent of the OS.
I'm happy to help, but I will be travelling tomorrow and will probably not be
able to look any deeper until Wednesday.
I don't know if such a thing exists, but e.g. a Vagrant setup that could build
ovs and run the tests would be a huge help in avoiding this kind of breakage
(just
a thought...)
Regards,
Lance
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] multiple controllers to OVS secured via TLS
> From: "Shivaram Mysore" > To: ovs-discuss@openvswitch.org > Sent: Friday, 21 July, 2017 8:18:08 PM > Subject: Re: [ovs-discuss] multiple controllers to OVS secured via TLS > > Any pointers to my question? > Thanks! > > On Thu, Jul 20, 2017 at 9:30 AM, Shivaram Mysore < shivaram.mys...@gmail.com > > wrote: > > > > Hi, > I am using ovs-vsctl set-ssl to set certificate and key information for OF > Control channel secured via TLS. I need to have more than one SSL controller > configured. The certs, keys and even CA certs are different. How can use the > set-ssl option to configure the same? > > Pointers to any documentation is also highly appreciated. > > thanks > > /Shivaram > This isn't possible with the current implementation. Regards, Lance ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Remote connection method for ovn-controller ovs-ofctl invocation.
> From: "Ben Pfaff" ... > However, this is not going to be the only problem that the OP will > encounter, since ovn-controller makes other assumptions that it is > running on the ovs-switchd host. > Right, e.g. OVN's QoS features will not work if ovn-controller and ovs-vswitchd are running on different hosts. Lance ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Subject: [openvswitch 2.7.1] testsuite: 7 8 767 1891 1892 1893 1894 1895 1896 1900 1902 failed
> From: "Lance Richardson"
> To: "Ben Pfaff"
> Cc: develo...@it-offshore.co.uk, b...@openvswitch.org
> Sent: Thursday, 13 July, 2017 8:12:30 PM
> Subject: Re: [ovs-discuss] Subject: [openvswitch 2.7.1] testsuite: 7 8 767
> 1891 1892 1893 1894 1895 1896 1900 1902
> failed
>
> > From: "Ben Pfaff"
> > To: "Lance Richardson"
> > Cc: develo...@it-offshore.co.uk, b...@openvswitch.org
> > Sent: Thursday, 13 July, 2017 7:46:13 PM
> > Subject: Re: [ovs-discuss] Subject: [openvswitch 2.7.1] testsuite: 7 8 767
> > 1891 1892 1893 1894 1895 1896 1900 1902
> > failed
> >
> > On Mon, Jul 10, 2017 at 01:14:38PM -0400, Lance Richardson wrote:
> > > > From: "Stuart Cardall"
> > > > To: b...@openvswitch.org
> > > > Sent: Saturday, 8 July, 2017 5:22:17 PM
> > > > Subject: [ovs-discuss] Subject: [openvswitch 2.7.1] testsuite: 7 8 767
> > > > 1891 1892 1893 1894 1895 1896 1900 1902 failed
> > > >
> > > >
> > > >
> > > > Hello,
> > > >
> > > > Attached is the test suite log for ovs 2.7.1 in Alpine Linux / musl c:
> > > >
> > > > testsuite: 7 8 767 1891 1892 1893 1894 1895 1896 1900 1902 failed
> > > >
> > > >
> > > > Kind Regards,
> > > >
> > > > Stuart Cardall.
> > > >
> > >
> > > These will pass if GNU awk is used instead of busybox awk (apk add gawk).
> > >
> > >7: completion.at:343 vsctl-bashcomp - basic verification
> > >8: completion.at:425 vsctl-bashcomp - argument completion
> >
> > That's interesting. I thought I'd try to figure out the root of the
> > problem, but I don't get failures in my usual environment if I replace
> > "awk" by "busybox awk" and run these tests, so I wonder whether there's
> > something else at play.
> >
>
> I just tried that (s/awk/busybox awk/ in utilities/ovs-vsctl-bashcomp.bash)
> and got failures in those tests with similar symptom (no completions given).
>
> This was on F26, x86_64, with busybox-1.22.1-6.
>
> Strange... no idea. I did find a nice wiki explaining some differences
> between
> busybox awk and some other implementations:
>
> https://wiki.alpinelinux.org/wiki/Awk
>
One more tidbit... if I use busybox awk here, I get failures, otherwise I
don't (the other invocations of awk in this script work either way):
# This is a convenience function to make sure that user input is
# looked at as a fixed string when being compared to something. $1 is
# the input; this behaves like 'grep "^$1"' but deals with regex
# metacharacters in $1.
_ovs_vsctl_check_startswith_string () {
awk 'index($0, thearg)==1' thearg="$1"
}
The extent of my awk knowledge is knowing where the name comes from, so
I have no idea what might causing the problem here or what alternative
implementations might be worth trying...
Regards,
Lance
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Subject: [openvswitch 2.7.1] testsuite: 7 8 767 1891 1892 1893 1894 1895 1896 1900 1902 failed
> From: "Ben Pfaff" > To: "Lance Richardson" > Cc: develo...@it-offshore.co.uk, b...@openvswitch.org > Sent: Thursday, 13 July, 2017 7:46:13 PM > Subject: Re: [ovs-discuss] Subject: [openvswitch 2.7.1] testsuite: 7 8 767 > 1891 1892 1893 1894 1895 1896 1900 1902 > failed > > On Mon, Jul 10, 2017 at 01:14:38PM -0400, Lance Richardson wrote: > > > From: "Stuart Cardall" > > > To: b...@openvswitch.org > > > Sent: Saturday, 8 July, 2017 5:22:17 PM > > > Subject: [ovs-discuss] Subject: [openvswitch 2.7.1] testsuite: 7 8 767 > > > 1891 1892 1893 1894 1895 1896 1900 1902 failed > > > > > > > > > > > > Hello, > > > > > > Attached is the test suite log for ovs 2.7.1 in Alpine Linux / musl c: > > > > > > testsuite: 7 8 767 1891 1892 1893 1894 1895 1896 1900 1902 failed > > > > > > > > > Kind Regards, > > > > > > Stuart Cardall. > > > > > > > These will pass if GNU awk is used instead of busybox awk (apk add gawk). > > > >7: completion.at:343 vsctl-bashcomp - basic verification > >8: completion.at:425 vsctl-bashcomp - argument completion > > That's interesting. I thought I'd try to figure out the root of the > problem, but I don't get failures in my usual environment if I replace > "awk" by "busybox awk" and run these tests, so I wonder whether there's > something else at play. > I just tried that (s/awk/busybox awk/ in utilities/ovs-vsctl-bashcomp.bash) and got failures in those tests with similar symptom (no completions given). This was on F26, x86_64, with busybox-1.22.1-6. Strange... no idea. I did find a nice wiki explaining some differences between busybox awk and some other implementations: https://wiki.alpinelinux.org/wiki/Awk ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Remote connection method for ovn-controller ovs-ofctl invocation.
> From: "Ben Pfaff" > To: "Lance Richardson" > Cc: "JaiSingh Rana" , ovs-discuss@openvswitch.org > Sent: Thursday, 13 July, 2017 12:47:47 PM > Subject: Re: [ovs-discuss] Remote connection method for ovn-controller > ovs-ofctl invocation. > > On Thu, Jul 13, 2017 at 09:35:01AM -0400, Lance Richardson wrote: > > > From: "JaiSingh Rana" > > > To: ovs-discuss@openvswitch.org > > > Sent: Thursday, 13 July, 2017 3:49:15 AM > > > Subject: [ovs-discuss] Remote connection method for ovn-controller > > > ovs-ofctl invocation. > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > Currently in Openvswitch-2.7.1, ovn-controller hard codes connection > > > method > > > for ovs-ofctl invokation as unix:file as assumption is there will be unix > > > file created by vswitchd in OVS_RUNDIR for managing OF controller on > > > bridge > > > e.g. br-int.mgmt > > > > > > > > > > > > > > > There is an issue in our Openvswitch offload model where vswitchd is > > > running > > > on nic and ovn-controller on host. As there is no option for telling > > > ovn-controller to use tcp:port connection method for ovs-ofctl , flows > > > are > > > not being pushed to vswitchd. > > > > > > > > > > > > > > > For providing the patch, need some input. Should connection method be > > > provided as an argument to ovn-controller or it can be written to > > > /etc/sysconfig/openvswitch from where ovn-controller can read and use if > > > option is present otherwise it defaults to unix file method. > > > > > > > > > > My suggestion would be to use external-ids in the local ovsdb, as is > > currently done for ovn-remote and ovn-encap. Maybe something like: > > > > ovs-vsctl set open . external-ids:ovn-ofctl=tcp:w.x.y.z:abcd > > Using the name "ovs-ofctl" here is weird. ovn-controller doesn't use > ovs-ofctl. > Well, I'm terrible with naming things, and should have added a comment to that effect :-) My rationale for "ovn-ofctl" was shallowly based on the the related file, ovn/controller/ofctrl.c (well, I omitted the 'r' for some reason,.) What would be a more appropriate name? Thanks, Lance ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Remote connection method for ovn-controller ovs-ofctl invocation.
> From: "JaiSingh Rana" > To: ovs-discuss@openvswitch.org > Sent: Thursday, 13 July, 2017 3:49:15 AM > Subject: [ovs-discuss] Remote connection method for ovn-controller ovs-ofctl > invocation. > > > > Hi, > > > > > Currently in Openvswitch-2.7.1, ovn-controller hard codes connection method > for ovs-ofctl invokation as unix:file as assumption is there will be unix > file created by vswitchd in OVS_RUNDIR for managing OF controller on bridge > e.g. br-int.mgmt > > > > > There is an issue in our Openvswitch offload model where vswitchd is running > on nic and ovn-controller on host. As there is no option for telling > ovn-controller to use tcp:port connection method for ovs-ofctl , flows are > not being pushed to vswitchd. > > > > > For providing the patch, need some input. Should connection method be > provided as an argument to ovn-controller or it can be written to > /etc/sysconfig/openvswitch from where ovn-controller can read and use if > option is present otherwise it defaults to unix file method. > > My suggestion would be to use external-ids in the local ovsdb, as is currently done for ovn-remote and ovn-encap. Maybe something like: ovs-vsctl set open . external-ids:ovn-ofctl=tcp:w.x.y.z:abcd ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Subject: [openvswitch 2.7.1] testsuite: 7 8 767 1891 1892 1893 1894 1895 1896 1900 1902 failed
> From: "Stuart Cardall" > To: b...@openvswitch.org > Sent: Saturday, 8 July, 2017 5:22:17 PM > Subject: [ovs-discuss] Subject: [openvswitch 2.7.1] testsuite: 7 8 767 1891 > 1892 1893 1894 1895 1896 1900 1902 failed > > > > Hello, > > Attached is the test suite log for ovs 2.7.1 in Alpine Linux / musl c: > > testsuite: 7 8 767 1891 1892 1893 1894 1895 1896 1900 1902 failed > > > Kind Regards, > > Stuart Cardall. > These will pass if GNU awk is used instead of busybox awk (apk add gawk). 7: completion.at:343 vsctl-bashcomp - basic verification 8: completion.at:425 vsctl-bashcomp - argument completion The other failures mostly seem to have the pattern of a "hard failure" in OVS_WAIT_WHILE() or OVS_WAIT_UNTIL() immediately after a "kill -SEGV". It's not clear from a quick look what the root cause might be. Lance ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] enforce TLSv1.2 in OVN
> From: "Dominik Holler" > To: "Lance Richardson" > Cc: ovs-discuss@openvswitch.org, "Numan Siddique" , > "Marcin Mirecki" , "Dan > Kenigsberg" > Sent: Wednesday, 7 June, 2017 3:48:45 AM > Subject: Re: enforce TLSv1.2 in OVN > > On Tue, 6 Jun 2017 12:26:21 -0400 (EDT) > Lance Richardson wrote: > > > I think we'll need to add a new option to ovn-ctl to allow this option > > to be specified. > > > > I also think we should allow the --ssl-protocols configuration to be > > stored in the ovsdb database and have support in ovn-nbctl/ovn-sbctl > > etc. for setting it. Thinking about this a bit more, I don't think we need to add a new option to ovn-ctl. SSL key and certificate configuration for OVN nb/sb ovsdb-server is handled solely through db entries (no command-line option for these in ovn-ctl), so we should do the same for SSL protocol and cipher configuration. Regards, Lance ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] enforce TLSv1.2 in OVN
> From: "Dominik Holler" > To: ovs-discuss@openvswitch.org > Cc: "Lance Richardson" , "Numan Siddique" > , "Marcin Mirecki" > , "Dan Kenigsberg" > Sent: Tuesday, 6 June, 2017 11:30:07 AM > Subject: enforce TLSv1.2 in OVN > > Hello, > We want to ensure that OVN uses only TLSv1.2, but not TLSv1 or TLSv1.1 > in our scenario. > > There are multiple connection, identified to be relevant: > > - The tunneling data connection between the hypervisors/chassis, like > geneve listening on UDP port 6081. > > - The meta data connections: > > - The connections to the OVN Southbound DB, which is hosted by >ovsdb-server and listening typically TCP port 6642. Connections >may be initiated by from the ovn-controllers and ovn-northd. > > - The connections to the OVN Northbound DB, which is hosted by >ovsdb-server and listening typically on TCP port 6641. Connections >may be initiated by the Cloud Management System and ovn-northd. > > Is it correct that encryption is not supported at all for the tunneling > data connection? That's correct. There has been some recent work to support the use of IPSec for tunnel encryption, but as far as I know no one has investigated using IPSec with OVN tunnels. If there is a need for this, we could look into it. See: https://patchwork.ozlabs.org/patch/674858/ > > For the meta data connections ovsdb-server acts as the server. > ovsdb-server has the command line option --ssl-protocols, but I do not > understand how to apply this. ovsdb-server seems to be started by > ovn-ctl, but I do not recognize a way to utilize ovn-ctl to > pass the --ssl-protocols option. > How should the --ssl-protocols option passed to ovsdb-server? > I think we'll need to add a new option to ovn-ctl to allow this option to be specified. I also think we should allow the --ssl-protocols configuration to be stored in the ovsdb database and have support in ovn-nbctl/ovn-sbctl etc. for setting it. I'll go ahead and start working on that, it would be good if you could open a BZ for tracking the upstream and backport work. > Thanks and regards > Dominik > > > > > > ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Geneve Support Question
> From: "John McDowall" > To: ovs-discuss@openvswitch.org > Sent: Monday, 5 June, 2017 2:48:07 PM > Subject: [ovs-discuss] Geneve Support Question > > > > I am trying to do some distributed testing with OVN/OVS. I have a set of > Centos 7 (3.10.0-514 kernel) machines. > > > > There are Geneve modules in /usr/lib/modules/’uname’/… Has anyone tried this > ? I often use current CentOS 7 for OVN development and testing. No issues running OVN or Geneve tunnels. Regards, Lance ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] modules_install, SSL Error
> From: "Ali Volkan Atli" > To: disc...@openvswitch.org > Sent: Tuesday, 23 May, 2017 8:17:37 AM > Subject: [ovs-discuss] modules_install, SSL Error > > > Hello > > I'm getting the following error while modules install. Is there anyone who is > experiencing this problem in the master? I disabled ssl while configuring > > $ sudo ./configure --disable-ssl CFLAGS="-g -O0" > --with-linux=/lib/modules/$(uname -r)/build > $ uname -a > Linux avatli 4.4.0-78-generic #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 > x86_64 x86_64 x86_64 GNU/Linux > > Thanks in advance > > - Volkan > See: https://mail.openvswitch.org/pipermail/ovs-discuss/2017-May/044410.html (The "SSL error" messages are coming from the utility used by the kernel build infrastructure to sign modules, they have nothing to do with whether SSL support is included in the openvswitch build.) Regards, Lance ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] SSL error
> From: y...@panath.cn > To: "ovs-discuss" > Sent: Wednesday, 10 May, 2017 5:05:36 AM > Subject: [ovs-discuss] SSL error > > Hi everyone, > After install openvswitch-2.6.1, prompt SSL error, Does anyone know what > reason is this? > > root@ubuntu:/home/ych/openvswitch-2.6.1# ./boot.sh > root@ubuntu:/home/ych/openvswitch-2.6.1# ./configure > --with-linux=/lib/modules/$(uname -r)/build > root@ubuntu:/home/ych/openvswitch-2.6.1# make > root@ubuntu:/home/ych/openvswitch-2.6.1# make install > root@ubuntu:/home/ych/openvswitch-2.6.1# make modules_install > = > root@ubuntu:/home/ych/openvswitch-2.6.1# sudo make modules_install > cd datapath/linux && make modules_install > make[1]: Entering directory '/home/ych/openvswitch-2.6.1/datapath/linux' > make -C /lib/modules/4.4.0-75-generic/build > M=/home/ych/openvswitch-2.6.1/datapath/linux modules_install > make[2]: Entering directory '/usr/src/linux-headers-4.4.0-75-generic' > INSTALL /home/ych/openvswitch-2.6.1/datapath/linux/openvswitch.ko > At main.c:222: > - SSL error:02001002:system library:fopen:No such file or directory: > bss_file.c:175 > - SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178 > sign-file: certs/signing_key.pem: No such file or directory > INSTALL /home/ych/openvswitch-2.6.1/datapath/linux/vport-geneve.ko > At main.c:222: > - SSL error:02001002:system library:fopen:No such file or directory: > bss_file.c:175 > - SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178 > sign-file: certs/signing_key.pem: No such file or directory > INSTALL /home/ych/openvswitch-2.6.1/datapath/linux/vport-gre.ko > At main.c:222: > - SSL error:02001002:system library:fopen:No such file or directory: > bss_file.c:175 > - SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178 > sign-file: certs/signing_key.pem: No such file or directory > INSTALL /home/ych/openvswitch-2.6.1/datapath/linux/vport-lisp.ko > At main.c:222: > - SSL error:02001002:system library:fopen:No such file or directory: > bss_file.c:175 > - SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178 > sign-file: certs/signing_key.pem: No such file or directory > INSTALL /home/ych/openvswitch-2.6.1/datapath/linux/vport-stt.ko > At main.c:222: > - SSL error:02001002:system library:fopen:No such file or directory: > bss_file.c:175 > - SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178 > sign-file: certs/signing_key.pem: No such file or directory > INSTALL /home/ych/openvswitch-2.6.1/datapath/linux/vport-vxlan.ko > At main.c:222: > - SSL error:02001002:system library:fopen:No such file or directory: > bss_file.c:175 > - SSL error:2006D080:BIO routines:BIO_new_file:no such file: bss_file.c:178 > sign-file: certs/signing_key.pem: No such file or directory > DEPMOD 4.4.0-75-generic > make[2]: Leaving directory '/usr/src/linux-headers-4.4.0-75-generic' > depmod `sed -n 's/#define UTS_RELEASE "\([^"]*\)"/\1/p' > /lib/modules/4.4.0-75-generic/build/include/generated/utsrelease.h` > make[1]: Leaving directory '/home/ych/openvswitch-2.6.1/datapath/linux' > > > > Best wishes! > > > y...@panath.cn > It seems your kernel is configured with CONFIG_MODULE_SIG=y, so "make modules_install" is attempting to add a signature to each kernel module, but this is failing because the signing key certificate is not present. The signing key certificate is most often created as part of the base kernel build, and not included in distribution packages (for obvious reasons!), so I suspect this is a common situation. Based on looking at the kernel makefiles, this won't be treated as a fatal error and in fact from your "make modules_install" output it looks like it completed successfully. I think these errors can safely be ignored. Regards, Lance Richardson ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
Re: [ovs-discuss] Running ovs test cases
> From: "satish kondapalli" > To: ovs-discuss@openvswitch.org > Sent: Monday, December 5, 2016 7:17:36 PM > Subject: [ovs-discuss] Running ovs test cases > > Hi, > > is there way to run only specific test case in ovs( instead of running all > cases -- make check). How to run only connection tracking test case and logs > for the same test? > > Sateesh > Sure, take a look at references to TESTSUITEFLAGS in INSTALL.rst (or INSTALL.md if you're on an older branch). For example, you can list all test cases with the keyword "conntrack" via: make check TESTSUITEFLAGS="-l -k conntrack" And you can execute them via: make check TESTSUITEFLAGS="-k conntrack" To execute one or more tests by number: make check TESTSUITEFLAGS="1,3,4-14" If you want to preserve logs for test cases that execute successfully, specifiy the "debug" flag, e.g.: make check TESTSUITEFLAGS="-k conntrack -d" If you're interested in testing data path support for conntrack, you might also be interested in the "check-kernel" and "check-system-userspace". Hope this helps, Lance targets. ___ discuss mailing list disc...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
