Hi Thomas,
This picture just takes NSH_SFC plugin for example.
You could replace it with any other plugins.
They share the same framework.
Thanks,
Hongjun
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Thomas F Herbert
Sent: Thursday, October 27, 2016 9:55
On 10/27/2016 12:11 PM, Feng Pan wrote:
I agree with Chris here. I also want to bring Centos into the
conversation, Centos 7.2 ships with QEMU version 1.5.3 by default and
2.3.0 in qemu-ev channel, both of those supported versions in Centos
contain backports from newer releases. I think it
It's an SMT [simple matter of typing] to create a number xxx.api files, related
message handler implementation files, and to place them next to whatever the
indicate API collection controls.
The current setup is a historical artifact.
Thanks... Dave
From: Luke, Chris
Thanks Klement!
That worked.
From: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
[mailto:ksek...@cisco.com]
Sent: Thursday, October 27, 2016 2:17 PM
To: Shravan Ambati
Cc: vpp-dev
Subject: Re: [vpp-dev] Connecting Vpp to a physical
Hi
I am new to vpp and I was trying to connect a pci interface to vpp.
I am using stable/1606 branch.
As per instructions in the following the wiki
https://wiki.fd.io/view/VPP/How_To_Connect_A_PCI_Interface_To_VPP
I have appended the pci address to the startup config file -
dpdk {
socket-mem
Tom, thanks for “barking” to the mailer :)
Per Dave’s note, Centos is indeed on CSIT project to-do list for some time.
Your proposal is also very timely as some consumers of Centos, namely
OPNFV/FDS have been “crying” to get it covered in CSIT too - per notes
from the last CSIT project call.
But
Folks,
I'd like to suggest that we undertake several clean-up tasks once we reach the
17.01 F0 (API freeze) milestone:
*Clean up Coverity warnings
*Split .../vpp/vpp-infra/{vpe.api, api.c} into groups of related APIs,
to reduce future merge collisions
*Finish
fd.io Folks,
I apologize in advance for "barking" on all the fd.io lists but this
topic really is cross functional,
I want to formally propose that we add Centos 7 server to CSIT. The
purpose would be to:
1. Perf and func tests of Centos deployment of VPP and Honeycomb etc.
2. Func and
I agree with Chris here. I also want to bring Centos into the conversation,
Centos 7.2 ships with QEMU version 1.5.3 by default and 2.3.0 in qemu-ev
channel, both of those supported versions in Centos contain backports from
newer releases. I think it would be helpful if a commit (or set of
+1
On 10/26/16 1:30 PM, Dave Barach (dbarach) wrote:
I would like to nominate Neale Ranns as a vpp project committer. Neale
designed and built the vpp FIB 2.0, a massive contribution.
History of Neale’s merged contributions to the vpp project:
Yes, we should not break QEMU 2.5 compatibility, specially if that version is
default version provided in ubuntu 16.04.
IMO we need to test both with 2.5 and 2.7 as long as ubuntu 16.04 is in game.
My understanding so far was that this is only "2.5-RC1" issue.
On 27 Oct 2016, at 09:56, Peter
+1
On Thu, Oct 27, 2016 at 9:33 AM, wrote:
> > Would the current vpp committers please vote (+1, 0, -1) by email to
> vpp-dev@lists.fd.io no later than Tuesday, 11/1 at 11:59pm EDT?
>
> +1 (without doubt).
>
> Cheers,
> Ole
>
>
Hey Ray,
>From usability perspective, you are right, JVPP is not useful outside of VPP.
But on the other hand, VPP plugins are also not useful outside of VPP but they
still get dedicated projects. Same applies for Honeycomb (the VPP specific
distribution of HC at least), it is not useful
> Would the current vpp committers please vote (+1, 0, -1) by email to
> vpp-dev@lists.fd.io no later than Tuesday, 11/1 at 11:59pm EDT?
+1 (without doubt).
Cheers,
Ole
___
vpp-dev mailing list
vpp-dev@lists.fd.io
Oh. Just notices you merged.
I actually merged and pushed too... So a new test is started. Will probably
fail.
Ideal Qemu would be 2.7.
2.5 is *old*. And the failing qemu was 2.5-rc1. Anything above 2.5-rc1 should
be good.
- Pierre
Le 27 oct. 2016 à 07:36, Peter Mikus -X (pmikus - PANTHEON
15 matches
Mail list logo