[ovs-dev] une alternative

[Benjamin]

Épanouissez-vous en aidant les autres !



Découvrez notre formation en .M.A.G.N.E.T.I.S.M.E.

























Apprenez,  par simple imposition des mains à soulager en ré-harmonisant les 
énergies.  Découvrez, comprenez et contrôlez ces incroyables pouvoirs qui sont 
cachés en vous.
Cliquez ICIpour en savoir plus













 Ce cursus estOUVERT A TOUSLe Magnétisme est une thérapie "alternative" 
efficace, sans danger, facile à  apprendre et à  pratiquer, afin de pouvoir 
aider les autres à  retrouver Santé et bien-être tant physique que 
psychologique.













Pour élaborer le contenu de ce stage nous nous sommes inspirés, à  la fois des 
méthodes utilisées par les guérisseurs traditionnels tels H. Durville, Kaly, 
Charly Samson, tout en y lire la suite

























Répondez à ce mail avec RETRAIT dans l'objet, afin de ne plus en recevoir 














---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
https://www.avast.com/antivirus
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] [PATCH 1/2] ovn: support applying ACLs to port groups

[Han Zhou]

On Mon, Apr 30, 2018 at 2:43 PM, Guru Shetty  wrote:

>
>
> On 22 April 2018 at 09:52, Han Zhou  wrote:
>
>> Although port group can be used in match conditions of ACLs, it is
>> still inconvenient for clients to figure out the lswitches that each
>> ACL should be applied to.
>>
>> This patch supports applying ACLs to port groups directly instead of
>> applying to each related lswitch individually. It provides convenience
>> for clients such as k8s and OpenStack Neutron.
>>
>> Requested-at: https://mail.openvswitch.org/p
>> ipermail/ovs-dev/2018-March/344856.html
>> Requested-by: Guru Shetty 
>> Requested-by: Daniel Alvarez Sanchez 
>> Signed-off-by: Han Zhou 
>>
>
> Thanks for the patch. I have not tested it, but just looked through the
> code and it looks like what I had in mind.
> So, you can technically use address sets or port groups in the ACLs inside
> a port group, right?
>
> Hi Guru, yes, you are right :)

>
>
>> ---
>>  NEWS|   3 +-
>>  ovn/northd/ovn-northd.c | 422 ++
>> +-
>>  ovn/ovn-nb.ovsschema|   9 +-
>>  ovn/ovn-nb.xml  |  19 ++-
>>  tests/ovn.at| 229 ++
>>  5 files changed, 526 insertions(+), 156 deletions(-)
>>
>> diff --git a/NEWS b/NEWS
>> index cd4ffbb..8601cfc 100644
>> --- a/NEWS
>> +++ b/NEWS
>> @@ -22,7 +22,8 @@ Post-v2.9.0
>> and reply with a RST for TCP or ICMPv4/ICMPv6 unreachable message
>> for
>> other IPv4/IPv6-based protocols whenever a reject ACL rule is hit.
>>   * ACL match conditions can now match on Port_Groups as well as
>> address
>> -   sets that are automatically generated by Port_Groups.
>> +   sets that are automatically generated by Port_Groups.  ACLs can be
>> +   applied directly to Port_Groups as well.
>>
>>  v2.9.0 - 19 Feb 2018
>>  
>> diff --git a/ovn/northd/ovn-northd.c b/ovn/northd/ovn-northd.c
>> index ce472a5..cd01756 100644
>> --- a/ovn/northd/ovn-northd.c
>> +++ b/ovn/northd/ovn-northd.c
>> @@ -3162,7 +3162,259 @@ build_reject_acl_rules(struct ovn_datapath *od,
>> struct hmap *lflows,
>>  }
>>
>>  static void
>> -build_acls(struct ovn_datapath *od, struct hmap *lflows)
>> +consider_acl(struct hmap *lflows, struct ovn_datapath *od,
>> + struct nbrec_acl *acl, bool has_stateful)
>> +{
>> +bool ingress = !strcmp(acl->direction, "from-lport") ? true :false;
>> +enum ovn_stage stage = ingress ? S_SWITCH_IN_ACL : S_SWITCH_OUT_ACL;
>> +
>> +char *stage_hint = xasprintf("%08x", acl->header_.uuid.parts[0]);
>> +if (!strcmp(acl->action, "allow")
>> +|| !strcmp(acl->action, "allow-related")) {
>> +/* If there are any stateful flows, we must even commit "allow"
>> + * actions.  This is because, while the initiater's
>> + * direction may not have any stateful rules, the server's
>> + * may and then its return traffic would not have an
>> + * associated conntrack entry and would return "+invalid". */
>> +if (!has_stateful) {
>> +struct ds actions = DS_EMPTY_INITIALIZER;
>> +build_acl_log(, acl);
>> +ds_put_cstr(, "next;");
>> +ovn_lflow_add_with_hint(lflows, od, stage,
>> +acl->priority + OVN_ACL_PRI_OFFSET,
>> +acl->match, ds_cstr(),
>> +stage_hint);
>> +ds_destroy();
>> +} else {
>> +struct ds match = DS_EMPTY_INITIALIZER;
>> +struct ds actions = DS_EMPTY_INITIALIZER;
>> +
>> +/* Commit the connection tracking entry if it's a new
>> + * connection that matches this ACL.  After this commit,
>> + * the reply traffic is allowed by a flow we create at
>> + * priority 65535, defined earlier.
>> + *
>> + * It's also possible that a known connection was marked for
>> + * deletion after a policy was deleted, but the policy was
>> + * re-added while that connection is still known.  We catch
>> + * that case here and un-set ct_label.blocked (which will be
>> done
>> + * by ct_commit in the "stateful" stage) to indicate that the
>> + * connection should be allowed to resume.
>> + */
>> +ds_put_format(, "((ct.new && !ct.est)"
>> +  " || (!ct.new && ct.est && !ct.rpl "
>> +   "&& ct_label.blocked == 1)) "
>> +  "&& (%s)", acl->match);
>> +ds_put_cstr(, REGBIT_CONNTRACK_COMMIT" = 1; ");
>> +build_acl_log(, acl);
>> +ds_put_cstr(, "next;");
>> +ovn_lflow_add_with_hint(lflows, od, stage,
>> +acl->priority + 

Re: [ovs-dev] [PATCH 1/2] ovn: support applying ACLs to port groups

[Guru Shetty]

On 22 April 2018 at 09:52, Han Zhou  wrote:

> Although port group can be used in match conditions of ACLs, it is
> still inconvenient for clients to figure out the lswitches that each
> ACL should be applied to.
>
> This patch supports applying ACLs to port groups directly instead of
> applying to each related lswitch individually. It provides convenience
> for clients such as k8s and OpenStack Neutron.
>
> Requested-at: https://mail.openvswitch.org/pipermail/ovs-dev/2018-March/
> 344856.html
> Requested-by: Guru Shetty 
> Requested-by: Daniel Alvarez Sanchez 
> Signed-off-by: Han Zhou 
>

Thanks for the patch. I have not tested it, but just looked through the
code and it looks like what I had in mind.
So, you can technically use address sets or port groups in the ACLs inside
a port group, right?



> ---
>  NEWS|   3 +-
>  ovn/northd/ovn-northd.c | 422 ++
> +-
>  ovn/ovn-nb.ovsschema|   9 +-
>  ovn/ovn-nb.xml  |  19 ++-
>  tests/ovn.at| 229 ++
>  5 files changed, 526 insertions(+), 156 deletions(-)
>
> diff --git a/NEWS b/NEWS
> index cd4ffbb..8601cfc 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -22,7 +22,8 @@ Post-v2.9.0
> and reply with a RST for TCP or ICMPv4/ICMPv6 unreachable message
> for
> other IPv4/IPv6-based protocols whenever a reject ACL rule is hit.
>   * ACL match conditions can now match on Port_Groups as well as
> address
> -   sets that are automatically generated by Port_Groups.
> +   sets that are automatically generated by Port_Groups.  ACLs can be
> +   applied directly to Port_Groups as well.
>
>  v2.9.0 - 19 Feb 2018
>  
> diff --git a/ovn/northd/ovn-northd.c b/ovn/northd/ovn-northd.c
> index ce472a5..cd01756 100644
> --- a/ovn/northd/ovn-northd.c
> +++ b/ovn/northd/ovn-northd.c
> @@ -3162,7 +3162,259 @@ build_reject_acl_rules(struct ovn_datapath *od,
> struct hmap *lflows,
>  }
>
>  static void
> -build_acls(struct ovn_datapath *od, struct hmap *lflows)
> +consider_acl(struct hmap *lflows, struct ovn_datapath *od,
> + struct nbrec_acl *acl, bool has_stateful)
> +{
> +bool ingress = !strcmp(acl->direction, "from-lport") ? true :false;
> +enum ovn_stage stage = ingress ? S_SWITCH_IN_ACL : S_SWITCH_OUT_ACL;
> +
> +char *stage_hint = xasprintf("%08x", acl->header_.uuid.parts[0]);
> +if (!strcmp(acl->action, "allow")
> +|| !strcmp(acl->action, "allow-related")) {
> +/* If there are any stateful flows, we must even commit "allow"
> + * actions.  This is because, while the initiater's
> + * direction may not have any stateful rules, the server's
> + * may and then its return traffic would not have an
> + * associated conntrack entry and would return "+invalid". */
> +if (!has_stateful) {
> +struct ds actions = DS_EMPTY_INITIALIZER;
> +build_acl_log(, acl);
> +ds_put_cstr(, "next;");
> +ovn_lflow_add_with_hint(lflows, od, stage,
> +acl->priority + OVN_ACL_PRI_OFFSET,
> +acl->match, ds_cstr(),
> +stage_hint);
> +ds_destroy();
> +} else {
> +struct ds match = DS_EMPTY_INITIALIZER;
> +struct ds actions = DS_EMPTY_INITIALIZER;
> +
> +/* Commit the connection tracking entry if it's a new
> + * connection that matches this ACL.  After this commit,
> + * the reply traffic is allowed by a flow we create at
> + * priority 65535, defined earlier.
> + *
> + * It's also possible that a known connection was marked for
> + * deletion after a policy was deleted, but the policy was
> + * re-added while that connection is still known.  We catch
> + * that case here and un-set ct_label.blocked (which will be
> done
> + * by ct_commit in the "stateful" stage) to indicate that the
> + * connection should be allowed to resume.
> + */
> +ds_put_format(, "((ct.new && !ct.est)"
> +  " || (!ct.new && ct.est && !ct.rpl "
> +   "&& ct_label.blocked == 1)) "
> +  "&& (%s)", acl->match);
> +ds_put_cstr(, REGBIT_CONNTRACK_COMMIT" = 1; ");
> +build_acl_log(, acl);
> +ds_put_cstr(, "next;");
> +ovn_lflow_add_with_hint(lflows, od, stage,
> +acl->priority + OVN_ACL_PRI_OFFSET,
> +ds_cstr(),
> +ds_cstr(),
> +stage_hint);
> +
> +/* Match on traffic in the request 

Re: [ovs-dev] [PATCH v2] datapath-windows: Prevent ct-counters from getting redundantly incremented

[Ben Pfaff]

On Mon, Apr 30, 2018 at 11:47:43PM +0300, Alin Gabriel Serdean wrote:
> 
> 
> > On 30 Apr 2018, at 23:36, Ben Pfaff  wrote:
> > 
> > On Mon, Apr 30, 2018 at 11:26:52PM +0300, Alin Gabriel Serdean wrote:
> >> 
> >>> On 28 Apr 2018, at 21:26, Ben Pfaff  wrote:
> >>> 
> >>> On Fri, Apr 27, 2018 at 08:03:43PM +0300, Alin Gabriel Serdean wrote:
>  
> > On 27 Apr 2018, at 20:00, Anand Kumar  wrote:
> > 
> > The conntrack-counters ought to be incremented only if it's a new lookup
> > or if it's recirculated through a different zone for the first time.
> > 
> > Signed-off-by: Anand Kumar 
> > ---
> > datapath-windows/ovsext/Conntrack.c | 7 ---
> > 1 file changed, 4 insertions(+), 3 deletions(-)
> > 
> > diff --git a/datapath-windows/ovsext/Conntrack.c 
> > b/datapath-windows/ovsext/Conntrack.c
> > index 678bedb..add1491 100644
> > --- a/datapath-windows/ovsext/Conntrack.c
> > +++ b/datapath-windows/ovsext/Conntrack.c
> > @@ -886,10 +886,11 @@ OvsCtExecute_(OvsForwardingContext *fwdCtx,
> >   return NDIS_STATUS_RESOURCES;
> >   }
> > 
> > -/* Increment the counters soon after the lookup, since we set 
> > ct.state
> > - * to OVS_CS_F_TRACKED after processing the ct entry.
> > +/* Increment stats for the entry if it wasn't tracked previously or
> > + * if they are on different zones
> >*/
> > -if (entry && (!(key->ct.state & OVS_CS_F_TRACKED))) {
> > +if (entry && (entry->key.zone != key->ct.zone ||
> > +   (!(key->ct.state & OVS_CS_F_TRACKED {
> >   OvsCtIncrementCounters(entry, ctx.reply, curNbl);
> >   }
> > 
> > -- 
> > 2.9.3.windows.1
> > 
> > ___
> > dev mailing list
> > d...@openvswitch.org
> > https://mail.openvswitch.org/mailman/listinfo/ovs-dev 
> > 
>  
>  Acked-by: Alin Gabriel Serdean   >
> >>> 
> >>> Do you want to apply this to the tree?
> >> 
> >> I will apply them thanks for asking Ben. I am on vacation this week so 
> >> response will be increased :).
> > 
> > I'll be in Copenhagen this week (leaving for the airport in about 90
> > minutes actually), so me too.
> 
> I saw that you are going to kubecon! I hope you enjoy your time over there 
> :). 
> 
> I hope you and Alin Balutoiu can come and say hi!

That's a good idea.  Alin B., will you be at the Cloudbase booth?  I'm
going to be at the VMware booth myself Wednesday 3:30-4:30 and Thursday
4:30-5:30 for "open source office hours".
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] [PATCH v2] datapath-windows: Prevent ct-counters from getting redundantly incremented

[Alin Gabriel Serdean]

> On 30 Apr 2018, at 23:36, Ben Pfaff  wrote:
> 
> On Mon, Apr 30, 2018 at 11:26:52PM +0300, Alin Gabriel Serdean wrote:
>> 
>>> On 28 Apr 2018, at 21:26, Ben Pfaff  wrote:
>>> 
>>> On Fri, Apr 27, 2018 at 08:03:43PM +0300, Alin Gabriel Serdean wrote:
 
> On 27 Apr 2018, at 20:00, Anand Kumar  wrote:
> 
> The conntrack-counters ought to be incremented only if it's a new lookup
> or if it's recirculated through a different zone for the first time.
> 
> Signed-off-by: Anand Kumar 
> ---
> datapath-windows/ovsext/Conntrack.c | 7 ---
> 1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/datapath-windows/ovsext/Conntrack.c 
> b/datapath-windows/ovsext/Conntrack.c
> index 678bedb..add1491 100644
> --- a/datapath-windows/ovsext/Conntrack.c
> +++ b/datapath-windows/ovsext/Conntrack.c
> @@ -886,10 +886,11 @@ OvsCtExecute_(OvsForwardingContext *fwdCtx,
>   return NDIS_STATUS_RESOURCES;
>   }
> 
> -/* Increment the counters soon after the lookup, since we set 
> ct.state
> - * to OVS_CS_F_TRACKED after processing the ct entry.
> +/* Increment stats for the entry if it wasn't tracked previously or
> + * if they are on different zones
>*/
> -if (entry && (!(key->ct.state & OVS_CS_F_TRACKED))) {
> +if (entry && (entry->key.zone != key->ct.zone ||
> +   (!(key->ct.state & OVS_CS_F_TRACKED {
>   OvsCtIncrementCounters(entry, ctx.reply, curNbl);
>   }
> 
> -- 
> 2.9.3.windows.1
> 
> ___
> dev mailing list
> d...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev 
> 
 
 Acked-by: Alin Gabriel Serdean >
>>> 
>>> Do you want to apply this to the tree?
>> 
>> I will apply them thanks for asking Ben. I am on vacation this week so 
>> response will be increased :).
> 
> I'll be in Copenhagen this week (leaving for the airport in about 90
> minutes actually), so me too.

I saw that you are going to kubecon! I hope you enjoy your time over there :). 

I hope you and Alin Balutoiu can come and say hi!

- Alin.

___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

[ovs-dev] [PATCH] windows: Fix return value in case of named pipe send failure

[Alin Gabriel Serdean]

Named pipes should emulate UNIX socket behavior.

Until now the named pipes returned WSA (Windows implementation of BSD sockets
errors) return codes, for send errors.

In case of a disconnected named pipe (UNIX socket) send error, we should return
EPIPE.

Fixes: `check_logs` transient errors when checking for EPIPE.

Signed-off-by: Alin Gabriel Serdean 
---
 lib/stream-windows.c | 6 +++---
 tests/test-vconn.c   | 4 
 2 files changed, 3 insertions(+), 7 deletions(-)

diff --git a/lib/stream-windows.c b/lib/stream-windows.c
index d908ee972..34bc610b6 100644
--- a/lib/stream-windows.c
+++ b/lib/stream-windows.c
@@ -308,7 +308,7 @@ windows_send(struct stream *stream, const void *buffer, 
size_t n)
|| last_error == ERROR_NO_DATA
|| last_error == ERROR_BROKEN_PIPE) {
 /* If the pipe was disconnected, return connection reset. */
-return -WSAECONNRESET;
+return -EPIPE;
 } else {
 VLOG_ERR_RL(, "Could not send data on named pipe. Last "
 "error: %s", ovs_lasterror_to_string());
@@ -321,7 +321,7 @@ windows_send(struct stream *stream, const void *buffer, 
size_t n)
 
 result = WriteFile(s->fd, buffer, n, &(DWORD)retval, ov);
 last_error = GetLastError();
-if (!result && GetLastError() == ERROR_IO_PENDING) {
+if (!result && last_error == ERROR_IO_PENDING) {
 /* Mark the send operation as pending. */
 s->write_pending = true;
 return -EAGAIN;
@@ -330,7 +330,7 @@ windows_send(struct stream *stream, const void *buffer, 
size_t n)
|| last_error == ERROR_NO_DATA
|| last_error == ERROR_BROKEN_PIPE)) {
 /* If the pipe was disconnected, return connection reset. */
-return -WSAECONNRESET;
+return -EPIPE;
 } else if (!result) {
 VLOG_ERR_RL(, "Could not send data on synchronous named pipe. Last "
 "error: %s", ovs_lasterror_to_string());
diff --git a/tests/test-vconn.c b/tests/test-vconn.c
index 0c17a8395..8b8d12e36 100644
--- a/tests/test-vconn.c
+++ b/tests/test-vconn.c
@@ -163,11 +163,7 @@ test_refuse_connection(struct ovs_cmdl_context *ctx)
   error, ovs_strerror(error));
 }
 } else if (!strcmp(type, "unix")) {
-#ifndef _WIN32
 CHECK_ERRNO(error, EPIPE);
-#else
-CHECK_ERRNO(error, WSAECONNRESET);
-#endif
 } else if (!strcmp(type, "ssl")) {
 if (error != EPROTO && error != ECONNRESET) {
 ovs_fatal(0, "unexpected vconn_connect() return value %d (%s)",
-- 
2.16.1.windows.1

___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] [PATCH v2] datapath-windows: Prevent ct-counters from getting redundantly incremented

[Ben Pfaff]

On Mon, Apr 30, 2018 at 11:26:52PM +0300, Alin Gabriel Serdean wrote:
> 
> > On 28 Apr 2018, at 21:26, Ben Pfaff  wrote:
> > 
> > On Fri, Apr 27, 2018 at 08:03:43PM +0300, Alin Gabriel Serdean wrote:
> >> 
> >>> On 27 Apr 2018, at 20:00, Anand Kumar  wrote:
> >>> 
> >>> The conntrack-counters ought to be incremented only if it's a new lookup
> >>> or if it's recirculated through a different zone for the first time.
> >>> 
> >>> Signed-off-by: Anand Kumar 
> >>> ---
> >>> datapath-windows/ovsext/Conntrack.c | 7 ---
> >>> 1 file changed, 4 insertions(+), 3 deletions(-)
> >>> 
> >>> diff --git a/datapath-windows/ovsext/Conntrack.c 
> >>> b/datapath-windows/ovsext/Conntrack.c
> >>> index 678bedb..add1491 100644
> >>> --- a/datapath-windows/ovsext/Conntrack.c
> >>> +++ b/datapath-windows/ovsext/Conntrack.c
> >>> @@ -886,10 +886,11 @@ OvsCtExecute_(OvsForwardingContext *fwdCtx,
> >>>return NDIS_STATUS_RESOURCES;
> >>>}
> >>> 
> >>> -/* Increment the counters soon after the lookup, since we set 
> >>> ct.state
> >>> - * to OVS_CS_F_TRACKED after processing the ct entry.
> >>> +/* Increment stats for the entry if it wasn't tracked previously or
> >>> + * if they are on different zones
> >>> */
> >>> -if (entry && (!(key->ct.state & OVS_CS_F_TRACKED))) {
> >>> +if (entry && (entry->key.zone != key->ct.zone ||
> >>> +   (!(key->ct.state & OVS_CS_F_TRACKED {
> >>>OvsCtIncrementCounters(entry, ctx.reply, curNbl);
> >>>}
> >>> 
> >>> -- 
> >>> 2.9.3.windows.1
> >>> 
> >>> ___
> >>> dev mailing list
> >>> d...@openvswitch.org
> >>> https://mail.openvswitch.org/mailman/listinfo/ovs-dev 
> >>> 
> >> 
> >> Acked-by: Alin Gabriel Serdean >
> > 
> > Do you want to apply this to the tree?
> 
> I will apply them thanks for asking Ben. I am on vacation this week so 
> response will be increased :).

I'll be in Copenhagen this week (leaving for the airport in about 90
minutes actually), so me too.
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] [PATCH v2] datapath-windows: Prevent ct-counters from getting redundantly incremented

[Alin Serdean]

> On 27 Apr 2018, at 20:00, Anand Kumar  wrote:
> 
> The conntrack-counters ought to be incremented only if it's a new lookup
> or if it's recirculated through a different zone for the first time.
> 
> Signed-off-by: Anand Kumar 

Applied on master. Thanks Anand!

___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] [PATCH v2] datapath-windows: Prevent ct-counters from getting redundantly incremented

[Alin Gabriel Serdean]

> On 28 Apr 2018, at 21:26, Ben Pfaff  wrote:
> 
> On Fri, Apr 27, 2018 at 08:03:43PM +0300, Alin Gabriel Serdean wrote:
>> 
>>> On 27 Apr 2018, at 20:00, Anand Kumar  wrote:
>>> 
>>> The conntrack-counters ought to be incremented only if it's a new lookup
>>> or if it's recirculated through a different zone for the first time.
>>> 
>>> Signed-off-by: Anand Kumar 
>>> ---
>>> datapath-windows/ovsext/Conntrack.c | 7 ---
>>> 1 file changed, 4 insertions(+), 3 deletions(-)
>>> 
>>> diff --git a/datapath-windows/ovsext/Conntrack.c 
>>> b/datapath-windows/ovsext/Conntrack.c
>>> index 678bedb..add1491 100644
>>> --- a/datapath-windows/ovsext/Conntrack.c
>>> +++ b/datapath-windows/ovsext/Conntrack.c
>>> @@ -886,10 +886,11 @@ OvsCtExecute_(OvsForwardingContext *fwdCtx,
>>>return NDIS_STATUS_RESOURCES;
>>>}
>>> 
>>> -/* Increment the counters soon after the lookup, since we set ct.state
>>> - * to OVS_CS_F_TRACKED after processing the ct entry.
>>> +/* Increment stats for the entry if it wasn't tracked previously or
>>> + * if they are on different zones
>>> */
>>> -if (entry && (!(key->ct.state & OVS_CS_F_TRACKED))) {
>>> +if (entry && (entry->key.zone != key->ct.zone ||
>>> +   (!(key->ct.state & OVS_CS_F_TRACKED {
>>>OvsCtIncrementCounters(entry, ctx.reply, curNbl);
>>>}
>>> 
>>> -- 
>>> 2.9.3.windows.1
>>> 
>>> ___
>>> dev mailing list
>>> d...@openvswitch.org
>>> https://mail.openvswitch.org/mailman/listinfo/ovs-dev 
>>> 
>> 
>> Acked-by: Alin Gabriel Serdean >
> 
> Do you want to apply this to the tree?

I will apply them thanks for asking Ben. I am on vacation this week so response 
will be increased :).

> ___
> dev mailing list
> d...@openvswitch.org 
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev 
> 
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

[ovs-dev] Call Center Services for H Gateway International Inc

[Emily Kirkland]

Hello,

My name is Emily and I am with TryCallCenter,
a service that compares quotes for Call Centers.
Call Centers can be leveraged for Customer Support,
scheduling appointments and increasing sales in many industries.
Handle all your customer calls in a professional manner
and generate sales utilizing qualified salespeople.

Please provide the following information in order to compose a Quote:

* First and Last Name
* Company Name
* Phone number
* Postal code
* How many monthly calls do you anticipate?
* What type of coverage are you looking for ?


I encourage you check our pricing by replying to this email.

Best regards,
Emily Kirkland
Call Center Specialist
em...@trycallcenter.site


Unsubscribe by reply back "REMOVE".
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] [PATCH v3] rhel: user/group openvswitch does not exist

[Aaron Conole]

Markos Chandras  writes:

> On 19/04/18 16:27, Aaron Conole wrote:
>> From: Alan Pevec 
>> 
>> Default ownership[1] for config files is failing on an empty system:
>>   Running scriptlet: openvswitch-2.9.0-3.fc28.x86_64
>> warning: user openvswitch does not exist - using root
>> warning: group openvswitch does not exist - using root
>> ...
>> 
>> Required user/group need to be created in %pre as documented in
>> Fedora guideline[2]
>> 
>> [1]
>> https://github.com/openvswitch/ovs/commit/951d79e638ecdb3b1dcd19df1adb2ff91fe61af8
>> 
>> [2] 
>> https://fedoraproject.org/wiki/Packaging:UsersAndGroups#Dynamic_allocation
>> 
>> Submitted-at: https://github.com/openvswitch/ovs/pull/223
>> Signed-off-by: Alan Pevec 
>> Co-authored-by: Aaron Conole 
>> Signed-off-by: Aaron Conole 
>
> Reviewed-by: Markos Chandras 

Thanks Markos.

Timothy, Russell, sorry I forgot to CC you, it seems.

___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] [PATCH v3] rhel: user/group openvswitch does not exist

[Markos Chandras]

On 19/04/18 16:27, Aaron Conole wrote:
> From: Alan Pevec 
> 
> Default ownership[1] for config files is failing on an empty system:
>   Running scriptlet: openvswitch-2.9.0-3.fc28.x86_64
> warning: user openvswitch does not exist - using root
> warning: group openvswitch does not exist - using root
> ...
> 
> Required user/group need to be created in %pre as documented in
> Fedora guideline[2]
> 
> [1] 
> https://github.com/openvswitch/ovs/commit/951d79e638ecdb3b1dcd19df1adb2ff91fe61af8
> 
> [2] https://fedoraproject.org/wiki/Packaging:UsersAndGroups#Dynamic_allocation
> 
> Submitted-at: https://github.com/openvswitch/ovs/pull/223
> Signed-off-by: Alan Pevec 
> Co-authored-by: Aaron Conole 
> Signed-off-by: Aaron Conole 

Reviewed-by: Markos Chandras 

-- 
markos

SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] interface mac setting

[Ben Pfaff]

On Tue, Apr 24, 2018 at 10:55:36AM +0800, Tonghao Zhang wrote:
> One question, why now ovs can only set the mac of internal interface,
> for example:
> 
> ovs-vsctl set Interface p1 type=internal mac=\"00:11:22:33:44:55\"
> ovs-vsctl get Interface p1 mac_in_use
> 
> And the doc about 'mac' is not explained, why we cannot set it for
> other type interface. So it's a bug?

It's more like a bug in the documentation.  Please feel free to submit
an update.

The reasoning here is that the OVS database isn't a good place to set
things for which OVS is not the source of truth.  Suppose someone comes
along and runs "ifconfig" or "ip" to change the MAC address.  In that
case, the OVS database is then out-of-date.  Should OVS then immediately
set the MAC address back to what's in the database?  It's not good for
OVS to start fights like that.
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

[ovs-dev] [PATCH] ovn.at: fix occasional dns lookup test failure

[Han Zhou]

The option "--wait=hv" was missed when adding back the DNS options
for ls1-lp1 using ovn-nbctl, so the test case failed occasionally.
This commit fix the same.

Signed-off-by: Han Zhou 
---
 tests/ovn.at | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/ovn.at b/tests/ovn.at
index 4a53165..3cc135d 100644
--- a/tests/ovn.at
+++ b/tests/ovn.at
@@ -7064,7 +7064,7 @@ rm -f 2.expected
 
 # Test IPv6 ( records) using IPv4 packet.
 # Add back the DNS options for ls1-lp1.
-ovn-nbctl set DNS $DNS1 records:vm1.ovn.org="10.0.0.4 aef0::4"
+ovn-nbctl --wait=hv set DNS $DNS1 records:vm1.ovn.org="10.0.0.4 aef0::4"
 
 set_dns_params vm1_ipv6_only
 src_ip=`ip_to_hex 10 0 0 6`
-- 
2.1.0

___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

[ovs-dev] Técnicas y cierres de Venta

[Dificultades y objeciones en el cierre]

 
 

 

Mayo 04- webinar Interactivo
Técnicas y cierres de Venta

Empieza a Negociar:

1. Delimitación de la necesidad del cliente: sondeo abierto y sondeo cerrado.
2. Conocimiento del producto o servicio: características, ventajas, beneficios 
y pruebas para satisfacer la necesidad.
3. Negociar a la manera competitivo-defensiva: ¿en qué consiste?
4. Pautas para negociar. 
5. Reglas básicas a tener muy en cuenta al empezar. 

Temas a tratar:

- No todos los clientes son iguales. 
- Fidelizar a un clienten.
- Diez cosas que puedes hacer para que tu cliente responda positivamente. 
- Causas de Terminación y Rescisión Laboral. 

 
 
Temario e Inscripciones:

Respondiendo por este medio "Cierres"+TELÉFONO + NOMBRE o marcando al:

045 + 5515546630  



___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] OVS DPDK: dpdk_merge pull request for master

[Stokes, Ian]

> -Original Message-
> From: Ben Pfaff [mailto:b...@ovn.org]
> Sent: Monday, April 30, 2018 4:45 PM
> To: Stokes, Ian 
> Cc: d...@openvswitch.org
> Subject: Re: OVS DPDK: dpdk_merge pull request for master
> 
> On Mon, Apr 30, 2018 at 08:40:33AM -0700, Ben Pfaff wrote:
> > On Mon, Apr 30, 2018 at 03:29:56PM +, Stokes, Ian wrote:
> > > > Hi Ben,
> > > >
> > > > The following changes since commit
> > > > f82b3b6a2f4d024ce671b1e3b11aa92d29f2564d:
> > > >
> > > >   ofproto-dpif-upcall: Only call ovsrcu_postpone() on active
> > > > actions
> > > > (2018-04-19 09:29:22 -0700)
> > > >
> > > > are available in the git repository at:
> > > >
> > > >   https://github.com/istokes/ovs dpdk_merge
> > > >
> > > > for you to fetch changes up to
> a7e4849ef0096f4396cc17afeb5325af8d1b4e3b:
> > > >
> > > >   tests: Add system-dpdk-testsuite (2018-04-21 18:29:57 +0100)
> > >
> > > Hi Ben,
> > >
> > > Just a quick ping on this, I know you mentioned your busy with travel
> but if you have time to merge these pull requests when time allows it
> would be greatly appreciated.
> >
> > Thanks for the reminder.  I did mean to get to this sooner than I have.
> >
> > I merged this to master.
> 
> I've merged all of the other pull requests into their respective branches
> now too.  Thank you!

Thanks Ben,

Much appreciated!

Ian
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] OVS DPDK: dpdk_merge pull request for master

[Ben Pfaff]

On Mon, Apr 30, 2018 at 08:40:33AM -0700, Ben Pfaff wrote:
> On Mon, Apr 30, 2018 at 03:29:56PM +, Stokes, Ian wrote:
> > > Hi Ben,
> > > 
> > > The following changes since commit
> > > f82b3b6a2f4d024ce671b1e3b11aa92d29f2564d:
> > > 
> > >   ofproto-dpif-upcall: Only call ovsrcu_postpone() on active actions
> > > (2018-04-19 09:29:22 -0700)
> > > 
> > > are available in the git repository at:
> > > 
> > >   https://github.com/istokes/ovs dpdk_merge
> > > 
> > > for you to fetch changes up to a7e4849ef0096f4396cc17afeb5325af8d1b4e3b:
> > > 
> > >   tests: Add system-dpdk-testsuite (2018-04-21 18:29:57 +0100)
> > 
> > Hi Ben,
> > 
> > Just a quick ping on this, I know you mentioned your busy with travel but 
> > if you have time to merge these pull requests when time allows it would be 
> > greatly appreciated.
> 
> Thanks for the reminder.  I did mean to get to this sooner than I have.
> 
> I merged this to master.

I've merged all of the other pull requests into their respective
branches now too.  Thank you!
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] OVS DPDK: dpdk_merge pull request for master

[Ben Pfaff]

On Mon, Apr 30, 2018 at 03:29:56PM +, Stokes, Ian wrote:
> > Hi Ben,
> > 
> > The following changes since commit
> > f82b3b6a2f4d024ce671b1e3b11aa92d29f2564d:
> > 
> >   ofproto-dpif-upcall: Only call ovsrcu_postpone() on active actions
> > (2018-04-19 09:29:22 -0700)
> > 
> > are available in the git repository at:
> > 
> >   https://github.com/istokes/ovs dpdk_merge
> > 
> > for you to fetch changes up to a7e4849ef0096f4396cc17afeb5325af8d1b4e3b:
> > 
> >   tests: Add system-dpdk-testsuite (2018-04-21 18:29:57 +0100)
> 
> Hi Ben,
> 
> Just a quick ping on this, I know you mentioned your busy with travel but if 
> you have time to merge these pull requests when time allows it would be 
> greatly appreciated.

Thanks for the reminder.  I did mean to get to this sooner than I have.

I merged this to master.
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] OVS DPDK: dpdk_merge pull request for master

[Stokes, Ian]

> Hi Ben,
> 
> The following changes since commit
> f82b3b6a2f4d024ce671b1e3b11aa92d29f2564d:
> 
>   ofproto-dpif-upcall: Only call ovsrcu_postpone() on active actions
> (2018-04-19 09:29:22 -0700)
> 
> are available in the git repository at:
> 
>   https://github.com/istokes/ovs dpdk_merge
> 
> for you to fetch changes up to a7e4849ef0096f4396cc17afeb5325af8d1b4e3b:
> 
>   tests: Add system-dpdk-testsuite (2018-04-21 18:29:57 +0100)

Hi Ben,

Just a quick ping on this, I know you mentioned your busy with travel but if 
you have time to merge these pull requests when time allows it would be greatly 
appreciated.

Thanks
Ian
> 
> 
> Ian Stokes (4):
>   docs: Fix sflow documentation url and markup.
>   docs: Fix style guide url in DocumentationStyle.rst.
>   docs: Fix sphinx urls.
>   docs: Fix urls in index.rst.
> 
> Kevin Traynor (1):
>   netdev-dpdk: Free mempool only when no in-use mbufs.
> 
> Marcelo Ricardo Leitner (1):
>   netdev-dpdk: fix MAC address in port addr example
> 
> Marcin Rybka (1):
>   tests: Add system-dpdk-testsuite
> 
> Stephen Finucane (9):
>   doc: Add an overview of the 'dpdk' port
>   doc: Add "PMD" topic document
>   doc: Move additional sections to "physical ports" doc
>   doc: Add "vdev" topic document
>   doc: Move "QoS" guide to its own document
>   doc: Add "bridge" topic document
>   doc: Move "pdump" guide to its own document
>   doc: Add "jumbo frames" topic document
>   docs: Clarify changes in Rx queue allocation
> 
> Tiago Lam (2):
>   dpdk docs: Drop qemu-kvm for qemu-system-x86_64.
>   dpdk docs: Drop file share in libvirt config.
> 
>  Documentation/automake.mk|   7 +++
>  Documentation/conf.py|   2 +-
>  Documentation/howto/dpdk.rst | 415
> +-
> --
> 
>  Documentation/howto/sflow.rst|   9 ++--
>  Documentation/internals/contributing/documentation-style.rst |   7 +--
>  Documentation/intro/install/documentation.rst|   4 +-
>  Documentation/ref/index.rst  | 214
> +++---
> -
>  Documentation/topics/dpdk/bridge.rst | 104
> ++
>  Documentation/topics/dpdk/index.rst  |  14 +-
>  Documentation/topics/dpdk/jumbo-frames.rst   |  73
> ++
>  Documentation/topics/dpdk/pdump.rst  |  67
> +++
>  Documentation/topics/dpdk/phy.rst| 226
> ++
> +
>  Documentation/topics/dpdk/pmd.rst| 164
> ++
>  Documentation/topics/dpdk/qos.rst|  78
> 
>  Documentation/topics/dpdk/ring.rst   |   5 +++
>  Documentation/topics/dpdk/vdev.rst   |  66
> +++
>  Documentation/topics/dpdk/vhost-user.rst |  47
> +--
>  Documentation/topics/testing.rst |  23
> ++
>  NEWS |   5 +++
>  lib/netdev-dpdk.c|  86
> ---
>  tests/automake.mk|  17
> +++
>  tests/system-dpdk-macros.at  |  56
> +++
>  tests/system-dpdk-testsuite.at   |  25
> +++
>  tests/system-dpdk.at |  67
> +++
>  24 files changed, 1238 insertions(+), 543 deletions(-)  create mode
> 100644 Documentation/topics/dpdk/bridge.rst
>  create mode 100644 Documentation/topics/dpdk/jumbo-frames.rst
>  create mode 100644 Documentation/topics/dpdk/pdump.rst
>  create mode 100644 Documentation/topics/dpdk/phy.rst  create mode 100644
> Documentation/topics/dpdk/pmd.rst  create mode 100644
> Documentation/topics/dpdk/qos.rst  create mode 100644
> Documentation/topics/dpdk/vdev.rst
>  create mode 100644 tests/system-dpdk-macros.at  create mode 100644
> tests/system-dpdk-testsuite.at  create mode 100644 tests/system-dpdk.at
> 
> Regards
> Ian
> ___
> dev mailing list
> d...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev

[ovs-dev] indicadores clave para el desempeño

[Primero define los objetivos]

En línea y en Vivo / Para todo su Equipo con una sola Conexión 

Cómo diseñar y aplicar indicadores clave para el desempeño
18 de Mayo - Online en Vivo - 10:00 a 13:00 y de 15:00 a 18:00 Hrs   
 
Para lograr crecimiento en una empresa no solo basta con definir objetivos. Lo 
ideal es generar indicadores que permitan realizar una radiografía de los 
procedimientos realizados para alcanzar una meta. Al construir tu medición de 
resultados debes tener claridad en la meta que esperas y en la forma en la que 
los empleados llegarán a ella. La Matriz de Indicadores para Resultados (MIR) 
se construye para alinear los objetivos de las Empresas.
 
TEMARIO: 


1. Tipos de indicadores.

2. Cómo definir un indicador.

3. Partes de un indicador.

4. Otros conceptos.

...¡Y mucho más!

 
¿Requiere la información a la Brevedad?
responda este email con la palabra: 
Indicadores.
Junto con los siguientes datos:
Nombre:
Teléfono:
Empresa:
centro telefónico: 018002129393
  

Lic. Arturo López
Coordinador de Evento
 
¿Demasiados mensajes en su cuenta? Responda este mensaje indicando que solo 
desea recibir CALENDARIO y sólo recibirá un correo al mes. Si desea cancelar la 
suscripción, solicite su BAJA. 
 
 


___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

[ovs-dev] Dell Users Contact List

[Meghan Hudson]

Hi,

Hope you having a great day!

I just wanted to be aware if you would be interested in acquiring Dell Users 
Contact List for marketing your product or service.

Some of your target interest: Dell Boomi, Dell Clerity, Dell Cloud, Dell 
Credant, Dell EqualLogic, Dell OptiPlex, Dell Wyse, Dell SecureWorks, Dell 
PowerVault and many more...
These are the fields that we provide for each contacts: Names, Title, Email, 
Contact Number, Company Name, Company URL, and Company physical location, SIC 
Code, Industry and Company Size (Revenue and Employee).

Kindly review and let me be aware of your interest so that I can get back to 
you with the exact counts and more info regarding the same.

Do let me be aware if you have any questions for me.

Regards,
Meghan Hudson
Database Executive
If you do not wish to receive these emails. Please respond Exit.
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

[ovs-dev] OpenvSwitch and VLAN trunk flapping

[Alvaro Jimenez Moreno]

Hi everyone,
Im trying to connect 2 hosts via OpenvSwitch and a Cisco Catalyst 2960
between the two hosts. I want to have 3 VLANs between this hosts. I've
first created the 3 VLAN interfaces via ip command (enp63s0.10,  enp63s0.11
and  enp63s0.12). Then I added these interfaces to de ovs bridge (on both
hosts). On the Cisco switch, i configured both host ports as trunk ports
and allowed vlans 10,11 and 12, getting a MAC flapping error between both
Cisco switch ports. I'm a newbie at networking and i dont really know how
to solve this.

Thanks in advance.
Alvaro
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] [PATCH] odp-util: Remove unnecessary TOS ECN bits rewrite for tunnels

[Simon Horman]

On 26 April 2018 at 14:50, Simon Horman  wrote:

> Thanks Jianbo,
>
> On 26 April 2018 at 07:54, Jianbo Liu  wrote:
>
>> For tunnels, TOS ECN bits are never wildcard for the reason that they
>> are always inherited. OVS will create a rewrite action if we add rule
>> to modify other IP headers. But it also adds an extra ECN rewrite for
>> the action because of this ECN un-wildcarding.
>>
>> It seems no error because the ECN bits to be changed are same in this
>> case. But as rule can't be offloaded to hardware, the unnecssary ECN
>> rewrite should be removed.
>>
>> Signed-off-by: Jianbo Liu 
>> Reviewed-by: Paul Blakey 
>> Reviewed-by: Roi Dayan 
>>
>
> I'd like to take a little time to test this one.
>

Hi Jinbao,

thanks again for your patch. We have tested this patch and from a
functional point of view it looks good to me.
Could you post a v2 which addresses the style concerns raised separately by
Ben?

Thanks!
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev