Re: [vpp-dev] getting a rid of vpe.api

[Edward Warnicke]

+1 :)

>From the 'consumer of api' side... the 'catch all' nature of vpe.api makes
VPP less usable.  Proper modularity would improve that, and be a benefit
beyond the ones Damjan already mentioned.

That said, ccing the some of the GoVPP folks, because there are some
(hopefully quite tractable) issues to consider in downstream generated APIs.

Ed

On Thu, Sep 9, 2021 at 11:18 AM Damjan Marion via lists.fd.io  wrote:

>
> Guys,
>
> Can we get a rid of vpp/api/vpe.api and vpp/api/vpe_types.api by moving
> content to more
> appropriate places. I.e. some basic types and control_ping may be good
> candidate for vlibapi/.
>
> It is quite weird that we have dozens of plugins depending on header files
> autogenerated from the main executable directory….
>
> If we gat a rid of hardcoded dependencies like we have with APIs today, we
> will be able to modularize build. I.e. Florin asking to way to just build
> VCL….
>
>
> Any volunteers?
>
> Thanks,
>
> —
> Damjan
>
>
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20111): https://lists.fd.io/g/vpp-dev/message/20111
Mute This Topic: https://lists.fd.io/mt/85488417/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Adding new route via ipv6 link-local

[Edward Warnicke]

Neale,

Could this be hitting the same /32 issue I'm in the process of fixing with
https://gerrit.fd.io/r/c/vpp/+/33495 ?  If the interface has an IPv6 /32
assigned... it would be IPv6 enabled, but fib_sas would fail to get its
source address, ND would fail, and we'd hit the SEGV we are seeing on
copy... is that possibly the root cause?

Ed

On Fri, Aug 20, 2021 at 10:05 AM Ed Warnicke  wrote:

> Got it.  That makes sense :)
>
> Ed
>
> On Fri, Aug 20, 2021 at 9:58 AM Neale Ranns  wrote:
>
>> Hi Ed,
>>
>>
>>
>> When creating an adjacency for the first time we send out a probe packet
>> (ARP/ND) to see if the peer will resolve it.
>>
>>
>>
>> /neale
>>
>>
>>
>> *From: *Ed Warnicke 
>> *Date: *Friday, 20 August 2021 at 16:54
>> *To: *Neale Ranns 
>> *Cc: *zsta...@gmail.com , Artem Glazychev <
>> artem.glazyc...@xored.com>, vpp-dev 
>> *Subject: *Re: [vpp-dev] Adding new route via ipv6 link-local
>>
>> Neale,
>>
>>
>>
>> Question... looking at the trace it looks like we are having an issue
>> with fib_sas6_get ... could you help me understand why we are calling
>> fib_sas6_get in this situation?
>>
>>
>>
>> Ed
>>
>>
>>
>> On Fri, Aug 20, 2021 at 9:49 AM Neale Ranns  wrote:
>>
>>
>>
>> Hi Ed,
>>
>>
>>
>> It does. But in this case the command is adding a route through an
>> interface, which is not the same as configuring a prefix on an interface
>> (nor ip6 enabling it).
>>
>>
>>
>> /neale
>>
>>
>>
>> *From: *Ed Warnicke 
>> *Date: *Friday, 20 August 2021 at 16:40
>> *To: *Neale Ranns 
>> *Cc: *zsta...@gmail.com , Artem Glazychev <
>> artem.glazyc...@xored.com>, vpp-dev 
>> *Subject: *Re: [vpp-dev] Adding new route via ipv6 link-local
>>
>> Neale,
>>
>>
>>
>> I'm a bit confused... I had previously thought that *adding* an IPv6
>> address to a link *did* IPv6 enable it...
>>
>>
>>
>> Ed
>>
>>
>>
>> On Fri, Aug 20, 2021 at 9:20 AM Neale Ranns  wrote:
>>
>> Hi Artem, Stanislav,
>>
>>
>>
>> I agree graceful handling is needed, return false if there is no link
>> local.
>>
>>
>>
>> If you enabled ip6 on the link first, this wouldn’t be a problem. The
>> link will need to be ip6 enabled if you want something to reply.
>>
>>
>>
>> /neale
>>
>>
>>
>>
>>
>> *From: *vpp-dev@lists.fd.io  on behalf of Stanislav
>> Zaikin via lists.fd.io 
>> *Date: *Friday, 20 August 2021 at 16:10
>> *To: *Artem Glazychev 
>> *Cc: *vpp-dev 
>> *Subject: *Re: [vpp-dev] Adding new route via ipv6 link-local
>>
>> Hello Artem,
>>
>>
>>
>> Looks like we need (at least) to add a check for nullptr.
>>
>>
>>
>> DBGvpp# create tap
>> tap0
>> DBGvpp# set interface state tap0 up
>> DBGvpp# ip route add fa::1/120 via fe80::1 tap0
>>
>> Thread 1 "vpp_main" received signal SIGSEGV, Segmentation fault.
>> 0x7774ba90 in ip6_address_copy (dst=0x7fffaf487aa0, src=0x0) at
>> /home/zstas/vpp/src/vnet/ip/ip6_packet.h:129
>> 129  dst->as_u64[0] = src->as_u64[0];
>> (gdb) bt
>> #0  0x7774ba90 in ip6_address_copy (dst=0x7fffaf487aa0, src=0x0)
>> at /home/zstas/vpp/src/vnet/ip/ip6_packet.h:129
>> #1  0x7774b892 in fib_sas6_get (sw_if_index=1,
>> dst=0x7fffb91b4e50, src=0x7fffaf487aa0) at
>> /home/zstas/vpp/src/vnet/fib/fib_sas.c:105
>>
>>
>>
>> On Fri, 20 Aug 2021 at 15:20, Artem Glazychev 
>> wrote:
>>
>> Hello,
>>
>> Found a crash: if we add the route via fe80:: * after* the interface
>> upping - vpp crashes.
>>
>> For example:
>>
>> DBGvpp# create tap
>>
>> tap0
>>
>> DBGvpp# set int state tap0 up
>>
>> DBGvpp# ip route add fa::1/120 via fe80::1 tap0
>>
>> make: *** [Makefile:537: run] Aborted
>>
>>
>>
>> If we swap *set ... up* and *ip route ...* - no crashes.
>>
>> Could you please explain me if such a situation is possible at all?
>> In any case, I believe that vpp should not crash.
>>
>> Thanks.
>>
>>
>>
>>
>>
>> --
>>
>> Best regards
>> Stanislav Zaikin
>>
>>
>> 
>>
>>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20005): https://lists.fd.io/g/vpp-dev/message/20005
Mute This Topic: https://lists.fd.io/mt/85020362/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Adding new route via ipv6 link-local

[Edward Warnicke]

Got it.  That makes sense :)

Ed

On Fri, Aug 20, 2021 at 9:58 AM Neale Ranns  wrote:

> Hi Ed,
>
>
>
> When creating an adjacency for the first time we send out a probe packet
> (ARP/ND) to see if the peer will resolve it.
>
>
>
> /neale
>
>
>
> *From: *Ed Warnicke 
> *Date: *Friday, 20 August 2021 at 16:54
> *To: *Neale Ranns 
> *Cc: *zsta...@gmail.com , Artem Glazychev <
> artem.glazyc...@xored.com>, vpp-dev 
> *Subject: *Re: [vpp-dev] Adding new route via ipv6 link-local
>
> Neale,
>
>
>
> Question... looking at the trace it looks like we are having an issue with
> fib_sas6_get ... could you help me understand why we are calling
> fib_sas6_get in this situation?
>
>
>
> Ed
>
>
>
> On Fri, Aug 20, 2021 at 9:49 AM Neale Ranns  wrote:
>
>
>
> Hi Ed,
>
>
>
> It does. But in this case the command is adding a route through an
> interface, which is not the same as configuring a prefix on an interface
> (nor ip6 enabling it).
>
>
>
> /neale
>
>
>
> *From: *Ed Warnicke 
> *Date: *Friday, 20 August 2021 at 16:40
> *To: *Neale Ranns 
> *Cc: *zsta...@gmail.com , Artem Glazychev <
> artem.glazyc...@xored.com>, vpp-dev 
> *Subject: *Re: [vpp-dev] Adding new route via ipv6 link-local
>
> Neale,
>
>
>
> I'm a bit confused... I had previously thought that *adding* an IPv6
> address to a link *did* IPv6 enable it...
>
>
>
> Ed
>
>
>
> On Fri, Aug 20, 2021 at 9:20 AM Neale Ranns  wrote:
>
> Hi Artem, Stanislav,
>
>
>
> I agree graceful handling is needed, return false if there is no link
> local.
>
>
>
> If you enabled ip6 on the link first, this wouldn’t be a problem. The link
> will need to be ip6 enabled if you want something to reply.
>
>
>
> /neale
>
>
>
>
>
> *From: *vpp-dev@lists.fd.io  on behalf of Stanislav
> Zaikin via lists.fd.io 
> *Date: *Friday, 20 August 2021 at 16:10
> *To: *Artem Glazychev 
> *Cc: *vpp-dev 
> *Subject: *Re: [vpp-dev] Adding new route via ipv6 link-local
>
> Hello Artem,
>
>
>
> Looks like we need (at least) to add a check for nullptr.
>
>
>
> DBGvpp# create tap
> tap0
> DBGvpp# set interface state tap0 up
> DBGvpp# ip route add fa::1/120 via fe80::1 tap0
>
> Thread 1 "vpp_main" received signal SIGSEGV, Segmentation fault.
> 0x7774ba90 in ip6_address_copy (dst=0x7fffaf487aa0, src=0x0) at
> /home/zstas/vpp/src/vnet/ip/ip6_packet.h:129
> 129  dst->as_u64[0] = src->as_u64[0];
> (gdb) bt
> #0  0x7774ba90 in ip6_address_copy (dst=0x7fffaf487aa0, src=0x0)
> at /home/zstas/vpp/src/vnet/ip/ip6_packet.h:129
> #1  0x7774b892 in fib_sas6_get (sw_if_index=1, dst=0x7fffb91b4e50,
> src=0x7fffaf487aa0) at /home/zstas/vpp/src/vnet/fib/fib_sas.c:105
>
>
>
> On Fri, 20 Aug 2021 at 15:20, Artem Glazychev 
> wrote:
>
> Hello,
>
> Found a crash: if we add the route via fe80:: * after* the interface
> upping - vpp crashes.
>
> For example:
>
> DBGvpp# create tap
>
> tap0
>
> DBGvpp# set int state tap0 up
>
> DBGvpp# ip route add fa::1/120 via fe80::1 tap0
>
> make: *** [Makefile:537: run] Aborted
>
>
>
> If we swap *set ... up* and *ip route ...* - no crashes.
>
> Could you please explain me if such a situation is possible at all?
> In any case, I believe that vpp should not crash.
>
> Thanks.
>
>
>
>
>
> --
>
> Best regards
> Stanislav Zaikin
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20003): https://lists.fd.io/g/vpp-dev/message/20003
Mute This Topic: https://lists.fd.io/mt/85020362/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Adding new route via ipv6 link-local

[Edward Warnicke]

Neale,

Question... looking at the trace it looks like we are having an issue with
fib_sas6_get ... could you help me understand why we are calling
fib_sas6_get in this situation?

Ed

On Fri, Aug 20, 2021 at 9:49 AM Neale Ranns  wrote:

>
>
> Hi Ed,
>
>
>
> It does. But in this case the command is adding a route through an
> interface, which is not the same as configuring a prefix on an interface
> (nor ip6 enabling it).
>
>
>
> /neale
>
>
>
> *From: *Ed Warnicke 
> *Date: *Friday, 20 August 2021 at 16:40
> *To: *Neale Ranns 
> *Cc: *zsta...@gmail.com , Artem Glazychev <
> artem.glazyc...@xored.com>, vpp-dev 
> *Subject: *Re: [vpp-dev] Adding new route via ipv6 link-local
>
> Neale,
>
>
>
> I'm a bit confused... I had previously thought that *adding* an IPv6
> address to a link *did* IPv6 enable it...
>
>
>
> Ed
>
>
>
> On Fri, Aug 20, 2021 at 9:20 AM Neale Ranns  wrote:
>
> Hi Artem, Stanislav,
>
>
>
> I agree graceful handling is needed, return false if there is no link
> local.
>
>
>
> If you enabled ip6 on the link first, this wouldn’t be a problem. The link
> will need to be ip6 enabled if you want something to reply.
>
>
>
> /neale
>
>
>
>
>
> *From: *vpp-dev@lists.fd.io  on behalf of Stanislav
> Zaikin via lists.fd.io 
> *Date: *Friday, 20 August 2021 at 16:10
> *To: *Artem Glazychev 
> *Cc: *vpp-dev 
> *Subject: *Re: [vpp-dev] Adding new route via ipv6 link-local
>
> Hello Artem,
>
>
>
> Looks like we need (at least) to add a check for nullptr.
>
>
>
> DBGvpp# create tap
> tap0
> DBGvpp# set interface state tap0 up
> DBGvpp# ip route add fa::1/120 via fe80::1 tap0
>
> Thread 1 "vpp_main" received signal SIGSEGV, Segmentation fault.
> 0x7774ba90 in ip6_address_copy (dst=0x7fffaf487aa0, src=0x0) at
> /home/zstas/vpp/src/vnet/ip/ip6_packet.h:129
> 129  dst->as_u64[0] = src->as_u64[0];
> (gdb) bt
> #0  0x7774ba90 in ip6_address_copy (dst=0x7fffaf487aa0, src=0x0)
> at /home/zstas/vpp/src/vnet/ip/ip6_packet.h:129
> #1  0x7774b892 in fib_sas6_get (sw_if_index=1, dst=0x7fffb91b4e50,
> src=0x7fffaf487aa0) at /home/zstas/vpp/src/vnet/fib/fib_sas.c:105
>
>
>
> On Fri, 20 Aug 2021 at 15:20, Artem Glazychev 
> wrote:
>
> Hello,
>
> Found a crash: if we add the route via fe80:: *after* the interface
> upping - vpp crashes.
>
> For example:
>
> DBGvpp# create tap
>
> tap0
>
> DBGvpp# set int state tap0 up
>
> DBGvpp# ip route add fa::1/120 via fe80::1 tap0
>
> make: *** [Makefile:537: run] Aborted
>
>
>
> If we swap *set ... up* and *ip route ...* - no crashes.
>
> Could you please explain me if such a situation is possible at all?
> In any case, I believe that vpp should not crash.
>
> Thanks.
>
>
>
>
>
> --
>
> Best regards
> Stanislav Zaikin
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20001): https://lists.fd.io/g/vpp-dev/message/20001
Mute This Topic: https://lists.fd.io/mt/85020362/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Adding new route via ipv6 link-local

[Edward Warnicke]

Neale,

I'm a bit confused... I had previously thought that *adding* an IPv6
address to a link *did* IPv6 enable it...

Ed

On Fri, Aug 20, 2021 at 9:20 AM Neale Ranns  wrote:

> Hi Artem, Stanislav,
>
>
>
> I agree graceful handling is needed, return false if there is no link
> local.
>
>
>
> If you enabled ip6 on the link first, this wouldn’t be a problem. The link
> will need to be ip6 enabled if you want something to reply.
>
>
>
> /neale
>
>
>
>
>
> *From: *vpp-dev@lists.fd.io  on behalf of Stanislav
> Zaikin via lists.fd.io 
> *Date: *Friday, 20 August 2021 at 16:10
> *To: *Artem Glazychev 
> *Cc: *vpp-dev 
> *Subject: *Re: [vpp-dev] Adding new route via ipv6 link-local
>
> Hello Artem,
>
>
>
> Looks like we need (at least) to add a check for nullptr.
>
>
>
> DBGvpp# create tap
> tap0
> DBGvpp# set interface state tap0 up
> DBGvpp# ip route add fa::1/120 via fe80::1 tap0
>
> Thread 1 "vpp_main" received signal SIGSEGV, Segmentation fault.
> 0x7774ba90 in ip6_address_copy (dst=0x7fffaf487aa0, src=0x0) at
> /home/zstas/vpp/src/vnet/ip/ip6_packet.h:129
> 129  dst->as_u64[0] = src->as_u64[0];
> (gdb) bt
> #0  0x7774ba90 in ip6_address_copy (dst=0x7fffaf487aa0, src=0x0)
> at /home/zstas/vpp/src/vnet/ip/ip6_packet.h:129
> #1  0x7774b892 in fib_sas6_get (sw_if_index=1, dst=0x7fffb91b4e50,
> src=0x7fffaf487aa0) at /home/zstas/vpp/src/vnet/fib/fib_sas.c:105
>
>
>
> On Fri, 20 Aug 2021 at 15:20, Artem Glazychev 
> wrote:
>
> Hello,
>
> Found a crash: if we add the route via fe80:: *after* the interface
> upping - vpp crashes.
>
> For example:
>
> DBGvpp# create tap
>
> tap0
>
> DBGvpp# set int state tap0 up
>
> DBGvpp# ip route add fa::1/120 via fe80::1 tap0
>
> make: *** [Makefile:537: run] Aborted
>
>
>
> If we swap *set ... up* and *ip route ...* - no crashes.
>
> Could you please explain me if such a situation is possible at all?
> In any case, I believe that vpp should not crash.
>
> Thanks.
>
>
>
>
>
> --
>
> Best regards
> Stanislav Zaikin
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#1): https://lists.fd.io/g/vpp-dev/message/1
Mute This Topic: https://lists.fd.io/mt/85020362/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] memif: failed: no source address for egress interface

[Edward Warnicke]

On Tue, Aug 10, 2021 at 2:39 AM Neale Ranns  wrote

>
>
> Again: GCP does this.  Calico for K8s (the most used K8s CNI plugin) does
> this.  Its  basically the direction Cloud is going in the generic.
>
>
>
> Ah well, that’s different, if all the cool kids are doing it, then it must
> be the right way 
>
> But as I said before, this IP-host-interworking, or L2/3, or [insert
> catchy phrase here], wasn’t a use case for VPP’s original IP functionality,
> so you may have more surprises down the track.
>

Yeah... we'd already sorted all of those in previous versions of VPP ...
these are all new issues that *seem* to have been introduced by the SAS
rework.  On net, I think that SAS is a good idea,
so see this as part of the normal 'shake down' process of such a big shift,
but I see it less as rooted in VPP's original functionality and more as
rooted in the SAS rework.

Ed

>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19956): https://lists.fd.io/g/vpp-dev/message/19956
Mute This Topic: https://lists.fd.io/mt/84656776/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] memif: failed: no source address for egress interface

[Edward Warnicke]

On Mon, Aug 9, 2021 at 7:40 AM Neale Ranns  wrote:

>
>
> i would argue the contrary, not subnetting (i.e. using /32) is not a valid
> approach to subnetting.
>

Again: GCP does this.  Calico for K8s (the most used K8s CNI plugin) does
this.  Its  basically the direction Cloud is going in the generic.


>
>
> The BSD approach where you have to independent /32s on each side and a
> routing entry for the other side. Or a connected route /31 or larger. The
> act of configuring an address with a prefix is really a shortcut for
> configuring the address _and_ the connected prefix of course.
>
>
>
> And it’s an expression that there are other hosts attached to this link so
> you don’t need to add /32 routes for any such hosts. IOW it’s a way of say
> stating that there is a sub-network of hosts attached to this router. And
> my routing protocol can advertise this.
>
> If you add only a /32 you make none of those statements, and any routing
> protocol, if it still works over links without a subnet, does not include
> (without rediest static) reachability to those attached hosts. IOW it’s
> broken , or at a minimum not standard IP networking.
>
> Of course I may be wrong, I often am, but this was my position when
> writing IP functionality for VPP, so there may be other surprises …
>
>
>
> Sounds to me like the SAS algorithm needs a bit of work.
>
>
>
> Now on that topic I heartily agree  my SAS implementation is flawed in
> that it uses the glean adjacency to store the link’s receive address. P2p
> links don’t have a glean adj, hence SAS is broken on p2p links. It was an
> oversight on my part, I know I need to fix it.
>
> My goal with the SAS implementation done that way was to be able to do
> basic SAS without needing the interface addresses programmed via ‘set int
> ip adrr …’, but rather completely through the RIB (i.e. ip route add …).
> This is more like what one might expect at the bottom of a router stack. To
> say that goal is imcomplete, is an understatement :(
>




> The p2p fix, using the directly added IP link addresses is easy, it’s here:
>
>   https://gerrit.fd.io/r/c/vpp/+/32801
>
>
>
> (I'd like to use it for ICMP error sending too, where it also should
> handle the case of picking a source address from another interface than the
> outgoing interface).
>

And NBMA interfaces?

Ed


>
>
> SAS++ 
>
>
>
> /neale
>
>
>
> Cheers,
>
> Ole
>
>
>
> > From: vpp-dev@lists.fd.io  on behalf of Artem
> Glazychev via lists.fd.io 
>
> > Date: Wednesday, 4 August 2021 at 08:37
>
> > To: vpp-dev@lists.fd.io 
>
> > Subject: [vpp-dev] memif: failed: no source address for egress interface
>
> >
>
> > Hello,
>
> > Found a problem with some types of interfaces.
>
> >
>
> > For example, memif. When I'm creating memif interfaces and run ping I
> see:
>
> >
>
> > DBGvpp# ping 10.10.2.1
>
> > Failed: no source address for egress interface
>
> > ...
>
> >
>
> > But it is worth mentioning that I am setting /32 mask for IP address
>
> >
>
> > Managed to fix IP mode with these patches:
> https://gerrit.fd.io/r/c/vpp/+/32801, https://gerrit.fd.io/r/c/vpp/+/33303
>
> >
>
> > But Ethernet mode still doesn't work.
>
> >
>
> > ==
>
> >
>
> > There was already a similar topic:
> https://lists.fd.io/g/vpp-dev/topic/84038840
>
> >
>
> > Created a jira issue with details: https://jira.fd.io/browse/VPP-1992
>
> >
>
> > Does anyone have any thoughts on this? Thank you.
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
>
>
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19933): https://lists.fd.io/g/vpp-dev/message/19933
Mute This Topic: https://lists.fd.io/mt/84656776/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] memif: failed: no source address for egress interface

[Edward Warnicke]

Neale,

/32s on interfaces that talk to other things are actually getting to be the
standard in Cloud.  GCP uses /32s in their VMs exclusively.  Calico uses
/32s on on Pod interfaces.  Its a common use case.

Ed

On Mon, Aug 9, 2021 at 3:03 AM Neale Ranns  wrote:

>
>
> Hi Artem,
>
>
>
> I think that is telling you not to use /32 address on interface for which
> you expect there to be connected peers.
>
> From an IP networking perspective, if you want two peers to be connected
> on an interface, they need to be within the same subnet, so use a /31.
>
>
>
> /neale
>
>
>
>
>
> *From: *vpp-dev@lists.fd.io  on behalf of Artem
> Glazychev via lists.fd.io 
> *Date: *Wednesday, 4 August 2021 at 08:37
> *To: *vpp-dev@lists.fd.io 
> *Subject: *[vpp-dev] memif: failed: no source address for egress interface
>
> Hello,
> Found a problem with some types of interfaces.
>
> For example, memif. When I'm creating memif interfaces and run ping I see:
>
> DBGvpp# ping 10.10.2.1
> Failed: no source address for egress interface
> ...
>
> But it is worth mentioning that I am setting /32 mask for IP address
>
> Managed to fix IP mode with these patches:
> https://gerrit.fd.io/r/c/vpp/+/32801, https://gerrit.fd.io/r/c/vpp/+/33303
>
> But Ethernet mode still doesn't work.
>
> ==
>
> There was already a similar topic:
> https://lists.fd.io/g/vpp-dev/topic/84038840
>
> Created a jira issue with details: https://jira.fd.io/browse/VPP-1992
>
> Does anyone have any thoughts on this? Thank you.
>
>
>
>
>
>
>
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19932): https://lists.fd.io/g/vpp-dev/message/19932
Mute This Topic: https://lists.fd.io/mt/84656776/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Draft revision of FD.io Community Doc (Governance)

[Edward Warnicke]

As part of the ongoing discussion around evolving the TSC, and in keeping
with the previously socialized slide deck
.
Please provide feedback on this PR 
to update the FD.io Community Doc (our governance doc for how we do things
like Elect TSC members).

Ed

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19420): https://lists.fd.io/g/vpp-dev/message/19420
Mute This Topic: https://lists.fd.io/mt/82968758/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] New Committer Proposal

[Edward Warnicke]

+1

On Wed, Mar 31, 2021 at 1:50 PM Florin Coras  wrote:

> +1
>
> Florin
>
> > On Mar 31, 2021, at 10:58 AM, Damjan Marion via lists.fd.io  me@lists.fd.io> wrote:
> >
> >
> > Dear VPP Committers,
> >
> > I would like to propose Roy Fan Zhang from Intel as a new VPP committer.
> > Fan made significant contributions to the VPP including the async crypto
> > infrastructure and crypto scheduler.
> > Beside that I found that Fan is active in the community, and willing to
> help.
> >
> > Please let me know if you agree/neutral/disagree with +1/0/-1
> (committers only please).
> >
> > My +1 is here.
> >
> > Thanks,
> >
> > Damjan
> >
> >
> >
> >
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#19073): https://lists.fd.io/g/vpp-dev/message/19073
Mute This Topic: https://lists.fd.io/mt/81756505/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] vpp musl integration and CI

[Edward Warnicke]

Dave,

Any chance we could get vpp down to a single statically linked binary?
That's roughly the way things are trending with Go... and it has a lot of
very very nice advantages in a containerized Cloud Native world.

Ed

On Thu, Jan 21, 2021 at 2:11 PM Dave Barach  wrote:

> I've been down this path before.
>
> s/glibc/musl/ fixes one set of issues, and a small set at that. [Back in
> the
> good old days, vpp wasn't even linked against glibc.]
>
> Here's a quick library summary:
>
> $ ldd /usr/bin/vpp
> linux-vdso.so.1 (0x7ffef81f2000)
> libvlibmemory.so.21.06 =>
> /lib/x86_64-linux-gnu/libvlibmemory.so.21.06 (0x7fc41d8c4000)
> libvnet.so.21.06 => /lib/x86_64-linux-gnu/libvnet.so.21.06
> (0x7fc41bedd000)
> libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fc41bed7000)
> libvlib.so.21.06 => /lib/x86_64-linux-gnu/libvlib.so.21.06
> (0x7fc41bd4c000)
> libsvm.so.21.06 => /lib/x86_64-linux-gnu/libsvm.so.21.06
> (0x7fc41bd2e000)
> librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fc41bd23000)
> libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> (0x7fc41bcfe000)
> libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1
> (0x7fc41bcf5000)
> libvppinfra.so.21.06 => /lib/x86_64-linux-gnu/libvppinfra.so.21.06
> (0x7fc41bc81000)
> libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fc41bb32000)
> libssl.so.1.1 => /lib/x86_64-linux-gnu/libssl.so.1.1
> (0x7fc41ba9f000)
> libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1
> (0x7fc41b7c9000)
> libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fc41b5d5000)
> /lib64/ld-linux-x86-64.so.2 (0x7fc41d9ba000)
>
> By the time all is said and done, there's little chance that a vpp alpine
> image would be less than O(10mb).
>
> I'd suggest that folks investigate single-image, one-size-fits-all
> packaging
> technology: snap, flatpak, or appimage.
>
> FWIW... Dave
>
> -Original Message-
> From: vpp-dev@lists.fd.io  On Behalf Of Benoit Ganne
> (bganne) via lists.fd.io
> Sent: Thursday, January 21, 2021 2:08 PM
> To: vpp-dev@lists.fd.io
> Cc: Nathan Moos (nmoos) 
> Subject: [vpp-dev] vpp musl integration and CI
>
> Hi everyone,
>
> There is some on-going work to make VPP works with musl libc instead of
> glibc:
>
> https://gerrit.fd.io/r/q/topic:%22musl%22+(status:open%20OR%20status:merged)
> The goal is to be able to run VPP on embedded platforms relying on musl.
> The modifications are overall pretty small, but we'd like to add an
> integration job using Alpine Linux which does use musl to make sure it will
> not break in the future.
> What do you think? Is it something that would be possible in the LF infra?
>
> Best
> ben
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18577): https://lists.fd.io/g/vpp-dev/message/18577
Mute This Topic: https://lists.fd.io/mt/80012247/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-committers] [vpp-dev] VPP committers: VPP PTL vote

[Edward Warnicke]

+1

On Fri, Sep 25, 2020 at 2:44 PM Dave Wallace  wrote:

> +1
>
> On 9/25/20 3:13 PM, Dave Barach via lists.fd.io wrote:
>
> Folks,
>
>
>
> The self-nomination period closed yesterday. We had one self-nomination,
> from Damjan Marion. At this point, we can proceed with a vote.
>
>
>
> I’m sure that Damjan will do a great job, so let me start:
>
>
>
> Damjan Marion as VPP PTL: +1
>
>
>
> Please vote +1, 0, -1. For once, the “reply-all” button is everyone’s
> friend.
>
>
>
> Thanks... Dave
>
>
>
> -Original Message-
> From: d...@barachs.net  
> Sent: Thursday, September 17, 2020 10:32 AM
> To: 'vpp-dev@lists.fd.io'  ; '
> t...@lists.fd.io'  
> Subject: Happy Trails to Me...
>
>
>
> Folks,
>
>
>
> I’m departing the employment rolls towards the end of next month. Although
> I intend to remain active in the fd.io vpp community as a coder,
> committer, and resident greybeard, it’s time for the community to pick a
> new PTL.
>
>
>
> According to the project governance document,
> https://fd.io/docs/tsc/FD.IO-Technical-Community-Document-12-12-2017.pdf:
>
>
>
>
> 3.2.3.1 Project Technical Leader Candidates Candidates for the project’s
> PTL will be derived from the Committers of the Project. Candidates must
> self-nominate.
>
>
>
> I'd like to invite any interested vpp project committer to self-nominate
> for the PTL role. Please email vpp-dev@lists.fd.io.
>
>
>
> Let's close the self-nomination period in one week: more specifically, by
> 5pm EDT on Thursday, September 24, 2020; committer vote to follow
> thereafter.
>
>
>
> I'll be glad to answer unicast questions about the PTL role from eligible
> committers.
>
>
>
> Thanks... Dave
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17529): https://lists.fd.io/g/vpp-dev/message/17529
Mute This Topic: https://lists.fd.io/mt/77124156/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [tsc] [vpp-dev] Replacing master/slave nomenclature

[Edward Warnicke]

In today's TSC meeting we had a discussion of what, if any, role the TSC
should play in the renaming process around nomenclatures like master/slave
whitelist/blacklist etc.

It's important to understand that the TSC in FD.io, quite intentionally,
does not and cannot tell the projects what to do.  Given that, and the fact
that there are technical details involved in making the proper renaming
decisions, we determined that there are two potentially helpful things we
can and do:

1)  Attempt to assemble helpful guidance to projects in making their
decisions.  This would include pointing out resources for alternate name
ideas, considerations like coordination with neighboring communities and
standards bodies that may also be renaming to attempt to achieve
consistency etc.

2)  Provide a publicly facing visible reporting of what various FD.io
projects are doing around renaming.  Some renaming is going to involve API
changes that take time to responsibly implement.  Some renaming will
involve consensus seeking with other communities and standards bodies.  We
want to make clear that we are taking this seriously, taking action, and
provide public visibility into the process.  As with most things in Open
Source, visibility and openness are the best medicine.

The TSC is also quite interested in input from the broader community about
what we could productively do, suggestions or comments around the current
thoughts, and participation from those who wish to be more involved in
solving these problems.

Ed



On Tue, Jul 14, 2020 at 1:15 PM Ed Warnicke  wrote:

> I tend to prefer permitlist/denylist personally... but I may have
> configured one too many ACLs in my life...
>
> Ed
>
> On Tue, Jul 14, 2020 at 12:49 PM Christian Hopps 
> wrote:
>
>>
>>
>> > On Jul 14, 2020, at 1:20 PM, St Leger, Jim 
>> wrote:
>> >
>> > I believe the DPDK community converged on:
>> > master/slave lcore -> initial/worker lcore
>>
>> VPP is ok here I think with "main" and "worker".
>>
>> > blacklist/whitelist -> blocklist/allowlist
>>
>> That one feels a bit clunky to me. I wonder why they didn't go for
>> something more natural like
>>
>>   nouns: blocked/allowed
>>   verbs: block/allow
>>
>> The terms blacklist/whitelist can be a nouns or verbs, and I suspect they
>> are often not implemented as an actual list data structure, so trying to
>> keep the "list" suffix seems an unnecessary carryover (and sounds clunky
>> IMHO). :)
>>
>> Thanks,
>> Chris.
>>
>> >
>> > Full community discussion:
>> https://mails.dpdk.org/archives/dev/2020-June/thread.html#169337
>> >
>> > Jim
>> >
>> > -Original Message-
>> > From: vpp-dev@lists.fd.io  On Behalf Of Jerome
>> Tollet via lists.fd.io
>> > Sent: Tuesday, July 14, 2020 10:10 AM
>> > To: Chris Luke ; Steven Luong (sluong) <
>> slu...@cisco.com>; Dave Barach (dbarach) ; Kinsella,
>> Ray ; Stephen Hemminger ;
>> vpp-dev@lists.fd.io; t...@lists.fd.io; Ed Warnicke (eaw) 
>> > Subject: Re: [tsc] [vpp-dev] Replacing master/slave nomenclature
>> >
>> > Hi Chris,
>> > I suspect it would be good to align on the new bond nomenclature coming
>> from other projects. DPDK and Linux are probably starting points we should
>> consider IMO.
>> > Jerome
>> >
>> > Le 14/07/2020 18:45, « t...@lists.fd.io au nom de Chris Luke » <
>> t...@lists.fd.io au nom de chris_l...@comcast.com> a écrit :
>> >
>> >It is subjective and contextualized. But in this case, if making the
>> effort to correct a wrong, why stop half way?
>> >
>> >Chris.
>> >
>> >-Original Message-
>> >From: vpp-dev@lists.fd.io  On Behalf Of Jerome
>> Tollet via lists.fd.io
>> >Sent: Tuesday, July 14, 2020 12:37
>> >To: Steven Luong (sluong) ; Dave Barach (dbarach)
>> ; Kinsella, Ray ; Stephen Hemminger <
>> step...@networkplumber.org>; vpp-dev@lists.fd.io; t...@lists.fd.io; Ed
>> Warnicke (eaw) 
>> >Subject: [EXTERNAL] Re: [vpp-dev] Replacing master/slave nomenclature
>> >
>> >Hi Steven,
>> >Please note that per this proposition,
>> https://urldefense.com/v3/__https://lkml.org/lkml/2020/7/4/229__;!!CQl3mcHX2A!QdLdxm4rtZW-mFe5jt_qzEpx-_X2KWnqvjyEl-7Py41jsEV7FrnEw0lTNcF8LdfUzQ$
>> , slave must be avoided but master can be kept.
>> >Maybe master/member or master/secondary could be options too.
>> >Jerome
>> >
>> >Le 14/07/2020 18:32, « vpp-dev@lists.fd.io au nom de steven luong
>> via lists.fd.io » > cisco@lists.fd.io> a écrit :
>> >
>> >I am in the process of pushing a patch to replace master/slave
>> with aggregator/member for the bonding.
>> >
>> >Steven
>> >
>> >On 7/13/20, 4:44 AM, "vpp-dev@lists.fd.io on behalf of Dave
>> Barach via lists.fd.io" > cisco@lists.fd.io> wrote:
>> >
>> >+1, especially since our next release will be supported for
>> a year, and API name changes are involved...
>> >
>> >-Original Message-
>> >From: Kinsella, Ray 
>> >Sent: Monday, July 13, 2020 6:01 AM
>> >To: Dave 

Re: [tsc] [vpp-dev] Replacing master/slave nomenclature

[Edward Warnicke]

I tend to prefer permitlist/denylist personally... but I may have
configured one too many ACLs in my life...

Ed

On Tue, Jul 14, 2020 at 12:49 PM Christian Hopps  wrote:

>
>
> > On Jul 14, 2020, at 1:20 PM, St Leger, Jim 
> wrote:
> >
> > I believe the DPDK community converged on:
> > master/slave lcore -> initial/worker lcore
>
> VPP is ok here I think with "main" and "worker".
>
> > blacklist/whitelist -> blocklist/allowlist
>
> That one feels a bit clunky to me. I wonder why they didn't go for
> something more natural like
>
>   nouns: blocked/allowed
>   verbs: block/allow
>
> The terms blacklist/whitelist can be a nouns or verbs, and I suspect they
> are often not implemented as an actual list data structure, so trying to
> keep the "list" suffix seems an unnecessary carryover (and sounds clunky
> IMHO). :)
>
> Thanks,
> Chris.
>
> >
> > Full community discussion:
> https://mails.dpdk.org/archives/dev/2020-June/thread.html#169337
> >
> > Jim
> >
> > -Original Message-
> > From: vpp-dev@lists.fd.io  On Behalf Of Jerome
> Tollet via lists.fd.io
> > Sent: Tuesday, July 14, 2020 10:10 AM
> > To: Chris Luke ; Steven Luong (sluong) <
> slu...@cisco.com>; Dave Barach (dbarach) ; Kinsella,
> Ray ; Stephen Hemminger ;
> vpp-dev@lists.fd.io; t...@lists.fd.io; Ed Warnicke (eaw) 
> > Subject: Re: [tsc] [vpp-dev] Replacing master/slave nomenclature
> >
> > Hi Chris,
> > I suspect it would be good to align on the new bond nomenclature coming
> from other projects. DPDK and Linux are probably starting points we should
> consider IMO.
> > Jerome
> >
> > Le 14/07/2020 18:45, « t...@lists.fd.io au nom de Chris Luke » <
> t...@lists.fd.io au nom de chris_l...@comcast.com> a écrit :
> >
> >It is subjective and contextualized. But in this case, if making the
> effort to correct a wrong, why stop half way?
> >
> >Chris.
> >
> >-Original Message-
> >From: vpp-dev@lists.fd.io  On Behalf Of Jerome
> Tollet via lists.fd.io
> >Sent: Tuesday, July 14, 2020 12:37
> >To: Steven Luong (sluong) ; Dave Barach (dbarach) <
> dbar...@cisco.com>; Kinsella, Ray ; Stephen Hemminger <
> step...@networkplumber.org>; vpp-dev@lists.fd.io; t...@lists.fd.io; Ed
> Warnicke (eaw) 
> >Subject: [EXTERNAL] Re: [vpp-dev] Replacing master/slave nomenclature
> >
> >Hi Steven,
> >Please note that per this proposition,
> https://urldefense.com/v3/__https://lkml.org/lkml/2020/7/4/229__;!!CQl3mcHX2A!QdLdxm4rtZW-mFe5jt_qzEpx-_X2KWnqvjyEl-7Py41jsEV7FrnEw0lTNcF8LdfUzQ$
> , slave must be avoided but master can be kept.
> >Maybe master/member or master/secondary could be options too.
> >Jerome
> >
> >Le 14/07/2020 18:32, « vpp-dev@lists.fd.io au nom de steven luong
> via lists.fd.io »  cisco@lists.fd.io> a écrit :
> >
> >I am in the process of pushing a patch to replace master/slave
> with aggregator/member for the bonding.
> >
> >Steven
> >
> >On 7/13/20, 4:44 AM, "vpp-dev@lists.fd.io on behalf of Dave
> Barach via lists.fd.io"  cisco@lists.fd.io> wrote:
> >
> >+1, especially since our next release will be supported for a
> year, and API name changes are involved...
> >
> >-Original Message-
> >From: Kinsella, Ray 
> >Sent: Monday, July 13, 2020 6:01 AM
> >To: Dave Barach (dbarach) ; Stephen
> Hemminger ; vpp-dev@lists.fd.io;
> t...@lists.fd.io; Ed Warnicke (eaw) 
> >Subject: Re: [vpp-dev] Replacing master/slave nomenclature
> >
> >Hi Stephen,
> >
> >I agree, I don't think we should ignore this.
> >Ed - I suggest we table a discussion at the next FD.io TSC?
> >
> >Ray K
> >
> >On 09/07/2020 17:05, Dave Barach via lists.fd.io wrote:
> >> Looping in the technical steering committee...
> >>
> >> -Original Message-
> >> From: vpp-dev@lists.fd.io  On Behalf Of Stephen
> Hemminger
> >> Sent: Thursday, July 2, 2020 7:02 PM
> >> To: vpp-dev@lists.fd.io
> >> Subject: [vpp-dev] Replacing master/slave nomenclature
> >>
> >> Is the VPP project addressing the use of master/slave nomenclature in
> the code base, documentation and CLI?  We are doing this for DPDK and it
> would be good if the replacement wording used in DPDK matched the wording
> used in FD.io projects.
> >>
> >> Particularly problematic is the use of master/slave in bonding.
> >> This seems to be a leftover from Linux, since none of the commercial
> products use that terminology and it is not present in 802.1AX standard.
> >>
> >> The IEEE and IETF are doing an across the board look at these terms in
> standards.
> >>
> >>
> >>
> >>
> >
> >
> >
> >
>
> 
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#16960): https://lists.fd.io/g/vpp-dev/message/16960
Mute This Topic: https://lists.fd.io/mt/75503531/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  

Re: [tsc] [vpp-dev] Replacing master/slave nomenclature

[Edward Warnicke]

Steven,

That sounds good to me.  I tend to see this as "Get the good ideas for
possible replacements out there so the folks doing the work have some
inspiration for the choices".  Please don't take the link as suggesting
that list is the end all and be all of possible choices :)

Ed

On Tue, Jul 14, 2020 at 11:54 AM Steven Luong (sluong) 
wrote:

> The list has a good number of suggestions. In 802.1ax spec, they use the
> term aggregator and member link. So I am inclined to stick to
> aggregator/member unless someone finds that it is unacceptable.
>
>
>
> Steven
>
>
>
> *From: *Ed Warnicke 
> *Date: *Tuesday, July 14, 2020 at 9:45 AM
> *To: *"Jerome Tollet (jtollet)" 
> *Cc: *"Steven Luong (sluong)" , "Dave Barach (dbarach)"
> , "Kinsella, Ray" , Stephen Hemminger <
> step...@networkplumber.org>, "vpp-dev@lists.fd.io" ,
> "t...@lists.fd.io" , "Ed Warnicke (eaw)" 
> *Subject: *Re: [tsc] [vpp-dev] Replacing master/slave nomenclature
>
>
>
> This is a pretty good summary of various suggestions for replacement terms:
>
>
>
>
> https://www.zdnet.com/article/linux-team-approves-new-terminology-bans-terms-like-blacklist-and-slave/
>
>
>
> Ed
>
>
>
> On Tue, Jul 14, 2020 at 11:36 AM Jerome Tollet via lists.fd.io  cisco@lists.fd.io> wrote:
>
> Hi Steven,
> Please note that per this proposition,  https://lkml.org/lkml/2020/7/4/229,
> slave must be avoided but master can be kept.
> Maybe master/member or master/secondary could be options too.
> Jerome
>
> Le 14/07/2020 18:32, « vpp-dev@lists.fd.io au nom de steven luong via
> lists.fd.io » 
> a écrit :
>
> I am in the process of pushing a patch to replace master/slave with
> aggregator/member for the bonding.
>
> Steven
>
> On 7/13/20, 4:44 AM, "vpp-dev@lists.fd.io on behalf of Dave Barach
> via lists.fd.io"  cisco@lists.fd.io> wrote:
>
> +1, especially since our next release will be supported for a
> year, and API name changes are involved...
>
> -Original Message-
> From: Kinsella, Ray 
> Sent: Monday, July 13, 2020 6:01 AM
> To: Dave Barach (dbarach) ; Stephen Hemminger <
> step...@networkplumber.org>; vpp-dev@lists.fd.io; t...@lists.fd.io; Ed
> Warnicke (eaw) 
> Subject: Re: [vpp-dev] Replacing master/slave nomenclature
>
> Hi Stephen,
>
> I agree, I don't think we should ignore this.
> Ed - I suggest we table a discussion at the next FD.io TSC?
>
> Ray K
>
> On 09/07/2020 17:05, Dave Barach via lists.fd.io wrote:
> > Looping in the technical steering committee...
> >
> > -Original Message-
> > From: vpp-dev@lists.fd.io  On Behalf Of
> Stephen Hemminger
> > Sent: Thursday, July 2, 2020 7:02 PM
> > To: vpp-dev@lists.fd.io
> > Subject: [vpp-dev] Replacing master/slave nomenclature
> >
> > Is the VPP project addressing the use of master/slave
> nomenclature in the code base, documentation and CLI?  We are doing this
> for DPDK and it would be good if the replacement wording used in DPDK
> matched the wording used in FD.io projects.
> >
> > Particularly problematic is the use of master/slave in bonding.
> > This seems to be a leftover from Linux, since none of the
> commercial products use that terminology and it is not present in 802.1AX
> standard.
> >
> > The IEEE and IETF are doing an across the board look at these
> terms in standards.
> >
> >
> >
> >
>
>
> 
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#16954): https://lists.fd.io/g/vpp-dev/message/16954
Mute This Topic: https://lists.fd.io/mt/75503014/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [tsc] [vpp-dev] Replacing master/slave nomenclature

[Edward Warnicke]

This is a pretty good summary of various suggestions for replacement terms:

https://www.zdnet.com/article/linux-team-approves-new-terminology-bans-terms-like-blacklist-and-slave/

Ed

On Tue, Jul 14, 2020 at 11:36 AM Jerome Tollet via lists.fd.io  wrote:

> Hi Steven,
> Please note that per this proposition,  https://lkml.org/lkml/2020/7/4/229,
> slave must be avoided but master can be kept.
> Maybe master/member or master/secondary could be options too.
> Jerome
>
> Le 14/07/2020 18:32, « vpp-dev@lists.fd.io au nom de steven luong via
> lists.fd.io » 
> a écrit :
>
> I am in the process of pushing a patch to replace master/slave with
> aggregator/member for the bonding.
>
> Steven
>
> On 7/13/20, 4:44 AM, "vpp-dev@lists.fd.io on behalf of Dave Barach
> via lists.fd.io"  cisco@lists.fd.io> wrote:
>
> +1, especially since our next release will be supported for a
> year, and API name changes are involved...
>
> -Original Message-
> From: Kinsella, Ray 
> Sent: Monday, July 13, 2020 6:01 AM
> To: Dave Barach (dbarach) ; Stephen Hemminger <
> step...@networkplumber.org>; vpp-dev@lists.fd.io; t...@lists.fd.io; Ed
> Warnicke (eaw) 
> Subject: Re: [vpp-dev] Replacing master/slave nomenclature
>
> Hi Stephen,
>
> I agree, I don't think we should ignore this.
> Ed - I suggest we table a discussion at the next FD.io TSC?
>
> Ray K
>
> On 09/07/2020 17:05, Dave Barach via lists.fd.io wrote:
> > Looping in the technical steering committee...
> >
> > -Original Message-
> > From: vpp-dev@lists.fd.io  On Behalf Of
> Stephen Hemminger
> > Sent: Thursday, July 2, 2020 7:02 PM
> > To: vpp-dev@lists.fd.io
> > Subject: [vpp-dev] Replacing master/slave nomenclature
> >
> > Is the VPP project addressing the use of master/slave
> nomenclature in the code base, documentation and CLI?  We are doing this
> for DPDK and it would be good if the replacement wording used in DPDK
> matched the wording used in FD.io projects.
> >
> > Particularly problematic is the use of master/slave in bonding.
> > This seems to be a leftover from Linux, since none of the
> commercial products use that terminology and it is not present in 802.1AX
> standard.
> >
> > The IEEE and IETF are doing an across the board look at these
> terms in standards.
> >
> >
> >
> >
>
>
> 
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#16950): https://lists.fd.io/g/vpp-dev/message/16950
Mute This Topic: https://lists.fd.io/mt/75503014/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] vpp project committer nomination: Benoit Ganne

[Edward Warnicke]

+1

On Tue, Apr 21, 2020 at 6:45 AM Dave Barach via lists.fd.io  wrote:

> +1... Dave
>
> -Original Message-
> From: vpp-dev@lists.fd.io  On Behalf Of Dave Barach
> via lists.fd.io
> Sent: Tuesday, April 21, 2020 7:40 AM
> To: vpp-dev@lists.fd.io
> Subject: [vpp-dev] vpp project committer nomination: Benoit Ganne
>
> Vpp project committers: please vote +1, 0, -1 on the mailto:
> vpp-dev@lists.fd.io mailer as to whether we should add Benoit Ganne as a
> vpp project committer.
>
> Ben has about 150 merged patches, see
> https://gerrit.fd.io/r/q/status:merged+owner:bganne%2540cisco.com. He has
> expressed interest in the role, and I believe that he will make a fine
> committer.
>
> Thanks... Dave
> 
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#16140): https://lists.fd.io/g/vpp-dev/message/16140
Mute This Topic: https://lists.fd.io/mt/73170252/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] vpp project committers: formal vote to add Matt Smith as a vpp committer

[Edward Warnicke]

+1

On Mon, Mar 2, 2020 at 8:52 AM Ole Troan  wrote:

> +1
>
> Best regards,
> Ole
>
> > On 2 Mar 2020, at 15:15, d...@barachs.net wrote:
> >
> > VPP committers, please vote +1, 0, -1 on adding Matt Smith (
> mgsm...@netgate.com) as a vpp project committer.
> > Matt has contributed O(100) merged patches, and he recently contributed
> the entire vrrp plugin. See
> https://gerrit.fd.io/r/q/owner:mgsmith%2540netgate.com
> > Please vote (on vpp-dev@lists.fd.io) by the end of this Wednesday,
> 2/4/2020, so we can put the results in front of the TSC this Thursday.
> > Thanks... Dave
> >
> >
>
> 
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#15654): https://lists.fd.io/g/vpp-dev/message/15654
Mute This Topic: https://lists.fd.io/mt/71675525/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] 2020 LFN Governing Board Committer Representative Self-Nomination Period Open

[Edward Warnicke]

-- Forwarded message -
From: Casey Cain 
Date: Wed, Feb 19, 2020 at 7:31 PM
Subject: 2020 LFN Governing Board Committer Representative Self-Nomination
Period Open
To:


 Hello, everyone.

This is to inform you that the self-nomination period for the LFN Governing
Board Committer Representative (LGBMCR) has started.  If you have received
this email, you have been identified as an eligible candidate.
*Role:*

   - The role of the LFN Governing Board Member Committers Representative
   (LGBMCR) is to represent the committers and contributors to LFN projects at
   the LFN Governing board.  The expectation of the LGBMCR is to attend all
   LFN Governing board meetings (and any appropriate ancillary meetings),
   gather input from the committer community for issues raised at the board
   level, and to communicate to the committer community key activities from
   board.
   - LGBMCR is elected for the 1 year. Re-election is not possible.


If you are interested in becoming the technical representative to the
Governing Body, please self-nominate at the link below by March 4th, 2020.
https://wiki.lfnetworking.org/x/bYPrAQ

Voting will begin on March 5th, 2020 and close by March 19th, 2020 at 5pm
Pacific Time.

If you would like more information on the LGBMCR, please see
https://wiki.lfnetworking.org/x/AgIiAQ or reach out to your community
Technical Program Manager / Community Architect.


Best,
Casey Cain
Technical Program Manager / Community Architect
Linux Foundation
_
IRC - CaseyLF
WeChat - okaru6
Book a Meeting w/ Casey 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#15474): https://lists.fd.io/g/vpp-dev/message/15474
Mute This Topic: https://lists.fd.io/mt/71428504/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] [tsc] Project Proposal for uDPI

[Edward Warnicke]

Do you have a preference as to dates?

Ed

On Tue, Aug 13, 2019 at 7:44 PM Ni, Hongjun  wrote:

> Hi Ed,
>
>
>
> Thank you for scheduling the proposal review.
>
>
>
> I think a TSC meeting after Aug 21 is better, to follow the FD.io TSC
> policy.
>
>
>
> Thanks,
>
> Hongjun
>
>
>
> *From:* Ed Warnicke [mailto:hagb...@gmail.com]
> *Sent:* Wednesday, August 14, 2019 5:09 AM
> *To:* Ni, Hongjun 
> *Cc:* t...@lists.fd.io; vpp-dev@lists.fd.io; Wang, Xiang W <
> xiang.w.w...@intel.com>; Hong, Yang A ; Chang,
> Harry ; gu.ji...@zte.com.cn; Shan Jianghua <
> shanjia...@chinatelecom.cn>; Zhang Yang ; Li
> Xingfu ; Wu Shuai ; Xia
> Yuying ; Fan Chenggang ;
> Gao Feng ; Liu Zhong ;
> Zhao Yong ; Chen Haiquan 
> *Subject:* Re: [tsc] Project Proposal for uDPI
>
>
>
> Hongjun,
>
>
>
> You guys are eligible for project creation review starting at the Aug 21
> TSC meeting I believe (based on sending the notification to the TSC on Aug
> 8) ... when would you like to schedule for that Thu's TSC meeting, or a
> subsequent one?
>
>
>
> Ed
>
>
>
> On Thu, Aug 8, 2019 at 8:11 PM Ni, Hongjun  wrote:
>
> Hello FD.io TSCs
>
>
>
> Please accept this project proposal for uDPI for consideration.
>
> https://wiki.fd.io/view/Project_Proposals/uDPI
>
>
>
> So far, this project has 11 founders and 15 initial committers from
>
> Intel, ZTE, China Telecom, HuachenTel, Inspur, Yxlink, Sunyainfo, Tencent,
> China Unicom, Huawei, QingCloud.
>
>
>
> If possible, I would like to present this on TSC meeting.
>
>
>
> Thanks,
>
> Hongjun
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#1070): https://lists.fd.io/g/tsc/message/1070
> Mute This Topic: https://lists.fd.io/mt/32805806/464962
> Group Owner: tsc+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/tsc/unsub  [hagb...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#1077): https://lists.fd.io/g/tsc/message/1077
> Mute This Topic: https://lists.fd.io/mt/32805806/464962
> Group Owner: tsc+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/tsc/unsub  [hagb...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13736): https://lists.fd.io/g/vpp-dev/message/13736
Mute This Topic: https://lists.fd.io/mt/32857358/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] [tsc] Project Proposal for uDPI

[Edward Warnicke]

Hongjun,

You guys are eligible for project creation review starting at the Aug 21
TSC meeting I believe (based on sending the notification to the TSC on Aug
8) ... when would you like to schedule for that Thu's TSC meeting, or a
subsequent one?

Ed

On Thu, Aug 8, 2019 at 8:11 PM Ni, Hongjun  wrote:

> Hello FD.io TSCs
>
>
>
> Please accept this project proposal for uDPI for consideration.
>
> https://wiki.fd.io/view/Project_Proposals/uDPI
>
>
>
> So far, this project has 11 founders and 15 initial committers from
>
> Intel, ZTE, China Telecom, HuachenTel, Inspur, Yxlink, Sunyainfo, Tencent,
> China Unicom, Huawei, QingCloud.
>
>
>
> If possible, I would like to present this on TSC meeting.
>
>
>
> Thanks,
>
> Hongjun
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#1070): https://lists.fd.io/g/tsc/message/1070
> Mute This Topic: https://lists.fd.io/mt/32805806/464962
> Group Owner: tsc+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/tsc/unsub  [hagb...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13727): https://lists.fd.io/g/vpp-dev/message/13727
Mute This Topic: https://lists.fd.io/mt/32857358/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] REMINDER: LFN Booth Demo Ideas for ONS Europe Due 7/31

[Edward Warnicke]

FD.io folks,

We hope that you are planning to attend ONS Europe, September 23-25, in
Antwerp, Belgium
.
Those in attendance at the last three ONS events will recall that we hosted
an *LF Networking Booth* that showcased 8-10 compelling, community-driven
demos from the LFN technical projects. See this blog post

from
ONS North America last April to learn more about the opportunity.

We wanted to reach out now to the FD.io community to let you know that
there will be space for 8-10 networking demos inside the LFN booth again at
ONS Europe and they are seeking demo ideas using the same process. The goal
is to show compelling uses of networking project technology to solve real
world industry challenges.

Demos that show cross-project elements (e.g. between LFN projects and other
networking projects), that map to a specific industry use case, or are
endorsed by a service provider are preferred. That said, there is some room
for demos that highlight the good work and value-add from projects that
don't necessarily meet these criteria. At least one demo slot will be made
available for each LFN project (FD.io, ONAP, ODL, OPNFV, PNDA, SNAS,
Tungsten Fabric) that submits a quality idea.

Demos stations will again have storage space, a counter, backdrop, monitor,
power, and Wi-Fi internet provided. There is no cost to host a standard
demo in the LFN booth although additional power, internet, space, etc. may
incur a cost.

Here are the key dates to keep in mind:

   - July 10: Demo idea solicitation email sent to community lists
   - *July 31: Demo ideas submissions due*
   - August 14: Demos ideas reviewed, chosen, and notifications sent
   - September 23-25: Demos shown at ONS

To submit your demo idea for consideration, please collect and provide the
following information:

   - Demo title (10 words max)
   - Brief demo description (200 words max)
   - List of demo manager(s) with contact information
   - List of open source projects involved
   - List of companies involved
   - Any extra requirements or special considerations

Demo manager responsibilities include:

   - Creating the demo concept and actual demo to be shown
   - Responding promptly to requests for information
   - Meeting all demo preparation deadlines
   - Setting up and testing the demo pre-show and taking down post-show
   - Staffing the demo during ONS expo hours (along with other designated
   team members to help share the load)
   - Being willing to participate in media activities, e.g. photos, videos

ONS sponsor companies are of course welcome to host demos in their booths
on the show floor as well. Please check with your ONS sponsorship manager
to explore these opportunities.

*Submit your demo ideas by July 31st by sending an email
to bw...@linuxfoundation.org *. LFN staff
leadership (Heather, Arpit) will then review the submissions, get back to
submitters with questions/suggestions if needed, and recommend a final demo
roster by August 14th. Send any questions you may have to
bw...@linuxfoundation.org.

We look forward to seeing your demo ideas.

Ed
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13594): https://lists.fd.io/g/vpp-dev/message/13594
Mute This Topic: https://lists.fd.io/mt/32611845/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] OpenSuse builds failing for stable/1901

[Edward Warnicke]

Paul,

Looks like it was a ships in the night effect on a fix going into
stable/1901... rebase *appears* to have fixed it:

https://gerrit.fd.io/r/#/c/17884/

Ed

On Wed, Feb 27, 2019 at 2:14 PM Paul Vinciguerra 
wrote:

> Ok.
>
> Let me know if I can do anything to help!
>
> On Wed, Feb 27, 2019 at 3:09 PM Ed Kern (ejk)  wrote:
>
>> thats a perfectly good and reasonable change and I support it..
>>
>> But that’s not the problem that the other ed is having right now.
>>
>> Ed
>>
>>
>>
>> On Feb 27, 2019, at 12:47 PM, Paul Vinciguerra <
>> pvi...@vinciconsulting.com> wrote:
>>
>> Ed,
>>
>> There is an issue.  I am testing a fix.
>> See: https://gerrit.fd.io/r/#/c/17917/
>>
>> Paul
>>
>> On Wed, Feb 27, 2019 at 2:23 PM Ed Warnicke  wrote:
>>
>>> Paul,
>>>
>>> Good first thing to check... I've pushed
>>> https://gerrit.fd.io/r/#/c/17916/
>>>
>>> to cause the opensuse jobs to cat the /etc/os-release as you suggested,
>>> and rechecked: https://gerrit.fd.io/r/#/c/17884/
>>> to see what happens :)
>>>
>>> Ed
>>>
>>> On Wed, Feb 27, 2019 at 12:48 PM Paul Vinciguerra <
>>> pvi...@vinciconsulting.com> wrote:
>>>
>>>> Can we confirm that they are truly osleap15?
>>>>
>>>> An osleap box reports correctly for me:
>>>> docker run --shm-size=1024m -it opensuse/leap:leap-15 /bin/bash
>>>> *ee4938c281e4:/ #* cat /etc/os-release
>>>> NAME="openSUSE Leap"
>>>> VERSION="15.0 Beta"
>>>> ID="opensuse"
>>>> ID_LIKE="suse"
>>>> VERSION_ID="15.0"
>>>> PRETTY_NAME="openSUSE Leap 15.0 Beta"
>>>> ANSI_COLOR="0;32"
>>>> CPE_NAME="cpe:/o:opensuse:leap:15.0"
>>>> BUG_REPORT_URL="https://bugs.opensuse.org;
>>>> HOME_URL="https://www.opensuse.org/;
>>>>
>>>> On Wed, Feb 27, 2019 at 1:12 PM Edward Warnicke 
>>>> wrote:
>>>>
>>>>> In cherry picking some fixes back to stable/1901, I've found that the
>>>>> builds for 1901 for OpenSuse Leap seem to be failing during install-deps:
>>>>>
>>>>> https://jenkins.fd.io/job/vpp-verify-1901-osleap15/77/console
>>>>>
>>>>> *10:50:21* No provider of 'libboost_thread1_68_0-devel-1.68.0' found.
>>>>>
>>>>>
>>>>> Which looks like there is some upstream issue with a dependency no
>>>>> longer being available for libboost.
>>>>>
>>>>> Digging deeper, it would appear that we are tripping on
>>>>> SUSE_NAME=Tumbleweed:
>>>>>
>>>>> https://github.com/FDio/vpp/blob/stable/1901/Makefile#L131
>>>>>
>>>>> ifeq ($(OS_ID),opensuse)
>>>>> ifeq ($(SUSE_NAME),Tumbleweed)
>>>>> RPM_SUSE_DEVEL_DEPS = libboost_headers1_68_0-devel-1.68.0
>>>>> libboost_thread1_68_0-devel-1.68.0 gcc
>>>>> RPM_SUSE_PYTHON_DEPS += python2-ply python2-virtualenv
>>>>> endif
>>>>> ifeq ($(SUSE_ID),15.0)
>>>>> RPM_SUSE_DEVEL_DEPS = libboost_headers-devel libboost_thread-devel gcc6
>>>>> else
>>>>> RPM_SUSE_DEVEL_DEPS += libboost_headers1_68_0-devel-1.68.0 gcc6
>>>>> RPM_SUSE_PYTHON_DEPS += python-virtualenv
>>>>> endif
>>>>> endif
>>>>>
>>>>> So for some reason, the servers are reporting SUSE_NAME=Tumbelweed,
>>>>> and being asked to install the wrong packages even though they are OSLEAP
>>>>> 15 boxes.  Note: this same Makefile fragment is identical on master where
>>>>> the corresponding jobs are succeeding.
>>>>>
>>>>> Do any of the OpenSuse folks have ideas as to what could be happening
>>>>> here?
>>>>>
>>>>> Ed
>>>>>
>>>>> -=-=-=-=-=-=-=-=-=-=-=-
>>>>> Links: You receive all messages sent to this group.
>>>>>
>>>>> View/Reply Online (#12366):
>>>>> https://lists.fd.io/g/vpp-dev/message/12366
>>>>> Mute This Topic: https://lists.fd.io/mt/30154873/1594641
>>>>> Group Owner: vpp-dev+ow...@lists.fd.io
>>>>> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [
>>>>> pvi...@vinciconsulting.com]
>>>>> -=-=-=-=-=-=-=-=-=-=-=-
>>>>>
>>>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>>
>> View/Reply Online (#12371): https://lists.fd.io/g/vpp-dev/message/12371
>> Mute This Topic: https://lists.fd.io/mt/30154873/675649
>> Group Owner: vpp-dev+ow...@lists.fd.io
>> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [e...@cisco.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
>>
>>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12374): https://lists.fd.io/g/vpp-dev/message/12374
Mute This Topic: https://lists.fd.io/mt/30154873/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] OpenSuse builds failing for stable/1901

[Edward Warnicke]

Paul,

Good first thing to check... I've pushed
https://gerrit.fd.io/r/#/c/17916/

to cause the opensuse jobs to cat the /etc/os-release as you suggested, and
rechecked: https://gerrit.fd.io/r/#/c/17884/
to see what happens :)

Ed

On Wed, Feb 27, 2019 at 12:48 PM Paul Vinciguerra <
pvi...@vinciconsulting.com> wrote:

> Can we confirm that they are truly osleap15?
>
> An osleap box reports correctly for me:
>
> docker run --shm-size=1024m -it opensuse/leap:leap-15 /bin/bash
>
> *ee4938c281e4:/ #* cat /etc/os-release
>
> NAME="openSUSE Leap"
>
> VERSION="15.0 Beta"
>
> ID="opensuse"
>
> ID_LIKE="suse"
>
> VERSION_ID="15.0"
>
> PRETTY_NAME="openSUSE Leap 15.0 Beta"
>
> ANSI_COLOR="0;32"
>
> CPE_NAME="cpe:/o:opensuse:leap:15.0"
>
> BUG_REPORT_URL="https://bugs.opensuse.org;
> HOME_URL="https://www.opensuse.org/;
>
> On Wed, Feb 27, 2019 at 1:12 PM Edward Warnicke  wrote:
>
>> In cherry picking some fixes back to stable/1901, I've found that the
>> builds for 1901 for OpenSuse Leap seem to be failing during install-deps:
>>
>> https://jenkins.fd.io/job/vpp-verify-1901-osleap15/77/console
>>
>> *10:50:21* No provider of 'libboost_thread1_68_0-devel-1.68.0' found.
>>
>>
>> Which looks like there is some upstream issue with a dependency no longer
>> being available for libboost.
>>
>> Digging deeper, it would appear that we are tripping on
>> SUSE_NAME=Tumbleweed:
>>
>> https://github.com/FDio/vpp/blob/stable/1901/Makefile#L131
>>
>> ifeq ($(OS_ID),opensuse)
>> ifeq ($(SUSE_NAME),Tumbleweed)
>> RPM_SUSE_DEVEL_DEPS = libboost_headers1_68_0-devel-1.68.0
>> libboost_thread1_68_0-devel-1.68.0 gcc
>> RPM_SUSE_PYTHON_DEPS += python2-ply python2-virtualenv
>> endif
>> ifeq ($(SUSE_ID),15.0)
>> RPM_SUSE_DEVEL_DEPS = libboost_headers-devel libboost_thread-devel gcc6
>> else
>> RPM_SUSE_DEVEL_DEPS += libboost_headers1_68_0-devel-1.68.0 gcc6
>> RPM_SUSE_PYTHON_DEPS += python-virtualenv
>> endif
>> endif
>>
>> So for some reason, the servers are reporting SUSE_NAME=Tumbelweed, and
>> being asked to install the wrong packages even though they are OSLEAP 15
>> boxes.  Note: this same Makefile fragment is identical on master where the
>> corresponding jobs are succeeding.
>>
>> Do any of the OpenSuse folks have ideas as to what could be happening
>> here?
>>
>> Ed
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>>
>> View/Reply Online (#12366): https://lists.fd.io/g/vpp-dev/message/12366
>> Mute This Topic: https://lists.fd.io/mt/30154873/1594641
>> Group Owner: vpp-dev+ow...@lists.fd.io
>> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [
>> pvi...@vinciconsulting.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12368): https://lists.fd.io/g/vpp-dev/message/12368
Mute This Topic: https://lists.fd.io/mt/30154873/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] OpenSuse builds failing for stable/1901

[Edward Warnicke]

In cherry picking some fixes back to stable/1901, I've found that the
builds for 1901 for OpenSuse Leap seem to be failing during install-deps:

https://jenkins.fd.io/job/vpp-verify-1901-osleap15/77/console

*10:50:21* No provider of 'libboost_thread1_68_0-devel-1.68.0' found.


Which looks like there is some upstream issue with a dependency no longer
being available for libboost.

Digging deeper, it would appear that we are tripping on
SUSE_NAME=Tumbleweed:

https://github.com/FDio/vpp/blob/stable/1901/Makefile#L131

ifeq ($(OS_ID),opensuse)
ifeq ($(SUSE_NAME),Tumbleweed)
RPM_SUSE_DEVEL_DEPS = libboost_headers1_68_0-devel-1.68.0
libboost_thread1_68_0-devel-1.68.0 gcc
RPM_SUSE_PYTHON_DEPS += python2-ply python2-virtualenv
endif
ifeq ($(SUSE_ID),15.0)
RPM_SUSE_DEVEL_DEPS = libboost_headers-devel libboost_thread-devel gcc6
else
RPM_SUSE_DEVEL_DEPS += libboost_headers1_68_0-devel-1.68.0 gcc6
RPM_SUSE_PYTHON_DEPS += python-virtualenv
endif
endif

So for some reason, the servers are reporting SUSE_NAME=Tumbelweed, and
being asked to install the wrong packages even though they are OSLEAP 15
boxes.  Note: this same Makefile fragment is identical on master where the
corresponding jobs are succeeding.

Do any of the OpenSuse folks have ideas as to what could be happening here?

Ed
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12366): https://lists.fd.io/g/vpp-dev/message/12366
Mute This Topic: https://lists.fd.io/mt/30154873/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] New vpp project committer nomination: Paul Vinciguerra

[Edward Warnicke]

+1

On Wed, Feb 27, 2019 at 7:21 AM Damjan Marion via Lists.Fd.Io  wrote:

> +1
>
> On 27 Feb 2019, at 14:20, Dave Barach via Lists.Fd.Io <
> dbarach=cisco@lists.fd.io> wrote:
>
> +1... Dave
>
> *From:* vpp-dev@lists.fd.io  *On Behalf Of *Dave
> Barach via Lists.Fd.Io
> *Sent:* Wednesday, February 27, 2019 7:38 AM
> *To:* vpp-dev@lists.fd.io
> *Cc:* vpp-dev@lists.fd.io
> *Subject:* [vpp-dev] New vpp project committer nomination: Paul
> Vinciguerra
>
> In view of significant code contributions to the vpp project - see below -
> I'm pleased to nominate Paul Vinciguerra as a vpp project committer. I have
> high confidence that he'll be a major asset to the project in a committer
> role.
>
> Paul has contributed 100 merged patches, concentrating on the “make test”
> .py framework. See
> https://gerrit.fd.io/r/#/q/status:merged+owner:%22Paul+Vinciguerra+%253Cpvinci%2540vinciconsulting.com%253E%22
>
> Committers, please vote (+1, 0, -1) on vpp-dev@lists.fd.io. We'll need a
> recorded vote so that the TSC will approve Paul’s nomination.
>
> If at all possible please vote *today*, February 27, 2019 so we can add
> Paul’s nomination to tomorrow’s TSC agenda for final approval.
>
> Thanks... Dave
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#12356): https://lists.fd.io/g/vpp-dev/message/12356
> Mute This Topic: https://lists.fd.io/mt/30151621/675642
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [dmar...@me.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
> --
> Damjan
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#12357): https://lists.fd.io/g/vpp-dev/message/12357
> Mute This Topic: https://lists.fd.io/mt/30151621/464962
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [hagb...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12358): https://lists.fd.io/g/vpp-dev/message/12358
Mute This Topic: https://lists.fd.io/mt/30151621/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] FD.io minisummit at Kubecon EU (May 21-23, Barcelona)

[Edward Warnicke]

+ hicn and sweetcomb, who's lists were misconfigured the first time I sent
it :)

Ed

On Thu, Feb 21, 2019 at 1:04 PM Ed Warnicke  wrote:

> Traditionally in the past FD.io has held collocated minisummits at Kubecon
> (NA and EU).
>
> We are fortunate to have budget to do Kubecon EU, Kubecon NA, and one
> other collocated event (probably best to be held in Asia and possibly at an
> embedded event).
>
> In the course of discussing this, the FD.io Marketing group felt that
> doing a separate FD.io booth at Kubecon EU was a clear win, but raised the
> question:
>
> - Is there a better choice for an EU event to collocate with for the FD.io
> minisummit?
>
> This is a good question, and so wanted to open the discussion to the
> broader community, as it differs from what had previously been discussed in
> the community and decided on.
>
> So, thoughts?  Opinions?  Ideas?
>
> Ed
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12317): https://lists.fd.io/g/vpp-dev/message/12317
Mute This Topic: https://lists.fd.io/mt/29989425/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] FD.io minisummit at Kubecon EU (May 21-23, Barcelona)

[Edward Warnicke]

Traditionally in the past FD.io has held collocated minisummits at Kubecon
(NA and EU).

We are fortunate to have budget to do Kubecon EU, Kubecon NA, and one other
collocated event (probably best to be held in Asia and possibly at an
embedded event).

In the course of discussing this, the FD.io Marketing group felt that doing
a separate FD.io booth at Kubecon EU was a clear win, but raised the
question:

- Is there a better choice for an EU event to collocate with for the FD.io
minisummit?

This is a good question, and so wanted to open the discussion to the
broader community, as it differs from what had previously been discussed in
the community and decided on.

So, thoughts?  Opinions?  Ideas?

Ed
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12316): https://lists.fd.io/g/vpp-dev/message/12316
Mute This Topic: https://lists.fd.io/mt/29989425/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] wireshark vpp dispatch trace dissector merged

[Edward Warnicke]

Woot!

On Thu, Jan 17, 2019 at 10:25 AM Florin Coras 
wrote:

> Awesome!
>
> Florin
>
> On Jan 17, 2019, at 5:11 AM, Dave Barach via Lists.Fd.Io <
> dbarach=cisco@lists.fd.io> wrote:
>
> I’m pleased to announce that our dispatch trace wireshark dissector has
> been merged. At some point in the indefinite future, everyone’s favorite
> distro will include a copy of wireshark which knows how to dissect vpp
> dispatch trace pcap files.
>
> I’ll update the docs accordingly.
>
> Dave
>
> *From:* bugzilla-dae...@wireshark.org 
> *Sent:* Thursday, January 17, 2019 6:32 AM
> *To:* wiresh...@barachs.net
> *Subject:* [Bug 15411] [dissector] Add dissector for vector packet
> processing dispatch traces
>
> *Comment # 2
>  on bug 15411
>  from Gerrit
> Code Review *
>
> Change 31466 merged by Anders Broman:
>
> VPP: add vpp graph dispatch trace dissector
>
>
>
> https://code.wireshark.org/review/31466
>
> --
> You are receiving this mail because:
>
>- You reported the bug.
>- You are the assignee for the bug.
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#11939): https://lists.fd.io/g/vpp-dev/message/11939
> Mute This Topic: https://lists.fd.io/mt/29172119/675152
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [fcoras.li...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#11940): https://lists.fd.io/g/vpp-dev/message/11940
> Mute This Topic: https://lists.fd.io/mt/29172119/464962
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [hagb...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11941): https://lists.fd.io/g/vpp-dev/message/11941
Mute This Topic: https://lists.fd.io/mt/29172119/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Kubecon EU CFP closes Jan 18

[Edward Warnicke]

For folks in the FD.io community looking to submit talks to the Kubecon EU
CFP:

https://events.linuxfoundation.org/events/kubecon-cloudnativecon-europe-2019/cfp/

It closes Jan 18.

Ed
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11684): https://lists.fd.io/g/vpp-dev/message/11684
Mute This Topic: https://lists.fd.io/mt/28795578/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP/Envoy integration status

[Edward Warnicke]

Checkout:

https://github.com/envoyproxy/envoy/pull/5177

The Envoy side modularity work is in progress :)

Ed

On Thu, Dec 6, 2018 at 6:45 PM dado via Lists.Fd.Io  wrote:

> Hi Florin,
>
> Thanks for the quick response. Do you know who I may contact regarding
> about VPP/Envoy integration status?
>
> Thanks,
> Dai -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#11518): https://lists.fd.io/g/vpp-dev/message/11518
> Mute This Topic: https://lists.fd.io/mt/28631119/464962
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [hagb...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11519): https://lists.fd.io/g/vpp-dev/message/11519
Mute This Topic: https://lists.fd.io/mt/28631119/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] [tsc] Project Proposal for Sweetcomb

[Edward Warnicke]

Congratulations!

Ed

On Thu, Nov 8, 2018 at 9:32 PM Ni, Hongjun  wrote:

> Hi all,
>
>
>
> Sweetcomb project has been approved by FD.io TSC.
>
> And project creation has been completed.
>
> Thank you all for your great help to make this happen!
>
>
>
> Below is the project resource:
>
>
>
> Committers group:  fdio-gerrit-sweetcomb-committers Invites sent to the
> initial committers:
> https://wiki.fd.io/view/Project_Proposals/Sweetcomb#Initial_Committers
>
> JIRA:  https://jira.fd.io/projects/SWEET/issues
>
> Jenkins:  https://jenkins.fd.io/view/sweetcomb/
>
> Gerrit:  https://gerrit.fd.io/r/#/admin/projects/sweetcomb
>
> Groups.io:  https://lists.fd.io/g/sweetcomb-dev
>
> GitHub Replication:  https://github.com/FDio/sweetcomb
>
>
>
> We also have submitted initial code for IPR Review.
>
> https://gerrit.fd.io/r/#/c/15835/ Initial code checkin for Sweetcomb
> project
>
>
>
> The initial code is contributed by HuachenTel, and we help to refactor it.
>
> If you have any concern, please raise it in project mail list:
> sweetcomb-...@lists.fd.io
>
>
>
> Thank you again,
>
> Hongjun
>
>
>
> *From:* t...@lists.fd.io [mailto:t...@lists.fd.io] *On Behalf Of *Ni,
> Hongjun
> *Sent:* Thursday, November 8, 2018 10:57 PM
> *To:* Ni, Hongjun ; Edward Warnicke <
> hagb...@gmail.com>
> *Cc:* t...@lists.fd.io; vpp-dev@lists.fd.io; Wang, Drenfong <
> drenfong.w...@intel.com>; ??? ;
> chen...@huachentel.com; lizhuo...@cmhi.chinamobile.com; ??? <
> lihf...@chinaunicom.cn>; zhijl@chinatelecom.cn; changlin...@nxp.com;
> Wang Tianyi ; davidfgao(?? ;
> lixin...@huachentel.com; jingqing@alibaba-inc.com; gu.ji...@zte.com.cn;
> Jerome Tollet (jtollet) 
> *Subject:* Re: [vpp-dev] [tsc] Project Proposal for Sweetcomb
>
>
>
> Hi TSC members,
>
>
>
> Our Initial code has been refactored and  gone through internal legal
> review.
>
>
>
> How can we submit the code to the fd.io Foundation for IPR Review?
>
>
>
> Thanks,
>
> Hongjun
>
>
>
> *From:* vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io
> ] *On Behalf Of *Ni, Hongjun
> *Sent:* Thursday, November 8, 2018 12:04 PM
> *To:* Ni, Hongjun ; Edward Warnicke <
> hagb...@gmail.com>
> *Cc:* t...@lists.fd.io; vpp-dev@lists.fd.io; Wang, Drenfong <
> drenfong.w...@intel.com>; ??? ;
> chen...@huachentel.com; lizhuo...@cmhi.chinamobile.com; ??? <
> lihf...@chinaunicom.cn>; zhijl@chinatelecom.cn; changlin...@nxp.com;
> Wang Tianyi ; davidfgao(?? ;
> lixin...@huachentel.com; jingqing@alibaba-inc.com; gu.ji...@zte.com.cn;
> Jerome Tollet (jtollet) 
> *Subject:* Re: [vpp-dev] [tsc] Project Proposal for Sweetcomb
>
>
>
>
>
> Welcome Cisco to join Sweetcomb project!
>
>
>
> https://wiki.fd.io/view/Project_Proposals/Sweetcomb
>
>
>
> Thanks a lot,
>
> Hongjun
>
>
>
> *From:* t...@lists.fd.io [mailto:t...@lists.fd.io ] *On
> Behalf Of *Ni, Hongjun
> *Sent:* Thursday, November 1, 2018 8:40 AM
> *To:* Ni, Hongjun ; Edward Warnicke <
> hagb...@gmail.com>
> *Cc:* t...@lists.fd.io; vpp-dev@lists.fd.io; Wang, Drenfong <
> drenfong.w...@intel.com>; ??? ;
> chen...@huachentel.com; lizhuo...@cmhi.chinamobile.com; ??? <
> lihf...@chinaunicom.cn>; zhijl....@chinatelecom.cn; changlin...@nxp.com;
> Wang Tianyi ; davidfgao(?? ;
> lixin...@huachentel.com; jingqing@alibaba-inc.com; gu.ji...@zte.com.cn
> *Subject:* Re: [vpp-dev] [tsc] Project Proposal for Sweetcomb
>
>
>
>
>
> Welcome ZTE to join!
>
>
>
> Thanks,
>
> Hongjun
>
>
>
> *From:* vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io
> ] *On Behalf Of *Ni, Hongjun
> *Sent:* Thursday, October 25, 2018 9:22 AM
> *To:* Edward Warnicke 
> *Cc:* t...@lists.fd.io; vpp-dev@lists.fd.io; Wang, Drenfong <
> drenfong.w...@intel.com>; ??? ;
> chen...@huachentel.com; lizhuo...@cmhi.chinamobile.com; ??? <
> lihf...@chinaunicom.cn>; zhijl@chinatelecom.cn; changlin...@nxp.com;
> Wang Tianyi ; davidfgao(?? ;
> lixin...@huachentel.com; jingqing@alibaba-inc.com
> *Subject:* Re: [vpp-dev] [tsc] Project Proposal for Sweetcomb
>
>
>
> Hi all,
>
>
>
> Some guys are asking for the original code in private.
>
> Here is our answer:
>
>
>
> We are working on reworking the original code, and doing internal legal
> review.
>
> When it is done,  we will submit the code to FD.io community for IPR
> review in one or two weeks.
>
>
>
> Thanks a lot,
>
> Hongjun
>
>
>
> *From:* vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io
> ] *On Behalf Of *Edward 

[vpp-dev] Call for Demos at Kubecon Seattle Dec 11-13

[Edward Warnicke]

FD.io will have a booth at Kubecon Seattle Dec 11-13.  This is a call out
to the community for demo proposals to show in the booth.

Please respond with a brief description of a demo you would like to run in
the FD.io booth.
If you wish to reply privately, please ensure you include Trishan on your
reply, as he's compiling the responses.

The Call for Demos is expected to close COB PT (5pm PT) Thu Nov 8.

Ed
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11108): https://lists.fd.io/g/vpp-dev/message/11108
Mute This Topic: https://lists.fd.io/mt/27860317/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] [tsc] Project Proposal for Sweetcomb

[Edward Warnicke]

I look forward to it :)

Ed

On Tue, Oct 23, 2018 at 8:42 AM Ni, Hongjun  wrote:

> Hi Ed,
>
>
>
> OK. I or some project proposer will join the Nov 8 8am PT TSC meeting and
> present the proposal.
>
>
>
> Thanks a lot,
>
> Hongjun
>
>
>
> *From:* t...@lists.fd.io [mailto:t...@lists.fd.io] *On Behalf Of *Edward
> Warnicke
> *Sent:* Tuesday, October 23, 2018 9:15 PM
> *To:* Ni, Hongjun 
> *Cc:* t...@lists.fd.io; vpp-dev@lists.fd.io; Wang, Drenfong <
> drenfong.w...@intel.com>; ??? ;
> chen...@huachentel.com; lizhuo...@cmhi.chinamobile.com; ??? <
> lihf...@chinaunicom.cn>; zhijl@chinatelecom.cn; changlin...@nxp.com;
> Wang Tianyi ; davidfgao(?? ;
> lixin...@huachentel.com; jingqing@alibaba-inc.com
> *Subject:* Re: [tsc] Project Proposal for Sweetcomb
>
>
>
> Hongjun,
>
>
>
> Thank you for the proposal :)  Per the FD.io technical charter, all
> proposals must be out for public review for two weeks prior to approval by
> the TSC.  I believe this makes Nov 8 the earliest TSC meeting where we
> could approve at the TSC.  Would you like to schedule the project creation
> review for the Nov 8 8am PT TSC meeting?  Will you (or other proposers of
> the project) be able to make that time to present the proposal?
>
>
>
> Ed
>
>
>
> On Tue, Oct 23, 2018 at 7:01 AM Ni, Hongjun  wrote:
>
> Hello FD.io TSCs
>
>
>
> Please accept this project proposal for Sweetcomb for consideration.
>
> https://wiki.fd.io/view/Project_Proposals/Sweetcomb
>
>
>
> This project has nine founding companies:
>
> Intel, HuachenTel, China Mobile, China Unicom, China Telecom, NXP, Tieto,
> Tencent, Alibaba.
>
>
>
> If possible, I would like to present this on TSC meeting.
>
>
>
> Thanks,
>
> Hongjun
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#856): https://lists.fd.io/g/tsc/message/856
> Mute This Topic: https://lists.fd.io/mt/27567539/464962
> Group Owner: tsc+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/tsc/unsub  [hagb...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10924): https://lists.fd.io/g/vpp-dev/message/10924
Mute This Topic: https://lists.fd.io/mt/27568384/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] [tsc] Project Proposal for Sweetcomb

[Edward Warnicke]

Hongjun,

Thank you for the proposal :)  Per the FD.io technical charter, all
proposals must be out for public review for two weeks prior to approval by
the TSC.  I believe this makes Nov 8 the earliest TSC meeting where we
could approve at the TSC.  Would you like to schedule the project creation
review for the Nov 8 8am PT TSC meeting?  Will you (or other proposers of
the project) be able to make that time to present the proposal?

Ed

On Tue, Oct 23, 2018 at 7:01 AM Ni, Hongjun  wrote:

> Hello FD.io TSCs
>
>
>
> Please accept this project proposal for Sweetcomb for consideration.
>
> https://wiki.fd.io/view/Project_Proposals/Sweetcomb
>
>
>
> This project has nine founding companies:
>
> Intel, HuachenTel, China Mobile, China Unicom, China Telecom, NXP, Tieto,
> Tencent, Alibaba.
>
>
>
> If possible, I would like to present this on TSC meeting.
>
>
>
> Thanks,
>
> Hongjun
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#856): https://lists.fd.io/g/tsc/message/856
> Mute This Topic: https://lists.fd.io/mt/27567539/464962
> Group Owner: tsc+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/tsc/unsub  [hagb...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10922): https://lists.fd.io/g/vpp-dev/message/10922
Mute This Topic: https://lists.fd.io/mt/27568384/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Problem downloading always VPP 19.01 instead of VPP 18.07

[Edward Warnicke]

Perhaps a bit of an explanation about how the repos are organized might
help:

https://packagecloud.io/fdio/release - Only released packages.  The latest
in there should be 18.07.1 (at least until 18.10 releases soon!)

https://packagecloud.io/fdio/1807 - the throttle branch for 1807 packages.
Not a lot interesting here any more, https://packagecloud.io/fdio/1810 is
the throttle for the upcoming 1810 release, much more fun :)

https://packagecloud.io/fdio/master - follows the master branch, merge by
merge.  That should be the only repo with 19.01-rc0 packages in it at this
time.

Is it possible you were pulling from fdio/master ?

Ed

On Thu, Oct 18, 2018 at 7:06 AM Francesco Spinelli <
francescospinell...@live.it> wrote:

> Hello VPP experts,
>
> I'm trying to download VPP version 18.07  but when I build it and run it,
> I notice that both VPP and the packages belong always to the 19.01 version
>
> It happens if I download them from here
> , using the command:
>
> curl -s https://packagecloud.io/install/repositories/fdio/1807/script.deb.sh 
> | sudo bash
>
>
> and when I pull VPP from gerrit:
>
> git clone https://gerrit.fd.io/r/vpp
>
>
> and then buidling it.
>
> Am I missing anything in my buildling process? How can I retrieve  18.07
> packages and avoid to use the  most recent ones?
>
> Thanks a lot for your help,
> Best Regards,
>
> Francesco
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#10868): https://lists.fd.io/g/vpp-dev/message/10868
> Mute This Topic: https://lists.fd.io/mt/27401834/464962
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [hagb...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10870): https://lists.fd.io/g/vpp-dev/message/10870
Mute This Topic: https://lists.fd.io/mt/27401834/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP 18.07.1 RPM release packages available in Centos

[Edward Warnicke]

Woot!

Ed

On Tue, Oct 2, 2018 at 10:45 AM Thomas F Herbert 
wrote:

> All,
>
> 18.07.1 release packages are in Centos mirrors.
>
> To install Centos update release packages of VPP on a Centos, install the
> Centos NFV SIG yum repo and then install vpp as follows.
>
> yum install centos-release-fdio
>
> yum install vpp*
>
> If already installed,
>
> yum update
>
> --Tom
> --
> *Thomas F Herbert*
> NFV and Fast Data Planes
> Networking Group Office of the CTO
> *Red Hat*
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#10731): https://lists.fd.io/g/vpp-dev/message/10731
> Mute This Topic: https://lists.fd.io/mt/26654231/464962
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [hagb...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10732): https://lists.fd.io/g/vpp-dev/message/10732
Mute This Topic: https://lists.fd.io/mt/26654231/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] how to pull a 18.07 code??

[Edward Warnicke]

git checkout v18.07.1

will get you to the latest release code

If you want the stable/18.07 branch:

git checkout stable/1807

Ed


On September 24, 2018 at 1:43:06 PM, Jit Mehta (
jitendra.harshad...@gmail.com) wrote:

Could someone tell me how do I pull the 18.07 code?

I have never pulled tree with a label before so

not sure how to do it.

BTW, I pulled latest VPP (*git* clone http://gerrit.fd.io/r/vpp)and have
run into the following cmake error:

CMake Error at /usr/share/cmake-3.5/Modules/CMakeTestCCompiler.cmake:61
(message):

  The C compiler "/usr/lib/ccache/cc" is not able to compile a simple test

  program.


  It fails with the following output:


   Change Dir:
/home/lab/VPP/vpp/build-root/build-vpp-native/vpp/CMakeFiles/CMakeTmp


  Run Build Command:"/usr/bin/ninja" "cmTC_4d84d"

The 18.07 code I had built fine earlier.


Thanks,

J

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10630): https://lists.fd.io/g/vpp-dev/message/10630
Mute This Topic: https://lists.fd.io/mt/26202696/464962
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [hagb...@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10659): https://lists.fd.io/g/vpp-dev/message/10659
Mute This Topic: https://lists.fd.io/mt/26202696/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [**EXTERNAL**] Fwd: [vpp-dev] Failing to create untagged sub-interface

[Edward Warnicke]

Guys,
Anyone have any thoughts on this?

Ed


On September 20, 2018 at 12:01:05 PM, Bly, Mike (m...@ciena.com) wrote:

Ed/Keith, et al,



What Vijay is digging into is trying to understand how to provide the
following sub-interface setup on a common/single physical NIC. I am hoping
you can shed some light on the feasibility of this, given the current code
to date.



Our goal is to provide proper separation of untagged vs. explicit-vlan
(EVPL) vs. default (all remaining vlans) vs. EPL as needed on a given NIC,
independent of any choice of forwarding mode (L2 vs L3).



GigabitEthernet5/0/0 à “not used to forward traffic” (see next three
sub-if’s), calling it sub_if_0 for reference below (seen as possible EPL
path, but not covered here, since already “working”)

GigabitEthernet5/0/0.untagged à all untagged traffic on this port goes to
sub_if_1

GigabitEthernet5/0/0.vid1 à all traffic arriving with outer tag == 1 goes
to sub_if_2

GigabitEthernet5/0/0.default à all other tagged traffic goes to sub_if_3



The only way we seem to be able to get sub_if_3 to process traffic is to
disable sub_if_0 (set mode to l3).



Additionally, the current configuration checking in
src/vnet/ethernet/node.c does not seem amenable to allowing the actual
configuration and support of untagged vs default as two distinct sub-if’s
processing traffic at the same time (my sub_if_1 and sub_if_3 above). Are
we missing something here in how this is supposed to work? We would be fine
with letting “sub_if_0” carry the untagged traffic (in place of sub_if_1),
but we have yet to figure out how to do that while still having sub_if_3
processing “all other tagged frames”. We can say in all of our testing that
we in fact do correctly see sub_if_2 working as expected.



Here is a simple configuration showing our current efforts in this area:



create bridge-domain 1

create bridge-domain 2

create bridge-domain 3



set interface l2 bridge GigabitEthernet5/0/0 1

set interface l2 bridge GigabitEthernet5/0/1 1



create sub-interfaces GigabitEthernet5/0/0 4095 default

create sub-interfaces GigabitEthernet5/0/1 4095 default

set interface l2 bridge GigabitEthernet5/0/0.4095 2

set interface l2 bridge GigabitEthernet5/0/1.4095 2



create sub-interfaces GigabitEthernet5/0/0 1

create sub-interfaces GigabitEthernet5/0/1 1

set interface l2 bridge GigabitEthernet5/0/1.1 3

set interface l2 bridge GigabitEthernet5/0/0.1 3





set interface state GigabitEthernet5/0/0 up

set interface state GigabitEthernet5/0/1 up

set interface state GigabitEthernet5/0/0.4095 up

set interface state GigabitEthernet5/0/1.4095 up

set interface state GigabitEthernet5/0/0.1 up

set interface state GigabitEthernet5/0/1.1 up



As noted above, the only way to get GigabitEthernet5/0/0.4095 to process
frames is to do the following, but doing so drops all untagged traffic.



set interface l3 GigabitEthernet5/0/0



Let us know next steps in resolving this.



Best Regards,

Mike



-- Forwarded message --
From: *Chandra Mohan, Vijay Mohan* 
Date: Tue, Sep 18, 2018 at 8:35 PM
Subject: Re: [vpp-dev] Failing to create untagged sub-interface
To: "vpp-dev@lists.fd.io" 



typedef struct

{

  u32 sw_if_index;

  u32 flags;

  // config entry is-valid flag

  // exact match flags (valid if packet has 0/1/2/3 tags)

  // L2 vs L3 forwarding mode

#define SUBINT_CONFIG_MATCH_0_TAG (1<<0)

#define SUBINT_CONFIG_MATCH_1_TAG (1<<1)

#define SUBINT_CONFIG_MATCH_2_TAG (1<<2)

#define SUBINT_CONFIG_MATCH_3_TAG (1<<3)

#define SUBINT_CONFIG_VALID   (1<<4)

#define SUBINT_CONFIG_L2  (1<<5)

#define SUBINT_CONFIG_P2P (1<<6)



} subint_config_t;





typedef struct

{

  subint_config_t untagged_subint;

  subint_config_t default_subint;

  u16 dot1q_vlans;  // pool id for vlan table

  u16 dot1ad_vlans; // pool id for vlan table

} main_intf_t;



Each main interface has untagged_subint and default_subint. The sw_if_index
in untagged_subint is same as the sw_if_index of the physical interface and
the ‘flags’ has ‘SUBINT_CONFIG_VALID’ set. Since, by default, physical
interface forwards untagged traffic, is the physical interface itself is
being treated as untagged sub-interface ? is my understanding correct ?



-vijay







*From: *"Chandra Mohan, Vijay Mohan" 
*Date: *Tuesday, September 18, 2018 at 3:52 PM
*To: *"vpp-dev@lists.fd.io" 
*Subject: *Re: Failing to create untagged sub-interface



Fd.io pages states following in the “create sub-interfaces” section:

Example of how to created a subinterface to process untagged packets:

*vpp# create sub-interfaces GigabitEthernet2/0/0 5 untagged*



I am trying to do exactly same thing mentioned above and it fails. Is this
a known issue (a bug) ??



-vijay





*From: *"Chandra Mohan, Vijay Mohan" 
*Date: *Tuesday, September 18, 2018 at 2:37 PM
*To: *"vpp-dev@lists.fd.io" 
*Subject: *Failing to create untagged sub-interface



Was not sure if this email is being delivered properly or not, so, 

Re: 答复: [E] [vpp-dev] Build a telecom-class Security gateway device with VPP

[Edward Warnicke]

The normal pattern in VPP is what we call ‘Dataplane Management Agents’.

VPP is an amazing dataplane, feature rich and fast.  It exposes a fast and
rich API via a shared memory message bus,
and we autogenerate C, C++, Python, Java, Lua, and Go APIs for it.

When you want to expose some element of control of VPP off of the box, you
write a Dataplane Management Agent.

Examples include:

Honeycomb  - Netconf/yang dataplane
management agent with BGP
Contiv-VPP  - K8s CNI plugin
networking-vpp  - Neutron
plugin for VPP

If you want to write your Dataplane Management Agent for SNMP or TR069 in
Go, you might want to look at Ligato , which provides a
toolkit of libraries to make writing
Dataplane Management Agents easier.

Ed

On September 18, 2018 at 8:25:31 AM, Tian Ye2(田野) (tian...@twsz.com) wrote:

Hi



Thanks for your reply.

It is look like VPP does not support any kind of OAM system(like
SNMP,TR069, or web based management page)

Am I right?

If I want to support SNMP server or TR069 client to VPP based product,

What is your suggestion? Build them from scratch or there already exist
something I could reuse?





*发件人:* Kevin Yan [mailto:kevin@mavenir.com]
*发送时间:* 2018年9月18日 15:29
*收件人:* Tian Ye2(田野) ; vpp-dev@lists.fd.io
*主题:* RE: [E] [vpp-dev] Build a telecom-class Security gateway device with
VPP



Hi Tianye,



 I suppose VPP is a good choice acting as a fast-path,  free and
efficient. And I think most of the requirements listed in your mail are
supported by native VPP.







*From:*vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io ]
*On Behalf Of* Tian Ye2(田野)
*Sent:* Monday, September 17, 2018 5:18 PM
*To:* vpp-dev@lists.fd.io
*Subject:* [E] [vpp-dev] Build a telecom-class Security gateway device with
VPP



Dear VPP developers:



I am a project manager from China mainland.

Currently we are planning to develop a high performance Security gateway
device to connect

between HNB/ENB and 3G/4G core network.

The basic requirement is:

l Support 10K Ipsec tunnels concurrently and up to 10G+ uplink throughput.

n At least support IKEv2

n DPD

l Support IPv4/IPv6

l Support NAT

l Support duo-uplink port for backup and load balance.

l Support OAM system(cli or web based or SNMP)

l Support Qos



I think this kind of product is already exist, just like the “CASA Axyom
Security Gateway”(I already attached it with this email)

My question is：

1. Is it a good idea to build it with VPP？What feature I listed
above could be reused with VPP?

2. If VPP is a good choice, is there anything I need to do by
myself? If any, can you brief me what kind of customization or development
I need to do?


--

This e-mail message may contain confidential or proprietary information of
Mavenir Systems, Inc. or its affiliates and is intended solely for the use
of the intended recipient(s). If you are not the intended recipient of this
message, you are hereby notified that any review, use or distribution of
this information is absolutely prohibited and we request that you delete
all copies in your control and contact us by e-mailing to
secur...@mavenir.com. This message contains the views of its author and may
not necessarily reflect the views of Mavenir Systems, Inc. or its
affiliates, who employ systems to monitor email messages, but make no
representation that such messages are authorized, secure, uncompromised, or
free from computer viruses, malware, or other defects. Thank You
本电子邮件（包括任何的附件）为本公司保密文件。本文件仅仅可为以上指定的收件人或公司使用，如果阁下非电子邮件所指定之收件人，那么阁下对该邮件部分或全部的泄漏、阅览、复印、变更、散布或对邮件内容的使用都是被严格禁止的。如果阁下接收了该错误传送的电子邮件，敬请阁下通过回复该邮件的方式立即通知寄件人，同时删除你所接收到的文本。
This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden. -=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10539): https://lists.fd.io/g/vpp-dev/message/10539
Mute This Topic: https://lists.fd.io/mt/25745520/464962
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [hagb...@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10542): https://lists.fd.io/g/vpp-dev/message/10542
Mute This Topic: https://lists.fd.io/mt/25745520/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] DO NOT MERGE ANY PATCHES onto stable/1807

[Edward Warnicke]

Due to ongoing technical difficulties with the 18.07 merge jobs, still
being worked out, please continue to not merge patches on stable/1807.

Ed

On Thu, Sep 13, 2018 at 5:48 PM Edward Warnicke  wrote:

> Due to some technical difficulties with the 18.07 merge jobs we will be
> unable to resolve till tomorrow, please continue to not merge patches on
> stable/1807
>
> Ed
>
> On Thu, Sep 13, 2018 at 3:12 PM Edward Warnicke  wrote:
>
>> I am in the process of doing the 18.07.1 release.  Will let you know when
>> it is done and stable/1807 can be merged to again.
>>
>> Ed
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>>
>> View/Reply Online (#10495): https://lists.fd.io/g/vpp-dev/message/10495
>> Mute This Topic: https://lists.fd.io/mt/25646407/464962
>> Group Owner: vpp-dev+ow...@lists.fd.io
>> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [hagb...@gmail.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#10497): https://lists.fd.io/g/vpp-dev/message/10497
> Mute This Topic: https://lists.fd.io/mt/25646407/464962
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [hagb...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10505): https://lists.fd.io/g/vpp-dev/message/10505
Mute This Topic: https://lists.fd.io/mt/25646407/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] vppctl start error

[Edward Warnicke]

Could you attach your new startup.conf file?

I can't be completely certain from the info provided... but it looks a lot
like vpp didn't really start... which might be because your edit of the
startup.conf file produced a syntactically invalid file.

You might also use systemctl to grab any logs from the startup

Another quick way to check is to simply try manually

/usr/bin/vpp -c /etc/vpp/startup.conf

That way you will see the output  from startup, and can find out if vpp is
failing to start due to issues with the config file.

Ed

On Fri, Sep 14, 2018 at 6:30 AM Evan Wang  wrote:

> Hi
>
> First, thank you to read my email.
>
>
>
> I build vpp,(latest from master) and install on my Centos-7.4.
>
> The SElinux is disabled.
>
>
>
> I start the service of vpp, #systemctl start vpp
>
>
>
> Then I run vppctl.
>
>
>
> If I use the default /etc/vpp/startup.conf, the vppctl start correctly.
>
>
>
> If I want to enable more dpdk rx/tx queue via updating startup.conf, and
> then restart vpp service.
>
> After that I run vppctl again, it failed with below log:
>
>
>
> [root@h3c_skylake_8hdd vpp]# vppctl
>
> clib_socket_init: connect (fd 3, '/run/vpp/cli.sock'): Connection refused
>
>
>
>
>
> would you like to tell me the similar issue appeared before? How to fix it?
>
>
>
> Thank you!
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#10501): https://lists.fd.io/g/vpp-dev/message/10501
> Mute This Topic: https://lists.fd.io/mt/25673019/464962
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [hagb...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10503): https://lists.fd.io/g/vpp-dev/message/10503
Mute This Topic: https://lists.fd.io/mt/25673019/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] DO NOT MERGE ANY PATCHES onto stable/1807

[Edward Warnicke]

Due to some technical difficulties with the 18.07 merge jobs we will be
unable to resolve till tomorrow, please continue to not merge patches on
stable/1807

Ed

On Thu, Sep 13, 2018 at 3:12 PM Edward Warnicke  wrote:

> I am in the process of doing the 18.07.1 release.  Will let you know when
> it is done and stable/1807 can be merged to again.
>
> Ed
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#10495): https://lists.fd.io/g/vpp-dev/message/10495
> Mute This Topic: https://lists.fd.io/mt/25646407/464962
> Group Owner: vpp-dev+ow...@lists.fd.io
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [hagb...@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10497): https://lists.fd.io/g/vpp-dev/message/10497
Mute This Topic: https://lists.fd.io/mt/25646407/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] DO NOT MERGE ANY PATCHES onto stable/1807

[Edward Warnicke]

I am in the process of doing the 18.07.1 release.  Will let you know when
it is done and stable/1807 can be merged to again.

Ed
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10495): https://lists.fd.io/g/vpp-dev/message/10495
Mute This Topic: https://lists.fd.io/mt/25646407/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP 18.07 RPM release packages available in Centos

[Edward Warnicke]

Woot!

Ed

On September 13, 2018 at 2:29:41 PM, Thomas F Herbert (therb...@redhat.com)
wrote:

Jerome,

18.07 release packages are in Centos mirrors.

To install Centos release packages of VPP on a Centos, install the Centos
NFV SIG yum repo and then install vpp as follows.

yum install centos-release-fdio
yum install vpp*

--Tom

On 05/23/2018 10:32 AM, Jerome Tollet (jtollet) wrote:

Hey Thomas,

Can you let us know what you are planning to do for next releases?

Are you manually building those RPMs or will you automatically include
bugfix versions as well as future versions (e.g. 18.07)?

Jerome



On 5/21/2018 12:24 PM, Thomas F Herbert wrote:

VPP 18.04 RPMs are available in the Centos mirrors by way of the Centos NFV
SIG.

>From an updated Centos:

To install VPP on a Centos host, intall the Centos NFV SIG yum repo and
then install vpp as follows.

yum install centos-release-fdio

yum install vpp*

--Tom

-- 
*Thomas F Herbert*
NFV and Fast Data Planes
Networking Group Office of the CTO
*Red Hat*



_._,_._,_
--

Links:

You receive all messages sent to this group.

View/Reply Online (#9338)  | Reply
To Sender

| Reply To Group

| Mute This Topic  | New Topic


Change Your Subscription 
Group Home 
Contact Group Owner 
Terms Of Service 
Unsubscribe From This Group 

_._,_._,_


-- 
*Thomas F Herbert*
NFV and Fast Data Planes
Networking Group Office of the CTO
*Red Hat*
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10492): https://lists.fd.io/g/vpp-dev/message/10492
Mute This Topic: https://lists.fd.io/mt/25646023/464962
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [hagb...@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10493): https://lists.fd.io/g/vpp-dev/message/10493
Mute This Topic: https://lists.fd.io/mt/25646023/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Cutting 18.07.1 release Thu Sept 13

[Edward Warnicke]

I would like to cut the vpp 18.07.1 dot release on Thu Sept 13.

We have three outstanding patches still against stable/1807:

1) nat: fix busy ports of each thread  -
which came in just this morning, and looks serious

2) Fix create memif socket  - minor issue
with memif cli usability, non-blocking, but nice to have

3) fix issue with missing sample_main in sample plugin
 - being rechecked to see if there is an
issue with the patch or if CI was hiccuping.

Is anyone aware of anything else for which the 18.07.1 release should be
held once #1 goes in?

I'm going to allow to COB PT Wed Sept 12 for folks to speak up, otherwise,
we'll cut on Thu.

Ed
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10468): https://lists.fd.io/g/vpp-dev/message/10468
Mute This Topic: https://lists.fd.io/mt/25512877/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] 18.07.1 dot release

[Edward Warnicke]

You can send the patch now to vpp/master … master is open for business :)
 18.07 is on the stable/1807 branch :)

Ed


On September 4, 2018 at 12:24:52 PM, Gonsalves, Avinash (Nokia -
IN/Bangalore) (avinash.gonsal...@nokia.com) wrote:

Done. Will send the patch for review after 18.07.1 is out.



-Avinash



*From:* Ed Warnicke 
*Sent:* Tuesday, September 04, 2018 10:52 PM
*To:* Damjan Marion via Lists.Fd.Io ;
dmar...@me.com; Gonsalves, Avinash (Nokia - IN/Bangalore) <
avinash.gonsal...@nokia.com>
*Cc:* vpp-dev@lists.fd.io
*Subject:* Re: [vpp-dev] 18.07.1 dot release



Second that… bug fixes in 18.07.1… new features on master for 18.10



Ed





On September 4, 2018 at 12:21:28 PM, Damjan Marion via Lists.Fd.Io (
dmarion=me@lists.fd.io) wrote:



Dear Avinash,



Dot releases are only for bug fixes, new features should not go there...



-- 
Damjan



On 4 Sep 2018, at 18:12, avinash.gonsal...@nokia.com wrote:



I would like to propose an enhancement for vpp to work with dpdk
multicore-crypto scheduler (
http://doc.dpdk.org/guides-18.02/cryptodevs/scheduler.html).

For the software crypto pmd to be scheduled on multiple cores the following
dpdk configuration is required:
vdev
crypto_scheduler,slave=aesni_mb_1,slave=aesni_mb_2,mode=multi-core,corelist=3-4,ordering=enable

This does not work directly with base VPP code, the following enhancements
are required

1. VPP Changes:

- Recognize slave-lcore corelist assigned for multi-core crypto and
pass the configuration during dpdk plugin device init(startup.conf)

- Start the multi-core crypto scheduler for the correct device_id.

2. DPDK Patch

- Enable RTE_LIBRTE_PMD_CRYPTO_SCHEDULER

- Enable PER_SLAVE_BUFF_SIZE to be configurable from start
parameters(slave_buff_size=8192)

- Ordering Fix for Multi Producer Queue

A patch was performance tested off VPP 17.10 (DPDK 17.08) release with
2,3,4 crypto cores.

If everyone thinks this merits going into 18.07.1, i'll initiate a review
(there have been a couple of posts on this already)

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10353): https://lists.fd.io/g/vpp-dev/message/10353
Mute This Topic: https://lists.fd.io/mt/25177447/675642
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [dmar...@me.com]
-=-=-=-=-=-=-=-=-=-=-=-



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10356): https://lists.fd.io/g/vpp-dev/message/10356
Mute This Topic: https://lists.fd.io/mt/25177447/464962
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [hagb...@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10359): https://lists.fd.io/g/vpp-dev/message/10359
Mute This Topic: https://lists.fd.io/mt/25177447/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] 18.07.1 dot release

[Edward Warnicke]

Second that… bug fixes in 18.07.1… new features on master for 18.10

Ed


On September 4, 2018 at 12:21:28 PM, Damjan Marion via Lists.Fd.Io (
dmarion=me@lists.fd.io) wrote:


Dear Avinash,

Dot releases are only for bug fixes, new features should not go there...

-- 
Damjan

On 4 Sep 2018, at 18:12, avinash.gonsal...@nokia.com wrote:

I would like to propose an enhancement for vpp to work with dpdk
multicore-crypto scheduler (
http://doc.dpdk.org/guides-18.02/cryptodevs/scheduler.html).

For the software crypto pmd to be scheduled on multiple cores the following
dpdk configuration is required:
vdev
crypto_scheduler,slave=aesni_mb_1,slave=aesni_mb_2,mode=multi-core,corelist=3-4,ordering=enable

This does not work directly with base VPP code, the following enhancements
are required

1. VPP Changes:

- Recognize slave-lcore corelist assigned for multi-core crypto and
pass the configuration during dpdk plugin device init(startup.conf)

- Start the multi-core crypto scheduler for the correct device_id.

2. DPDK Patch

- Enable RTE_LIBRTE_PMD_CRYPTO_SCHEDULER

- Enable PER_SLAVE_BUFF_SIZE to be configurable from start
parameters(slave_buff_size=8192)

- Ordering Fix for Multi Producer Queue

A patch was performance tested off VPP 17.10 (DPDK 17.08) release with
2,3,4 crypto cores.

If everyone thinks this merits going into 18.07.1, i'll initiate a review
(there have been a couple of posts on this already)
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10353): https://lists.fd.io/g/vpp-dev/message/10353
Mute This Topic: https://lists.fd.io/mt/25177447/675642
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [dmar...@me.com]
-=-=-=-=-=-=-=-=-=-=-=-


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10356): https://lists.fd.io/g/vpp-dev/message/10356
Mute This Topic: https://lists.fd.io/mt/25177447/464962
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [hagb...@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10357): https://lists.fd.io/g/vpp-dev/message/10357
Mute This Topic: https://lists.fd.io/mt/25177447/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] 18.07.1 dot release

[Edward Warnicke]

A number of fixes have been added to the stable/1807 branch since we cut
the 18.07 release.  Several of them merit a dot release.

I’d like to be able to do an 18.07.1 dot release this week or next, and
wanted to open the discussion here for folks who may have fixes they
would like to see in that release.

Ed
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10351): https://lists.fd.io/g/vpp-dev/message/10351
Mute This Topic: https://lists.fd.io/mt/25177447/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] VPP and mlx4 issue

[Edward Warnicke]

Brandon,
Looping in Amir from Mellanox who is trying to get to the bottom of these
kinds of issues.

Ed

On August 14, 2018 at 10:05:35 AM, Brandon Kopinski (bkopinsk...@gmail.com)
wrote:

Hi,

I have been trying to use VPP with the mlx4 pmd.  However, VPP is not
processing any packets.  My current setup includes two machines that are
directly connected.  One machine is running VPP with the mlx4 pmd.  The
other machine is using the Linux kernel for networking. I assigned an ip
address (10.0.1.1/24) to the VPP interface and brought the interface up. I
assigned (10.0.1.2/24) to the interface on the other machine and brought it
up. Pinging the VPP interface from the other machine is unsuccessful. Also,
the 'show int' command displays 'dpdk tx failure' after pinging from VPP.
I was able to verify with a debugger that the RX queues are being polled,
but there are no packets available to process.  I enabled tracing on the
dpdk input node, but no packets end up being traced.  I'm not sure if this
is just a configuration issue or some other problem.

Here is the VPP and DPDK versions I am currently using. Any help will be
greatly appreciated.

Version:  v18.10-rc0~43-g631de0d
Compiled by:  bkopinski
Compile host: localhost.localdomain
Compile date: Wed Aug  1 14:13:41 EDT 2018
Compile location: /home/bkopinski/sw/vpp
Compiler: GCC 4.8.5 20150623 (Red Hat 4.8.5-28)
Current PID:  7355

DPDK Version: DPDK 18.05.0
DPDK EAL init args:   -c 2 -n 4 --huge-dir /run/vpp/hugepages
--file-prefix vpp -w :09:00.0 --master-lcore 1 --socket-mem 1024


Sincerely,
Brandon Kopinski


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10146): https://lists.fd.io/g/vpp-dev/message/10146
Mute This Topic: https://lists.fd.io/mt/24525868/464962
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [hagb...@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10164): https://lists.fd.io/g/vpp-dev/message/10164
Mute This Topic: https://lists.fd.io/mt/24525868/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] :: vppctl fails to start in Container (Centos 7.5.1804)

[Edward Warnicke]

Tom,

Do you perhaps have more insight here?

Ed

On August 15, 2018 at 5:00:32 AM, omer.maj...@sofioni.com (
omer.maj...@sofioni.com) wrote:

Thanks Ed, in centos installing vpp automatically installs
vpp-selinux-policy with it. So enforcing selinux on the host machine make
vpp work.

However, when I try installing VPP in centos container there vpp doesn't
start. Can't enforce selinux in container and vpp-selinux-policy is
installed with vpp due to dependency. When I run vpp in the container

$docker exec  /usr/bin/vpp -c /etc/vpp/startup.conf

I get following errors

tls_openssl_init:650: failed to initialize TLS CA chain


dpdk_config: mount failed 1

Seems like an selinux issue or what? Could I get any help there? :)

Best Regards,

Omer


On 2018-08-13 22:43, Edward Warnicke wrote:

We do have an se linux package that should in principle let you keep
working with se linux enforce
try

yum install vpp-selinux-policy

and see if that helps :)

Ed

On August 13, 2018 at 12:41:37 PM, omer.maj...@sofioni.com (
omer.maj...@sofioni.com) wrote:



Thank Ed.

Changed SELINUX=enforcing in /etc/selinux/config

Restarted the machine, and it worked.

Best Regards,

Omer



On 2018-08-13 22:21, Edward Warnicke wrote:

This feels like SE Linux may be involved...

Ed



On August 13, 2018 at 12:17:09 PM, omer.maj...@sofioni.com (
omer.maj...@sofioni.com) wrote:



Hi,

I've built VPP on centos 7.5.1804, took the RPM packages to another machine
to deploy VPP there.

After installing RPM packages there when I run $vppctl it gives me
following error.

*clib_socket_init: connect (fd 3, '/run/vpp/cli.sock'): No such file or
directory*


I thought there might be something wrong with the build or something so
took packages from following repository

http://a.centos.org/centos/7.5.1804/nfv/x86_64/fdio/vpp/vpp-1804/

I get the same error when running vppctl after installation. Could someone
help with the error?

Best Regards,

Omer
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10126): https://lists.fd.io/g/vpp-dev/message/10126
Mute This Topic: https://lists.fd.io/mt/24505099/464962
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [hagb...@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10127): https://lists.fd.io/g/vpp-dev/message/10127
Mute This Topic: https://lists.fd.io/mt/24505099/984664
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [omer.maj...@sofioni.com]
-=-=-=-=-=-=-=-=-=-=-=-


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10129): https://lists.fd.io/g/vpp-dev/message/10129
Mute This Topic: https://lists.fd.io/mt/24505099/984664
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [omer.maj...@sofioni.com]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10161): https://lists.fd.io/g/vpp-dev/message/10161
Mute This Topic: https://lists.fd.io/mt/24532686/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] :: vppctl fails to start (Centos 7.5.1804)

[Edward Warnicke]

We do have an se linux package that should in principle let you keep
working with se linux enforce
try

yum install vpp-selinux-policy

and see if that helps :)

Ed

On August 13, 2018 at 12:41:37 PM, omer.maj...@sofioni.com (
omer.maj...@sofioni.com) wrote:

Thank Ed.

Changed SELINUX=enforcing in /etc/selinux/config

Restarted the machine, and it worked.

Best Regards,

Omer



On 2018-08-13 22:21, Edward Warnicke wrote:

This feels like SE Linux may be involved...

Ed



On August 13, 2018 at 12:17:09 PM, omer.maj...@sofioni.com (
omer.maj...@sofioni.com) wrote:



Hi,

I've built VPP on centos 7.5.1804, took the RPM packages to another machine
to deploy VPP there.

After installing RPM packages there when I run $vppctl it gives me
following error.

*clib_socket_init: connect (fd 3, '/run/vpp/cli.sock'): No such file or
directory*


I thought there might be something wrong with the build or something so
took packages from following repository

http://a.centos.org/centos/7.5.1804/nfv/x86_64/fdio/vpp/vpp-1804/

I get the same error when running vppctl after installation. Could someone
help with the error?

Best Regards,

Omer
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10126): https://lists.fd.io/g/vpp-dev/message/10126
Mute This Topic: https://lists.fd.io/mt/24505099/464962
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [hagb...@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10127): https://lists.fd.io/g/vpp-dev/message/10127
Mute This Topic: https://lists.fd.io/mt/24505099/984664
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [omer.maj...@sofioni.com]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10129): https://lists.fd.io/g/vpp-dev/message/10129
Mute This Topic: https://lists.fd.io/mt/24505099/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] :: vppctl fails to start (Centos 7.5.1804)

[Edward Warnicke]

This feels like SE Linux may be involved…

Ed


On August 13, 2018 at 12:17:09 PM, omer.maj...@sofioni.com (
omer.maj...@sofioni.com) wrote:

Hi,

I've built VPP on centos 7.5.1804, took the RPM packages to another machine
to deploy VPP there.

After installing RPM packages there when I run $vppctl it gives me
following error.

*clib_socket_init: connect (fd 3, '/run/vpp/cli.sock'): No such file or
directory*


I thought there might be something wrong with the build or something so
took packages from following repository

http://a.centos.org/centos/7.5.1804/nfv/x86_64/fdio/vpp/vpp-1804/

I get the same error when running vppctl after installation. Could someone
help with the error?

Best Regards,

Omer
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10126): https://lists.fd.io/g/vpp-dev/message/10126
Mute This Topic: https://lists.fd.io/mt/24505099/464962
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [hagb...@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10127): https://lists.fd.io/g/vpp-dev/message/10127
Mute This Topic: https://lists.fd.io/mt/24505099/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Traffic generator

[Edward Warnicke]

Have a look at: https://wiki.fd.io/view/Trex :)

Ed


On August 8, 2018 at 8:07:45 AM, Gulakh (holoogul...@gmail.com) wrote:

Hi,
I have setup a VPLS scenario in VPP and now I want to test its performance
to see whether it is able to handle customer traffics of 10G/s. i.e.
customer is generating 10 G/s traffic
I found a dpdk-based traffic generator here
 but I
couldn't run it.

*My Question* is that how can I generate 10G/s traffic by software??

Could you please help me with any link, tutorials and etc.

Thanks
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10064): https://lists.fd.io/g/vpp-dev/message/10064
Mute This Topic: https://lists.fd.io/mt/24229782/464962
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [hagb...@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10065): https://lists.fd.io/g/vpp-dev/message/10065
Mute This Topic: https://lists.fd.io/mt/24229782/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP Release 18.07 is out!

[Edward Warnicke]

VPP Release 18.07 is out.  Packages are in the usual places.

Ed
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#9978): https://lists.fd.io/g/vpp-dev/message/9978
Mute This Topic: https://lists.fd.io/mt/23900471/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] VPP 18.07 Release Milestone RC2 is complete!

[Edward Warnicke]

Folks,

I have created the v18.07-rc2 tag on stable/1807 I will be verifying that
18.07-rc2 build artifacts have been uploaded to nexus.fd.io.  VPP 18.07
Release Milestone RC2 is complete!

As a reminder, the VPP 18.07 Release next Monday Jul 30, 2018.

https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.07#Release_Milestones


It is important that only bugs which address critical issues (as determined
by the VPP committers), ideally limited to addressing bugs found by CSIT
testing.

Per the standard process, all bug fixes to stable branches should follow
the best practices:

   - All bug fixes must be double-committed to the release throttle as well
   as to the master branch
  - Commit first to the release throttle, then "git cherry-pick" into
  master
  - Manual merges may be required, depending on the degree of
  divergence between throttle and master
   - All bug fixes need to have a Jira ticket
  - Please put Jira IDs into the commit messages.
  - Please use the same Jira ID for both the stable branch and master.

Ed
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#9912): https://lists.fd.io/g/vpp-dev/message/9912
Mute This Topic: https://lists.fd.io/mt/23796480/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [EXTERNAL] Re: [vpp-dev] 18.07 RC1: stable/1807 branch pulled, master reopened

[Edward Warnicke]

Apologies, I miscalculated.   Will fix.

Ed


On July 18, 2018 at 7:29:23 AM, Luke, Chris (chris_l...@comcast.com) wrote:

I do not recall a discussion about this.



*From:* vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] *On Behalf Of *Damjan
Marion via Lists.Fd.Io
*Sent:* Wednesday, July 18, 2018 7:19 AM
*To:* Edward Warnicke 
*Cc:* vpp-dev@lists.fd.io
*Subject:* [EXTERNAL] Re: [vpp-dev] 18.07 RC1: stable/1807 branch pulled,
master reopened





I can see that we have 18.11-rc0 tag. Have we decided to break our 3-month
cadence?



-- 
Damjan



On 17 Jul 2018, at 04:27, Edward Warnicke  wrote:



We've reached 18.07 RC1.  The stable/1807 branch has been pulled.



Master is reopened.



Due to a maintenance window today, I have not been able to test merge
pushing of packages to apt/yum repos for stable/1807.  I will do so
tomorrow.



Ed

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#9851): https://lists.fd.io/g/vpp-dev/message/9851
Mute This Topic: https://lists.fd.io/mt/23538528/675642
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [dmar...@me.com]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#9875): https://lists.fd.io/g/vpp-dev/message/9875
Mute This Topic: https://lists.fd.io/mt/23670477/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] Ubuntu 18.04 LTS (Bionic Beaver) packages

[Edward Warnicke]

Michal,
I am delighted to know you are excited about vpp on Bionic :)  I am
currently working with the LF IT staff to fix the issues with the Bionic
repo, they are on the nexus side, not the VPP side.   Thank you for raising
the issue.  It helps :)

Ed


On July 17, 2018 at 6:47:46 AM, Michal Cmarada (michal.cmar...@pantheon.tech)
wrote:

Hi vpp-devs,



I was wondering if 18.07 release of VPP will also bring the support for
Ubuntu 18.04 LTS (Bionic Beaver). Right now I can see some folders in nexus
repository marked as bionic, but no packages are present.



Thanks



Michal
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#9857): https://lists.fd.io/g/vpp-dev/message/9857
Mute This Topic: https://lists.fd.io/mt/23540780/464962
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [hagb...@gmail.com]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#9859): https://lists.fd.io/g/vpp-dev/message/9859
Mute This Topic: https://lists.fd.io/mt/23540780/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] 18.07 RC1: stable/1807 branch pulled, master reopened

[Edward Warnicke]

We've reached 18.07 RC1.  The stable/1807 branch has been pulled.

Master is reopened.

Due to a maintenance window today, I have not been able to test merge
pushing of packages to apt/yum repos for stable/1807.  I will do so
tomorrow.

Ed
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#9851): https://lists.fd.io/g/vpp-dev/message/9851
Mute This Topic: https://lists.fd.io/mt/23538528/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [tsc] Seeking LFN Booth Demo Ideas for ONS Europe: FD.io

[Edward Warnicke]

FYI


On June 12, 2018 at 2:32:25 PM, Brandon Wick (bw...@linuxfoundation.org)
wrote:

Hello FD.io Community:

Those in attendance at OSN North America in Los Angeles last March will
recall that we hosted an *LF Networking Booth* that showcased 8
compelling, community-driven
demos from the LFN technical projects. See this blog post

 for a description of the ONS North America booth demos, their focus areas,
and how they fit together.

We wanted to reach out now to each of the LFN project communities to let
you know that there will be space for ~8 networking demos inside the LFN
booth again at ONS Europe

 (Sept 25-27, Amsterdam) and we are seeking demo ideas again using the same
process as last time. Our goal again is to show compelling uses of LFN
networking project technology to solve real world industry challenges.
Demos that show cross-project elements (e.g. between LFN projects and
others), that map to a specific industry use case, and that are endorsed by
a service provider are preferred. That said, we have some room for demos
that highlight the good work and value-add from projects that don't
necessarily meet these criteria. At least one demo slot will be made
available for each LFN project that submits a quality idea.

Another LFN Booth demo option we're exploring is to feature the PNDA project
  analyzing data from other open source projects (e.g.
FD.io). If we went this direction, it would require participation and
coordination with the PNDA team for demo development and execution. If you
have been working on PNDA integration and are interested in pursuing this
idea, please contact Nick Hall: nich...@cisco.com.

Demos stations will again have storage space, a counter, backdrop, monitor,
power, and Wi-Fi internet provided. A demo station mock up is now under
development and will be shared back with interested parties. There is no
cost to host a demo in the LFN booth although additional power, internet,
spaces, etc. may incur a cost.

Here are the key dates to keep in mind:

   - June 12: Demo idea solicitation email sent to community lists
   - July 9: Demo ideas submissions due
   - July 20: Demos ideas reviewed, chosen, and notifications sent

To submit your demo idea for consideration, please collect and provide the
following information:

   - Demo title (10 words max)
   - Brief demo description (200 words max)
   - List of demo manager(s) with contact information
   - List of open source projects involved
   - List of companies involved
   - Any extra requirements or special considerations

Demo manager responsibilities include:

   - Creating the demo concept and actual demo to be shown
   - Responding promptly to requests for information
   - Meeting all demo prep deadlines
   - Setting up and testing the demo pre-show and taking down post-show
   - Staffing the demo during ONS expo hours (along with other designated
   team members to help share the load)
   - Being willing to participate in media activities, e.g. photos, videos

ONS sponsor companies are of course welcome to host demos in their booths
on the show floor as well. Please heck with your ONS Europe sponsorship
managers to explore these opportunities.

* Submit your demo ideas by July 9 by sending an email
to bw...@linuxfoundation.org *. LFN staff
leadership (Heather, Phil, Arpit) will then review the submissions, get
back to submitters with questions, suggestions, and recommend a final demo
roster by July 20th. Send any questions you may have to
bw...@linuxfoundation.org.

We look forward to seeing your demo ideas.

Best,

Brandon Wick
Senior Integrated Marketing Manager
The Linux Foundation
bw...@linuxfoundation.org
+1.917.282.0960




-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#9591): https://lists.fd.io/g/vpp-dev/message/9591
Mute This Topic: https://lists.fd.io/mt/22037238/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] GTPu

[Edward Warnicke]

Please do push a patch :)

Ed

On June 8, 2018 at 4:16:19 AM, Kingwel Xie (kingwel@ericsson.com) wrote:

Hi all,



We are working on improving gtpu plugin, to make it better comply with 3GPP
standard.



Here is the brief of what we have done:



   1. Path management – gtpu-process was added
   2. Error indication
   3. Bi-direction TEID
   4. Some bug fixes



I’m thinking of pushing up-stream the improvement. We can make the patch
soon. Any comments?



Regards,

Kingwel


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#9569): https://lists.fd.io/g/vpp-dev/message/9569
Mute This Topic: https://lists.fd.io/mt/21792620/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Leave: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Volunteering for Release Manager Roll for 18.07

[Edward Warnicke]

Guys,

   I think its come around to be my turn to look after Release
Management details for VPP.  VPP committers, are you OK with me taking up
that mantle?  Is there someone else who wants to?

Also, I've been poking at the VPP 18.07 Release Plan and have a draft here:
https://wiki.fd.io/view/Projects/vpp/Release_Plans/Release_Plan_18.07

I'd like to discuss a bit here (and in next Tuesday's meeting) two things:

1)  The Dates I'm proposing (Release: 2018-07-30, RC2: 2018-07-23,
RC1: 2018-07-16, F0: 2018-07-09) - Note: these are closer together than
before in an attempt to hit an 1807 release while still leaving some time
for development.

2)  Release Deliverables.  I've captured things I've heard folks mention,
but it's likely I've both missed some things or captured some idle musing
that were never intended to be interpreted as 'planned'.

Ed

Re: [vpp-dev] containers interconnect via memif

[Edward Warnicke]

Sara,

A couple  question:

What are you wanting to connect via memif in your containers?  Is it a CNF
(Cloud-native Network Function... ie something meant to process packets) or
a traditional app (think webserver, databace, etc)?

Ed

On Thu, May 24, 2018 at 3:37 AM Sara Gittlin  wrote:

> Hello All,
> I've followed the example as per
> https://docs.fd.io/vpp/17.10/libmemif_doc.html .
> everything works fine.
> My  question is how to connect 2 containers where the container image is a
> common  image [not necessarily libmemif-sample-service] ?
> what to install ? how to create the memif interface ? connect ?
> in the vpp example - we create the interface in vpp and connect in the
> container daemon with the specific image 'conn' command.
> i understand that memif is a feature under VPP although VPP is not
> required  for containers interconect
>
> Thank you
> -Sara
> 
>

Re: [vpp-dev] git.fd.io not updating

[Edward Warnicke]

Could we get this to a helpdesk ticket to drive to close? :)

Ed

On Tue, May 22, 2018 at 9:08 AM Ed Kern  wrote:

> well it certainly has…we just need it to accept the new key.
>
> Ed
>
>
> On May 22, 2018, at 7:42 AM, Thomas F Herbert  wrote:
>
> I noticed this with an attempted git pull.
>
> The ECDSA host key for [gerrit.fd.io]:29418 has changed,
> Surrounded by nasty warnings.
>
> On 05/22/2018 02:58 AM, Marco Varlese wrote:
>
> Roughly a week ago, I noticed there was a DNS/IP change when cloning a new
> VPP repo... I wonder if what I saw is somehow connected to this issue.
>
> On Mon, 2018-05-21 at 16:34 -0700, Florin Coras wrote:
>
> Hi,
>
> It would seem that git.fd.io [1] thinks that we last committed a patch to
> vpp almost 1 week ago. Any idea what might’ve triggered this?
>
> Thanks,
> Florin
>
> [1] https://git.fd.io/vpp/log/
>
> --
>
> Marco V
>
> SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton
> HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg
> 
>
>
> --
> *Thomas F Herbert*
> NFV and Fast Data Planes
> Networking Group Office of the CTO
> *Red Hat*
>
>
> 
>

Re: [vpp-dev] question about the VCL

[Edward Warnicke]

Xyxue,

If you want to move raw IP/Ethernet around, I'd suggest looking at memif :)

Ed

On Mon, May 14, 2018 at 3:44 AM Florin Coras  wrote:

> Hi Xyxue,
>
> No, the stack does not support IPPROTO_RAW. Given that this is a user
> space stack and that you have access to things like memif, may I ask what
> use case you would need that for?
>
> Florin
>
>
> On May 14, 2018, at 12:58 AM, xyxue  wrote:
>
>
> Hi guys,
>
> Is the VCL support RAW_IP now ? Or is there a plan to support it?
>
> Thanks,
> Xyxue
>
>
> 
>

Re: [vpp-dev] VPP/AArch64 weekly meeting time

[Edward Warnicke]

A few observations:

1)  Meeting Fri means that any issues uncovered in the meeting will be
deferred to the following week
2)  I generally can't make that time slot (not that my ability to attend
should be the deciding factor).

Ed

On Thu, Apr 19, 2018 at 12:05 PM Tina Tsou  wrote:

> Dear all,
>
> Nitin suggested to move our current meeting time (California)
> Wednesday
> 6-7am AArch64 meeting
> 8-9am AArch64 meeting overflow
>
> To
> Friday
> 7:30-9:30am AArch64 meeting
>
> Agree?
>
>
> Thank you,
> Tina
>
> On Apr 18, 2018, at 10:08 AM, Saxena, Nitin 
> wrote:
>
> Hi Tina,
>
> I find Friday completely free. We can move our meetings to Friday 7:30 am
> to 9:30 am PST
>
> Regards,
> Nitin
>
> On 18-Apr-2018, at 22:13, Tina Tsou  wrote:
>
> https://wiki.fd.io/view/Meetings#Google_Calendar
>
> Shared via the Google app
> 
>
>
>
>
> Thank you,
> Tina
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
> 
>

[vpp-dev] [FD.io] CFP: FD.io minisummit @Kubecon EU May 2-4 in Copenhagen.

[Edward Warnicke]

Folks, let's get your talk proposals in :)

Ed

-- Forwarded message -
From: Trishan de Lanerolle 
Date: Wed, Apr 4, 2018 at 11:08 AM
Subject: [FD.io] CFP: FD.io minisummit @Kubecon EU May 2-4 in Copenhagen.
To: 


Call for Proposals Open until EoD tomorrow.

Join the FD.io community in Copenhagen, Denmark, for  a co-located FD.io
Mini summit at KubeCon+CloudNativeCon.  Hear and learn from FD.io and
industry experts who will be sharing information about the projects, use
cases, capabilities, integration between FD.io and
Kubernetes/ODL/OPNFV/other communities, tools and many more exciting
topics. This is a great opportunity for  KubeCon+CloudNativeCon attendees
to share their thought leadership and innovations at one of the industry’s
premier events.

TO SUBMIT A SPEAKING PROPOSAL:
*https://goo.gl/sPf7cu * .

*Submissions must be received by 11:59pm PST on Thursday, April 5th, 2018.*

Dates to Remember
CFP Open: Wednesday, March 14, 2018
CFP Close: Thursday, April 5, 2018, 11:59 PST
CFP Notifications: Week of April 9th
Mini-Summit Day: Co-located as a one day event at KubeCon, May 2-4th,
Copenhagen, Europe

[vpp-dev] FD.io minisummit @ Kubecon EU May 2-4 Copenhagen CFP opens

[Edward Warnicke]

FD.io will be holding a minisummit @Kubecon EU May 2-4 in Copenhagen.
Please submit your talks at the CFP here:

https://fd.io/event/fd-io-mini-summit-at-kubecon-cloudnativecon-europe/

Ed

Re: [vpp-dev] FD.io ARM virtual key signing Wed Mar 14 6am PST

[Edward Warnicke]

If you could reply to me privately with your:

(name, GPG fingerprint) that would greatly expedite the key signing today
at 6am PST.  Please note, I *will* have to verify your ID/fingerprint on
the call, but having it in front of my as a reference helps tremendously
expedite the process.

Ed

On Tue, Mar 13, 2018 at 11:23 AM Tina Tsou  wrote:

> Dear all,
>
> If you wish to access Arm hardware in the community lab for FD.io work,
> please join tomorrow’s meeting, with your keys, IDs, webcams ready, you
> will be signed virtual key.
>
> https://wiki.fd.io/view/VPP/AArch64
>
> https://zoom.us/j/5301185804
>
>
> More information how to get ready is below. Thanks Ed and Andy.
>
>
> Thank you,
> Tina
>
> Begin forwarded message:
>
> *From:* Ed Warnicke 
> *Date:* March 13, 2018 at 9:11:37 AM PDT
> *To:* Andrew Grimberg 
> *Cc:* Vanessa Valderrama , Tina Tsou <
> tina.t...@arm.com>,  Brian Brooks ,  Trishan de
> Lanerolle 
> *Subject:* *Re: FD.io  ARM virtual key signing Wed Mar 14
> 6am PST*
>
> Tina,
>
> Have you prepped the folks for tomorrows ARM call so they show up with
> their keys ready, ids at hand, and webcams blazing? :)
>
> Ed
>
> On Thu, Mar 8, 2018 at 6:27 PM Andrew Grimberg <
> agrimb...@linuxfoundation.org> wrote:
>
>> On 03/07/2018 03:24 PM, Ed Warnicke wrote:
>> > Andy,
>> > As we discussed on IM, we need to do a virtual keysigning for the
>> > ARM subcommunity at FD.io so they can get VPN access to the new ARM
>> > gear.  The current plan is to do that at 6am PST Wed Mar 14 on the
>> FD.io
>> > ARM community webconference:
>> >
>> > https://wiki.fd.io/view/VPP/AArch64#Meeting_Details
>> >
>> > Could you:
>> > a)  Provide a pointer to documentation of how to do so (how to prep etc)
>> > b)  If convenient, come to the keysigning... its just not a keysigning
>> > without you :)
>>
>> Ok, I may (or may not) be able to attend due to timing constraints on
>> me. Feel free to send this mail on to whomever needs it.
>>
>> First let me point everyone to an excellent series [0] our resident
>> security director has been writing on protecting code integrity using
>> PGP. He's (currently) up to 4 parts and it sounds like a 5th (and maybea
>> 6th?) is in the offing. Which, given where the series is coming from is
>> likely true. The source document is here [1] if you want to read ahead ;)
>>
>> That series basically goes over the intro to the PGP Web of Trust (WoT)
>> concepts and how to generate keys, move them to smart card devices (if
>> you so desire) and how to use them with git. For a more in depth look at
>> how the WoT actually functions see his much older article series (which
>> he sadly never finished for reasons) here [2].
>>
>> With that out of the way I will now assume people have keys and are
>> ready to do a keysigning :) normally we do these sort of things in
>> person and there's a major lead time component / pre-documentation step
>> that is needed. However, virtual signings tend to be a little
>> moreloose, I know this because we do one anytime we hire a new
>> member of our systems administration, release engineering, or helpdesk
>> teams here at The Linux Foundation. The basics for a virtual signing are
>> as follows:
>>
>> 1) Have your key ready ;)
>>
>> 2) Have your key published to a key server that is part of the overall
>> keyserver mesh. No, having a key on keybase isn't the best as it doesn't
>> participate in the mesh. Having your key there is just useful for other
>> things :D
>>
>> 3) Have a form of valid identification:
>>
>> a) Two forms of valid identification available (drivers license,
>> passport basically some method of getting to 100 points according to
>> this [3] Wikipedia article (yes that's information related to Australia
>> as they're the ones that came up with this very useful metric). I
>> normally use my current passport and drivers license.
>>
>> b) Alternative to 100 points documents. Have someone that people trust
>> vouch for you. The problem here is that everyone would have to agree
>> that said party vouching for you is a good form of trust ;)
>>
>> 4) Have a webcam for your virtual signing. You cannot participate if
>> people cannot see you. Yes, video feeds can be faked, but still, it's
>> required :P
>>
>> During your virtual signing
>> 5) Provide the short and/or full keygrip of your key into your video
>> conference chat channel (after all participants have joined)
>>
>> 6) Wait for everyone to retrieve the key(s) from the keyservers
>>
>> 7) For each person that is needing to have their key signed they will do
>> the following:
>>
>> a) State their full name (as on the key being signed)
>>
>> b) Provide to the camera their forms of identification that in some way
>> connect said name to said person and the key(s) in question. Give enough
>> time for participants to 

Re: [vpp-dev] [csit-dev] fd.io Community Goals and Objectives for reporting to the LFN board

[Edward Warnicke]

Ray,

Thanks for calling attention to this.  I've taken the feedback I've
received thus far and added it to:

https://docs.google.com/presentation/d/1jUoqWt9tbMaiUsLE2IaUSSbTcjKN6c3cQ-PXID5nz0k/edit?usp=sharing

It's a rough cut, let's work it together as a community overnight and at
the TSC meeting tomorrow.  Feel free to edit to improve.

Ed

On Thu, Mar 1, 2018 at 8:51 AM Ray Kinsella  wrote:

> Hi folks,
>
> So the LFN TAC is looking to close on the “Community goals and priorities”
> rollup by 9th March.
> This exercise is part of the process of obtaining a fair share of
> resources for FD.io in 2018.
>
> So if you haven’t already, please canvass your committers and contributors
> for their 2018 project plans.
> What new features do they anticipate developing? Are there plans for
> validation, new platform or hardware support etc ?
> You can either reply to this email directly, or send a note to myself or
> Ed W.
>
> Much appreciated, thanks,
>
> Ray K
>
> From: csit-dev-boun...@lists.fd.io [mailto:csit-dev-boun...@lists.fd.io]
> On Behalf Of Ed Warnicke
> Sent: Thursday 1 February 2018 16:43
> To: t...@lists.fd.io; disc...@lists.fd.io; vpp-dev ;
> csit-...@lists.fd.io; cicn-...@lists.fd.io; tldk-...@lists.fd.io;
> dmm-...@lists.fd.io; odp4vpp-...@lists.fd.io; pma_tools-...@lists.fd.io
> Subject: [csit-dev] fd.io Community Goals and Objectives for reporting to
> the LFN board
>
> FD.io has recently transitioned from being its own independent foundation,
> to being one of several projects (ONAP, OpNFV, ODL, etc) under the Linux
> Foundation Networking (LFN) umbrella.
>
> As part of this transition, the LFN board has asked to be educated about
> what Goals and Objectives the community intends to undertake in the next
> year.   Since an Open Source community intrinsically is a harmonious
> collection of folks working on different things, the only way to
> ascertain what its is really planning to do is to *ask* what folks are
> planning to do.
>
> What are the plans of various folks participating in the community for
> 2018?  What are the themes of the problems you are planning to address, the
> kinds of features you are looking to implement etc?
>
> Ed
>
> 
>
>

Re: [vpp-dev] Error when trying to add interface to vpp on ARM server.

[Edward Warnicke]

Looping in JohnD, who may be able to help... :)

Ed

On Thu, Feb 1, 2018 at 7:43 AM adarsh m via vpp-dev 
wrote:

> Hi,
>
> After removing socket-mem now vpp is stable but when we try to connect
> through CLI connection is refused.
>
>
> ubuntu@vasily:~$ sudo service vpp status
> ● vpp.service - vector packet processing engine
>Loaded: loaded (/lib/systemd/system/vpp.service; enabled; vendor
> preset: enabled)
>Active: active (running) since Thu 2018-02-01 21:42:23 CST; 1s ago
>   Process: 49787 ExecStopPost=/bin/rm -f /dev/shm/db /dev/shm/global_vm
> /dev/shm/vpe-api (code=exited, status=0/SUCCESS)
>   Process: 49793 ExecStartPre=/sbin/modprobe uio_pci_generic (code=exited,
> status=0/SUCCESS)
>   Process: 49790 ExecStartPre=/bin/rm -f /dev/shm/db /dev/shm/global_vm
> /dev/shm/vpe-api (code=exited, status=0/SUCCESS)
>  Main PID: 49796 (vpp)
>CGroup: /system.slice/vpp.service
>└─49796 /usr/bin/vpp -c /etc/vpp/startup.conf
>
> Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded
> plugin: /usr/lib/vpp_api_test_plugins/acl_test_plugin.so
> Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded
> plugin: /usr/lib/vpp_api_test_plugins/kubeproxy_test_plugin.so
> Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded
> plugin: /usr/lib/vpp_api_test_plugins/pppoe_test_plugin.so
> Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded
> plugin: /usr/lib/vpp_api_test_plugins/ioam_vxlan_gpe_test_plugin.so
> Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded
> plugin: /usr/lib/vpp_api_test_plugins/dpdk_test_plugin.so
> Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: load_one_plugin:63: Loaded
> plugin: /usr/lib/vpp_api_test_plugins/udp_ping_test_plugin.so
> Feb 01 19:37:16 vasily vpp[43454]: /usr/bin/vpp[43454]: dpdk_config:1240:
> EAL init args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w
> 0002:f9:00.0 --master-lcore 0 --socket-mem 1024,
> Feb 01 19:37:16 vasily /usr/bin/vpp[43454]: dpdk_config:1240: EAL init
> args: -c 1 -n 4 --huge-dir /run/vpp/hugepages --file-prefix vpp -w
> 0002:f9:00.0 --master-lcore 0 --socket-mem 1024,0,0,0
> Feb 01 19:37:16 vasily vpp[43454]: EAL: VFIO support initialized
> Feb 01 19:37:16 vasily vnet[43454]: EAL: VFIO support initialized
>
>
> *ubuntu@vasily:~$ sudo vppctl show intclib_socket_init: connect (fd 3,
> '/run/vpp/cli.sock'): Connection refusedubuntu@vasily:~$ *
>
>
> *Startup.conf :*
> unix {
>   nodaemon
>   log /tmp/vpp.log
>   full-coredump
>   cli-listen /run/vpp/cli.sock
>   gid vpp
> }
>
> api-trace {
> ## This stanza controls binary API tracing. Unless there is a very strong
> reason,
> ## please leave this feature enabled.
>   on
> ## Additional parameters:
> ##
> ## To set the number of binary API trace records in the circular buffer,
> configure nitems
> ##
> ## nitems 
> ##
> ## To save the api message table decode tables, configure a filename.
> Results in /tmp/
> ## Very handy for understanding api message changes between versions,
> identifying missing
> ## plugins, and so forth.
> ##
> ## save-api-table 
> }
>
> api-segment {
>   gid vpp
> }
>
> cpu {
> ## In the VPP there is one main thread and optionally the user can
> create worker(s)
> ## The main thread and worker thread(s) can be pinned to CPU core(s)
> manually or automatically
>
> ## Manual pinning of thread(s) to CPU core(s)
>
> ## Set logical CPU core where main thread runs
> # main-core 1
>
> ## Set logical CPU core(s) where worker threads are running
> # corelist-workers 2-3,18-19
>
> ## Automatic pinning of thread(s) to CPU core(s)
>
> ## Sets number of CPU core(s) to be skipped (1 ... N-1)
> ## Skipped CPU core(s) are not used for pinning main thread and
> working thread(s).
> ## The main thread is automatically pinned to the first available CPU
> core and worker(s)
> ## are pinned to next free CPU core(s) after core assigned to main
> thread
> # skip-cores 4
>
> ## Specify a number of workers to be created
> ## Workers are pinned to N consecutive CPU cores while skipping
> "skip-cores" CPU core(s)
> ## and main thread's CPU core
> # workers 2
>
> ## Set scheduling policy and priority of main and worker threads
>
> ## Scheduling policy options are: other (SCHED_OTHER), batch
> (SCHED_BATCH)
> ## idle (SCHED_IDLE), fifo (SCHED_FIFO), rr (SCHED_RR)
> # scheduler-policy fifo
>
> ## Scheduling priority is used only for "real-time policies (fifo and
> rr),
> ## and has to be in the range of priorities supported for a particular
> policy
> # scheduler-priority 50
> }
>
>
>
> * dpdk {  dev 0002:f9:00.0*
> ## Change default settings for all intefaces
> # dev default {
> ## Number of receive queues, enables RSS
> ## Default is 1
> # num-rx-queues 3
>
> ## Number of transmit queues, Default is equal
> ## to 

Re: [vpp-dev] Congrats to Marco Varlese on his election as a vpp project committer

[Edward Warnicke]

Woot!

Ed

On Thu, Feb 8, 2018 at 8:57 AM Dave Wallace  wrote:

> Congrats Marco!
> -daw-
>
> On 2/8/2018 11:23 AM, Dave Barach (dbarach) wrote:
>
> It gives me great pleasure to announce Marco’s election as a vpp project
> committer, confirmed a few minutes ago by the fd.io vpp TSC.
>
>
>
> Vanessa V. will take care of [+2 button] mechanics shortly.
>
>
>
> Thanks much to Marco for his interest in the vpp project!
>
>
>
> Dave
>
>
> ___
> vpp-dev mailing 
> listvpp-...@lists.fd.iohttps://lists.fd.io/mailman/listinfo/vpp-dev
>
>
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Tagging for vpp 17.01-rc0

[Edward Warnicke]

I've pushed the tag to our current HEAD on master (so as not to rewrite
history).

Local testing behaves as expected, and I've got a probe patch to be extra
special certain :)
A simple probe patch worked as expected:

https://gerrit.fd.io/r/#/c/3053/

I think we are good :)

Ed

On Thu, Nov 3, 2016 at 12:04 PM, Florin Coras <fcoras.li...@gmail.com>
wrote:

> +1
>
> Florin
>
> On Nov 3, 2016, at 11:51 AM, Dave Barach (dbarach) <dbar...@cisco.com>
> wrote:
>
> +1, hoping for no surprises... (;-)...
>
> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io
> <vpp-dev-boun...@lists.fd.io>] *On Behalf Of *Luke, Chris
> *Sent:* Thursday, November 3, 2016 1:29 PM
> *To:* Edward Warnicke <hagb...@gmail.com>; vpp-dev <vpp-dev@lists.fd.io>
> *Subject:* Re: [vpp-dev] Tagging for vpp 17.01-rc0
>
> +1
>
> Makes sense to me. Gotta do it sometime and it’s just a label.
>
> Chris
>
> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io
> <vpp-dev-boun...@lists.fd.io>] *On Behalf Of *Edward Warnicke
> *Sent:* Thursday, November 03, 2016 1:07 PM
> *To:* vpp-dev <vpp-dev@lists.fd.io>
> *Subject:* [vpp-dev] Tagging for vpp 17.01-rc0
>
> At the time we laid the current tag for master, we thought we were doing a
> 16.12 release, so the
> tag was laid as:
>
> v16.12-rc0
>
> The result is that all of our merge by merge patches for master are being
> built as 16.12-rc0 packages.
>
> I would like to tag with
>
> v17.01-rc0
>
> to correct that.  Any objections?
>
> Ed
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
>
>
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [csit-dev] vhost multi-queue patch - verify job failing

[Edward Warnicke]

Thank you for this, it should be incredibly useful :)

Ed

On Fri, Oct 28, 2016 at 8:16 AM, Pierre Pfister (ppfister) <
ppfis...@cisco.com> wrote:

> Nailed it.
>
> The bug was only happening in setups with single working thread, which was
> not the case in my test setup.
> Test succeeded. The patch is ready to be merged.
>
> I am going to create a new vpp-sandbox directory called vhost-test.
> This sandbox effort intends to provide reference scripts for testing VPP
> vhost user, in the most user-friendly fashion (hopefully).
> Goal being to give pointers to people willing to test vhost user, but also
> to give reference parameters and configuration for people willing to use it.
>
> Thanks everyone,
>
> - Pierre
>
> Le 28 oct. 2016 à 10:55, Pierre Pfister (ppfister) <ppfis...@cisco.com> a
> écrit :
>
> So I tested in my setup with qemu from git with tags: v2.5.0-rc0
> v2.5.0-rc1 v2.5.0 v2.5.1
> They all work.
>
> Could you please have a look at the patch and give me some more logs ?
> VPP with VHOST_USER_DEBUG_SOCKET set to 1 usually helps a lot, as it logs
> all vhost messages received by VPP.
>
> Thanks,
>
> - Pierre
>
>
> Le 26 oct. 2016 à 23:45, Maciek Konstantynowicz (mkonstan) <
> mkons...@cisco.com> a écrit :
>
> Excellent, thanks Ed! And let’s see …
>
> -Maciek
>
> On 26 Oct 2016, at 22:40, Edward Warnicke <hagb...@gmail.com> wrote:
>
> Maciek,
>
> Looks like the patch was based at a point in the past that was pointing to
> the old CSIT branch.
>
> I rebased the patch, so hopefully it will now pick up the correct CSIT
> branch.
>
> Ed
>
> On Wed, Oct 26, 2016 at 2:15 PM, Maciek Konstantynowicz (mkonstan) <
> mkons...@cisco.com> wrote:
>
>> //reduced list, updated subject
>>
>> Peter is right: https://gerrit.fd.io/r/#/c/2922/16
>>
>> looking at the last failed job - https://jenkins.fd.io/job/vp
>> p-csit-verify-virl-master/1940/consoleFull - it's using old csit branch
>> - "CSIT_BRANCH=oper-161017", without ubuntu1604, so pointless. you should
>> rebase to pick up this commit https://gerrit.fd.io/r/#/c/3553/ that's
>> updating to latest csit branch oper-161024.
>>
>> -Maciek
>>
>> On 26 Oct 2016, at 10:06, Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES
>> at Cisco) <pmi...@cisco.com> wrote:
>>
>> Looks like it is still testing with oper-161017 not oper-161024.
>>
>> + CSIT_BRANCH=oper-161017
>> + git clone https://gerrit.fd.io/r/csit --branch oper-161017
>>
>> Can you please use the latest one (code rebase)?
>>
>> Thanks.
>>
>> *Peter Mikus*
>> Engineer – Software
>> *Cisco Systems Limited*
>>
>> Planned absence: 28.10., 1.11., 17.11., 9.12., 19.-31.12.
>>
>> *From:* Pierre Pfister (ppfister)
>> *Sent:* Wednesday, October 26, 2016 10:52 AM
>> *To:* Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) <
>> pmi...@cisco.com>
>> *Cc:* Andrew Theurer <atheu...@redhat.com>; Douglas Shakshober <
>> dsh...@redhat.com>; Damjan Marion (damarion) <damar...@cisco.com>; Bill
>> Michalowski <bmich...@redhat.com>; vpp-dev <vpp-dev@lists.fd.io>; Rashid
>> Khan <rk...@redhat.com>; kris...@redhat.com; csit-...@lists.fd.io;
>> Edward Warnicke <hagb...@gmail.com>; Thomas F Herbert <
>> therb...@redhat.com>
>> *Subject:* Re: [vpp-dev] updated ovs vs. vpp results for 0.002% and 0%
>> loss
>>
>> The recheck failed.
>> https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1937/console
>>
>> Are you sure you updated qemu ?
>>
>> Thanks,
>>
>> - Pierre
>>
>>
>>
>>
>> ___
>> csit-dev mailing list
>> csit-...@lists.fd.io
>> https://lists.fd.io/mailman/listinfo/csit-dev
>>
>
>
>
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
>
>
>
> ___
> csit-dev mailing list
> csit-...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/csit-dev
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [csit-dev] vhost multi-queue patch - verify job failing

[Edward Warnicke]

Still failing, but apparently now using the correct CSIT branch:

https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1949/consoleFull

"*14:55:18* + git clone https://gerrit.fd.io/r/csit --branch oper-161024"

On Wed, Oct 26, 2016 at 2:45 PM, Maciek Konstantynowicz (mkonstan) <
mkons...@cisco.com> wrote:

> Excellent, thanks Ed! And let’s see …
>
> -Maciek
>
> On 26 Oct 2016, at 22:40, Edward Warnicke <hagb...@gmail.com> wrote:
>
> Maciek,
>
> Looks like the patch was based at a point in the past that was pointing to
> the old CSIT branch.
>
> I rebased the patch, so hopefully it will now pick up the correct CSIT
> branch.
>
> Ed
>
> On Wed, Oct 26, 2016 at 2:15 PM, Maciek Konstantynowicz (mkonstan) <
> mkons...@cisco.com> wrote:
>
>> //reduced list, updated subject
>>
>> Peter is right: https://gerrit.fd.io/r/#/c/2922/16
>>
>> looking at the last failed job - https://jenkins.fd.io/job/vp
>> p-csit-verify-virl-master/1940/consoleFull - it's using old csit branch
>> - "CSIT_BRANCH=oper-161017", without ubuntu1604, so pointless. you should
>> rebase to pick up this commit https://gerrit.fd.io/r/#/c/3553/ that's
>> updating to latest csit branch oper-161024.
>>
>> -Maciek
>>
>> On 26 Oct 2016, at 10:06, Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES
>> at Cisco) <pmi...@cisco.com> wrote:
>>
>> Looks like it is still testing with oper-161017 not oper-161024.
>>
>> + CSIT_BRANCH=oper-161017
>> + git clone https://gerrit.fd.io/r/csit --branch oper-161017
>>
>> Can you please use the latest one (code rebase)?
>>
>> Thanks.
>>
>> *Peter Mikus*
>> Engineer – Software
>> *Cisco Systems Limited*
>>
>> Planned absence: 28.10., 1.11., 17.11., 9.12., 19.-31.12.
>>
>> *From:* Pierre Pfister (ppfister)
>> *Sent:* Wednesday, October 26, 2016 10:52 AM
>> *To:* Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) <
>> pmi...@cisco.com>
>> *Cc:* Andrew Theurer <atheu...@redhat.com>; Douglas Shakshober <
>> dsh...@redhat.com>; Damjan Marion (damarion) <damar...@cisco.com>; Bill
>> Michalowski <bmich...@redhat.com>; vpp-dev <vpp-dev@lists.fd.io>; Rashid
>> Khan <rk...@redhat.com>; kris...@redhat.com; csit-...@lists.fd.io;
>> Edward Warnicke <hagb...@gmail.com>; Thomas F Herbert <
>> therb...@redhat.com>
>> *Subject:* Re: [vpp-dev] updated ovs vs. vpp results for 0.002% and 0%
>> loss
>>
>> The recheck failed.
>> https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1937/console
>>
>> Are you sure you updated qemu ?
>>
>> Thanks,
>>
>> - Pierre
>>
>>
>>
>>
>> ___
>> csit-dev mailing list
>> csit-...@lists.fd.io
>> https://lists.fd.io/mailman/listinfo/csit-dev
>>
>
>
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [csit-dev] vhost multi-queue patch - verify job failing

[Edward Warnicke]

Maciek,

Looks like the patch was based at a point in the past that was pointing to
the old CSIT branch.

I rebased the patch, so hopefully it will now pick up the correct CSIT
branch.

Ed

On Wed, Oct 26, 2016 at 2:15 PM, Maciek Konstantynowicz (mkonstan) <
mkons...@cisco.com> wrote:

> //reduced list, updated subject
>
> Peter is right: https://gerrit.fd.io/r/#/c/2922/16
>
> looking at the last failed job - https://jenkins.fd.io/job/
> vpp-csit-verify-virl-master/1940/consoleFull - it's using old csit branch
> - "CSIT_BRANCH=oper-161017", without ubuntu1604, so pointless. you should
> rebase to pick up this commit https://gerrit.fd.io/r/#/c/3553/ that's
> updating to latest csit branch oper-161024.
>
> -Maciek
>
> On 26 Oct 2016, at 10:06, Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES
> at Cisco) <pmi...@cisco.com> wrote:
>
> Looks like it is still testing with oper-161017 not oper-161024.
>
> + CSIT_BRANCH=oper-161017
> + git clone https://gerrit.fd.io/r/csit --branch oper-161017
>
> Can you please use the latest one (code rebase)?
>
> Thanks.
>
> *Peter Mikus*
> Engineer – Software
> *Cisco Systems Limited*
>
> Planned absence: 28.10., 1.11., 17.11., 9.12., 19.-31.12.
>
> *From:* Pierre Pfister (ppfister)
> *Sent:* Wednesday, October 26, 2016 10:52 AM
> *To:* Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco) <
> pmi...@cisco.com>
> *Cc:* Andrew Theurer <atheu...@redhat.com>; Douglas Shakshober <
> dsh...@redhat.com>; Damjan Marion (damarion) <damar...@cisco.com>; Bill
> Michalowski <bmich...@redhat.com>; vpp-dev <vpp-dev@lists.fd.io>; Rashid
> Khan <rk...@redhat.com>; kris...@redhat.com; csit-...@lists.fd.io; Edward
> Warnicke <hagb...@gmail.com>; Thomas F Herbert <therb...@redhat.com>
> *Subject:* Re: [vpp-dev] updated ovs vs. vpp results for 0.002% and 0%
> loss
>
> The recheck failed.
> https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1937/console
>
> Are you sure you updated qemu ?
>
> Thanks,
>
> - Pierre
>
>
>
>
> ___
> csit-dev mailing list
> csit-...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/csit-dev
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [csit-dev] DO_NOT_MERGE

[Edward Warnicke]

OK... as a matter of personal opinion, I still favor simply making Drafts
public... that said, I do hear the sentiment in other directions, and the
useful pointer from Damjan about 'Change Owner'.

So... I've opened a gerrit:

https://gerrit.fd.io/r/#/c/3517/

Which would allow Change Owner (ie, the person who submitted the patch) to
-2 their own patch (not random other patches).
-2 should still be persistent, and should still block merge.

I think the sanest way forward here would be for the fd.io committers to
weigh in with code review +1 or -1 depending on their opinions
on that gerrit.

Ed

On Wed, Oct 19, 2016 at 7:51 AM, Dave Wallace <dwallac...@gmail.com> wrote:

> +1
>
>
> On 10/19/16 8:11 AM, Damjan Marion (damarion) wrote:
>
>
> I think simply allowing “Change Owner” to do -2 on his own change should
> address all issues here as only person who put -2 can remove it.
>
> (you remember that i had to ping you to remove -2 on one change as I was
> not able to merge it…)
>
> On 18 Oct 2016, at 20:32, Keith Burns <alaga...@gmail.com> wrote:
>
> But if the contributor -1 it then I'm ok putting -2 on it as a lock if I'm
> a committer on that project.
>
> You can make drafts public but all that will do is force folks who like
> that feature (private draft) to go to github where we don't get our
> CSIT/verify jobs.
>
> (Drafts are an easy way to check for CSIT compliance before publish. Just
> add JJB as reviewer)
>
> On Tue, Oct 18, 2016, 11:24 AM Edward Warnicke <hagb...@gmail.com> wrote:
>
>> I'm fine with -2, except for the problem that a contributor who is not a
>> committer cannot -2 their patch (only committers have -2 or +2).
>>
>> Ed
>>
>> On Tue, Oct 18, 2016 at 11:11 AM, Maciek Konstantynowicz (mkonstan) <
>> mkons...@cisco.com> wrote:
>>
>> +csit-dev
>>
>> And I asked for this merge :(
>> Agree that -2 is best way forward. Will ask csit-dev folks to follow this
>> practice too from now onwards.
>>
>> -Maciek
>>
>> > On 18 Oct 2016, at 18:51, Damjan Marion (damarion) <damar...@cisco.com>
>> wrote:
>> >
>> >
>> > Hey Dave,
>> >
>> > It can happen to anybody. I’m the first one who will do the same.
>> >
>> > That’s why I’m suggesting that we stop that practice. “-2” is hard lock
>> which will prevent merging it in until reviewer revokes it.
>> >
>> > D.
>> >
>> >> On 18 Oct 2016, at 19:29, Dave Wallace <dwallac...@gmail.com> wrote:
>> >>
>> >> Damjan,
>> >>
>> >> My bad -- sorry 'bout that. Not my best day at multi-tasking :-(
>> >>
>> >> For those patches like the csit operational testing patch that I just
>> merged, I prefer -2 so everyone can see the status of tests and help out if
>> possible.
>> >>
>> >> I agree with Ed, that transparency is very important for community
>> development.
>> >>
>> >> Thanks,
>> >> -daw-
>> >>
>> >> On 10/18/16 1:13 PM, Damjan Marion (damarion) wrote:
>> >>> Folks,
>> >>>
>> >>> We just got 1st DO_NOT_MERGE patch merged in.
>> >>>
>> >>> Can we going forward stop this practice, and use “-2” or Drafts
>> instead?
>> >>>
>> >>> Thanks,
>> >>>
>> >>> Damjan
>> >>>
>> >>>
>> >>> ___
>> >>> vpp-dev mailing list
>> >>> vpp-dev@lists.fd.io
>> >>> https://lists.fd.io/mailman/listinfo/vpp-dev
>> >>
>> >> ___
>> >> vpp-dev mailing list
>> >> vpp-dev@lists.fd.io
>> >> https://lists.fd.io/mailman/listinfo/vpp-dev
>> >
>> > ___
>> > vpp-dev mailing list
>> > vpp-dev@lists.fd.io
>> > https://lists.fd.io/mailman/listinfo/vpp-dev
>>
>> ___
>>
>> csit-dev mailing list
>> csit-...@lists.fd.io
>> https://lists.fd.io/mailman/listinfo/csit-dev
>>
>>
>> ___
>> vpp-dev mailing list
>> vpp-dev@lists.fd.io
>> https://lists.fd.io/mailman/listinfo/vpp-dev
>
> ___
> csit-dev mailing list
> csit-...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/csit-dev
>
>
>
>
> ___
> vpp-dev mailing 
> listvpp-...@lists.fd.iohttps://lists.fd.io/mailman/listinfo/vpp-dev
>
>
>
> ___
> csit-dev mailing list
> csit-...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/csit-dev
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [csit-dev] vpp-csit-verify-virl-master - some more build failures

[Edward Warnicke]

You mean like this:
https://gerrit.fd.io/r/#/c/3511/1/vpp-api/java/Makefile.am :)

Ed

On Thu, Oct 20, 2016 at 9:50 AM, Dave Wallace <dwallac...@gmail.com> wrote:

> Klement,
>
> Thanks for helping improve the java build infrastructure.
>
> I think that you may find that the execution of the build system is very
> different on the LF cloud infrastructure then on a typical development
> platform.  IIRC, this is not the first time we've been bitten by that
> particular bug.
>
> Here is Marek's patch which fixed this issue earlier:
> https://gerrit.fd.io/r/#/c/3131
>
> Looking at your patch, I think this deletion may be the primary culprit in
> opening up the race condition:
>
> -EXTRA_libjvpp_registry_la_DEPENDENCIES=libjvpp_common.la
>
> I think it would be worth pushing a patch with that dependency restored
> before reverting the entire patch.
>
> Thanks,
> -daw-
>
>
> On 10/20/2016 12:24 PM, Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES
> at Cisco) wrote:
>
> It's quite possible, I've made multiple builds and rebuilds to make sure I
> didn't break anything, but I apparently did. Feel free to revert the patch
> and I'll take a look at it again. That java build stuff is a real mess...
>
> Klement
>
> On Oct 20, 2016 6:22 PM, Edward Warnicke <hagb...@gmail.com>
> <hagb...@gmail.com> wrote:
>
> This change:
>
> https://gerrit.fd.io/r/#/c/3486/
>
> Was touching that part of the world... *if* it is a race condition, is it
> possible that this patch got lucky, and the ones that followed did not?
>
> Ed
>
> On Thu, Oct 20, 2016 at 9:15 AM, Dave Wallace <dwallac...@gmail.com>
> wrote:
>
> Maciek,
>
> This looks like a race condition in the build for JVPP.  All of the
> failures contain the following error:
>
> 09:32:35 make[5]: Entering directory '/w/workspace/vpp-verify-maste
> r-ubuntu1604/build-root/build-vpp-native/vpp-api/java'
> 09:32:35   CC   jvpp-common/libjvpp_common_la-jvpp_common.lo
> 09:32:35   CC   jvpp-core/libjvpp_core_la-jvpp_core.lo
> 09:32:35   CC   jvpp-registry/libjvpp_registry_la-jvpp_registry.lo
> 09:32:39   CCLD libjvpp_common.la
> 09:32:39   CCLD libjvpp_registry.la
> 09:32:40 ar: `u' modifier ignored since `D' is the default (see `U')
> 09:32:40 /usr/bin/ld: cannot find -ljvpp_common
> 09:32:40 collect2: error: ld returned 1 exit status
> 09:32:40 Makefile:551: recipe for target 'libjvpp_registry.la' failed
>
> It appears that the output of "CCLD libjvpp_common.la" is an input to
> "CCLD libjvpp_registry.la" and in the error case it is not found.
>
> I had thought that Maros or Marek had provided a fix for this issue a
> couple of weeks ago.  When I get the chance investigate further.
>
> Thanks,
> -daw-
>
>
> On 10/20/2016 10:31 AM, Maciek Konstantynowicz (mkonstan) wrote:
>
> Hi,
>
> Anybody with time and willingness to look at below jobs and see why they
> pass 1st time and fail 2nd time,
> ie not repeatable..
>
> All running on the new ubuntu1604 VMs in VIRL. Related to two vpp patches:
>
> https://gerrit.fd.io/r/#/c/3499/
> https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1838/ : SUCCESS
> https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/ : FAILURE
>
> Seem to be vpp build related, as the standalone ubuntu1604 build jobs for
> this patch are also yielding not repeatable results:
> https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1833/ : FAILURE
> https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1836/ : SUCCESS
>
>
> -Maciek
>
> from https://jenkins.fd.io/job/vpp-csit-verify-virl-master/
> 1841/consoleFull
> 10:52:23 make[1]: Entering directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/deb'
> 10:52:23 dh clean --with dkms --with systemd
> 10:52:24 dh: error: cannot read debian/changelog: No such file or directory
> 10:52:24 debian/rules:21: recipe for target 'clean' failed
> 10:52:24 make[1]: *** [clean] Error 2
> 10:52:24 make[1]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/deb'
> 10:52:24 Makefile:1159: recipe for target 'distclean' failed
> 10:52:24 make: *** [distclean] Error 2
>
> 10:59:49 collect2: error: ld returned 1 exit status
> 10:59:49 Makefile:551: recipe for target 'libjvpp_registry.la' failed
> 10:59:49 make[5]: *** [libjvpp_registry.la] Error 1
> 10:59:49 make[5]: *** Waiting for unfinished jobs
> 11:00:00 make[5]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/build-vpp-native/vpp-api/java'
> 11:00:00 Makefile:445: recipe for target 'all' failed
> 11:00:00 make[4]: *** [all] Error 2
> 11:00:00 make[4]: Leaving directory '/w/workspace/vpp-csit-v

Re: [vpp-dev] [csit-dev] vpp-csit-verify-virl-master - some more build failures

[Edward Warnicke]

This change:

https://gerrit.fd.io/r/#/c/3486/

Was touching that part of the world... *if* it is a race condition, is it
possible that this patch got lucky, and the ones that followed did not?

Ed

On Thu, Oct 20, 2016 at 9:15 AM, Dave Wallace  wrote:

> Maciek,
>
> This looks like a race condition in the build for JVPP.  All of the
> failures contain the following error:
>
> 09:32:35 make[5]: Entering directory '/w/workspace/vpp-verify-
> master-ubuntu1604/build-root/build-vpp-native/vpp-api/java'
> 09:32:35   CC   jvpp-common/libjvpp_common_la-jvpp_common.lo
> 09:32:35   CC   jvpp-core/libjvpp_core_la-jvpp_core.lo
> 09:32:35   CC   jvpp-registry/libjvpp_registry_la-jvpp_registry.lo
> 09:32:39   CCLD libjvpp_common.la
> 09:32:39   CCLD libjvpp_registry.la
> 09:32:40 ar: `u' modifier ignored since `D' is the default (see `U')
> 09:32:40 /usr/bin/ld: cannot find -ljvpp_common
> 09:32:40 collect2: error: ld returned 1 exit status
> 09:32:40 Makefile:551: recipe for target 'libjvpp_registry.la' failed
>
> It appears that the output of "CCLD libjvpp_common.la" is an input to
> "CCLD libjvpp_registry.la" and in the error case it is not found.
>
> I had thought that Maros or Marek had provided a fix for this issue a
> couple of weeks ago.  When I get the chance investigate further.
>
> Thanks,
> -daw-
>
>
> On 10/20/2016 10:31 AM, Maciek Konstantynowicz (mkonstan) wrote:
>
> Hi,
>
> Anybody with time and willingness to look at below jobs and see why they
> pass 1st time and fail 2nd time,
> ie not repeatable..
>
> All running on the new ubuntu1604 VMs in VIRL. Related to two vpp patches:
>
> https://gerrit.fd.io/r/#/c/3499/
> https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1838/ : SUCCESS
> https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/ : FAILURE
>
> Seem to be vpp build related, as the standalone ubuntu1604 build jobs for
> this patch are also yielding not repeatable results:
> https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1833/ : FAILURE
> https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1836/ : SUCCESS
>
>
> -Maciek
>
> from https://jenkins.fd.io/job/vpp-csit-verify-virl-
> master/1841/consoleFull
> 10:52:23 make[1]: Entering directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/deb'
> 10:52:23 dh clean --with dkms --with systemd
> 10:52:24 dh: error: cannot read debian/changelog: No such file or directory
> 10:52:24 debian/rules:21: recipe for target 'clean' failed
> 10:52:24 make[1]: *** [clean] Error 2
> 10:52:24 make[1]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/deb'
> 10:52:24 Makefile:1159: recipe for target 'distclean' failed
> 10:52:24 make: *** [distclean] Error 2
>
> 10:59:49 collect2: error: ld returned 1 exit status
> 10:59:49 Makefile:551: recipe for target 'libjvpp_registry.la' failed
> 10:59:49 make[5]: *** [libjvpp_registry.la] Error 1
> 10:59:49 make[5]: *** Waiting for unfinished jobs
> 11:00:00 make[5]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/build-vpp-native/vpp-api/java'
> 11:00:00 Makefile:445: recipe for target 'all' failed
> 11:00:00 make[4]: *** [all] Error 2
> 11:00:00 make[4]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/build-vpp-native/vpp-api/java'
> 11:00:00 Makefile:377: recipe for target 'all-recursive' failed
> 11:00:00 make[3]: *** [all-recursive] Error 1
> 11:00:00 make[3]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/build-vpp-native/vpp-api'
> 11:00:00 Makefile:699: recipe for target 'vpp-api-build' failed
> 11:00:00 make[2]: *** [vpp-api-build] Error 2
> 11:00:00 make[2]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root'
> 11:00:00 /w/workspace/vpp-csit-verify-virl-master/build-data/platfor
> ms.mk:20: recipe for target 'install-deb' failed
> 11:00:00 make[1]: *** [install-deb] Error 1
> 11:00:00 make[1]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root'
> 11:00:00 Makefile:264: recipe for target 'pkg-deb' failed
> 11:00:00 make: *** [pkg-deb] Error 2
>
>
> ___
> csit-dev mailing 
> listcsit-...@lists.fd.iohttps://lists.fd.io/mailman/listinfo/csit-dev
>
>
>
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Can't build Centos Vagrant Master

[Edward Warnicke]

New theory... are you by chance running this VM on a Mac that is running
Mac OS X Sierra?
I ask, because Siera apparently handles loading keys into ssh-agent
differently, and so your personal
ssh keys may not propogate into your Vagrant.   To fix it, try:

ssh-add -A

in Mac OS X Sierra before doing your vagrant up.

Ed

On Tue, Oct 18, 2016 at 5:27 PM, Edward Warnicke <hagb...@gmail.com> wrote:

> In which case my theory is likely incorrect ;)
>
> Ed
>
> On Tue, Oct 18, 2016 at 5:23 PM, Keith Burns <alaga...@gmail.com> wrote:
>
>> But aren't these RSA keys ?
>>
>> alagalah@thing1:~ $ cd .ssh
>> alagalah@thing1:.ssh $ ll
>> total 20K
>> -rw--- 1 alagalah alagalah 1.6K May 31 04:49 authorized_keys
>> -rw--- 1 alagalah alagalah 3.2K Mar  8  2016 id_rsa
>> -rw-r--r-- 1 alagalah alagalah  744 Mar  8  2016 id_rsa.pub
>>
>>
>>
>> On Tue, Oct 18, 2016 at 5:22 PM Edward Warnicke <hagb...@gmail.com>
>> wrote:
>>
>>> I didn't read to closely on it... but I suspect that over time it will
>>> likely mean that everywhere you use DSA (not RSA) keys you will need to
>>> replace (presuming I am correct... but replacing my old DSA keys with new
>>> RSA keys did fix this issue for me in fd.io and in ODL).
>>>
>>> Ed
>>>
>>>
>>> On Tue, Oct 18, 2016 at 5:19 PM, Keith Burns <alaga...@gmail.com> wrote:
>>>
>>> Oooops, spoke to soon. Well Dang and Blast ...
>>>
>>> I do use RSA keys ...
>>>
>>> Does this mean that every place I have my public key I will need to
>>> change ?
>>>
>>>
>>> On Tue, Oct 18, 2016 at 5:15 PM Keith Burns <alaga...@gmail.com> wrote:
>>>
>>> But Trusty works fine ... as in
>>>
>>> export VPP_VAGRANT_DISTRO="centos7"
>>> vagrant up
>>> (bang)
>>> vagrant destroy -f
>>> unset VPP_VAGRANT_DISTRO
>>> vagrant up
>>> profit.
>>>
>>>
>>>
>>> On Tue, Oct 18, 2016 at 5:02 PM Edward Warnicke <hagb...@gmail.com>
>>> wrote:
>>>
>>> At a guess... here's what I think is happening (because it bit me).  DSA
>>> keys have recently been deprecated.  You may need to create a new
>>> RSA key and add it to your keys in gerrit.
>>>
>>> Ed
>>>
>>> On Tue, Oct 18, 2016 at 4:56 PM, Keith Burns <alaga...@gmail.com> wrote:
>>>
>>> https://gist.github.com/aef7978ee4bbfc5848f0bdb775342eb8
>>>
>>> Trusty works fine even though the above complains about Gerrit keys.
>>>
>>> Is this a problem with Gerrit or with the Vagrant system?
>>>
>>>
>>>
>>> ___
>>> vpp-dev mailing list
>>> vpp-dev@lists.fd.io
>>> https://lists.fd.io/mailman/listinfo/vpp-dev
>>>
>>>
>>>
>>>
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Can't build Centos Vagrant Master

[Edward Warnicke]

At a guess... here's what I think is happening (because it bit me).  DSA
keys have recently been deprecated.  You may need to create a new
RSA key and add it to your keys in gerrit.

Ed

On Tue, Oct 18, 2016 at 4:56 PM, Keith Burns  wrote:

> https://gist.github.com/aef7978ee4bbfc5848f0bdb775342eb8
>
> Trusty works fine even though the above complains about Gerrit keys.
>
> Is this a problem with Gerrit or with the Vagrant system?
>
>
>
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev