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 P
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 wo
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 [mailto:chris_l...@comcast
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 NIC.
Hi,
I noticed the wiki doesn't say taht
Hi,
I noticed the wiki doesn't say taht the interface should be down. Is your
interface down before starting vpp? I think that the vpp won't touch an
interface which is up...
Klement
On Oct 27, 2016 11:08 PM, Shravan Ambati wrote:
Hi
I am new to vpp and I was trying to connect a pci inter
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 10
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
Sounds good to me. The api files in particular strike me as unmanageably large
right now. I've especially wondered if the API code for each "thing" can move
physically closer the "thing" it provides an interface for.
Chris.
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io]
Excellent. We'll add this topic to next week's CSIT meeting to discuss
the requirements and plan moving forward.
All contributions to CSIT are welcome.
Thanks,
-daw-
On 10/27/16 4:02 PM, Thomas F Herbert wrote:
On 10/27/2016 03:28 PM, Dave Wallace wrote:
Tom,
There are already Jira tick
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 .../vnet
On 10/27/2016 03:28 PM, Dave Wallace wrote:
Tom,
There are already Jira tickets open for this:
https://jira.fd.io/browse/CSIT-356
https://jira.fd.io/browse/CIMANAGE-15
https://jira.fd.io/browse/CIMANAGE-16
Unfortunately there are currently no resources assigned to work on
this i
Tom,
There are already Jira tickets open for this:
https://jira.fd.io/browse/CSIT-356
https://jira.fd.io/browse/CIMANAGE-15
https://jira.fd.io/browse/CIMANAGE-16
Unfortunately there are currently no resources assigned to work on this
issue. This topic was discussed in this week's CSI
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 perf
I just want to take that back.
In my setup, the VM is not even booting with qemu 2.5.
But this may be completely unrelated with virtio.
So the investigation is still going...
Le 27 oct. 2016 à 17:00, Pierre Pfister (ppfister)
mailto:ppfis...@cisco.com>> a écrit :
I do agree.
I actually just re
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 commits)
+1
On Thu, Oct 27, 2016 at 7:06 AM, Bud Grise (griseb)
wrote:
> +1
>
> Bud
>
>
>
> *From:* Dave Barach (dbarach)
> *Sent:* Wednesday, October 26, 2016 1:31 PM
> *To:* vpp-dev@lists.fd.io
> *Subject:* VPP project committer nomination: Neale Ranns
>
>
>
> I would like to nominate Neale Ranns as a
I do agree.
I actually just realized there is *another* bug. Which appears with qemu 2.5
(not rc0, not rc1, but the real 2.5 release).
So I am working it out.
For some reason VPP is getting 0 from recvmsg, which seems to mean that the
socket was closed by qemu.
Let's see...
Le 27 oct. 2016 à
Wait, you’re saying software people aren’t very good at documentation?
Say it ain’t so!
In any case, I echo Damjan’s sentiment; Just to publicly air my end user
oriented opinion: it’s important to minimize the variables to get VPP going;
that means it has to work with whatever QEMU/KVM Ubuntu 1
Hi Dave,
I'd like to bow out of my committer role for fd.io/vpp. I haven't had time to
really participate but of course I still plan to follow fd.io development
closely.
Thanks,
Bud
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mail
+1
Bud
From: Dave Barach (dbarach)
Sent: Wednesday, October 26, 2016 1:31 PM
To: vpp-dev@lists.fd.io
Subject: VPP project committer nomination: Neale Ranns
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
On 10/27/2016 06:57 AM, Ni, Hongjun wrote:
Hey,
From the attachment: JVPP.PNG
The JVPP code is located in VPP project,
but from the logical perspective, the JVPP should be within Honeycomb.
This is weird.
So it is better to separate JVPP (Red piece in the picture) from VPP and
Honeycomb.
Be
Well... Apparently the fix didn't work.
Test failed in the same way again.
Le 27 oct. 2016 à 13:49, Pierre Pfister (ppfister)
mailto:ppfis...@cisco.com>> a écrit :
I think I have a fix.
I mean... I re-interprated some text from vhost-user.txt... Reverse engineered
DPDK's implementation... Look
+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:
https://gerrit.fd.io/r/#/q/status:merged+owner:
I think I have a fix.
I mean... I re-interprated some text from vhost-user.txt... Reverse engineered
DPDK's implementation... Looked at qemu messages... And tried to find a way to
make it work.
It looks like the first ring pair is supposed to be enabled by default... Well.
I don't know if it is
Hey,
>From the attachment: JVPP.PNG
The JVPP code is located in VPP project,
but from the logical perspective, the JVPP should be within Honeycomb.
This is weird.
So it is better to separate JVPP (Red piece in the picture) from VPP and
Honeycomb.
Besides, if customers only want to use VPP's b
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
>
> ___
> vpp-dev mailing li
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 witho
I would leave decision to community.
By merge this patch basically vhost-user on Qemu 2.5 would be failing - maybe
some disclaimer should be made or what about backward compatibility?
Peter Mikus
Engineer – Software
Cisco Systems Limited
Planned absence: 28.10., 1.11., 17.11., 9.12., 19.-31.12.
> 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
https://lists.fd.io/mailman/listinfo/
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 T
31 matches
Mail list logo
