> The concern would be that without CI you have very limited visibility into
> the impact of the patches pre-merge. The automation at fd.io does a *lot*
> for you…
Absolutely. For the hackathons CI was an order or two of magnitude too slow.
And we would be doing the testing there and then.
I d
I was looking at the lb plugins, and had some basic questions.
https://docs.fd.io/vpp/17.07/lb_plugin_doc.html
1. Other than load balancer node that need to setup VPP (+ lb plugin), is
VPP setup needed on the backend servers and client machines?
2. On the VPP load balancer node, is separate NIC car
Ole,
The concern would be that without CI you have very limited visibility into
the impact of the patches pre-merge. The automation at fd.io does a *lot*
for you...
Ed
On Wed, Nov 15, 2017 at 3:50 PM Jon Loeliger wrote:
> On Wed, Nov 15, 2017 at 4:17 PM, Dave Wallace
> wrote:
>
>> Folks,
>>
+2, (3 w/jdl) though be prepared to see questions about when the repo will be
updated for the rest of time. (GitHub can be a kind of roach motel for code.)
Cherry-picking is OK, when it’s a 1-2x thing, but when you start carrying
diverging branches, the occurrence of “oops, forgot that one” sta
+1...
-Original Message-
From: Ole Troan [mailto:otr...@employees.org]
Sent: Wednesday, November 15, 2017 5:49 PM
To: Dave Wallace
Cc: Ed Warnicke ; Dave Barach (dbarach) ;
Keith Burns (krb) ; Florin Coras (fcoras) ;
John Lo (loj) ; Luke, Chris ; Damjan
Marion ; Neale Ranns (nranns)
On Wed, Nov 15, 2017 at 4:17 PM, Dave Wallace wrote:
> Folks,
>
> Per the action item from this yesterday's VPP weekly meeting, I'm asking
> for opinions from the VPP community on allowing the creation of demo
> branches in the VPP git repo.
>
> ...
>
> Pro: Will allow utilization of LF infra to
Just as a data-point.
What we have done for IETF hackathons is to create a branch on github. E.g:
https://github.com/vpp-dev/vpp/tree/ietf100-nat
This allows us to do "high speed collaboration". Then cherry pick what has
value after the event.
Perhaps something similar could be done for "demos"?
I have a mild preference that we avoid creating demo branches in the master vpp
repo. When faced with similar requirements, I’ve added branch(es) to ephemeral
downstream mirrors.
I suppose one could destroy demo branches in the master vpp repo, but
“something could go wrong...”
Thoughts?
Than
Folks,
Per the action item from this yesterday's VPP weekly meeting, I'm asking
for opinions from the VPP community on allowing the creation of demo
branches in the VPP git repo.
The definition of a demo branch is defined as a branch pulled from
master that:
1) Purpose is to demonstrate a
Ah... good... I was working on updating a tutorial using the 17.10 release
when I saw it :)
Ed
On Wed, Nov 15, 2017 at 12:31 PM Luke, Chris wrote:
> Addendum: https://jira.fd.io/browse/VPP-1038 has the history.
>
>
>
> Chris.
>
>
>
> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@l
Addendum: https://jira.fd.io/browse/VPP-1038 has the history.
Chris.
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Luke, Chris
Sent: Wednesday, November 15, 2017 14:30
To: Ed Warnicke ; vpp-dev
Subject: Re: [vpp-dev] Odd behavior running ping via vppctl
Up
Update to master or latest commits on stable/17.10. The fix just missed the
release.
Chris.
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Ed Warnicke
Sent: Wednesday, November 15, 2017 13:14
To: vpp-dev
Subject: [vpp-dev] Odd behavior running ping via vppc
When I attempt to run ping via vppctl I get:
sudo vppctl -s /run/vpp/cli-vpp1.sock ping 10.10.1.1
64 bytes from 10.10.1.1: icmp_seq=1 ttl=64 time=.0715 ms
Aborted due to a keypress.
Statistics: 1 sent, 1 received, 0% packet loss
Note: I'm not pressing any keys. How would we go about fixing this
You can safely ignore those messages. They're just odd artifacts of how the
build system is assembled.
Chris.
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of wanghongbo
Sent: Wednesday, November 15, 2017 5:50
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] hi vpp-
Hi guys:
Need you help! I have built vpp success in vmware environment. But i
got three problem about "libtool" when I built vpp on x86 server. My
environment was real server + centos7.4 and the vpp's version was v17.10.
The capture as follows. Thank you very much!
You are likely running out of memory and g++ crashes...
> On 14 Nov 2017, at 11:09, wanghongbo wrote:
>
> Hi vpp-dev:
>
> Excuse me. Could you give me a hand? I have a problem when I build
> vpp. My environment is vmware workstation + centos7.4 . The capture as
> follows. Was t
That's a good catch, Gabriel...
I tried checking out the version which introduced this test as part of:
commit 8a0a0ae60b8dd9da7cf53c895e85dc6daf67143d
Author: Hongjun Ni
Date: Sat May 27 20:23:09 2017 +0800
Rework vxlan-gpe to support FIB 2.0 and bypass mode
Change-Id: I0324f945bdb4
17 matches
Mail list logo
