[vpp-dev] VPP master branch is OPEN for commits

Folks, The VPP master branch is now open for all patches slated for 19.08 (and beyond). The stable/1904 branch package upload is still being verified so please do not merge any patches to it until the RC1 Milestone is complete. Thanks, -daw- "Your Friendly VPP 19.04 Release Manager" -=-=-=-

Re: [vpp-dev] VPP master branch is CLOSED for stable/1904 branch pull

On 4/10/2019 5:22 PM, Dave Wallace via Lists.Fd.Io wrote: On 4/10/2019 5:11 PM, Damjan Marion wrote: On 10 Apr 2019, at 22:52, Dave Wallace wrote: On 4/10/2019 4:43 PM, Damjan Marion wrote: On 10 Apr 2019, at 21:12, Dave Wallace wrote: Folks, The VPP master branch is now closed f

Re: [vpp-dev] VPP master branch is CLOSED for stable/1904 branch pull

On 4/10/2019 5:11 PM, Damjan Marion wrote: On 10 Apr 2019, at 22:52, Dave Wallace wrote: On 4/10/2019 4:43 PM, Damjan Marion wrote: On 10 Apr 2019, at 21:12, Dave Wallace wrote: Folks, The VPP master branch is now closed for the branch pull of stable/1904. Please do NOT merge any p

Re: [vpp-dev] VPP master branch is CLOSED for stable/1904 branch pull

> On 10 Apr 2019, at 22:52, Dave Wallace wrote: > > > > On 4/10/2019 4:43 PM, Damjan Marion wrote: >> >> >>> On 10 Apr 2019, at 21:12, Dave Wallace wrote: >>> >>> Folks, >>> >>> The VPP master branch is now closed for the branch pull of stable/1904. >>> >>> Please do NOT merge any patch

Re: [vpp-dev] VPP master branch is CLOSED for stable/1904 branch pull

On 4/10/2019 4:43 PM, Damjan Marion wrote: On 10 Apr 2019, at 21:12, Dave Wallace > wrote: Folks, The VPP master branch is now closed for the branch pull of stable/1904. Please do NOT merge any patches until I give the all clear once the branch pull has been

Re: [vpp-dev] VPP master branch is CLOSED for stable/1904 branch pull

> On 10 Apr 2019, at 21:12, Dave Wallace wrote: > > Folks, > > The VPP master branch is now closed for the branch pull of stable/1904. > > Please do NOT merge any patches until I give the all clear once the branch > pull has been completed and verified. > > I will send an update when master

[vpp-dev] VPP master branch is CLOSED for stable/1904 branch pull

Folks, The VPP master branch is now closed for the branch pull of stable/1904. Please do NOT merge any patches until I give the all clear once the branch pull has been completed and verified. I will send an update when master is re-open for business. Thanks in advance for your cooperation! -

Re: [vpp-dev] Unstable Builds

The issue has been identified and resolved.  We've restarted the unstable builds. Thank you, Vanessa On 04/10/2019 09:27 AM, Vanessa Valderrama wrote: > We are aware of the unstable builds issue and are working on resolving > it as quickly as possible. > > Thank you, > Vanessa -=-=-=-=-=-=-=-=-=

[vpp-dev] Unstable Builds

We are aware of the unstable builds issue and are working on resolving it as quickly as possible. Thank you, Vanessa -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12749): https://lists.fd.io/g/vpp-dev/message/12749 Mute This Topic: https://lists.f

Re: [vpp-dev] jenkins maven failure

i looked into this and see nothing that leads me believe this is a build infra issue. vanessa is looking into this now.. On Apr 10, 2019, at 7:50 AM, Dave Wallace mailto:dwallac...@gmail.com>> wrote: Ben, Have you opened a helpd...@fd.io ticket for this issue yet? If

Re: [vpp-dev] jenkins maven failure

Ben, Have you opened a helpd...@fd.io ticket for this issue yet?  If not, please do. This looks like an LF infra issue uploading the build logs.  Same error occurred for https://gerrit.fd.io/r/18748 Thanks, -daw- On 4/10/2019 9:11 AM, Benoit Ganne (bganne) via Lists.Fd.Io wrote: Hi all,

[vpp-dev] A few MAP-T Clarifications

Good Morning, We are working on some MAP-E and MAP-T testing, and we have a few questions. Some of the existing VPP documentation about MAP-E and MAP-T is a bit loose. Should the use of a pre-resolved forwarding address be applicable to both MAP-E and MAP-T? Or is that only a MAP-E thing? Spec

[vpp-dev] jenkins maven failure

Hi all, It looks like we have some Jenkins issue. Any idea on how to fix that? See for example https://jenkins.fd.io/job/vpp-checkstyle-verify-master/6719/console 14:56:21 Apr 10, 2019 12:56:21 PM org.apache.commons.httpclient.auth.AuthChallengeProcessor selectAuthScheme 14:56:21 INFO: basic a

[vpp-dev] VPP 19.04 RC1 Milestone (branch pull} is TODAY at 1800UTC

Folks, A gentle reminder that the VPP 19.04 RC1 Milestone is TODAY at 1800 UTC. All features required in the VPP 19.04 release must be merged to master prior to the creation of the release branch: stable/1904. Please unicast me ASAP the link of any gerrit reviews which are required in 19.04

Re: [vpp-dev] do not SNAT if forwarding enabled

Hi Ole, we have a bridge(loop0) with a private ip say 192.168.100.2/24. a TAP is also connected to this bridge and other end of TAP is on host side. we have one physical interface connected to another bridge (loop1) with outside network ip of say 192.168.10.1/24 and a GRE tunnel is created having

Re: [vpp-dev] Shared memory implemention #vpp

Ido, > I just want to make sure I understood correctly the shared memory implemented > in project files... > > As mentioned in the git repo the directory extra/libmemif is a library that > serve the client, a user application, use it as a slave to connect the VPP. > > The directory src/plugin

Re: [vpp-dev] do not SNAT if forwarding enabled

Hi Shahid, What are you trying to achieve? https://wiki.fd.io/view/VPP/NAT#Enable_or_disable_forwarding You do not typically enable the “forwarding” feature. Cheers, Ole > On 8 Apr 2019, at 07:52, Shahid Khan wrote: > > can someone look into below query ? > > -Shahid. > > On Wed, Apr 3, 201

[vpp-dev] Shared memory implemention #vpp

Hi, I just want to make sure I understood correctly the shared memory implemented in project files... As mentioned in the git repo the directory extra/libmemif is a library that serve the client, a user application,  use it as a slave to connect the VPP. The directory src/plugins/memif is the