Can I have a word with you?
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
This patch allows user to associate a value with acl,
which will be assigned to ct.label of the corresponding
connection tracking entry.
This value can be used to map a ct entry with corresponding
OVN ACL or higher level constructs like security group.
Signed-off-by: Ankur Sharma
---
OVN ACL implementation used ct_label to indicate if a previosuly
allowed connection shoudl not be allowed anymore and vice versa.
However, ct_label is a 128 bit value and we should rather leverage
on ct_mark which is a 32 bit value.
Using ct_mark for this purpose, allows us to use ct_label for
What:
a. Goal is to be able to associate some identifier with a connection tracking
entry.
b. This identifier can be used to map OVN ACL which added this entry or
higher level constructs like openstack security group etc.
c. There are 2 connection tracking fields which can be used for it.
"controller_id" was written as "controller-id" in one place. This spells
it consistently.
Signed-off-by: Ben Pfaff
---
lib/ovs-actions.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/ovs-actions.xml b/lib/ovs-actions.xml
index 84df842a1937..edf0511c6e5b 100644
---
On Fri, Mar 01, 2019 at 02:20:04PM +0100, Lorenzo Bianconi wrote:
> On Feb 28, Ben Pfaff wrote:
> > On upgrade, I think that this will suddenly change the MAC addresses of
> > all the VMs. Is there a way to avoid that? Should we add a release
> > note?
>
> Do you mean after the upgrade if
>
> On Mon, Mar 04, 2019 at 07:37:39PM +0100, Lorenzo Bianconi wrote:
> > > On Mon, Mar 04, 2019 at 05:14:14PM +0100, Lorenzo Bianconi wrote:
> > > > Update RA next_announce whenever min_interval and/or max_interval are
> > > > updated in sbrec_port_binding option. In the current implementation
>
On Mon, Mar 4, 2019 at 1:31 PM Ben Pfaff wrote:
>
> On Fri, Mar 01, 2019 at 10:56:37AM -0800, Han Zhou wrote:
> > From: Han Zhou
> >
> > In current OVSDB Raft design, when there are multiple transactions
> > pending, either from same server node or different nodes in the
> > cluster, only the
On Fri, Mar 01, 2019 at 10:56:37AM -0800, Han Zhou wrote:
> From: Han Zhou
>
> In current OVSDB Raft design, when there are multiple transactions
> pending, either from same server node or different nodes in the
> cluster, only the first one can be successful at once, and following
> ones will
Thanks! I think that 2-3 days should be fine.
On Mon, Mar 04, 2019 at 06:18:38PM +, Fernando Casas Schössow wrote:
> I'm running OVS through valgrind since last night and so far so good in terms
> of performance. Probably because this host is not running network intensive
> guests.
>
>
On Mon, Mar 04, 2019 at 07:37:39PM +0100, Lorenzo Bianconi wrote:
> > On Mon, Mar 04, 2019 at 05:14:14PM +0100, Lorenzo Bianconi wrote:
> > > Update RA next_announce whenever min_interval and/or max_interval are
> > > updated in sbrec_port_binding option. In the current implementation
> > > if
On Mon, Mar 04, 2019 at 12:36:20PM -0800, Han Zhou wrote:
> On Fri, Mar 1, 2019 at 9:34 PM Ben Pfaff wrote:
> >
> > On Fri, Mar 01, 2019 at 07:46:42PM -0800, Han Zhou wrote:
> > > From: Han Zhou
> > >
> > > Signed-off-by: Han Zhou
> > > ---
> > > v1->v2: update according to Ben's suggestion.
>
On Mon, Mar 04, 2019 at 12:10:22PM -0800, Han Zhou wrote:
> From: Han Zhou
>
> This patch updates text in NEWS committed by 5832e6a, so that it is
> easier to understand for end users.
>
> Signed-off-by: Han Zhou
Applied, thanks!
___
dev mailing
On Fri, Mar 1, 2019 at 9:34 PM Ben Pfaff wrote:
>
> On Fri, Mar 01, 2019 at 07:46:42PM -0800, Han Zhou wrote:
> > From: Han Zhou
> >
> > Signed-off-by: Han Zhou
> > ---
> > v1->v2: update according to Ben's suggestion.
>
> Thanks, applied to master.
I am terribly sorry that the v2 was actually
From: Han Zhou
This patch updates text in NEWS committed by 5832e6a, so that it is
easier to understand for end users.
Signed-off-by: Han Zhou
---
NEWS | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/NEWS b/NEWS
index 104b7be..5da6a74 100644
--- a/NEWS
+++
On Fri, Mar 01, 2019 at 10:56:36AM -0800, Han Zhou wrote:
> From: Han Zhou
>
> Run triggers after storage_run and read_db to make sure new raft
> updates are utilized in current iteration.
>
> Signed-off-by: Han Zhou
Thanks. I applied this patch to master.
I have not looked at patch 2 yet.
> On Mon, Mar 04, 2019 at 05:14:14PM +0100, Lorenzo Bianconi wrote:
> > Update RA next_announce whenever min_interval and/or max_interval are
> > updated in sbrec_port_binding option. In the current implementation
> > if ipv6_ra_configs:send_periodic is set to true before setting
> >
Glad to reach the devs! :D
Alpine Linux is currently using OVS 2.10.1 and the source for the package comes
from: http://www.openvswitch.org/releases/openvswitch-2.10.1.tar.gz
BTW I mentioned I'm running OVS on Alpine Linux a few times but just want to
give you more details about the build.
For
Cursos esenciales - Webinar Interactivo – Miércoles 13 de Marzo
Disminución del ausentismo laboral y problemas de horarios: Workshop
Innova Learn desarrolla este webinar para que aprendas a clasificar el
ausentismo, a trabajar con tus empleados
para erradicarlo y evitar que esta situación
I'm running OVS through valgrind since last night and so far so good in terms
of performance. Probably because this host is not running network intensive
guests.
I'm running this command from a screen session so I can detach from it without
killing valgrind:
valgrind --leak-check=full
On Sat, Mar 02, 2019 at 12:14:02PM +, Nitin Katiyar wrote:
> Hi,
>
> > -Original Message-
> > From: Ben Pfaff [mailto:b...@ovn.org]
> > Sent: Saturday, March 02, 2019 12:15 AM
> > To: Nitin Katiyar
> > Cc: ovs-dev@openvswitch.org; Manohar Krishnappa Chidambaraswamy
> >
> > Subject:
On Mon, Mar 04, 2019 at 05:14:14PM +0100, Lorenzo Bianconi wrote:
> Update RA next_announce whenever min_interval and/or max_interval are
> updated in sbrec_port_binding option. In the current implementation
> if ipv6_ra_configs:send_periodic is set to true before setting
>
On Sat, Mar 02, 2019 at 09:53:18AM +, Fernando Casas Schössow wrote:
> For this reason I'm adding OVS dev mailing list to the thread in case any of
> the devs want to have a look at the dump and debug this issue.
You've reached them already ;-)
> If anyone wants access to the dump, reply to
Running OVS through valgrind is probably going to be unacceptably slow.
If it works for you, though, then it will probably tell us the location
of the leak.
It is possibly a better option to use Address Sanitizer. It is just as
good as valgrind for locating memory leaks, but it is much, much
On Mon, Mar 04, 2019 at 06:45:37PM +0300, Ilya Maximets wrote:
> On 04.03.2019 18:37, Ben Pfaff wrote:
> > On Mon, Mar 04, 2019 at 10:14:10AM +0300, Ilya Maximets wrote:
> >> The master branch was force-pushed by someone recently.
> >> And I see some difference in the tree after that.
> >
> >
On Fri, Feb 01, 2019 at 03:58:31PM +, Pieter Jansen van Vuuren wrote:
> Firstly this patch introduces the notion of reserved priority, as the
> filter implementing ingress policing would require the highest priority.
> Secondly it allows setting rate limiters while tc-offloads has been
>
Update RA next_announce whenever min_interval and/or max_interval are
updated in sbrec_port_binding option. In the current implementation
if ipv6_ra_configs:send_periodic is set to true before setting
ipv6_ra_configs:{min,max}_interval, next_announce will be set using
default values and it will
Hi.
> Hello all,
> I have been trying build OVS using `make check` but I have been getting
> errors on a couple of branches.
>
> All of the mentioned branches were built with this script.
> ./boot.sh
> ./configure --enable-Werror
> make check
>
>
> On each I got these results:
> branch-2.6
On 04.03.2019 18:37, Ben Pfaff wrote:
> On Mon, Mar 04, 2019 at 10:14:10AM +0300, Ilya Maximets wrote:
>> The master branch was force-pushed by someone recently.
>> And I see some difference in the tree after that.
>
> Sorry about that. Justin accidentally pushed a huge messy merge to
> master,
On 28.02.2019 17:33, Ophir Munk wrote:
> From: Roni Bar Yanai
>
> Before offloading code was added to the netdev-dpdk.c file (MARK and
> RSS actions) the only DPDK RTE calls in use were rte_flow_create() and
> rte_flow_destroy(). In preparation for splitting the offloading code
> from the
Cursos esenciales - Webinar Interactivo – Martes 12 de Marzo
Finanzas para no Financieros.
Nuestro curso en una guía para el profesional que se desempeña en áreas
relativas al funcionamiento financiero de una organización
pero que no tiene precisamente la formación en el área. Abarcaremos los
"txfh2007" writes:
> Hi ：
> I got robot 0's reply as below, should I reply the rebot email by
> attaching the author information(Author:
> timo_liu (txfh2...@aliyun.com)) at the end of the patch ?
>
> Subject: Re: [ovs-dev] ovs-tcpdump: add dump_cmd checker before
> _doexec()
> Message-ID:
'netdev-dpdk.h' provides only 'netdev_dpdk_register' and
'free_dpdk_buf' which are not used in these files and should
not be used.
Leftovers from the already removed code.
Signed-off-by: Ilya Maximets
---
lib/dpctl.c | 1 -
lib/netdev.c | 1 -
lib/ofpbuf.c | 1 -
lib/ovs-thread.c |
33 matches
Mail list logo
