Re: [vpp-dev] VXLAN Tunnel IF Names

[Ed Warnicke]

Neale,

I think this really really fundamentally comes down to the ability to
configure in batch.  If I know I want to send something to vpp that creates
an interface and configures it in a *batch*, I can't know when I send that
batch configuration what sw_index will be.  So I either have to break up
the batch or have a way of getting a deterministic handle (name) to
configure the interface being created.When you are writing a local
control plane, you often just say "fuck it, I'm not going to be able to
batch.   But if you are writing a remote control plane (high latency per
message) or have a user copy pasting over configs via a CLI (not our CLI,
but another CLI you write) etc... batching is crucially important.

Ed




On Wed, Feb 7, 2018 at 7:18 AM Neale Ranns (nranns) 
wrote:

>
>
> But all control planes need to know the sw_if_index provided by VPP as it
> is this value (and not the interface name) that one needs to subsequently
> configure the interface. So why the reliance of VPP’s given name? AFIAK
> VPP’s given name is only important when interpreting CLI output.
>
> All control planes are free to choose whatever naming schemes they like,
> but they must maintain a control-plane-name to sw_if_index mapping. And to
> make VPP CLI output more useful, also maintain a control-plane-name to
> VPP-name mapping. In other words, X, is always the control-plane-name.
>
>
>
> /neale
>
>
>
>
>
> *From: *"John Lo (loj)" 
> *Date: *Wednesday, 7 February 2018 at 15:34
> *To: *"Neale Ranns (nranns)" , Jon Loeliger <
> j...@netgate.com>
> *Cc: *vpp-dev 
> *Subject: *RE: [vpp-dev] VXLAN Tunnel IF Names
>
>
>
> I guess Jon’s point was the control plane need to know exactly what X
> would be and not rely on VPP to provide the sw_if_index or query VPP for
> the name after the VXLAN create request.  This makes the control plane CLI
> script/template support more straight forward.  In the case of mixed usage
> where a requested instance is not available, I wonder how control plane
> should handle the error condition if it does not check the result of the
> VXLAN create request…   -John
>
>
>
> *From:* Neale Ranns (nranns)
> *Sent:* Wednesday, February 07, 2018 5:55 AM
> *To:* Jon Loeliger ; John Lo (loj) 
> *Cc:* vpp-dev 
> *Subject:* Re: [vpp-dev] VXLAN Tunnel IF Names
>
>
>
> Hi Jon,
>
>
>
> I feel I must ask J
>
> “That  has to match a VPP interface by name.  But what name?”
>
> why does it need to match a VPP interface name? shouldn’t  = MyVxlan23.
> Your control plane maintains mappings between MyVxlan23 and VPP’s
> sw_if_index.
>
>
>
> /neale
>
>
>
>
>
> *From: * on behalf of Jon Loeliger <
> j...@netgate.com>
> *Date: *Friday, 2 February 2018 at 22:08
> *To: *"John Lo (loj)" 
> *Cc: *vpp-dev 
> *Subject: *Re: [vpp-dev] VXLAN Tunnel IF Names
>
>
>
> On Wed, Jan 31, 2018 at 6:41 PM, John Lo (loj)  wrote:
>
> Hi Jon,
>
>
>
> Hi John,
>
>
>
> Thanks for taking the time to get back to me on this!
>
>
>
> All VPP tunnel creation uses the mechanism of returning a sw_if_index of
> the created tunnel.
>
>
>
> I know.  I get that.  It works.
>
>
>
> The name of the tunnel is then followed by a number being the instance or
> index to the tunnel struct vector. Thus, the first VXLAN tunnel created is
> called vxlan_tunnel0 followed by vxlan_tunnel1, etc. The number is
> incrementing unless tunnels are deleted and created again where a newly
> created tunnel will reuse the last deleted tunnel, hence its name. If all
> previously deleted tunnels are used up, then the tunnel name number will
> start incrementing again.
>
>
>
> Right.
>
>
>
> I am not sure if it is feasible to follow this behavior to “predict”
> tunnel name.
>
>
>
> It is not.
>
>
>
> The problem is not just "predict it", but the user has to be
>
> able to know the associated SW IF name at the time that
>
> the (vxlan tunnel) create API call happens.
>
>
>
> The reason for that is because the very next thing the
>
> API call user is going to want to do is configure that interface.
>
> Short of interrogating the system, there is no way to know
>
> the IF name.  (I understand that the name can be obtained
>
> from the sw_if_index.  That's not what I mean.)
>
>
>
> Consider this series of PEUDO API calls that are being
>
> issued by some client front-end.  Think of this as a batch
>
> of CLI commands:
>
>
>
> vxlan MyVxlan23
>
> source 1.2.3.4
>
> destination 10.11.12.13
>
> vni 19
>
> exit
>
>
>
> interface 
>
> do stuff to interface like apply an ACL or whatever
>
> exit
>
>
>
> There is no way to batch-run those as there is a step
>
> needed to determine what  is.  It could be "vxlan_tunnel..."
>
> anything.
>
>
>
> That  has to match a VPP interface by name.  But what name?
>
> The entire transactional  

Re: [vpp-dev] New fd.io vpp project committer vote: Marco Varlese

[Ed Warnicke]

+1

Ed

On Tue, Feb 6, 2018 at 2:38 PM Dave Wallace <dwallac...@gmail.com> wrote:

> +1
>
>
> On 02/06/2018 09:23 AM, Dave Barach (dbarach) wrote:
>
> Copying vpp-dev@lists.fd.io to formally open the vote described below.
> Voting is limited to current committers, and will remain open for 1 week,
> or until folks have voted.
>
>
>
> Thanks… Dave
>
>
>
> *From:* Dave Barach (dbarach)
> *Sent:* Tuesday, February 6, 2018 8:56 AM
> *To:* Keith Burns (krb) <k...@cisco.com> <k...@cisco.com>; Florin Coras
> (fcoras) <fco...@cisco.com> <fco...@cisco.com>; John Lo (loj)
> <l...@cisco.com> <l...@cisco.com>; Luke, Chris <chris_l...@comcast.com>
> <chris_l...@comcast.com>; Damjan Marion (damarion) <damar...@cisco.com>
> <damar...@cisco.com>; Neale Ranns (nranns) <nra...@cisco.com>
> <nra...@cisco.com>; Ole Troan <o...@cisco.com> <o...@cisco.com>; Dave Wallace
> <dwallac...@gmail.com> <dwallac...@gmail.com>; Ed Warnicke (eaw)
> <e...@cisco.com> <e...@cisco.com>
> *Subject:* New Committer Nomination: Marco Varlese
>
>
>
> Folks,
>
>
>
> In view of significant code contributions to the vpp project – see below –
> I’m pleased to nominate Marco Varlese as a vpp project committer. I have
> high confidence that he’ll be a major asset to the project in a committer
> role.
>
>
>
> Marco has contributed 46 merged patches, including significant new feature
> work.  Example: host stack implementation of SCTP, 8 KLOC
> https://gerrit.fd.io/r/#/c/9150. All merged patches:
> https://gerrit.fd.io/r/#/q/status:merged+owner:%22Marco+Varlese+%253Cmarco.varlese%2540suse.de%253E%22
>
>
>
>
>
> Please vote (+1, 0, -1) on vpp-dev@lists.fd.io. We’ll need a recorded
> vote so that the TSC will approve Marco’s nomination.
>
>
>
> Thanks... 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
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

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

[Ed Warnicke]

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
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Routing in VPP - newbie

[Ed Warnicke]

You need a route :)

See: https://wiki.fd.io/view/VPP/Progressive_VPP_Tutorial#Exercise:_Routing

(note: The Routing Exercise builds on previous exercises in the Tutorial...
but seems to be pretty close to what you are trying to do :) ).

Ed

On Mon, Jan 29, 2018 at 12:19 PM Abdul Hadi  wrote:

> Hi,
>
> I have just started with VPP. Please ignore my ignorance.
>
> Will VPP route my traffic from one subnet to another by default? or do i
> have to create additional routes in order to reach a subnet.
>
> I have a simple topology of Three VMs.
>
> 10.0.1.21 -> 10.0.1.22 (VM running VPP) 10.0.3.22 >10.0.3.23
> vpp1
> vpp2 vpp3
>
> i am able to ping from 10.0.1.21 to 10.0.1.22 and from 10.0.3.22 to
> 10.0.3.23
>
> But somehow  i can't reach from 10.0.1.21 to 10.0.3.23 (i know i am
> missing something but What?)
>
> vpp2 has two DPDK bound NICs.
>
> Please help in this regard.
>
> Br,
>
> Abdul
>
> ___
> 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] Supporting vpp releases besides N and N-1

[Ed Warnicke]

I think you've hit on the right metric: retire those streams which are no
longer supported.

What do others think?

Ed

On Fri, Jan 26, 2018 at 3:53 PM Ed Kern (ejk)  wrote:

>
> Id like to clean up jenkins ‘stream’ in the vpp section removing
> unsupported releases.
> Note: Its more than just cosmetically ugly problem.
>
> I could go into more detail but it comes down to “If they are not
> supported, why have them included in the build infra?”
>
> This would mean the removal from the stream of:
> 1707
> 1704
> 1701
> 1609
> 1606
>
> Anyone want to stand up and represent why these should remain?
>
> 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

[vpp-dev] Fwd: [tsc] Seeking demo ideas for LFN booth at ONS

[Ed Warnicke]

-- Forwarded message -
From: Brandon Wick 
Date: Fri, Jan 19, 2018 at 1:20 AM
Subject: [tsc] Seeking demo ideas for LFN booth at ONS
To: 


FD.io Technical Community:

We wanted to reach out and let you know that there will be space for a few
demos in the LF Networking (LFN) Booth at ONS. We've received a couple good
ideas already and are looking for a few more to consider. Our goal 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 ODL, ONAP, OPNFV, FD.io), 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 innovative work and value-add
from projects that don't necessarily meet these criteria.

Please submit your demo ideas by *January 26 *by sending an email to
bw...@linuxfoundation.org. LFN staff leadership will then review the
options make the final determination which demos can be accommodated. Idea
submitters will be notified by *February 2*.

In your email describing your demo idea and requirements, please indicate
who the demo manager(s) will be. A demo manager is required as part of each
demo proposal and will be responsible for the following:

   - Define the scope and storyline of the demo
   - Respond promptly to requests for additional information
   - Meet all requested deadlines
   - Setup and test the demo pre-show
   - Staff the demo during the expo hours (along with some other designated
   team members to help share the load)
   - Be willing to participate in media activities, e.g. video
   - Take down the demo post event

ONS sponsors are of course welcome to host demos in their booths on the
show floor. Check with your sponsorship managers to explore these
opportunities.

Please let me know if you have any questions and we look forward to hearing
your ideas.

Best,

Brandon Wick
Senior Integrated Marketing Manager, The Linux Foundation
Mobile: +1.917.282.0960 <(917)%20282-0960>  Skype: wick.brandon
Email / Google Talk: bw...@linuxfoundation.org


Brandon Wick
Senior Integrated Marketing Manager, The Linux Foundation
Mobile: +1.917.282.0960 <(917)%20282-0960>  Skype: wick.brandon
Email / Google Talk: bw...@linuxfoundation.org

___
tsc mailing list
t...@lists.fd.io
https://lists.fd.io/mailman/listinfo/tsc
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [nsh_sfc-dev] [tsc] Stepping down as NSH_SFC PTL

[Ed Warnicke]

Ray,

Thanks for letting us know!

Honjun,

Congratulations!

Ed

On Wed, Jan 17, 2018 at 7:11 AM Kinsella, Ray 
wrote:

>
>
> Hongjun is elected as NSH_SFC PLT.
>
> Trishan – can you make the update from the LF side?
>
>
>
> Thanks and congrats Hongjun,
>
>
>
> Ray K
>
>
>
> *From:* tsc-boun...@lists.fd.io [mailto:tsc-boun...@lists.fd.io] *On
> Behalf Of *Keith Burns
> *Sent:* Wednesday 10 January 2018 00:27
> *To:* Zhou, Danny 
> *Cc:* t...@lists.fd.io; nsh_sfc-...@lists.fd.io; vpp-dev@lists.fd.io
> *Subject:* Re: [tsc] [vpp-dev] [nsh_sfc-dev] Stepping down as NSH_SFC PTL
>
>
>
> +1 Hongjun!
>
>
>
> On Jan 4, 2018 7:15 PM, "Zhou, Danny"  wrote:
>
> +1 for Hongjun
>
>
>
> *From:* a...@yunify.org [mailto:a...@yunify.org]
> *Sent:* Friday, January 5, 2018 9:06 AM
> *To:* Zhou, Danny ; t...@lists.fd.io;
> nsh_sfc-...@lists.fd.io
> *Cc:* vpp-dev@lists.fd.io
> *Subject:* Re: [nsh_sfc-dev] Stepping down as NSH_SFC PTL
>
>
>
> +1
>
>
>
> Thanks for all your hard work!
>
>
>
> Ash
>
>
>
> Ash Young
>
> M: 408-628-7223 <(408)%20628-7223>
>
>
>
> On Wed, Jan 3, 2018 at 8:32 PM -0600, "Zhou, Danny" 
> wrote:
>
> Hi TSC,
>
> I've been taking the NSH_SFC PTL role 1 year ago. It has been a pleasure,
> but also a burden as there are some personal reasons make me cannot focus
> on NSH_SFC anymore, so I am stepping down as NSH_SFC PTL with immediate
> effect. Additionally, I would like to nominate Hongjun Ni, who is the
> most active NSH_SFC maintainer in 2017, as new NSH_SFC PTL for his
> excellent contribution as below:
>
> l  Upstreamed 42 patches totally cover Ingress Classifier, SFF, Egress
> Classifier, NSH-Proxy, NSH-aware NAT, MD-Type2, NSH over Ethernet and NSH
> TTL.
>
> l  Published four NSH_SFC Releases: 17.01, 17.04, 17.07 and 17.10.
>
>
>
> NSH_SFC maintainers,
>
>
>
> Pls vote for Hongjun Ni by directly replying this email.
>
>
>
> -Danny
>
>
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
>
> ___
> nsh_sfc-dev mailing list
> nsh_sfc-...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/nsh_sfc-dev
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] packet capture

[Ed Warnicke]

This may help:

https://docs.fd.io/vpp/17.10/clicmd_src_plugins_dpdk_device.html#clicmd_pcap_tx_trace

Ed

On Tue, Jan 9, 2018 at 9:49 AM Mohsin Kazmi (sykazmi) 
wrote:

> Please find the response inline:
>
>
> --
> *From:* Holoo Gulakh 
> *Sent:* Tuesday, January 9, 2018 12:22 PM
> *To:* Mohsin Kazmi (sykazmi); vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] packet capture
>
> there are labels like dpdk-input, ip4-input-no-checksum,
> ip4-icmp-echo-request and so on.
> As you know wireshark shows a single entry containing all information
> about a packet OR in other words wireshark captures packet at the physical
> layer.
>
>
> =
> Q1: Which of these labels in VPP act like wireshark??
> [mohsin] dpdk-input, af-packet-input etc. Input graph nodes which receive
> frames, act like wireshark.
>
> Q2: How to filter packets base on that label?? I want just one entry per
> packet containing all packet's info
> [mohsin] you can just add single label which you know interested packet
> should come from.
>
> i.e. trace add af-packet-input 10
>
> It will start tracing from af-packet-input and will report all the
> subsequent graph nodes which will process that received frame.
>
> =
>
> On Tue, Jan 9, 2018 at 2:41 PM, Mohsin Kazmi (sykazmi) 
> wrote:
>
>> Hello Holoo,
>>
>>
>> You can find examples of traces in VPP Uses Cases.
>>
>>
>> Specific to VPP packet tracing, please check the following link:
>>
>>
>>
>> https://wiki.fd.io/view/VPP/Command-line_Interface_(CLI)_Guide#packet_tracer
>>
>>
>> Apart from that, debug CLI list down the commands:
>>
>>
>> vpp# trace ?
>>   trace addTrace given number of packets
>>   trace filter filter trace output - include
>> NODE COUNT | exclude NODE COUNT | none
>>   trace frame-queuetrace frame-queue (on|off)
>> vpp#
>>
>> I hope that it will help.
>>
>> -br
>> Mohsin
>>
>>
>> --
>> *From:* vpp-dev-boun...@lists.fd.io  on
>> behalf of Holoo Gulakh 
>> *Sent:* Tuesday, January 9, 2018 11:58 AM
>> *To:* vpp-dev@lists.fd.io
>> *Subject:* [vpp-dev] packet capture
>>
>> Hi,
>> In a typical scenario, we usually use wireshark or tcpdump to capture
>> input/output packets from interfaces and we can use filters to filter them
>> base on different criteria such as protocol.
>> My question is that : when VPP handles one interface, then this interface
>> is out of kernel's control so we can't capture those packets using
>> wireshark or tcpdump.
>>
>> ===
>> What is an alternative in VPP for wireshark or tcpdump??
>> ===
>>
>> I read somewhere that there is a command named "trace" in VPP.
>> Is it correct?? if so, how to use it?? how to filter packets?? what is
>> the representation format of packets?? how to filter them base on network
>> stack layers??
>> I want to use this tool for debugging my scenarios which uses VPP as
>> dataplane.
>>
>
> ___
> 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] [nsh_sfc-dev] Stepping down as NSH_SFC PTL

[Ed Warnicke]

Danny,

Thank you for your service to the community. I hope you will continue to
participate in the future, and I hope our paths will continue to cross :)

You are correct on the procedure, the TSC does not need to approve PTL
elections, though it would be courteous to inform the TSC, and do make sure
to update the wiki page :)

Ed

On Fri, Jan 5, 2018 at 3:58 AM Wan, Qun  wrote:

> +1 for Hongjun
>
>
>
> Best Regards,
>
> Anna
>
>
>
> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
> Behalf Of *Zhou, Danny
> *Sent:* Friday, January 5, 2018 11:14 AM
> *To:* a...@yunify.org; t...@lists.fd.io; nsh_sfc-...@lists.fd.io
> *Cc:* vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] [nsh_sfc-dev] Stepping down as NSH_SFC PTL
>
>
>
> +1 for Hongjun
>
>
>
> *From:* a...@yunify.org [mailto:a...@yunify.org ]
> *Sent:* Friday, January 5, 2018 9:06 AM
> *To:* Zhou, Danny ; t...@lists.fd.io;
> nsh_sfc-...@lists.fd.io
> *Cc:* vpp-dev@lists.fd.io
> *Subject:* Re: [nsh_sfc-dev] Stepping down as NSH_SFC PTL
>
>
>
> +1
>
>
>
> Thanks for all your hard work!
>
>
>
> Ash
>
>
>
> Ash Young
>
> M: 408-628-7223 <(408)%20628-7223>
>
>
>
> On Wed, Jan 3, 2018 at 8:32 PM -0600, "Zhou, Danny" 
> wrote:
>
> Hi TSC,
>
> I've been taking the NSH_SFC PTL role 1 year ago. It has been a pleasure,
> but also a burden as there are some personal reasons make me cannot focus
> on NSH_SFC anymore, so I am stepping down as NSH_SFC PTL with immediate
> effect. Additionally, I would like to nominate Hongjun Ni, who is the
> most active NSH_SFC maintainer in 2017, as new NSH_SFC PTL for his
> excellent contribution as below:
>
> l  Upstreamed 42 patches totally cover Ingress Classifier, SFF, Egress
> Classifier, NSH-Proxy, NSH-aware NAT, MD-Type2, NSH over Ethernet and NSH
> TTL.
>
> l  Published four NSH_SFC Releases: 17.01, 17.04, 17.07 and 17.10.
>
>
>
> NSH_SFC maintainers,
>
>
>
> Pls vote for Hongjun Ni by directly replying this email.
>
>
>
> -Danny
>
> ___
> nsh_sfc-dev mailing list
> nsh_sfc-...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/nsh_sfc-dev
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] New Option for fd.io mailing lists: groups.io

[Ed Warnicke]

Bump...

Would it make sense to talk about this some at the vpp-dev meeting tomorrow?

Ed

On Fri, Dec 22, 2017 at 2:14 PM Burt Silverman <bur...@gmail.com> wrote:

> Search is somewhat painful with mailman. Otherwise I like it. Having said
> that, I have just learned about zgrep, and that simplifies the process,
> along with the fact that vim works on gzipped files.
>
> Burt
>
> On Fri, Dec 22, 2017 at 6:39 AM, Ole Troan <otr...@employees.org> wrote:
>
>> Two points:
>>
>> - What's their business model? Are we now going to be the product?
>> - History has shown that doing mail correctly has been too hard for
>> many... is there any indication that these people have clue?
>>   Or are they just focusing on "pretty" and lockin?
>>
>> Consider me skeptical,
>> Ole
>>
>> > On 14 Dec 2017, at 16:45, Ed Warnicke <hagb...@gmail.com> wrote:
>> >
>> > A new option has become available for handling mailing lists: groups.io
>> >
>> > As a community, we need to look at this option, provide feedback, and
>> come to a decision as to whether or not to migrate.  A critical part of
>> that is having folks take a look, ask questions, and express opinions :)
>> >
>> > We have a sandbox example at  https://groups.io/g/lfn  you can look at
>> >
>> > And an example with active list and imported archive:
>> https://lists.odpi.org/g/odpi-sig-bi
>> >
>> > Major benefits include searchability, better web interface, etc.
>> >
>> > The LF was kind enough to write a FAQ for us as we consider as a
>> community whether to migrate or not:
>> >
>> > FAQs
>> > Q: What are the key differences between Mailman and Groups.io?
>> > ●Groups.io has a modern interface, robust user security model, and
>> interactive, searchable archives
>> > ●Groups.io provides advanced features including muting threads and
>> integrations with modern tools like GitHub, Slack, and Trello
>> > ● Groups.io also has optional extras like a shared calendar,
>> polling, chat, a wiki, and more
>> > ● Groups.io uses a concept of subgroups, where members first join
>> the project “group” (a master list), then they choose the specific
>> “subgroup” lists they want to subscribe to
>> >
>> > Q: How is the experience different for me as a list moderator or
>> participant?
>> > In many ways, it is very much the same. You will still find the main
>> group at your existing URL and sub-groups equate to the more focused
>> mailing lists based on the community’s needs. Here is an example of main
>> group and sub-group URL patterns, and their respective emails:
>> >
>> > https://lists.fd.io/g/tsc
>> > https://lists.fd.io/g/discuss
>> > https:/lists.fd.io/g/vpp-dev
>> > t...@lists.fd.io
>> > disc...@lists.fd.io
>> > vpp-...@llists.fd.io
>> >
>> > What is different is Groups.io’s simple but highly functional UI that
>> will make the experience of moderating or participating in the community
>> discussions more enjoyable.
>> >
>> >
>> > ___
>> > 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

Re: [vpp-dev] [discuss] New Option for fd.io mailing lists: groups.io

[Ed Warnicke]

Joel,

We *sort* of moderate our discussions.  As an anti-spam measure currently,
if you are not subscribed to a mailer, and have not been previously
'whitelisted', your email is 'held for moderation' by the LF staff, which
take a quick look to see if you are a spammer, and if not, they add you to
the whitelist.   Essentially we 'moderate' out spammers, but all other
conversation is completely inbounds.

As to other features, part of the discussion is which features we want to
take advantage of.  Delighted to have your input on that :)

Ed

On Thu, Dec 14, 2017 at 9:51 AM Joel Halpern <joel.halp...@ericsson.com>
wrote:

> I like having good searchable archives.
>
>
>
> I have to say that I am completely turned off by the end of the FAQ.  We
> don’t “moderate” any of our discussions.  And unless something is very
> strange, the use of groups.io vs mailman better not have any visible
> effect on participation in the email discussions.
>
>
>
> Listing features like wikis seems also counter-productive.  I do not want
> us to have two separate wiki spaces.
>
>
>
> Polls would be nice once in a while (although doodle seems to work just
> fine for most folks.)
>
>
>
> If we want calendaring, I would want it integrated in the wiki, not part
> of the mailing list.
>
>
>
> Yours,
>
> Joel
>
>
>
> *From:* discuss-boun...@lists.fd.io [mailto:discuss-boun...@lists.fd.io] *On
> Behalf Of *Ed Warnicke
> *Sent:* Thursday, December 14, 2017 10:45 AM
> *To:* t...@lists.fd.io; disc...@lists.fd.io; vpp-dev <vpp-dev@lists.fd.io>;
> csit-...@lists.fd.io; cicn-...@lists.fd.io; honeycomb-dev <
> honeycomb-...@lists.fd.io>; deb_dpdk-...@lists.fd.io; rpm_d...@lists.fd.io;
> nsh_sfc-...@lists.fd.io; odp4vpp-...@lists.fd.io;
> pma_tools-...@lists.fd.io; puppet-f...@lists.fd.io; tldk-...@lists.fd.io;
> trex-...@lists.fd.io
> *Subject:* [discuss] New Option for fd.io mailing lists: groups.io
>
>
>
> A new option has become available for handling mailing lists: groups.io
>
>
>
> As a community, we need to look at this option, provide feedback, and come
> to a decision as to whether or not to migrate.  A critical part of that is
> having folks take a look, ask questions, and express opinions :)
>
>
>
> We have a sandbox example at  https://groups.io/g/lfn  you can look at
>
>
>
> And an example with active list and imported archive:
> https://lists.odpi.org/g/odpi-sig-bi
>
>
>
> Major benefits include searchability, better web interface, etc.
>
>
>
> The LF was kind enough to write a FAQ for us as we consider as a community
> whether to migrate or not:
>
>
>
> *FAQs*
>
> *Q: What are the key differences between Mailman and Groups.io?*
>
> ●Groups.io has a modern interface, robust user security model, and
> interactive, searchable archives
>
> ●Groups.io provides advanced features including muting threads and
> integrations with modern tools like GitHub, Slack, and Trello
>
> ● Groups.io also has optional extras like a shared calendar,
> polling, chat, a wiki, and more
>
> ● Groups.io uses a concept of subgroups, where members first
> join the project “group” (a master list), then they choose the specific
> “subgroup” lists they want to subscribe to
>
>
>
> *Q: How is the experience different for me as a list moderator or
> participant?*
>
> In many ways, it is very much the same. You will still find the main group
> at your existing URL and sub-groups equate to the more focused mailing
> lists based on the community’s needs. Here is an example of main group and
> sub-group URL patterns, and their respective emails:
>
>
>
> https://lists.fd.io/g/tsc
>
> https://lists.fd.io/g/discuss
>
> https:/lists.fd.io/g/vpp-dev
>
> t...@lists.fd.io
>
> disc...@lists.fd.io
>
> vpp-...@llists.fd.io
>
>
>
> What is different is Groups.io’s simple but highly functional UI that will
> make the experience of moderating or participating in the community
> discussions more enjoyable.
>
>
>
>
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] New Option for fd.io mailing lists: groups.io

[Ed Warnicke]

A new option has become available for handling mailing lists: groups.io

As a community, we need to look at this option, provide feedback, and come
to a decision as to whether or not to migrate.  A critical part of that is
having folks take a look, ask questions, and express opinions :)

We have a sandbox example at  https://groups.io/g/lfn  you can look at

And an example with active list and imported archive:
https://lists.odpi.org/g/odpi-sig-bi

Major benefits include searchability, better web interface, etc.

The LF was kind enough to write a FAQ for us as we consider as a community
whether to migrate or not:

*FAQs*
*Q: What are the key differences between Mailman and Groups.io?*
●Groups.io has a modern interface, robust user security model, and
interactive, searchable archives
●Groups.io provides advanced features including muting threads and
integrations with modern tools like GitHub, Slack, and Trello
● Groups.io also has optional extras like a shared calendar, polling, chat,
a wiki, and more
● Groups.io uses a concept of subgroups, where members first join the
project “group” (a master list), then they choose the specific “subgroup”
lists they want to subscribe to

*Q: How is the experience different for me as a list moderator or
participant?*
In many ways, it is very much the same. You will still find the main group
at your existing URL and sub-groups equate to the more focused mailing
lists based on the community’s needs. Here is an example of main group and
sub-group URL patterns, and their respective emails:

https://lists.fd.io/g/tsc
https://lists.fd.io/g/discuss
https:/lists.fd.io/g/vpp-dev
t...@lists.fd.io
disc...@lists.fd.io
vpp-...@llists.fd.io

What is different is Groups.io’s simple but highly functional UI that will
make the experience of moderating or participating in the community
discussions more enjoyable.
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] ONS CFP Open - Please propose fd.io related talks

[Ed Warnicke]

ONS will be held Mar 26-29 in Los Angeles.

The CFP has opened:

http://events.linuxfoundation.org/events/open-networking-summit-north-america/program/callforproposals

Please propose fd.io related talks there.

Ed
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] vpp continuous integration on armv8

[Ed Warnicke]

Gabriel,

We do need to have multiple workers to service the verify queue... having
the queue back up behind a single server wouldn't be good.  Do you know if
these boxes are installed with Ubuntu 16.04 already?

Ed

On Thu, Nov 16, 2017 at 9:03 AM Gabriel Ganne <gabriel.ga...@enea.com>
wrote:

> Yes, they are.
>
> I estimate it should take about 40 minutes to build and test with 8 cores
> in release mode, therefore I do not think that using all 3 ThunderX is
> necessary.
>
> I do not have access to a ThunderX platform on my side (I ran my tests on
> NXP and Hierofalcon platforms), if needed please see with Tina Tsou (in CC)
> for the specifics of ThunderX.
>
>
> I was thinking about duplicating the *vpp-verify-master-ubuntu1604*
> target as a first step.
>
> Ubuntu 16.04 is a LTS for armv8 and is one of the distributions already
> used for vpp x86 continuous testing.
>
>
> If all goes well, I was thinking about using fedora-26 (or above) as
> rhel-based distribution, since it also has aarch64 official support.
>
> But since it's not one of the distros already used in ci, let's keep it
> for later.
>
>
> Regards,
>
>
> --
>
> Gabriel Ganne
> --
> *From:* Ed Warnicke <hagb...@gmail.com>
> *Sent:* Thursday, November 16, 2017 4:47:14 PM
> *To:* Gabriel Ganne
> *Cc:* vpp-dev; Dave Barach (dbarach); Nicolas Bouthors;
> csit-...@lists.fd.io; Vanessa Valderrama
> *Subject:* Re: [vpp-dev] vpp continuous integration on armv8
>
> Gabriel,
>
> This is awesome news!
>
> Do I understand correctly that these ThunderX boards are intended to be
> used for build/make test/packaging?  If so, I've cced in Vanessa, our
> fearless sysadmin to help in figuring these things out :)
>
> Do you have opinions about which Linux distributions you want to package
> for (Ubuntu?, Centos?) and versions?
>
> Ed
>
> On Thu, Nov 16, 2017 at 5:27 AM Gabriel Ganne <gabriel.ga...@enea.com>
> wrote:
>
> Hi,
>
>
> We've been working on preparing vpp for armv8 continuous testing (See
> https://wiki.fd.io/view/VPP/AArch64
> <https://url10.mailanyone.net/v1/?m=1eFMO4-0003qy-3d=57e1b682=-ZITzwi6PGNT2EzKomkJRJ6M-7hD63QeHKT6tMIqMLSnlkmDUD9MfhdhuIw6iWayvj9HXr-SEr3zZlMt-TaTcUZhFRPyigiDDt7sfjQQxA8ESJIAyB06-QLH18FYzLWPwjJl8nmFi7D4ZD-9MfHHGQSEhj7_dqJNULEmezdjyETUcv28RNlzXlyC41ndbFhGIHD4TronLGLM7RL1QTG-dT2eyoBI4hyNrzA8GVmPHHM>
> ),
>
> and we think that we now have everything which is required to add arm as
> ci platform in the vpp review process (build, test and packaging). All the
> test have been done on "native".
>
> Also 3 thunderX platforms sent by ARM should have arrived yesterday in the
> fdio lab.
>
> I *think* that all that is required should be to set the platforms with
> VMs on it, and add them as build slaves.
>
>
> How should we proceed from here ?
>
>
> --
> Gabriel Ganne
>
>
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
> <https://url10.mailanyone.net/v1/?m=1eFMO4-0003qy-3d=57e1b682=O-sOs62iGkWatuIJLF4pSNDFFDG_8um2QvdTETSQnD4jA_r85x5l3Bf9qR7RJOonGi8xR9maOtNIkz_rsQpdGbKdnto4CMf5I6HVz8Fuvf8O0wwee8-H8NvmJBdthBWC63GiIordZqRTRpRonu_3HYVrEaz6pXyeEfp8SJT-AIJcmOBjMOnpVKHsnhio6kL9OijBIEROG5XpLW17H5dWsTPN_m3L28C7CUR0SBZauSoF89B0-0AT5GkPjJWEt4UQ>
>
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] vpp continuous integration on armv8

[Ed Warnicke]

Gabriel,

This is awesome news!

Do I understand correctly that these ThunderX boards are intended to be
used for build/make test/packaging?  If so, I've cced in Vanessa, our
fearless sysadmin to help in figuring these things out :)

Do you have opinions about which Linux distributions you want to package
for (Ubuntu?, Centos?) and versions?

Ed

On Thu, Nov 16, 2017 at 5:27 AM Gabriel Ganne 
wrote:

> Hi,
>
>
> We've been working on preparing vpp for armv8 continuous testing (See
> https://wiki.fd.io/view/VPP/AArch64),
>
> and we think that we now have everything which is required to add arm as
> ci platform in the vpp review process (build, test and packaging). All the
> test have been done on "native".
>
> Also 3 thunderX platforms sent by ARM should have arrived yesterday in the
> fdio lab.
>
> I *think* that all that is required should be to set the platforms with
> VMs on it, and add them as build slaves.
>
>
> How should we proceed from here ?
>
>
> --
> Gabriel Ganne
>
>
> ___
> 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] Odd behavior running ping via vppctl

[Ed Warnicke]

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 <chris_l...@comcast.com> wrote:

> 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 <hagb...@gmail.com>; vpp-dev <vpp-dev@lists.fd.io>
> *Subject:* Re: [vpp-dev] Odd behavior running ping via vppctl
>
>
>
> 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
> <vpp-dev-boun...@lists.fd.io>] *On Behalf Of *Ed Warnicke
> *Sent:* Wednesday, November 15, 2017 13:14
> *To:* vpp-dev <vpp-dev@lists.fd.io>
> *Subject:* [vpp-dev] Odd behavior running ping via vppctl
>
>
>
> 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?
>
>
>
> Ed
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] Odd behavior running ping via vppctl

[Ed Warnicke]

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?

Ed
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [FD.io Helpdesk #47942] Re: Merge jobs faiing

[Ed Warnicke via RT]

https://gerrit.fd.io/r/#/c/9329/ fixed it.

Ed

On Wed, Nov 8, 2017 at 3:39 PM Vanessa Valderrama via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> Change https://gerrit.fd.io/r/#/c/9327/ was submitted and merged to
> resolve this issue but the builds are still failing with the same error.
>
> On Wed Nov 08 10:16:01 2017, hagbard wrote:
> > So the more interesting question is... why are we building the vpp-
> > dpdk-dev
> > package at all given that the version in nexus matches the version in
> > the
> > repo which means we should simply be installing it from the repo
> > rather
> > than building it...
> >
> > Ed
> >
> > On Wed, Nov 8, 2017 at 7:52 AM Vanessa Valderrama via RT <
> > fdio-helpd...@rt.linuxfoundation.org> wrote:
> >
> > > This error typically occurs when an artifact that already exists is
> > > trying
> > > to be deployed.  Would you like to remove the artifacts that were
> > > deployed
> > > on 10/10? I believe that will resolve this error.
> > >
> > > vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb
> > >
> > > Thank you,
> > > Vanessa
> > >
> > > On Wed Nov 08 08:49:28 2017, hagbard wrote:
> > > > This appears to be something going wrong pushing to the nexus
> > > > server... it
> > > > looks like the nexus server is rejecting the push, from:
> > > >
> > > > https://jenkins.fd.io/view/vpp/job/vpp-merge-master-
> > > > ubuntu1604/3174/consoleFull
> > > >
> > > > 13:07:08 [ERROR] Failed to execute goal
> > > > org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file
> > > > (default-
> > > > cli)
> > > > on project standalone-pom: Failed to deploy artifacts: Could not
> > > > transfer
> > > > artifact io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to
> > > > fd.io.master.ubuntu.xenial.main (
> > > >
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main
> > > ):
> > > > Failed to transfer file:
> > > >
> > >
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> > > > dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> > > > Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> > > > 13:07:08 [ERROR]
> > > > 13:07:08 [ERROR] To see the full stack trace of the errors, re-run
> > > > Maven
> > > > with the -e switch.
> > > > 13:07:08 [ERROR] Re-run Maven using the -X switch to enable full
> > > > debug
> > > > logging.
> > > > 13:07:08 [ERROR]
> > > > 13:07:08 [ERROR] For more information about the errors and possible
> > > > solutions, please read the following articles:
> > > > 13:07:08 [ERROR] [Help 1]
> > > >
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> > > > 13:07:08 Build step 'Execute shell' marked build as failure
> > > >
> > > >
> > > > On Tue, Nov 7, 2017 at 11:50 PM Lori Jakab
> > > > <lorand.jakab+f...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > Any update on this? We can't get the latest patches via the
> > > > > Ubuntu
> > > > > package
> > > > > manager and that hurts certain test scenarios.
> > > > >
> > > > > -Lori
> > > > >
> > > > >
> > > > > On Mon, Nov 6, 2017 at 6:31 PM, Ed Warnicke <hagb...@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> This looks like we are hitting the limit on storage at
> > > > >> packagecloud.
> > > > >>
> > > > >> I've manually trimmed some old packages, but we really really
> > > > >> need
> > > > >> to get
> > > > >> the script going that autotrims for us.
> > > > >>
> > > > >> Vanessa,
> > > > >>
> > > > >> How are we doing on that?
> > > > >>
> > > > >> Ed
> > > > >>
> > > > >> On Mon, Nov 6, 2017 at 9:17 AM Luke, Chris
> > > > >> <chris_l...@comcast.com>
> > > > >> wrote:
> > > > >>
> > > > >>> The post-merge jobs are failing with errors like this:
>

Re: [vpp-dev] [FD.io Helpdesk #47942] Re: Merge jobs faiing

[Ed Warnicke]

https://gerrit.fd.io/r/#/c/9329/ fixed it.

Ed

On Wed, Nov 8, 2017 at 3:39 PM Vanessa Valderrama via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> Change https://gerrit.fd.io/r/#/c/9327/ was submitted and merged to
> resolve this issue but the builds are still failing with the same error.
>
> On Wed Nov 08 10:16:01 2017, hagbard wrote:
> > So the more interesting question is... why are we building the vpp-
> > dpdk-dev
> > package at all given that the version in nexus matches the version in
> > the
> > repo which means we should simply be installing it from the repo
> > rather
> > than building it...
> >
> > Ed
> >
> > On Wed, Nov 8, 2017 at 7:52 AM Vanessa Valderrama via RT <
> > fdio-helpd...@rt.linuxfoundation.org> wrote:
> >
> > > This error typically occurs when an artifact that already exists is
> > > trying
> > > to be deployed.  Would you like to remove the artifacts that were
> > > deployed
> > > on 10/10? I believe that will resolve this error.
> > >
> > > vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb
> > >
> > > Thank you,
> > > Vanessa
> > >
> > > On Wed Nov 08 08:49:28 2017, hagbard wrote:
> > > > This appears to be something going wrong pushing to the nexus
> > > > server... it
> > > > looks like the nexus server is rejecting the push, from:
> > > >
> > > > https://jenkins.fd.io/view/vpp/job/vpp-merge-master-
> > > > ubuntu1604/3174/consoleFull
> > > >
> > > > 13:07:08 [ERROR] Failed to execute goal
> > > > org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file
> > > > (default-
> > > > cli)
> > > > on project standalone-pom: Failed to deploy artifacts: Could not
> > > > transfer
> > > > artifact io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to
> > > > fd.io.master.ubuntu.xenial.main (
> > > >
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main
> > > ):
> > > > Failed to transfer file:
> > > >
> > >
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> > > > dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> > > > Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> > > > 13:07:08 [ERROR]
> > > > 13:07:08 [ERROR] To see the full stack trace of the errors, re-run
> > > > Maven
> > > > with the -e switch.
> > > > 13:07:08 [ERROR] Re-run Maven using the -X switch to enable full
> > > > debug
> > > > logging.
> > > > 13:07:08 [ERROR]
> > > > 13:07:08 [ERROR] For more information about the errors and possible
> > > > solutions, please read the following articles:
> > > > 13:07:08 [ERROR] [Help 1]
> > > >
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> > > > 13:07:08 Build step 'Execute shell' marked build as failure
> > > >
> > > >
> > > > On Tue, Nov 7, 2017 at 11:50 PM Lori Jakab
> > > > <lorand.jakab+f...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > Any update on this? We can't get the latest patches via the
> > > > > Ubuntu
> > > > > package
> > > > > manager and that hurts certain test scenarios.
> > > > >
> > > > > -Lori
> > > > >
> > > > >
> > > > > On Mon, Nov 6, 2017 at 6:31 PM, Ed Warnicke <hagb...@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> This looks like we are hitting the limit on storage at
> > > > >> packagecloud.
> > > > >>
> > > > >> I've manually trimmed some old packages, but we really really
> > > > >> need
> > > > >> to get
> > > > >> the script going that autotrims for us.
> > > > >>
> > > > >> Vanessa,
> > > > >>
> > > > >> How are we doing on that?
> > > > >>
> > > > >> Ed
> > > > >>
> > > > >> On Mon, Nov 6, 2017 at 9:17 AM Luke, Chris
> > > > >> <chris_l...@comcast.com>
> > > > >> wrote:
> > > > >>
> > > > >>> The post-merge jobs are failing with errors like this:
>

Re: [vpp-dev] [FD.io Helpdesk #47942] Re: Merge jobs faiing

[Ed Warnicke via RT]

So the more interesting question is... why are we building the vpp-dpdk-dev
package at all given that the version in nexus matches the version in the
repo which means we should simply be installing it from the repo rather
than building it...

Ed

On Wed, Nov 8, 2017 at 7:52 AM Vanessa Valderrama via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> This error typically occurs when an artifact that already exists is trying
> to be deployed.  Would you like to remove the artifacts that were deployed
> on 10/10? I believe that will resolve this error.
>
> vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb
>
> Thank you,
> Vanessa
>
> On Wed Nov 08 08:49:28 2017, hagbard wrote:
> > This appears to be something going wrong pushing to the nexus
> > server... it
> > looks like the nexus server is rejecting the push, from:
> >
> > https://jenkins.fd.io/view/vpp/job/vpp-merge-master-
> > ubuntu1604/3174/consoleFull
> >
> > 13:07:08 [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file (default-
> > cli)
> > on project standalone-pom: Failed to deploy artifacts: Could not
> > transfer
> > artifact io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to
> > fd.io.master.ubuntu.xenial.main (
> > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main
> ):
> > Failed to transfer file:
> >
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> > dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> > Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> > 13:07:08 [ERROR]
> > 13:07:08 [ERROR] To see the full stack trace of the errors, re-run
> > Maven
> > with the -e switch.
> > 13:07:08 [ERROR] Re-run Maven using the -X switch to enable full debug
> > logging.
> > 13:07:08 [ERROR]
> > 13:07:08 [ERROR] For more information about the errors and possible
> > solutions, please read the following articles:
> > 13:07:08 [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> > 13:07:08 Build step 'Execute shell' marked build as failure
> >
> >
> > On Tue, Nov 7, 2017 at 11:50 PM Lori Jakab
> > <lorand.jakab+f...@gmail.com>
> > wrote:
> >
> > > Hello,
> > >
> > > Any update on this? We can't get the latest patches via the Ubuntu
> > > package
> > > manager and that hurts certain test scenarios.
> > >
> > > -Lori
> > >
> > >
> > > On Mon, Nov 6, 2017 at 6:31 PM, Ed Warnicke <hagb...@gmail.com>
> > > wrote:
> > >
> > >> This looks like we are hitting the limit on storage at packagecloud.
> > >>
> > >> I've manually trimmed some old packages, but we really really need
> > >> to get
> > >> the script going that autotrims for us.
> > >>
> > >> Vanessa,
> > >>
> > >> How are we doing on that?
> > >>
> > >> Ed
> > >>
> > >> On Mon, Nov 6, 2017 at 9:17 AM Luke, Chris <chris_l...@comcast.com>
> > >> wrote:
> > >>
> > >>> The post-merge jobs are failing with errors like this:
> > >>>
> > >>>
> > >>>
> > >>> *16:04:05* [ERROR] Failed to execute goal
> > >>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file
> > >>> (default-cli) on project standalone-pom: Failed to deploy
> > >>> artifacts: Could not transfer artifact io.fd.vpp:vpp-dpdk-
> > >>> dev:deb:deb:17.08-vpp2_amd64 from/to
> > >>> fd.io.master.ubuntu.xenial.main
> > >>> (
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main):
> > >>> Failed to transfer file:
> > >>>
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> > >>> dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> > >>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> > >>>
> > >>>
> > >>>
> > >>> (from
> > >>> https://jenkins.fd.io/job/vpp-merge-master-
> > >>> ubuntu1604/3148/consoleFull)
> > >>>
> > >>>
> > >>>
> > >>> This is sufficiently voodoo for me to not know how to proceed. (The
> > >>> Nexus stuff consistently annoys and baffles me, not least the
> > >>> overly-verbose chatter in build logs)
> > >>>
> > >>>
> > >>>
> > >>> Could someone take a look, please?
> > >>>
> > >>>
> > >>>
> > >>> Net result: No packages are being stored from master, and docs are
> > >>> not
> > >>> getting generated. It has been doing for thia a few days as best I
> > >>> can tell.
> > >>>
> > >>>
> > >>>
> > >>> Thanks,
> > >>>
> > >>> Chris.
> > >>> ___
> > >>> 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

Re: [vpp-dev] Merge jobs faiing

[Ed Warnicke]

This appears to be something going wrong pushing to the nexus server... it
looks like the nexus server is rejecting the push, from:

https://jenkins.fd.io/view/vpp/job/vpp-merge-master-ubuntu1604/3174/consoleFull

13:07:08 [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file (default-cli)
on project standalone-pom: Failed to deploy artifacts: Could not transfer
artifact io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to
fd.io.master.ubuntu.xenial.main (
https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main):
Failed to transfer file:
https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
13:07:08 [ERROR]
13:07:08 [ERROR] To see the full stack trace of the errors, re-run Maven
with the -e switch.
13:07:08 [ERROR] Re-run Maven using the -X switch to enable full debug
logging.
13:07:08 [ERROR]
13:07:08 [ERROR] For more information about the errors and possible
solutions, please read the following articles:
13:07:08 [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
13:07:08 Build step 'Execute shell' marked build as failure


On Tue, Nov 7, 2017 at 11:50 PM Lori Jakab <lorand.jakab+f...@gmail.com>
wrote:

> Hello,
>
> Any update on this? We can't get the latest patches via the Ubuntu package
> manager and that hurts certain test scenarios.
>
> -Lori
>
>
> On Mon, Nov 6, 2017 at 6:31 PM, Ed Warnicke <hagb...@gmail.com> wrote:
>
>> This looks like we are hitting the limit on storage at packagecloud.
>>
>> I've manually trimmed some old packages, but we really really need to get
>> the script going that autotrims for us.
>>
>> Vanessa,
>>
>> How are we doing on that?
>>
>> Ed
>>
>> On Mon, Nov 6, 2017 at 9:17 AM Luke, Chris <chris_l...@comcast.com>
>> wrote:
>>
>>> The post-merge jobs are failing with errors like this:
>>>
>>>
>>>
>>> *16:04:05* [ERROR] Failed to execute goal 
>>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file (default-cli) 
>>> on project standalone-pom: Failed to deploy artifacts: Could not transfer 
>>> artifact io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to 
>>> fd.io.master.ubuntu.xenial.main 
>>> (https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main): 
>>> Failed to transfer file: 
>>> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
>>>  Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>>>
>>>
>>>
>>> (from
>>> https://jenkins.fd.io/job/vpp-merge-master-ubuntu1604/3148/consoleFull)
>>>
>>>
>>>
>>> This is sufficiently voodoo for me to not know how to proceed. (The
>>> Nexus stuff consistently annoys and baffles me, not least the
>>> overly-verbose chatter in build logs)
>>>
>>>
>>>
>>> Could someone take a look, please?
>>>
>>>
>>>
>>> Net result: No packages are being stored from master, and docs are not
>>> getting generated. It has been doing for thia a few days as best I can tell.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Chris.
>>> ___
>>> 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

Re: [vpp-dev] Merge jobs faiing

[Ed Warnicke]

This looks like we are hitting the limit on storage at packagecloud.

I've manually trimmed some old packages, but we really really need to get
the script going that autotrims for us.

Vanessa,

How are we doing on that?

Ed

On Mon, Nov 6, 2017 at 9:17 AM Luke, Chris  wrote:

> The post-merge jobs are failing with errors like this:
>
>
>
> *16:04:05* [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file (default-cli) on 
> project standalone-pom: Failed to deploy artifacts: Could not transfer 
> artifact io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to 
> fd.io.master.ubuntu.xenial.main 
> (https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main): 
> Failed to transfer file: 
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
>  Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>
>
>
> (from
> https://jenkins.fd.io/job/vpp-merge-master-ubuntu1604/3148/consoleFull)
>
>
>
> This is sufficiently voodoo for me to not know how to proceed. (The Nexus
> stuff consistently annoys and baffles me, not least the overly-verbose
> chatter in build logs)
>
>
>
> Could someone take a look, please?
>
>
>
> Net result: No packages are being stored from master, and docs are not
> getting generated. It has been doing for thia a few days as best I can tell.
>
>
>
> Thanks,
>
> Chris.
> ___
> 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] VPP 17.10 Released

[Ed Warnicke]

Woot!

On Thu, Oct 26, 2017 at 2:36 PM Florin Coras  wrote:

> Dear VPP community,
>
> The VPP 17.10 release is complete. The release artefacts are now available
> on the nexus server and the repos have been updated.
>
> I’d like to take this opportunity to thank you all for your continued
> support for VPP.
>
> Regards,
> Florin
> ___
> 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] 17.10 draft release notes

[Ed Warnicke]

A few question, possibly not for inclusion in the Release Notes, but for
use in explaining them in the coming PR about the release:

Florin,

 TCP performance/congestion improvements: Do we have any numbers we can
conveniently point to to illustrate the point?

Keith/Wallace,
 Anything particularly sexy you want to call out on the VCL work?


Hongjun,

  Could you provide some context around the PPPoE stuff and its
importance to NFV solutions in ONAP?

Andrew,

  Could you describe (or provide a link to the patch) that improves the
ACL API?  I'm pretty sure I know what you did, but want to be certain :)

Ole,

  Do you want to explain in your own words why one armed NAT is cool
and NAT64 is cool (I can swag something, but best to let you do so if you
want too :) ).

Sergio/Neale,

  Can you provide some color on the user-visible benefits to the IPSEC
rework?

Ed


On Mon, Oct 23, 2017 at 8:48 AM, Florin Coras 
wrote:

> Dear all,
>
> You can find a draft of VPP 17.10 release notes here [1]. Feel free to add
> comments, reply to this message or send me private messages if something is
> missing.
>
> Regards,
> Florin
>
> [1] https://gerrit.fd.io/r/#/c/8953/
>
> ___
> 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] Running multiple instances of VPP as it was allowed with VPP-lite

[Ed Warnicke]

If you want to take it to the next level, and do a great service to your
fellow man, I would encourage you to update the tutorial to use:

https://docs.fd.io/vpp/17.10/clicmd_src_plugins_memif.html

to interconnect the various vpp instances :)

Ed

On Thu, Oct 5, 2017 at 2:50 PM, Ed Warnicke <hagb...@gmail.com> wrote:

> Justin,
>
> I've fixed the tutorial in this area:
>
> https://wiki.fd.io/view/VPP/Progressive_VPP_Tutorial
>
> Here's the net net.  Damjan improved the vppctl, rewriting it in C, and
> having it talk over a file socket to vpp.  This is goodness.  It does mean
> you do the multi-vpp instance thing a bit differently though:
>
> sudo vpp unix {cli-listen /run/vpp/cli-vpp1.sock} api-segment { prefix
> vpp1 }
>
> sudo vppctl -s /run/vpp/cli-vpp1.sock
>
> Thanks for asking, it prompted me to fix the tutorial :)
>
> Ed
>
> On Wed, Oct 4, 2017 at 9:23 AM, Justin Iurman <justin.iur...@ulg.ac.be>
> wrote:
>
>> Hi all,
>>
>> Is it still possible to run multiple instances of VPP, just like it was
>> done with VPP-lite (see here: https://wiki.fd.io/view/VPP/Pr
>> ogressive_VPP_Tutorial) before merging it ?
>>
>> Actually, my problem is the following. I need to run several instances of
>> VPP (eg. vpp1, vpp2, vpp3, etc) to simulate a topology. But, for some
>> reason, I'm not able to make it work as expected. I've already disabled
>> DPDK plugin to run in "lite" mode. Could it be a configuration issue ? VPP
>> startup.conf:
>>
>> unix {
>>   nodaemon
>>   log /tmp/vpp.log
>>   full-coredump
>>   cli-listen /run/vpp/cli.sock
>>   gid vpp
>> }
>>
>> api-trace {
>>   on
>> }
>>
>> api-segment {
>>   gid vpp
>> }
>>
>> plugins {
>>   plugin dpdk_plugin.so { disable }
>> }
>>
>> I tried to compare both VPP and VPP-lite. A first observation showed that
>> VPP is installed as a service, which is not the case for VPP-lite. I've
>> also compared both config files. Here is VPP-lite startup.conf:
>>
>> unix {
>>   nodaemon
>>   log /tmp/vpp.log
>>   full-coredump
>> }
>>
>> api-trace {
>>   on
>> }
>>
>> api-segment {
>>   gid vpp
>> }
>>
>> Currently, here is how I try to mimic VPP-lite behavior with VPP:
>>
>> sudo vpp api-segment { prefix vpp1 } unix { cli-listen
>> /run/vpp/cli.vpp1.sock }
>> sudo vppctl -s /run/vpp/cli.vpp1.sock
>>
>> It works for one instance, but not for more, even if it does not throw
>> any error. Do you have any idea on how to proceed or what is wrong here ?
>>
>> Thanks !
>>
>> Justin
>> ___
>> 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] [releng] Proposal to redirect #opendaylight-releng to #lf-releng

[Ed Warnicke]

One  suggestion I would have would be to do a phased transition, with a
'topic' in the existing infra channels set to direct folks to lf-releng,
and a period (3 months?, 6 months?) of keeping a presence on the existing
channels, to be used  to politely request bouncing conversations that arise
in them to lf-releng... this way folks can get used to it, and in worst
case, see in the topic where to go :)

Ed

On Tue, Oct 3, 2017 at 11:12 AM, Thanh Ha 
wrote:

> On Tue, Sep 26, 2017 at 6:38 PM, Thanh Ha 
> wrote:
>
>> Hi Everyone,
>>
>> We'd like to pitch an idea to have #opendaylight-releng irc channel
>> redirect to a new #lf-releng channel. Something that's occurred to us is
>> that many of the networking at LF projects have their own separate releng
>> channels in which folks typically ask JJB related questions. Each of these
>> channels are typically moderately active.
>>
>> Something we've been thinking about is the idea of merging all these
>> releng channels into #lf-releng which we're hoping can combine the
>> communities JJB experts so that JJB and other releng related questions can
>> be more broadly asked.
>>
>> Thoughts?
>>
>> Regards,
>> Thanh
>>
>
> Hi Everyone,
>
> For those that don't know me. I am one of the release engineers working on
> the OpenDaylight project. I've added the fd.io, opnfv, and onap
> communities to this list to get feedback on the idea proposed above. Let me
> know if there's other mailing lists in the respective projects we should be
> cc'ing to include in the discussions.
>
> I'd like to hear from the fd.io, opnfv, and onap for their thoughts on
> the proposal to create a single lf-releng channel on IRC and have all the
> respective releng channels redirect to it. Since our respective releng
> projects use similar technologies like JJB, Jenkins, etc... it might be a
> benefit to pool together our expertise so that it is easier to ask
> questions to the broader community when we need help with things like JJB,
> Gerrit, etc...
>
> You can follow the discussion thread so far from the ODL community
> discussed here:
> https://lists.opendaylight.org/pipermail/dev/2017-September/004066.html
>
>
> Regards,
> Thanh
>
>
> ___
> 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] Gerrit Maintainer Plugin enabled for VPP

[Ed Warnicke]

Tests to verify functionality of the Gerrit Maintainer Plugin:

https://gerrit.fd.io/r/#/c/8451/
https://gerrit.fd.io/r/#/c/8450/
https://gerrit.fd.io/r/#/c/8449/

Reveal that:

a)  Nothing is broken
b) The Gerrit Maintainer Pluging does not appear to be functioning as
intended

Ed

On Mon, Sep 18, 2017 at 1:51 PM, Ed Warnicke <hagb...@gmail.com> wrote:

> Per our previous (admittedly long ago) discussions on the Gerrit
> Maintainer Plugin auto adding reviewers based on the vpp MAINTAINERS file,
> it has now been merged.  It *only* auto adds reviews, any action to be
> taken in terms of merging a patch will, per agreement, at this time, still
> require a committer's action.
>
> I'll be pushing some test patches shortly to do a final confirmation (and
> revert if any of them failed) that it is functioning properly.
>
> Please let me know if you see any issues that concern you in its operation.
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] Gerrit Maintainer Plugin enabled for VPP

[Ed Warnicke]

Per our previous (admittedly long ago) discussions on the Gerrit Maintainer
Plugin auto adding reviewers based on the vpp MAINTAINERS file, it has now
been merged.  It *only* auto adds reviews, any action to be taken in terms
of merging a patch will, per agreement, at this time, still require a
committer's action.

I'll be pushing some test patches shortly to do a final confirmation (and
revert if any of them failed) that it is functioning properly.

Please let me know if you see any issues that concern you in its operation.
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Icmp support in Stateful ACL

[Ed Warnicke]

Andrew,
 Could you have a look?

Ed

On Mon, Sep 11, 2017 at 2:37 AM, chore  wrote:

> Dear Team
>
> I had a commit in acl plugin to support Icmp proto in Stateful ACL. please
> kindly review the changes .
>
> Best Regards,
> Chore
>
> ___
> 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] Running CLI against named vpp instance

[Ed Warnicke]

Marek,

I don't think you have a local issue.  I think what is happening is that
the instructions for running multiple vpps has changed.

With the advent of the new C vppctl, which is using a different method:

sudo vpp api-segment { prefix vpp1 } unix { cli-listen
/run/vpp/cli.vpp1.sock }

(In the example above I arbitrarily chose the cli-listen socket name... you
can pick whatever you want as long as its unique among the set of vpps you
are running).

Then to address it with vppctl you'd use:

vppctl -s /run/vpp/cli.vpp1.sock

essentially -s is replacing -p.

Please note, the above is based on Wallace's excellent description in this
thread, I have not yet tried it, and would be grateful if you would do so
and tell me if it works :)

Ed

On Thu, Sep 7, 2017 at 1:00 AM, Marek Gradzki -X (mgradzki - PANTHEON
TECHNOLOGIES at Cisco) <mgrad...@cisco.com> wrote:

> Dave, Ed
>
>
>
> with 17.07 I was able to run two vpp instances and connect CLI to them as
> described here:
>
> https://wiki.fd.io/view/VPP/Progressive_VPP_Tutorial#Action:_Run_vpp
>
>
>
> So one needed just to specify prefix when starting vpp and vppctl.
>
> There was no need to do any other configuration changes.
>
>
>
> With current master (both build locally or using most recent ub16 packages)
>
> it does not work for me.
>
>
>
> I also tired explicitly specifying cfg files with different sockets,
>
> Api segments + corresponding vppctl parameters (-p, -s)
>
> + some combinations.
>
>
>
> It is possible I have some local issue,
>
> so I would be grateful if you could share config that works for you.
>
>
>
> Thanks,
>
> Marek
>
>
>
> *From:* Dave Wallace [mailto:dwallac...@gmail.com]
> *Sent:* 6 września 2017 18:07
> *To:* Ed Warnicke <hagb...@gmail.com>
> *Cc:* Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <
> mgrad...@cisco.com>; vpp-dev@lists.fd.io
>
> *Subject:* Re: [vpp-dev] Running CLI against named vpp instance
>
>
>
> Ed,
>
> vppctl already has a command line arg (-s) which allows the user to
> specify a specific socket pathname which must be the same as the
> "cli-listen " configuration in a given vpp instance.  Adding a
> naming convention to both vpp and vppctl is going to over-complicate the
> matter.
>
> Thanks,
> -daw-
>
>
> On 09/06/2017 11:01 AM, Ed Warnicke wrote:
>
> Dave,
>
>
>
> I think we would need to be sure that different vpp instances have
> different cli-listen socket files, and that vppctl has a mechanism to
> address them easily.
>
>
>
> I'd suggest a pattern like
>
>
>
> "unix { cli-listen /run/vpp.cli-${prefix}.sock"
>
>
>
> and
>
>
>
> vppctl -p ${prefix}
>
>
>
> to be in line with current usage.
>
>
>
> Ed
>
>
>
>
>
>
>
>
>
> On Wed, Sep 6, 2017 at 7:50 AM, Dave Wallace <dwallac...@gmail.com> wrote:
>
> Marek,
>
> Please check the vpp startup configuration (/etc/vpp/startup.conf) to
> ensure that "unix { cli-listen /run/vpp/cli.sock }" is present.  This is
> the default socket used by the 'c' implementation of vppctl.
>
> I'm going to fix the error message to output the socket file name to make
> this easier to debug.
>
> Thanks,
> -daw-
>
>
>
> On 09/06/2017 05:55 AM, Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES
> at Cisco) wrote:
>
> Dave,
>
>
>
> please find replies inline.
>
>
>
> *From:* Dave Wallace [mailto:dwallac...@gmail.com <dwallac...@gmail.com>]
> *Sent:* 5 września 2017 16:41
> *To:* Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)
> <mgrad...@cisco.com> <mgrad...@cisco.com>; vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] Running CLI against named vpp instance
>
>
>
> Marek,
>
> What is the uid/gid of /dev/shm/vpe-api ?
>
> root/vpp
>
> Is the user a member of the vpp group?
> yes
>
>
> Does your VPP workspace include the patch c900ccc34 "Enabled gid vpp in
> startup.conf to allow non-root vppctl access" ?
> yes (I’ve built master with HEAD @ 809bc74, also tested corresponding
> package from nexus)
>
>
> Thanks,
> -daw-
>
> On 09/05/2017 06:08 AM, Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES
> at Cisco) wrote:
>
> Hi,
>
>
>
> I am having problems with running CLI against named vpp instance
> (g809bc74):
>
>
>
> sudo vpp api-segment { prefix vpp0 }
>
>
>
> sudo vppctl -p vpp0 show int
>
> clib_socket_init: connect: Connection refused
>
>
>
> But ps shows vpp process is running.
>
>
>
> It worked with 17.07.
>
> Is it no longer supported or I need some additional configuration?
>
>
>
> Regards,
>
> Marek
>
>
>
> ___
>
> 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

Re: [vpp-dev] Running CLI against named vpp instance

[Ed Warnicke]

All good.  As long as we have a consistent way to handle it on both sides,
I'm good :)

Ed

On Wed, Sep 6, 2017 at 9:06 AM, Dave Wallace <dwallac...@gmail.com> wrote:

> Ed,
>
> vppctl already has a command line arg (-s) which allows the user to
> specify a specific socket pathname which must be the same as the
> "cli-listen " configuration in a given vpp instance.  Adding a
> naming convention to both vpp and vppctl is going to over-complicate the
> matter.
>
> Thanks,
> -daw-
>
>
>
> On 09/06/2017 11:01 AM, Ed Warnicke wrote:
>
> Dave,
>
> I think we would need to be sure that different vpp instances have
> different cli-listen socket files, and that vppctl has a mechanism to
> address them easily.
>
> I'd suggest a pattern like
>
> "unix { cli-listen /run/vpp.cli-${prefix}.sock"
>
> and
>
> vppctl -p ${prefix}
>
> to be in line with current usage.
>
> Ed
>
>
>
>
> On Wed, Sep 6, 2017 at 7:50 AM, Dave Wallace <dwallac...@gmail.com> wrote:
>
>> Marek,
>>
>> Please check the vpp startup configuration (/etc/vpp/startup.conf) to
>> ensure that "unix { cli-listen /run/vpp/cli.sock }" is present.  This is
>> the default socket used by the 'c' implementation of vppctl.
>>
>> I'm going to fix the error message to output the socket file name to make
>> this easier to debug.
>>
>> Thanks,
>> -daw-
>>
>> On 09/06/2017 05:55 AM, Marek Gradzki -X (mgradzki - PANTHEON
>> TECHNOLOGIES at Cisco) wrote:
>>
>> Dave,
>>
>>
>>
>> please find replies inline.
>>
>>
>>
>> *From:* Dave Wallace [mailto:dwallac...@gmail.com <dwallac...@gmail.com>]
>>
>> *Sent:* 5 września 2017 16:41
>> *To:* Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)
>> <mgrad...@cisco.com> <mgrad...@cisco.com>; vpp-dev@lists.fd.io
>> *Subject:* Re: [vpp-dev] Running CLI against named vpp instance
>>
>>
>>
>> Marek,
>>
>> What is the uid/gid of /dev/shm/vpe-api ?
>>
>> root/vpp
>>
>> Is the user a member of the vpp group?
>> yes
>>
>>
>> Does your VPP workspace include the patch c900ccc34 "Enabled gid vpp in
>> startup.conf to allow non-root vppctl access" ?
>> yes (I’ve built master with HEAD @ 809bc74, also tested corresponding
>> package from nexus)
>>
>>
>> Thanks,
>> -daw-
>>
>> On 09/05/2017 06:08 AM, Marek Gradzki -X (mgradzki - PANTHEON
>> TECHNOLOGIES at Cisco) wrote:
>>
>> Hi,
>>
>>
>>
>> I am having problems with running CLI against named vpp instance
>> (g809bc74):
>>
>>
>>
>> sudo vpp api-segment { prefix vpp0 }
>>
>>
>>
>> sudo vppctl -p vpp0 show int
>>
>> clib_socket_init: connect: Connection refused
>>
>>
>>
>> But ps shows vpp process is running.
>>
>>
>>
>> It worked with 17.07.
>>
>> Is it no longer supported or I need some additional configuration?
>>
>>
>>
>> Regards,
>>
>> Marek
>>
>>
>>
>>
>> ___
>>
>> 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

Re: [vpp-dev] Running CLI against named vpp instance

[Ed Warnicke]

Dave,

I think we would need to be sure that different vpp instances have
different cli-listen socket files, and that vppctl has a mechanism to
address them easily.

I'd suggest a pattern like

"unix { cli-listen /run/vpp.cli-${prefix}.sock"

and

vppctl -p ${prefix}

to be in line with current usage.

Ed




On Wed, Sep 6, 2017 at 7:50 AM, Dave Wallace  wrote:

> Marek,
>
> Please check the vpp startup configuration (/etc/vpp/startup.conf) to
> ensure that "unix { cli-listen /run/vpp/cli.sock }" is present.  This is
> the default socket used by the 'c' implementation of vppctl.
>
> I'm going to fix the error message to output the socket file name to make
> this easier to debug.
>
> Thanks,
> -daw-
>
> On 09/06/2017 05:55 AM, Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES
> at Cisco) wrote:
>
> Dave,
>
>
>
> please find replies inline.
>
>
>
> *From:* Dave Wallace [mailto:dwallac...@gmail.com ]
> *Sent:* 5 września 2017 16:41
> *To:* Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)
>  ; vpp-dev@lists.fd.io
> *Subject:* Re: [vpp-dev] Running CLI against named vpp instance
>
>
>
> Marek,
>
> What is the uid/gid of /dev/shm/vpe-api ?
>
> root/vpp
>
> Is the user a member of the vpp group?
> yes
>
>
> Does your VPP workspace include the patch c900ccc34 "Enabled gid vpp in
> startup.conf to allow non-root vppctl access" ?
> yes (I’ve built master with HEAD @ 809bc74, also tested corresponding
> package from nexus)
>
>
> Thanks,
> -daw-
>
> On 09/05/2017 06:08 AM, Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES
> at Cisco) wrote:
>
> Hi,
>
>
>
> I am having problems with running CLI against named vpp instance
> (g809bc74):
>
>
>
> sudo vpp api-segment { prefix vpp0 }
>
>
>
> sudo vppctl -p vpp0 show int
>
> clib_socket_init: connect: Connection refused
>
>
>
> But ps shows vpp process is running.
>
>
>
> It worked with 17.07.
>
> Is it no longer supported or I need some additional configuration?
>
>
>
> Regards,
>
> Marek
>
>
>
>
> ___
>
> 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

Re: [vpp-dev] VPP S-NAT rename

[Ed Warnicke]

Overall, I think the rename is a good idea.  The Linux guys are used to
thinking of SNAT as source NAT and DNAT as destination NAT.

Ed

On Mon, Aug 21, 2017 at 12:53 AM, Marek Gradzki -X (mgradzki - PANTHEON
TECHNOLOGIES at Cisco)  wrote:

> Hi,
>
> Hc2vpp uses SNAT API. The rename you suggest is very simple (I guess
> snat->nat44),
> so we will not mind if there will be no parallel API.
>
> Regards,
> Marek
>
> -Original Message-
> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
> Behalf Of Ole Troan
> Sent: 21 sierpnia 2017 09:40
> To: vpp-dev 
> Subject: [vpp-dev] VPP S-NAT rename
>
> Hi,
>
> The 'S' in VPP's S-NAT plugin name has often been confused with Linux'
> "Source NAT". The 'S' originally stood for "Simple", implying that it was a
> less complex implementation of NAT than the previous VCGN implementation.
>
> Because of this confusion (and possibly valid arguments that it isn't so
> simple anymore) we'd like to rename it.
> The feature supports all flavours of NAT44 and NAT64.
>
> The suggested new name is simply NAT. I.e. "VPP NAT".
>
> The proposal is to change the name in the wiki, documentation,
> folder/files and CLI.
> I am unsure if it is possible to change the API at this point. We might
> have to put in the new message names and allow those to live in parallel
> with the old ones for a release or two. Does anyone use the SNAT API?
>
> Opinions?
>
> Best regards,
> Ole
> ___
> 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] Verify jobs failing - opensuse

[Ed Warnicke]

If one of you would push a revert of: https://gerrit.fd.io/r/#/c/7998/

I'd be happy to merge it.

Ed

On Sat, Aug 12, 2017 at 1:17 PM, Florin Coras 
wrote:

> I second the request. It would be really helpful to have this fixed by
> Monday morning, CEST time.
>
> Thanks,
> Florin
>
> > On Aug 12, 2017, at 8:28 AM, Neale Ranns (nranns) 
> wrote:
> >
> >
> > Hi All,
> >
> > The verify jobs are failing due to the new opensuse job, e.g. from:
> >  https://gerrit.fd.io/r/#/c/8001/
> > error is below.
> >
> > Can we please fix ASAP or disable them.
> >
> > Thanks,
> > Neale
> >
> >
> > 18:49:56 [vpp-verify-master-opensuse] $ /bin/bash /tmp/
> hudson7746568270930707597.sh
> > 18:49:56 make[1]: Entering directory '/w/workspace/vpp-verify-
> master-opensuse/test'
> > 18:49:56 make[1]: virtualenv: Command not found
> > 18:49:56 Makefile:159: recipe for target 'checkstyle' failed
> > 18:49:56 make[1]: *** [checkstyle] Error 127
> > 18:49:56 make[1]: Leaving directory '/w/workspace/vpp-verify-
> master-opensuse/test'
> > 18:49:56 Makefile:379: recipe for target 'test-checkstyle' failed
> > 18:49:56 make: *** [test-checkstyle] Error 2
> > 18:49:56 Build step 'Execute shell' marked build as failure
> >
> >
> > ___
> > 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

Re: [vpp-dev] Can't install honeycomb master package from nexus on xenial

[Ed Warnicke]

Do the honeycomb 17.10 packages depend on the release vpp 17.10 packages?

Ed

On Tue, Aug 1, 2017 at 5:20 AM, Lori Jakab 
wrote:

> On Tue, Aug 1, 2017 at 1:46 PM, Jan Srnicek -X (jsrnicek - PANTHEON
> TECHNOLOGIES at Cisco)  wrote:
>
>> Hi lori
>>
>>
>>
>> This is known issue with apt-get , as honeycomb packages have compatible
>> vpp version defined ,but apt-get attempts to download the newest one.
>>
>>
>>
>> To solve this , you need to first install vpp like so:
>>
>>
>>
>> sudo apt-get install vpp=VERSION vpp-lib= VERSION vpp-plugins= VERSION
>>
>>
>>
>> and then install honeycomb
>>
>
> I have the installation as part of a script of a Vagrantfile, so I prefer
> not to hardcode version numbers, but having seen the "Merge job failing"
> thread you started confirms that this is an anomaly, and it will get fixed
> eventually.
>
> Thanks!
>
> -Lori
>
>
>>
>>
>> [image: banner11]
>>
>>
>>
>> *Jan Srnicek*
>>
>> Engineer - Software
>>
>> jsrni...@cisco.com
>>
>> Tel:
>>
>> *Cisco Systems, Inc.*
>>
>>
>>
>>
>> Slovakia
>> cisco.com
>>
>>
>>
>> [image: http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think
>> before you print.
>>
>> This email may contain confidential and privileged material for the sole
>> use of the intended recipient. Any review, use, distribution or disclosure
>> by others is strictly prohibited. If you are not the intended recipient (or
>> authorized to receive for the recipient), please contact the sender by
>> reply email and delete all copies of this message.
>>
>> Please click here
>>  for
>> Company Registration Information.
>>
>>
>>
>> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
>> Behalf Of *Lori Jakab
>> *Sent:* Tuesday, August 1, 2017 10:08 AM
>> *To:* vpp-dev@lists.fd.io; hc2vpp-...@lists.fd.io
>> *Cc:* Florin Coras (fcoras) 
>> *Subject:* [vpp-dev] Can't install honeycomb master package from nexus
>> on xenial
>>
>>
>>
>> Hi,
>>
>>
>>
>> I'm trying to install honeycomb on Ubuntu Xenial, after having added '
>> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main'
>> to the repository list. When installing honeycomb, I get the following
>> error:
>>
>>
>>
>> The following packages have unmet dependencies:
>>
>>  honeycomb : Depends: vpp (= 17.10-rc0~95-g6881062~b2627) but
>> 17.10-rc0~101-g5b31120~b2635 is to be installed
>>
>>  Depends: vpp-plugins (= 17.10-rc0~95-g6881062~b2627) but
>> 17.10-rc0~101-g5b31120~b2635 is to be installed
>>
>>
>>
>> Is there an easy way to solve this? Maybe a honeycomb artifact
>> publication job is failing?
>>
>>
>>
>> Thanks,
>>
>> -Lori
>>
>
>
> ___
> 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] Merge job failing

[Ed Warnicke]

That one is my fault.  Should now be fixed.  Running a remerge to confirm.

Ed

On Tue, Aug 1, 2017 at 6:31 AM, Luke, Chris  wrote:

> One failed because a test didn’t receive packets on pg0; possibly a fluke
>
>
>
> Two failed because:
>
>
>
> *16:15:11* Using https://packagecloud.io with token:**
>
> *16:15:11* Looking for repository at fdio/master... failed!
>
> *16:15:11* Build step 'Execute shell' marked build as failure
>
>
>
> I suspect this last is the real issue; don’t we normally use the name of
> the next release for this sort of thing, rather than ‘master’?
>
>
>
> Chris.
>
>
>
> *From: *"Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco)" <
> jsrni...@cisco.com>
> *Date: *Tuesday, August 1, 2017 at 07:16
> *To: *Chris Luke , vpp-dev <
> vpp-dev@lists.fd.io>
> *Cc: *"Peter Lapos -X (plapos - PANTHEON TECHNOLOGIES at Cisco)" <
> pla...@cisco.com>, "Samuel Elias -X (samelias - PANTHEON TECHNOLOGIES at
> Cisco)" 
> *Subject: *RE: [vpp-dev] Merge job failing
>
>
>
> This is the first run that failed
>
>
>
> https://jenkins.fd.io/job/vpp-merge-master-ubuntu1604/2628/
>
>
>
> [image: anner11]
>
>
>
> *Jan Srnicek*
>
> Engineer - Software
>
> jsrni...@cisco.com
>
> Tel:
>
> *Cisco Systems, Inc.*
>
>
>
>
> Slovakia
> cisco.com
>
>
>
> [image: ttp://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think
> before you print.
>
> This email may contain confidential and privileged material for the sole
> use of the intended recipient. Any review, use, distribution or disclosure
> by others is strictly prohibited. If you are not the intended recipient (or
> authorized to receive for the recipient), please contact the sender by
> reply email and delete all copies of this message.
>
> Please click here
>  for
> Company Registration Information.
>
>
>
> *From:* Luke, Chris [mailto:chris_l...@comcast.com]
> *Sent:* Tuesday, August 1, 2017 3:10 PM
> *To:* Jan Srnicek -X (jsrnicek - PANTHEON TECHNOLOGIES at Cisco) <
> jsrni...@cisco.com>; vpp-dev 
> *Cc:* Peter Lapos -X (plapos - PANTHEON TECHNOLOGIES at Cisco) <
> pla...@cisco.com>; Samuel Elias -X (samelias - PANTHEON TECHNOLOGIES at
> Cisco) 
> *Subject:* Re: [vpp-dev] Merge job failing
>
>
>
> When did that start? We re-instated the hook that builds docs after the
> Ubuntu merge job finishes; possibly related?
>
>
>
> It seems to work fine on the stable branch.
>
>
>
> Chris
>
>
>
> *From: * on behalf of "Jan Srnicek -X
> (jsrnicek - PANTHEON TECHNOLOGIES at Cisco)" 
> *Date: *Tuesday, August 1, 2017 at 04:36
> *To: *vpp-dev 
> *Cc: *"Peter Lapos -X (plapos - PANTHEON TECHNOLOGIES at Cisco)" <
> pla...@cisco.com>, "Samuel Elias -X (samelias - PANTHEON TECHNOLOGIES at
> Cisco)" 
> *Subject: *[vpp-dev] Merge job failing
>
>
>
> Hi everyone
>
>
>
> Can somebody please look at vpp-merge jobs ? (https://jenkins.fd.io/job/
> vpp-merge-master-ubuntu1604/ , https://jenkins.fd.io/job/vpp-
> merge-master-centos7/)
>
> They failed on last 8 occasions, which also translates to honeycomb
> integration jobs not beeing triggered which prevents deb/rpm packages to be
> published correctly.
>
>
>
> [image: nner11]
>
>
>
> *Jan Srnicek*
>
> Engineer - Software
>
> jsrni...@cisco.com
>
> Tel:
>
> *Cisco Systems, Inc.*
>
>
>
>
> Slovakia
> cisco.com
>
>
>
> [image: tp://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think
> before you print.
>
> This email may contain confidential and privileged material for the sole
> use of the intended recipient. Any review, use, distribution or disclosure
> by others is strictly prohibited. If you are not the intended recipient (or
> authorized to receive for the recipient), please contact the sender by
> reply email and delete all copies of this message.
>
> Please click here
>  for
> Company Registration Information.
>
>
>
> ___
> 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] 17.07 Release

[Ed Warnicke]

Many thanks to Neale for his hard work here :)

Ed

On Thu, Jul 20, 2017 at 4:56 PM, Neale Ranns (nranns) 
wrote:

>
> Dear VPP community,
>
> The VPP 17.07 release is complete. The release artefacts are now available
> on the nexus server.
>
> I’d like to take this opportunity to thank you all for your continued
> support for VPP.
>
> Best regards,
> Neale
>
>
> ___
> 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

[vpp-dev] VPP Terabit Performance at Scale

[Ed Warnicke]

Big announcement today, VPP is posting Terabit performance numbers:

https://fd.io/2017/07/fd-io-breaking-the-terabit-barrier/

Many thanks to Maciek and the CSIT team who did a lot of work on the
benchmarking/video/slides at the bottom of the post :)

And many thanks to all the vpp developers who have made this level of
performance at scale possible.

Ed
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] FYI... revamp of the fd.io website launched

[Ed Warnicke]

https://fd.io/

Ed
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] C Rewrite of vppctl and 1707

[Ed Warnicke]

Many thanks :)

Ed

On Thu, Jul 6, 2017 at 9:59 AM, Neale Ranns (nranns) <nra...@cisco.com>
wrote:

>
>
> Merged.
>
>
>
> Thanks,
>
> neale
>
>
>
> *From: *<vpp-dev-boun...@lists.fd.io> on behalf of Ed Warnicke <
> hagb...@gmail.com>
> *Date: *Thursday, 6 July 2017 at 17:06
> *To: *vpp-dev <vpp-dev@lists.fd.io>
> *Subject: *Re: [vpp-dev] C Rewrite of vppctl and 1707
>
>
>
> I've pushed https://gerrit.fd.io/r/#/c/7446/ to fix the vppctl sudo issue
> in 1707.
>
>
>
> Ed
>
>
>
> On Wed, Jul 5, 2017 at 6:29 PM, Ed Warnicke <hagb...@gmail.com> wrote:
>
> Guys,
>
>
>
> I just noticed that https://gerrit.fd.io/r/#/c/7230/ (C Rewrite of
> vppctl) went into master after the stable/1707 branch was pulled.  Do we
> intend to defer that to 17.10?
>
>
>
> If we intend to defer the C rewrite of vppctl to 17.10, I'd like to get
> the fix in to the python vppctl in 17.07 so that it doesn't require
> sudo access.
>
>
>
> Ed
>
>
>
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] C Rewrite of vppctl and 1707

[Ed Warnicke]

I've pushed https://gerrit.fd.io/r/#/c/7446/ to fix the vppctl sudo issue
in 1707.

Ed

On Wed, Jul 5, 2017 at 6:29 PM, Ed Warnicke <hagb...@gmail.com> wrote:

> Guys,
>
> I just noticed that https://gerrit.fd.io/r/#/c/7230/ (C Rewrite of
> vppctl) went into master after the stable/1707 branch was pulled.  Do we
> intend to defer that to 17.10?
>
> If we intend to defer the C rewrite of vppctl to 17.10, I'd like to get
> the fix in to the python vppctl in 17.07 so that it doesn't require
> sudo access.
>
> Ed
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] C Rewrite of vppctl and 1707

[Ed Warnicke]

Guys,

I just noticed that https://gerrit.fd.io/r/#/c/7230/ (C Rewrite of vppctl)
went into master after the stable/1707 branch was pulled.  Do we intend to
defer that to 17.10?

If we intend to defer the C rewrite of vppctl to 17.10, I'd like to get the
fix in to the python vppctl in 17.07 so that it doesn't require sudo access.

Ed
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] TWS call scheduled for 7/18 8am PDT / 11am EDT / 5pm CEST

[Ed Warnicke]

TWS updated here: https://wiki.fd.io/view/TWS and also on the fd.io
calendar:

https://calendar.google.com/calendar/embed?src=qpen2df76a954fieqdnc3avg0k%40group.calendar.google.com

Ed

On Wed, Jul 5, 2017 at 12:08 PM, Dave Barach (dbarach) 
wrote:

> Eric Ernst and Manohar Castelino will present their vpp integration with
> ClearContainer.
>
> Dial-in info will be added to https://wiki.fd.io/view/VPP/Meeting
> shortly...
>
> Thanks... Dave
>
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] PPPOE

[Ed Warnicke]

Hongjun,

That sounds good :)  Could you say more about your thoughts on control
plane?

Ed

On Sun, Jun 25, 2017 at 7:39 PM, Ni, Hongjun  wrote:

> To make it clear:
>
>
>
> The PPPoE plugin will contains fast path graph node and slow path graph
> node.
>
>
>
> The fast path graph node is for the data plane only and handle PPPoE
> session lookup, PPPoE decap and PPPoE encap.
>
>
>
> The slow path graph node will leverage existing control plane applications
> to handle the slow path traffics in the PPPoE discovery stage.
>
>
>
> Regards,
>
> Hongjun
>
>
>
> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
> Behalf Of *Ni, Hongjun
> *Sent:* Monday, June 26, 2017 10:23 AM
> *To:* yug...@telincn.com; Vincent Jardin 
>
> *Cc:* vpp-dev 
> *Subject:* Re: [vpp-dev] PPPOE
>
>
>
> Hi guys,
>
>
>
> We are developing PPPoE feature as a VPP plugin now, which plans to be
> upstreamed to VPP 17.10 release.
>
>
>
> Just let community know about this to avoid duplicate effort.
>
>
>
> Thanks,
>
> Hongjun
>
>
>
> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io
> ] *On Behalf Of *yug...@telincn.com
> *Sent:* Saturday, June 17, 2017 10:16 AM
> *To:* Vincent Jardin 
> *Cc:* vpp-dev 
> *Subject:* Re: [vpp-dev] PPPOE
>
>
>
> Hi，
>
> Linux's PPPoE is very slow on creating new session, i will figure that out.
>
>
>
> Thanks,
>
> Ewan
>
>
> --
>
> yug...@telincn.com
>
>
>
> *From:* Vincent Jardin 
>
> *Date:* 2017-06-17 04:29
>
> *To:* yug...@telincn.com
>
> *CC:* vpp-dev 
>
> *Subject:* Re: [vpp-dev] PPPOE
>
> FYI, 6WIND  provides a full PPP stack (L2TP, PPPoE) server and clients. It
>
> tooks years to develop it and unfortunately it has dependencies that
>
> prevent using it with VPP. But it works fine with DPDK. It is available
>
> both under source code or binary only but under specific licensing.
>
>
>
> But usually, most people are fine with Linux PPP, since most connections
>
> are slow (under 20Mbps), so why not using Linux?
>
>
>
>
>
> Le 16 juin 2017 7:53:44 PM Ole Troan  a écrit :
>
>
>
> >> Is there any plan to surpport pppoe?
>
> >
>
> > Not as far as I know.
>
> > Feel free to start a PPP project. You would need to implement some NCPs
> too.
>
> >
>
> > Cheers,
>
> > Ole
>
> >
>
> >
>
> >
>
> > --
>
> > ___
>
> > 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

Re: [vpp-dev] [discuss] Upcoming FD.io infra restarts

[Ed Warnicke]

Looping in the broader community as various release branch cutting is
happening this week.

Ed

On Mon, Jun 19, 2017 at 2:47 PM, Vanessa Valderrama <
vvalderr...@linuxfoundation.org> wrote:

> The Linux Foundation has been made aware of some extremely high priority
> security updates that will be getting released within the next 24 - 48
> hours. These updates are so critical that we will be taking immediate
> outage windows to apply them when they become available.
>
> This update will cause rolling restarts of the infrastructure as we do
> system reboots.
>
> An additional notice will go out prior to our starting this work and
> another when we complete it.
>
>
> ___
> discuss mailing list
> disc...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/discuss
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] State of the verify jobs

[Ed Warnicke]

We are still seeing the 'six' issue as of a few minutes ago:

https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/5699/console

Ed

On Thu, Jun 1, 2017 at 7:26 AM, Ed Kern (ejk) <e...@cisco.com> wrote:

> well as quickly as it came I no longer see this error on any build in the
> last three hours..
>
> One comment though Ed its not clear if its what WAS biting us here..
>
> I have a long history with deb/apt installed python packages (in this case
> python-six) ‘fighting’ with pip installed versions of packages
> over the last couple years alone (and varying wildly with the version of
> pip) this can manifest itself in any number of ways:
> a. pip not installing newer or prerequisite versions of a package because
> it refuses to ‘touch’ (aka remove) apt version of a package
> b. pip installing newer version but software still pointed at or favoring
> the older version.
> c. pip trying and failing (but thinking it succeeded) in removing deb
> installed version..
>
> imho.. take one ‘boat’ or the other and don’t straddle otherwise your
> bound to get wet.
>
> Ed
>
>
>
> On Jun 1, 2017, at 7:20 AM, Ed Warnicke <hagb...@gmail.com> wrote:
>
> Klement,
>
> It is an interesting question.  I presume however as we are installing
> things via pip that it could be an upstream change.
>
> Ed
>
> On Thu, Jun 1, 2017 at 12:37 AM, Klement Sekera -X (ksekera - PANTHEON
> TECHNOLOGIES at Cisco) <ksek...@cisco.com> wrote:
>
>> Hmm, system-wide modules will probably have no effect, as we use
>> virtualenv to install our own modules as needed as part of make test.
>>
>> I wonder why this suddenly fails, when it worked before?
>>
>> Quoting Ed Warnicke (2017-06-01 05:15:55)
>> >A brief probe patch indicates that we already have the latest
>> python 'six'
>> >module installed:
>> >[1]https://gerrit.fd.io/r/#/c/6966/
>> >[2]http://jenkins.ejkern.net:8080/job/vpp-verify-master-ubun
>> tu1604/581/console
>> >
>> >  02:59:03 python-six is already the newest version (1.10.0-3).
>> >
>> >  Ed
>> >
>> >On Wed, May 31, 2017 at 7:38 PM, Ed Warnicke <[3]hagb...@gmail.com>
>> wrote:
>> >
>> >  We've had some turbulence in the last couple of days.
>> >  We are back to triggering jobs correctly, but we appear to be
>> having an
>> >  issue with a missing python module that is causing issues for make
>> test:
>> >  [4]https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/56
>> 99/console
>> >  We are missing a module named '[5]six' that provides python2 and
>> python
>> >  3 compatibility. As a result several python module installs are
>> failing:
>> >  19:31:29   Copying subprocess32.egg-info to
>> >  build/bdist.linux-x86_64/wheel/subprocess32-3.2.7-py2.7.egg-info
>> >  19:31:29   running install_scripts
>> >  19:31:29   Traceback (most recent call last):
>> >  19:31:29 File "", line 1, in 
>> >  19:31:29 File "/tmp/pip-build-Yfbhm0/subprocess32/setup.py",
>> line
>> >  60, in 
>> >  19:31:29   main()
>> >  19:31:29 File "/tmp/pip-build-Yfbhm0/subprocess32/setup.py",
>> line
>> >  54, in main
>> >  19:31:29   'Programming Language :: Python :: Implementation ::
>> >  CPython',
>> >  19:31:29 File "/usr/lib/python2.7/distutils/core.py", line
>> 151, in
>> >  setup
>> >  19:31:29   dist.run_commands()
>> >  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line
>> 953, in
>> >  run_commands
>> >  19:31:29   self.run_command(cmd)
>> >  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line
>> 972, in
>> >  run_command
>> >  19:31:29   cmd_obj.run()
>> >  19:31:29 File
>> >  "/w/workspace/vpp-verify-master-ubuntu1604/build-root/python
>> /virtualenv/local/lib/python2.7/site-packages/wheel/bdist_wheel.py",
>> >  line 235, in run
>> >  19:31:29   self.run_command('install')
>> >  19:31:29 File "/usr/lib/python2.7/distutils/cmd.py", line
>> 326, in
>> >  run_command
>> >  19:31:29   self.distribution.run_command(command)
>> >  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line
>> 972, in
>> >  run_command
>> >  19:31:29  

Re: [vpp-dev] State of the verify jobs

[Ed Warnicke]

Klement,

It is an interesting question.  I presume however as we are installing
things via pip that it could be an upstream change.

Ed

On Thu, Jun 1, 2017 at 12:37 AM, Klement Sekera -X (ksekera - PANTHEON
TECHNOLOGIES at Cisco) <ksek...@cisco.com> wrote:

> Hmm, system-wide modules will probably have no effect, as we use
> virtualenv to install our own modules as needed as part of make test.
>
> I wonder why this suddenly fails, when it worked before?
>
> Quoting Ed Warnicke (2017-06-01 05:15:55)
> >A brief probe patch indicates that we already have the latest
> python 'six'
> >module installed:
> >[1]https://gerrit.fd.io/r/#/c/6966/
> >[2]http://jenkins.ejkern.net:8080/job/vpp-verify-master-
> ubuntu1604/581/console
> >
> >  02:59:03 python-six is already the newest version (1.10.0-3).
> >
> >  Ed
> >
> >On Wed, May 31, 2017 at 7:38 PM, Ed Warnicke <[3]hagb...@gmail.com>
> wrote:
> >
> >  We've had some turbulence in the last couple of days.
> >  We are back to triggering jobs correctly, but we appear to be
> having an
> >  issue with a missing python module that is causing issues for make
> test:
> >  [4]https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/
> 5699/console
> >  We are missing a module named '[5]six' that provides python2 and
> python
> >  3 compatibility. As a result several python module installs are
> failing:
> >  19:31:29   Copying subprocess32.egg-info to
> >  build/bdist.linux-x86_64/wheel/subprocess32-3.2.7-py2.7.egg-info
> >  19:31:29   running install_scripts
> >  19:31:29   Traceback (most recent call last):
> >  19:31:29 File "", line 1, in 
> >  19:31:29 File "/tmp/pip-build-Yfbhm0/subprocess32/setup.py",
> line
> >  60, in 
> >  19:31:29   main()
> >  19:31:29 File "/tmp/pip-build-Yfbhm0/subprocess32/setup.py",
> line
> >  54, in main
> >  19:31:29   'Programming Language :: Python :: Implementation ::
> >  CPython',
> >  19:31:29 File "/usr/lib/python2.7/distutils/core.py", line
> 151, in
> >  setup
> >  19:31:29   dist.run_commands()
> >  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line
> 953, in
> >  run_commands
> >  19:31:29   self.run_command(cmd)
> >  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line
> 972, in
> >  run_command
> >  19:31:29   cmd_obj.run()
> >  19:31:29 File
> >  "/w/workspace/vpp-verify-master-ubuntu1604/build-root/
> python/virtualenv/local/lib/python2.7/site-packages/wheel/bdist_wheel.py",
> >  line 235, in run
> >  19:31:29   self.run_command('install')
> >  19:31:29 File "/usr/lib/python2.7/distutils/cmd.py", line 326,
> in
> >  run_command
> >  19:31:29   self.distribution.run_command(command)
> >  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line
> 972, in
> >  run_command
> >  19:31:29   cmd_obj.run()
> >  19:31:29 File
> >  "/w/workspace/vpp-verify-master-ubuntu1604/build-root/
> python/virtualenv/local/lib/python2.7/site-packages/
> setuptools/command/install.py",
> >  line 61, in run
> >  19:31:29   return orig.install.run(self)
> >  19:31:29 File "/usr/lib/python2.7/distutils/
> command/install.py",
> >  line 613, in run
> >  19:31:29   self.run_command(cmd_name)
> >  19:31:29 File "/usr/lib/python2.7/distutils/cmd.py", line 326,
> in
> >  run_command
> >  19:31:29   self.distribution.run_command(command)
> >  19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line
> 972, in
> >  run_command
> >  19:31:29   cmd_obj.run()
> >  19:31:29 File
> >  "/w/workspace/vpp-verify-master-ubuntu1604/build-root/
> python/virtualenv/local/lib/python2.7/site-packages/
> setuptools/command/install_scripts.py",
> >  line 17, in run
> >  19:31:29   import setuptools.command.easy_install as ei
> >  19:31:29 File
> >  "/w/workspace/vpp-verify-master-ubuntu1604/build-root/
> python/virtualenv/local/lib/python2.7/site-packages/
> setuptools/command/easy_install.py",
> >  line 49, in 
> >  19:31:29   from setuptools.py27compat import rmtree_safe
> >  19:31:29 File
> >  "/w/w

Re: [vpp-dev] State of the verify jobs

[Ed Warnicke]

A brief probe patch indicates that we already have the latest python 'six'
module installed:

https://gerrit.fd.io/r/#/c/6966/
http://jenkins.ejkern.net:8080/job/vpp-verify-master-ubuntu1604/581/console

*02:59:03* python-six is already the newest version (1.10.0-3).


Ed


On Wed, May 31, 2017 at 7:38 PM, Ed Warnicke <hagb...@gmail.com> wrote:

> We've had some turbulence in the last couple of days.
>
> We are back to triggering jobs correctly, but we appear to be having an
> issue with a missing python module that is causing issues for make test:
>
> https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/5699/console
>
> We are missing a module named 'six <https://pypi.python.org/pypi/six>'
> that provides python2 and python 3 compatibility. As a result several
> python module installs are failing:
>
> 19:31:29   Copying subprocess32.egg-info to build/bdist.linux-x86_64/
> wheel/subprocess32-3.2.7-py2.7.egg-info
> 19:31:29   running install_scripts
> 19:31:29   Traceback (most recent call last):
> 19:31:29 File "", line 1, in 
> 19:31:29 File "/tmp/pip-build-Yfbhm0/subprocess32/setup.py", line 60,
> in 
> 19:31:29   main()
> 19:31:29 File "/tmp/pip-build-Yfbhm0/subprocess32/setup.py", line 54,
> in main
> 19:31:29   'Programming Language :: Python :: Implementation ::
> CPython',
> 19:31:29 File "/usr/lib/python2.7/distutils/core.py", line 151, in
> setup
> 19:31:29   dist.run_commands()
> 19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line 953, in
> run_commands
> 19:31:29   self.run_command(cmd)
> 19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line 972, in
> run_command
> 19:31:29   cmd_obj.run()
> 19:31:29 File "/w/workspace/vpp-verify-master-ubuntu1604/build-root/
> python/virtualenv/local/lib/python2.7/site-packages/wheel/bdist_wheel.py",
> line 235, in run
> 19:31:29   self.run_command('install')
> 19:31:29 File "/usr/lib/python2.7/distutils/cmd.py", line 326, in
> run_command
> 19:31:29   self.distribution.run_command(command)
> 19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line 972, in
> run_command
> 19:31:29   cmd_obj.run()
> 19:31:29 File "/w/workspace/vpp-verify-master-ubuntu1604/build-root/
> python/virtualenv/local/lib/python2.7/site-packages/
> setuptools/command/install.py", line 61, in run
> 19:31:29   return orig.install.run(self)
> 19:31:29 File "/usr/lib/python2.7/distutils/command/install.py", line
> 613, in run
> 19:31:29   self.run_command(cmd_name)
> 19:31:29 File "/usr/lib/python2.7/distutils/cmd.py", line 326, in
> run_command
> 19:31:29   self.distribution.run_command(command)
> 19:31:29 File "/usr/lib/python2.7/distutils/dist.py", line 972, in
> run_command
> 19:31:29   cmd_obj.run()
> 19:31:29 File "/w/workspace/vpp-verify-master-ubuntu1604/build-root/
> python/virtualenv/local/lib/python2.7/site-packages/
> setuptools/command/install_scripts.py", line 17, in run
> 19:31:29   import setuptools.command.easy_install as ei
> 19:31:29 File "/w/workspace/vpp-verify-master-ubuntu1604/build-root/
> python/virtualenv/local/lib/python2.7/site-packages/
> setuptools/command/easy_install.py", line 49, in 
> 19:31:29   from setuptools.py27compat import rmtree_safe
> 19:31:29 File "/w/workspace/vpp-verify-master-ubuntu1604/build-root/
> python/virtualenv/local/lib/python2.7/site-packages/setuptools/py27compat.py",
> line 7, in 
> 19:31:29   import six
> 19:31:29   ImportError: No module named six
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [csit-dev] [FD.io Helpdesk #41298] Jobs are not triggered from gerrit

[Ed Warnicke]

Anton,
  We are getting patches not triggering again:

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

Ed

On Wed, May 31, 2017 at 7:49 AM, Anton Baranov via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> Jan:
>
> Unfortunately there is nothing in the logs that indicates the root cause
> of the problem. Our guess is that Gerrit Trigger plugin just crushed and
> caused jobs not being triggered properly
>
> --
> Anton Baranov
> Systems and Network Administrator
> The Linux Foundation
>
>
> On Wed May 31 10:10:04 2017, jgel...@cisco.com wrote:
> > Hello Anton,
> >
> > Do you know, please, what was the root cause and how we can avoid such
> > situation in the future?
> >
> > Thanks,
> > Jan
> >
> > -Original Message-
> >  From: Anton Baranov via RT [mailto:fdio-
> > helpd...@rt.linuxfoundation.org]
> > Sent: Wednesday, May 31, 2017 16:03
> > To: Jan Gelety -X (jgelety - PANTHEON TECHNOLOGIES at Cisco)
> > 
> > Cc: csit-...@lists.fd.io; vpp-dev@lists.fd.io
> > Subject: [FD.io Helpdesk #41298] Jobs are not triggered from gerrit
> >
> > We triggered rechecks for two gerrit changes:
> > - https://gerrit.fd.io/r/#/c/6806/2
> > - https://gerrit.fd.io/r/#/c/6912/2
> >
> > Regards,
> >
> > On Wed May 31 09:58:32 2017, hagbard wrote:
> > > What did you do to confirm triggers are now happening?
> > >
> > > Ed
> > >
> > > On Wed, May 31, 2017 at 6:55 AM, Anton Baranov via RT <
> > > fdio-helpd...@rt.linuxfoundation.org> wrote:
> > >
> > > > Hello,
> > > >
> > > > We restarted jenkins service and that fixed jobs triggering.
> > > >
> > > > Best regards,
> > > > --
> > > > Anton Baranov
> > > > Systems and Network Administrator
> > > > The Linux Foundation
> > > >
> > > >
> > > > On Wed May 31 09:20:26 2017, abaranov wrote:
> > > > > Hello,
> > > > >
> > > > > We're checking that issue right now  and will keep you updated
> > > > >
> > > > > Thanks,
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > ___
> > > > vpp-dev mailing list
> > > > vpp-dev@lists.fd.io
> > > > https://lists.fd.io/mailman/listinfo/vpp-dev
> > > >
> >
> >
> > --
> > Anton Baranov
> > Systems and Network Administrator
> > The Linux Foundation
>
>
>
> ___
> 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] [FD.io Helpdesk #41298] Jobs are not triggered from gerrit

[Ed Warnicke via RT]

Anton,

How would we automate monitoring for this case in the future?

Ed

On Wed, May 31, 2017 at 7:49 AM, Anton Baranov via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> Jan:
>
> Unfortunately there is nothing in the logs that indicates the root cause
> of the problem. Our guess is that Gerrit Trigger plugin just crushed and
> caused jobs not being triggered properly
>
> --
> Anton Baranov
> Systems and Network Administrator
> The Linux Foundation
>
>
> On Wed May 31 10:10:04 2017, jgel...@cisco.com wrote:
> > Hello Anton,
> >
> > Do you know, please, what was the root cause and how we can avoid such
> > situation in the future?
> >
> > Thanks,
> > Jan
> >
> > -Original Message-
> >  From: Anton Baranov via RT [mailto:fdio-
> > helpd...@rt.linuxfoundation.org]
> > Sent: Wednesday, May 31, 2017 16:03
> > To: Jan Gelety -X (jgelety - PANTHEON TECHNOLOGIES at Cisco)
> > 
> > Cc: csit-...@lists.fd.io; vpp-dev@lists.fd.io
> > Subject: [FD.io Helpdesk #41298] Jobs are not triggered from gerrit
> >
> > We triggered rechecks for two gerrit changes:
> > - https://gerrit.fd.io/r/#/c/6806/2
> > - https://gerrit.fd.io/r/#/c/6912/2
> >
> > Regards,
> >
> > On Wed May 31 09:58:32 2017, hagbard wrote:
> > > What did you do to confirm triggers are now happening?
> > >
> > > Ed
> > >
> > > On Wed, May 31, 2017 at 6:55 AM, Anton Baranov via RT <
> > > fdio-helpd...@rt.linuxfoundation.org> wrote:
> > >
> > > > Hello,
> > > >
> > > > We restarted jenkins service and that fixed jobs triggering.
> > > >
> > > > Best regards,
> > > > --
> > > > Anton Baranov
> > > > Systems and Network Administrator
> > > > The Linux Foundation
> > > >
> > > >
> > > > On Wed May 31 09:20:26 2017, abaranov wrote:
> > > > > Hello,
> > > > >
> > > > > We're checking that issue right now  and will keep you updated
> > > > >
> > > > > Thanks,
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > ___
> > > > vpp-dev mailing list
> > > > vpp-dev@lists.fd.io
> > > > https://lists.fd.io/mailman/listinfo/vpp-dev
> > > >
> >
> >
> > --
> > Anton Baranov
> > Systems and Network Administrator
> > The Linux Foundation
>
>
>
> ___
> 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] [FD.io Helpdesk #41298] Jobs are not triggered from gerrit

[Ed Warnicke]

Anton,

How would we automate monitoring for this case in the future?

Ed

On Wed, May 31, 2017 at 7:49 AM, Anton Baranov via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> Jan:
>
> Unfortunately there is nothing in the logs that indicates the root cause
> of the problem. Our guess is that Gerrit Trigger plugin just crushed and
> caused jobs not being triggered properly
>
> --
> Anton Baranov
> Systems and Network Administrator
> The Linux Foundation
>
>
> On Wed May 31 10:10:04 2017, jgel...@cisco.com wrote:
> > Hello Anton,
> >
> > Do you know, please, what was the root cause and how we can avoid such
> > situation in the future?
> >
> > Thanks,
> > Jan
> >
> > -Original Message-
> >  From: Anton Baranov via RT [mailto:fdio-
> > helpd...@rt.linuxfoundation.org]
> > Sent: Wednesday, May 31, 2017 16:03
> > To: Jan Gelety -X (jgelety - PANTHEON TECHNOLOGIES at Cisco)
> > 
> > Cc: csit-...@lists.fd.io; vpp-dev@lists.fd.io
> > Subject: [FD.io Helpdesk #41298] Jobs are not triggered from gerrit
> >
> > We triggered rechecks for two gerrit changes:
> > - https://gerrit.fd.io/r/#/c/6806/2
> > - https://gerrit.fd.io/r/#/c/6912/2
> >
> > Regards,
> >
> > On Wed May 31 09:58:32 2017, hagbard wrote:
> > > What did you do to confirm triggers are now happening?
> > >
> > > Ed
> > >
> > > On Wed, May 31, 2017 at 6:55 AM, Anton Baranov via RT <
> > > fdio-helpd...@rt.linuxfoundation.org> wrote:
> > >
> > > > Hello,
> > > >
> > > > We restarted jenkins service and that fixed jobs triggering.
> > > >
> > > > Best regards,
> > > > --
> > > > Anton Baranov
> > > > Systems and Network Administrator
> > > > The Linux Foundation
> > > >
> > > >
> > > > On Wed May 31 09:20:26 2017, abaranov wrote:
> > > > > Hello,
> > > > >
> > > > > We're checking that issue right now  and will keep you updated
> > > > >
> > > > > Thanks,
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > ___
> > > > vpp-dev mailing list
> > > > vpp-dev@lists.fd.io
> > > > https://lists.fd.io/mailman/listinfo/vpp-dev
> > > >
> >
> >
> > --
> > Anton Baranov
> > Systems and Network Administrator
> > The Linux Foundation
>
>
>
> ___
> 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

[vpp-dev] CSIT handling of DPDK PACKAGE VERSION

[Ed Warnicke]

VPP folks,

Currently,  CSIT is 'pegging' to a particular DPDK version.

https://git.fd.io/csit/tree/DPDK_STABLE_VER

This is fragile and bit us this week.  Its been recognized that such
pegging is undesirable, and should be removed, but it was done to solve a
problem for which an alternate solution needs to be found.

CSIT builds all the vpp packages and then scp copies them to the boxes
where the tests are run.  The problem is, for reasons of efficiency, vpp
typically *doesn't* build dpdk packages unless there is a change in
version, and so generally doesn't build those packages.  To work around
that, CSIT uses  DPDK_STABLE_VER to peg a version of the dpdk packages and
fetches them from nexus.

It's been agreed in CSIT that we should be taking our queues from the vpp
repo on these matters, so we wanted to see how the vpp-dev folks would like
it to be solved.

Possibilities that come immediately to mind:

1)  Point CSIT to (or create and point CSIT to) a simple clean way to get
the DPDK version from the vpp/ tree.  It would be good for this to be some
kind of clean contract with low probability of simply changing unexpectedly.

2)  Point CSIT to (or create and point CSIT to) a simple clean way to force
DPDK build (this has a cost for verify times, so I suspect will not be the
desired outcome).

Ed
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [FD.io Helpdesk #41298] Jobs are not triggered from gerrit

[Ed Warnicke]

What did you do to confirm triggers are now happening?

Ed

On Wed, May 31, 2017 at 6:55 AM, Anton Baranov via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> Hello,
>
> We restarted jenkins service and that fixed jobs triggering.
>
> Best regards,
> --
> Anton Baranov
> Systems and Network Administrator
> The Linux Foundation
>
>
> On Wed May 31 09:20:26 2017, abaranov wrote:
> > Hello,
> >
> > We're checking that issue right now  and will keep you updated
> >
> > Thanks,
> >
> >
>
>
>
> ___
> 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] [FD.io Helpdesk #41298] [linuxfoundation.org #41298] Fwd: [csit-dev] Jobs are not triggered from gerrit

[Ed Warnicke via RT]

-- Forwarded message --
From: Jan Gelety -X (jgelety - PANTHEON TECHNOLOGIES at Cisco) <
jgel...@cisco.com>
Date: Wed, May 31, 2017 at 1:17 AM
Subject: [csit-dev] Jobs are not triggered from gerrit
To: "helpd...@fd.io" 
Cc: "csit-...@lists.fd.io" , vpp-dev <
vpp-dev@lists.fd.io>


Hello,



I set recheck comment in two csit patches (https://gerrit.fd.io/r/#/c/6802/
and https://gerrit.fd.io/r/#/c/6803/) to trigger corresponding csit jobs
but no success.



Then I tried to do rebase in csit patch https://gerrit.fd.io/r/#/c/6806/
with the same result.



Even no build is queued on the Jenkins server – maybe issue between gerrrit
and Jenkins?



Could you, please, check it?



Thanks,

Jan

___
csit-dev mailing list
csit-...@lists.fd.io
https://lists.fd.io/mailman/listinfo/csit-dev

-- 
You received this message because you are subscribed to the Google Groups 
"Emergency Admin Alert" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to emergency+unsubscr...@linuxfoundation.org.

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [FD.io Helpdesk #41053] sporadic gerrit.fd.io html error 500 "Internal server error"

[Ed Warnicke via RT]

I got that part.  My point is that it looks like the first DNS for the SOA
is pointing to the DNS in your Portland DC.

Is this the old OSLab DC that is having the power issues?  Or the one we
are considering using for cross project stuff?

Ed

On Tue, May 23, 2017 at 8:27 AM, Andrew Grimberg via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> On Tue May 23 11:03:18 2017, hagbard wrote:
> > OK... why is it listed first in the public SOA then?
> >
> > Ed
>
> Ed,
>
> I think you're missing what is happening here.
>
> Our _internal_ DNS is run out of Portland. The _external_ DNS for FD.io is
> run out of a third party DNS provider.
>
> The cause of the intermittent 500 errors that Gerrit was getting is
> because of connectivity issues affecting Portland itself, apparently
> there's a massive power outage and our DC has been on generators since
> yesterday but that doesn't mean the power problems aren't causing issues
> for the DC nail-ups themselves. The connectivity issues have been causing
> Gerrit to not be able to find the backend database server when it's
> re-opening a connection. As such we've forcibly added the IP resolution to
> the hosts file, which is something we don't normally do.
>
> -Andy-
>
> --
> Andrew Grimberg
> The Linux Foundation
> ___
> 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] [FD.io Helpdesk #41053] sporadic gerrit.fd.io html error 500 "Internal server error"

[Ed Warnicke]

I got that part.  My point is that it looks like the first DNS for the SOA
is pointing to the DNS in your Portland DC.

Is this the old OSLab DC that is having the power issues?  Or the one we
are considering using for cross project stuff?

Ed

On Tue, May 23, 2017 at 8:27 AM, Andrew Grimberg via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> On Tue May 23 11:03:18 2017, hagbard wrote:
> > OK... why is it listed first in the public SOA then?
> >
> > Ed
>
> Ed,
>
> I think you're missing what is happening here.
>
> Our _internal_ DNS is run out of Portland. The _external_ DNS for FD.io is
> run out of a third party DNS provider.
>
> The cause of the intermittent 500 errors that Gerrit was getting is
> because of connectivity issues affecting Portland itself, apparently
> there's a massive power outage and our DC has been on generators since
> yesterday but that doesn't mean the power problems aren't causing issues
> for the DC nail-ups themselves. The connectivity issues have been causing
> Gerrit to not be able to find the backend database server when it's
> re-opening a connection. As such we've forcibly added the IP resolution to
> the hosts file, which is something we don't normally do.
>
> -Andy-
>
> --
> Andrew Grimberg
> The Linux Foundation
> ___
> 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] VPP now has basic tab completion

[Ed Warnicke]

Tears.  Tears of joy!

Ed

On Tue, May 23, 2017 at 12:00 PM, Luke, Chris 
wrote:

> Thanks to the work of Yoann we now have some tab-completion goodness in
> the debug CLI! I know it has been a long-desired feature for many people
> here.
>
>
>
> It works pretty much as you’d expect with the obvious caveat it can only
> complete for things registered with the CLI parser; where commands
> implement their own unformat() parsing for parameters we have no hope of
> completing on, or after, those.
>
>
>
> Enjoy! Feedback and enchancements welcome, of course. :)
>
>
>
> Chris.
>
> ___
> 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] [FD.io Helpdesk #41053] sporadic gerrit.fd.io html error 500 "Internal server error"

[Ed Warnicke]

OK... why is it listed first in the public SOA then?

Ed

On Tue, May 23, 2017 at 7:57 AM, Jordan Conway via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> Hi Ed,
> This is internal DNS.
>
> Cheers,
> Jordan
>
> On Tue, May 23, 2017 at 10:47 AM, Ed Warnicke <hagb...@gmail.com> wrote:
> Jordan,
>
> Why are we still running DNS out of the Portland DC?  I thought we were
> having that handled professionally now?
>
> 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] [FD.io Helpdesk #41053] sporadic gerrit.fd.io html error 500 "Internal server error"

[Ed Warnicke via RT]

OK... why is it listed first in the public SOA then?

Ed

On Tue, May 23, 2017 at 7:57 AM, Jordan Conway via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> Hi Ed,
> This is internal DNS.
>
> Cheers,
> Jordan
>
> On Tue, May 23, 2017 at 10:47 AM, Ed Warnicke <hagb...@gmail.com> wrote:
> Jordan,
>
> Why are we still running DNS out of the Portland DC?  I thought we were
> having that handled professionally now?
>
> 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] CI Tests Failing

[Ed Warnicke]

Do you have any insight on this?

Ed

On Mon, May 22, 2017 at 1:29 AM, Klement Sekera -X (ksekera - PANTHEON
TECHNOLOGIES at Cisco)  wrote:

>
> Hi,
>
> the centos python crash is known, but we're unsure about the root cause.
> Building newer python from source on centos vm makes the crashes go away
> so we're assuming that the (older) python itself might be the culprit,
> since we haven't seen these on ubuntu at all.
>
> Regarding the second crash - I'm not sure whether this is 'make test'
> fault or not.
>
> If somebody could translate from java/hudson/... to english and/or
> provide logs, then I could take a look..
>
> Thanks,
> Klement
>
> Quoting Kinsella, Ray (2017-05-22 10:21:21)
> > Hi folks,
> >
> > Not sure if it's just me, but some CI tests have suddenly start failing
> > for me. Is it just me or a wider problem?
> >
> > Ray K
> >
> >
> > CENTOS
> > https://jenkins.fd.io/job/vpp-verify-master-centos7/5568/
> >
> > 19:52:10 IP Multicast Signabash: line 1: 21723 Segmentation fault
> > (core dumped) python run_tests.py -d
> > /w/workspace/vpp-verify-master-centos7/test
> > 19:54:03 make[2]: *** [test] Error 139
> > 19:54:03 make[2]: Leaving directory
> > `/w/workspace/vpp-verify-master-centos7/test'
> > 19:54:03 make[1]: *** [test] Error 2
> > 19:54:03 make[1]: Leaving directory `/w/workspace/vpp-verify-
> master-centos7'
> > 19:54:03 make: *** [verify] Error 2
> > 19:54:04 Build step 'Execute shell' marked build as failure
> >
> >
> > UBUNTU
> > https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/5573/console
> >
> > 19:37:57 IP NULL route
> >   OK
> > 19:37:57
> > FATAL:
> > command execution failed
> > 19:48:45 java.io.EOFException
> > 19:48:45at
> > java.io.ObjectInputStream$PeekInputStream.readFully(
> ObjectInputStream.java:2638)
> > 19:48:45at
> > java.io.ObjectInputStream$BlockDataInputStream.
> readShort(ObjectInputStream.java:3113)
> > 19:48:45at
> > java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:853)
> > 19:48:45at java.io.ObjectInputStream.<
> init>(ObjectInputStream.java:349)
> > 19:48:45at
> > hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:48)
> > 19:48:45at
> > hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(
> AbstractSynchronousByteArrayCommandTransport.java:34)
> > 19:48:45at
> > hudson.remoting.SynchronousCommandTransport$ReaderThread.run(
> SynchronousCommandTransport.java:59)
> > 19:48:45 Caused: java.io.IOException: Unexpected termination of the
> channel
> > 19:48:45at
> > hudson.remoting.SynchronousCommandTransport$ReaderThread.run(
> SynchronousCommandTransport.java:73)
> > 19:48:45 Caused: java.io.IOException: Backing channel
> > 'ubuntu1604-basebuild-4c-4g-5113' is disconnected.
> > 19:48:45at
> > hudson.remoting.RemoteInvocationHandler.channelOrFail(
> RemoteInvocationHandler.java:192)
> > 19:48:45at
> > hudson.remoting.RemoteInvocationHandler.invoke(
> RemoteInvocationHandler.java:257)
> > 19:48:45at com.sun.proxy.$Proxy87.isAlive(Unknown Source)
> > 19:48:45at
> > hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1043)
> > 19:48:45at
> > hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1035)
> > 19:48:45at
> > hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155)
> > 19:48:45at
> > hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109)
> > 19:48:45at
> > hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
> > 19:48:45at
> > hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
> > 19:48:45at
> > hudson.model.AbstractBuild$AbstractBuildExecution.
> perform(AbstractBuild.java:779)
> > 19:48:45at hudson.model.Build$BuildExecution.build(Build.
> java:206)
> > 19:48:45at hudson.model.Build$BuildExecution.doRun(Build.
> java:163)
> > 19:48:45at
> > hudson.model.AbstractBuild$AbstractBuildExecution.run(
> AbstractBuild.java:534)
> > 19:48:45at hudson.model.Run.execute(Run.java:1728)
> > 19:48:45at hudson.model.FreeStyleBuild.
> run(FreeStyleBuild.java:43)
> > 19:48:45at
> > hudson.model.ResourceController.execute(ResourceController.java:98)
> > 19:48:45at hudson.model.Executor.run(Executor.java:405)
> > 19:48:45 Build step 'Execute shell' marked build as failure
> > 19:48:45 FATAL: channel is already closed
> > 19:48:45 java.io.EOFException
> > 19:48:45at
> > java.io.ObjectInputStream$PeekInputStream.readFully(
> ObjectInputStream.java:2638)
> > 19:48:45at
> > java.io.ObjectInputStream$BlockDataInputStream.
> readShort(ObjectInputStream.java:3113)
> > 19:48:45at
> > java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:853)
> > 19:48:45at java.io.ObjectInputStream.<
> init>(ObjectInputStream.java:349)
> > 19:48:45

Re: [vpp-dev] Add support to CI for openSUSE

[Ed Warnicke]

Vanessa,
 Could you get Marco access to the ticketing system and where do we
stand on getting the OpenSuse VM?

Ed

On Wed, May 3, 2017 at 1:35 AM, Marco Varlese <marco.varl...@suse.com>
wrote:

> Hi Vanessa and Ed,
> Since I do not have permissions to see the status of the ticket (I get
> Unauthorized when accessing the link below after being correctly logged
> in), would you be so kind to provide some updates?
>
> Thanks and regards,
> Marco
>
> On Mon, 2017-04-10 at 10:12 -0500, Vanessa Valderrama wrote:
>
> Ed,
>
> I've opened RT https://rt-sso.linuxfoundation.org/Ticket/
> Display.html?id=39618 to track this issue.  This is a project so I'll
> need to review with Andy before I can provide an ETA.
> Thank you,
> Vanessa
>
> On 04/10/2017 09:49 AM, Ed Warnicke wrote:
>
> Looping in a few more folks to help get this moving at various levels.
>
> Vanessa/Andy,
>
> What do we need to do to get OpenSuse Jenkins Minions going?
>
> Ed
>
> On Mon, Apr 10, 2017 at 2:38 AM, Marco Varlese <marco.varl...@suse.com>
> wrote:
>
> Hi,
>
> I would like to ask if it is possible to add openSUSE distribution in the
> CI for
> FD.IO/VPP.
> We are currently packaging it and I think it would be extremely beneficial
> to
> have the CI running on our distribution too.
>
> Is it at all possible? If so would you please advise what would you
> require on
> my side to make this happen so that I can assist?
>
>
> Thanks and regards,
> Marco
>
>
>
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Requirement on Load Balancer plugin for VPP

[Ed Warnicke]

Hongjun,

Thinking it through a bit, there are *many* different approaches to load
balancers.  I would suggest if you want to support a different one, then
starting a new plugin for it may be a good move :)

Ed

On Mon, Apr 24, 2017 at 8:04 PM, Ni, Hongjun <hongjun...@intel.com> wrote:

> Hi Ed,
>
>
>
> Thanks for your prompt response.
>
>
>
> This item is required to handle legacy AS, because some legacy AS does not
> want to change their underlay forwarding infrastructure.
>
>
>
> Besides, some AS IPs are private and invisible outside the AS cluster
> domain, and not allowed to expose to external network.
>
>
>
> Thanks,
>
> Hongjun
>
>
>
> *From:* Ed Warnicke [mailto:hagb...@gmail.com]
> *Sent:* Tuesday, April 25, 2017 10:44 AM
> *To:* Ni, Hongjun <hongjun...@intel.com>
> *Cc:* vpp-dev@lists.fd.io; Li, Johnson <johnson...@intel.com>
> *Subject:* Re: [vpp-dev] Requirement on Load Balancer plugin for VPP
>
>
>
> Hongjun,
>
>
>
> I can see this point of view, but it radically reduces the scalability of
> the whole system.
>
> Wouldn't it just make sense to run vpp or some other mechanism to decap
> the GRE on whatever is running the other AS and feed whatever we are
>
> load balancing to?  Forcing back traffic through the central load balancer
> radically reduces scalability (which is why
>
> Maglev, which inspired what we are doing here, doesn't do it that way
> either).
>
>
>
> Ed
>
>
>
> On Mon, Apr 24, 2017 at 7:18 PM, Ni, Hongjun <hongjun...@intel.com> wrote:
>
> Hey,
>
>
>
> Currently, traffic received for a given VIP (or VIP prefix) is tunneled
> using GRE towards
>
> the different ASs in a way that (tries to) ensure that a given session
> will
>
> always be tunneled to the same AS.
>
>
>
> But in real environment, many Application Servers do not support GRE
> feature.
>
> So we raise a requirement for LB in VPP:
>
> (1). When received traffic for a VIP, the LB need to do load balance, then
> do DNAT to change traffic’s destination IP from VIP to AS’s IP.
>
> (2). When returned traffic from AS, the LB will do SNAT first to change
> traffic’s source IP from AS’s IP to VIP, then go through load balance
> sessions, and then sent to clients.
>
>
>
> Any comments about this requirement are welcome.
>
>
>
> Thanks a lot,
>
> Hongjun
>
>
>
>
> ___
> 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] Requirement on Load Balancer plugin for VPP

[Ed Warnicke]

Hongjun,

I can see this point of view, but it radically reduces the scalability of
the whole system.
Wouldn't it just make sense to run vpp or some other mechanism to decap the
GRE on whatever is running the other AS and feed whatever we are
load balancing to?  Forcing back traffic through the central load balancer
radically reduces scalability (which is why
Maglev, which inspired what we are doing here, doesn't do it that way
either).

Ed

On Mon, Apr 24, 2017 at 7:18 PM, Ni, Hongjun  wrote:

> Hey,
>
>
>
> Currently, traffic received for a given VIP (or VIP prefix) is tunneled
> using GRE towards
>
> the different ASs in a way that (tries to) ensure that a given session
> will
>
> always be tunneled to the same AS.
>
>
>
> But in real environment, many Application Servers do not support GRE
> feature.
>
> So we raise a requirement for LB in VPP:
>
> (1). When received traffic for a VIP, the LB need to do load balance, then
> do DNAT to change traffic’s destination IP from VIP to AS’s IP.
>
> (2). When returned traffic from AS, the LB will do SNAT first to change
> traffic’s source IP from AS’s IP to VIP, then go through load balance
> sessions, and then sent to clients.
>
>
>
> Any comments about this requirement are welcome.
>
>
>
> Thanks a lot,
>
> Hongjun
>
>
>
> ___
> 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] 17.04 Features to highlight in press release

[Ed Warnicke]

Could you expand on what you mean by Interface updates?

Ed

On Thu, Apr 20, 2017 at 6:30 AM, Bernier, Daniel <daniel.bern...@bell.ca>
wrote:

> Hi,
>
>
>
> From my “biased” point of view :-) and not in any order of preference
>
>
>
> 1)   SRv6
>
> 2)   Host Stack
>
> 3)   iOAM
>
> 4)   Interfaces updates
>
>
>
> Thanks,
>
>
>
> PS: sorry for the double mail, touched the wrong key :-)
>
> 
>
> Daniel Bernier | Bell Canada
>
>
>
>
>
> *From: *<csit-dev-boun...@lists.fd.io> on behalf of Ed Warnicke <
> hagb...@gmail.com>
> *Date: *Wednesday, April 19, 2017 at 5:23 PM
> *To: *vpp-dev <vpp-dev@lists.fd.io>, honeycomb-dev <
> honeycomb-...@lists.fd.io>, "csit-...@lists.fd.io" <csit-...@lists.fd.io>,
> "nsh_sfc-...@lists.fd.io" <nsh_sfc-...@lists.fd.io>, "t...@lists.fd.io" <
> t...@lists.fd.io>, "disc...@lists.fd.io" <disc...@lists.fd.io>
> *Cc: *"market...@lists.fd.io" <market...@lists.fd.io>
> *Subject: *[csit-dev] 17.04 Features to highlight in press release
>
>
>
> The fd.io marketing committee would like to do a press release about the
> various
>
> 17.04 releases of projects in fd.io (vpp, honeycomb, nsh_sfc, csit, etc).
>
>
>
> In order to produce the best press release, we wanted to ask the community
> to chime in about what they think the most exciting new features in 17.04
> are.  Please speak up :)
>
>
>
> Ed
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP 17.04 released

[Ed Warnicke]

Eric,

Thanks very much for getting this reported so quickly, we'll get it fixed
and respun.

Ed

On Wed, Apr 19, 2017 at 2:47 PM, Ernst, Eric <eric.er...@intel.com> wrote:

> On Wed, Apr 19, 2017 at 02:32:56PM -0700, Ed Warnicke wrote:
> > Looks like:
> >
> > https://gerrit.fd.io/r/#/c/5837/
> >
> >  wasn't cherry picked down to stable/1704
>
> FYI, I made the update locally to /etc/vpp/startup.conf and VPP then
> starts without issue.  Thanks for the quick confirmation.
>
> -Eric
>
> >
> > Ole, could we get that cherry picked down and the release respun?
> >
> > Also looks like we need a test for 'working out of the box on package
> > install'.
> >
> > Ed
> >
> > On Wed, Apr 19, 2017 at 2:27 PM, Ernst, Eric <eric.er...@intel.com>
> wrote:
> >
> > > Excited to start looking @ memifc.  On 1701 the package worked out of
> the
> > > box; should I expect same for 1704 on Xenial?
> > >
> > > I pulled from https://nexus.fd.io/content/repositories/fd.io.stable.
> > > 1704.ubuntu.xenial.main/
> > > after uninstalling prior vpp packages, and when starting the service I
> see:
> > >
> > > Apr 19 14:20:09 eernstworkstation systemd[1]: Starting vector packet
> > > processing engine...
> > > Apr 19 14:20:09 eernstworkstation systemd[1]: Started vector packet
> > > processing engine.
> > > Apr 19 14:20:09 eernstworkstation vpp[10368]:
> vlib_plugin_early_init:360:
> > > plugin path /usr/lib/vpp_plugins
> > > Apr 19 14:20:09 eernstworkstation vpp[10368]: vlib_call_all_config_
> functions:
> > > unknown input `dpdk  '
> > > Apr 19 14:20:09 eernstworkstation systemd[1]: vpp.service: Main process
> > > exited, code=exited, status=1/FAILURE
> > > Apr 19 14:20:09 eernstworkstation systemd[1]: vpp.service: Unit entered
> > > failed state.
> > > Apr 19 14:20:09 eernstworkstation systemd[1]: vpp.service: Failed with
> > > result 'exit-code'.
> > > Apr 19 14:20:10 eernstworkstation systemd[1]: vpp.service: Service
> > > hold-off time over, scheduling restart.
> > > Apr 19 14:20:10 eernstworkstation systemd[1]: Stopped vector packet
> > > processing engine.
> > >
> > >
> > > I see similar after a reboot.
> > >
> > > Thanks!
> > > Eric
> > >
> > >
> > >
> > > On Wed, Apr 19, 2017 at 02:14:48PM -0700, Ed Warnicke wrote:
> > > > Congratulations!
> > > >
> > > > Ed
> > > >
> > > > On Wed, Apr 19, 2017 at 1:46 PM, Luke, Chris <chris_l...@comcast.com
> >
> > > wrote:
> > > >
> > > > > Yay! Great stuff!
> > > > >
> > > > > But also, eek! I think the 17.01 release notes didn't get
> > > dual-committed
> > > > > last time around. It's empty.
> > > > >
> > > > > I'm about to head out; I'll rustle that up when I get home if
> nobody
> > > else
> > > > > beats me to it.
> > > > >
> > > > > Chris.
> > > > >
> > > > > > -Original Message-
> > > > > > From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-bounces@lists.
> > > fd.io]
> > > > > On
> > > > > > Behalf Of otr...@employees.org
> > > > > > Sent: Wednesday, April 19, 2017 4:37 PM
> > > > > > To: vpp-dev <vpp-dev@lists.fd.io>
> > > > > > Subject: [vpp-dev] VPP 17.04 released
> > > > > >
> > > > > > The images are built, the wiki is updated (let me know if
> something
> > > has
> > > > > been
> > > > > > missed).
> > > > > >
> > > > > > Release notes:
> > > > > > https://docs.fd.io/vpp/17.04/release_notes_1704.html
> > > > > >
> > > > > > Images at:
> > > > > > https://nexus.fd.io/
> > > > > >
> > > > > > Best regards,
> > > > > > Ole
> > > > > ___
> > > > > 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

Re: [vpp-dev] VPP 17.04 released

[Ed Warnicke]

Looks like:

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

 wasn't cherry picked down to stable/1704

Ole, could we get that cherry picked down and the release respun?

Also looks like we need a test for 'working out of the box on package
install'.

Ed

On Wed, Apr 19, 2017 at 2:27 PM, Ernst, Eric <eric.er...@intel.com> wrote:

> Excited to start looking @ memifc.  On 1701 the package worked out of the
> box; should I expect same for 1704 on Xenial?
>
> I pulled from https://nexus.fd.io/content/repositories/fd.io.stable.
> 1704.ubuntu.xenial.main/
> after uninstalling prior vpp packages, and when starting the service I see:
>
> Apr 19 14:20:09 eernstworkstation systemd[1]: Starting vector packet
> processing engine...
> Apr 19 14:20:09 eernstworkstation systemd[1]: Started vector packet
> processing engine.
> Apr 19 14:20:09 eernstworkstation vpp[10368]: vlib_plugin_early_init:360:
> plugin path /usr/lib/vpp_plugins
> Apr 19 14:20:09 eernstworkstation vpp[10368]: vlib_call_all_config_functions:
> unknown input `dpdk  '
> Apr 19 14:20:09 eernstworkstation systemd[1]: vpp.service: Main process
> exited, code=exited, status=1/FAILURE
> Apr 19 14:20:09 eernstworkstation systemd[1]: vpp.service: Unit entered
> failed state.
> Apr 19 14:20:09 eernstworkstation systemd[1]: vpp.service: Failed with
> result 'exit-code'.
> Apr 19 14:20:10 eernstworkstation systemd[1]: vpp.service: Service
> hold-off time over, scheduling restart.
> Apr 19 14:20:10 eernstworkstation systemd[1]: Stopped vector packet
> processing engine.
>
>
> I see similar after a reboot.
>
> Thanks!
> Eric
>
>
>
> On Wed, Apr 19, 2017 at 02:14:48PM -0700, Ed Warnicke wrote:
> > Congratulations!
> >
> > Ed
> >
> > On Wed, Apr 19, 2017 at 1:46 PM, Luke, Chris <chris_l...@comcast.com>
> wrote:
> >
> > > Yay! Great stuff!
> > >
> > > But also, eek! I think the 17.01 release notes didn't get
> dual-committed
> > > last time around. It's empty.
> > >
> > > I'm about to head out; I'll rustle that up when I get home if nobody
> else
> > > beats me to it.
> > >
> > > Chris.
> > >
> > > > -Original Message-
> > > > From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-bounces@lists.
> fd.io]
> > > On
> > > > Behalf Of otr...@employees.org
> > > > Sent: Wednesday, April 19, 2017 4:37 PM
> > > > To: vpp-dev <vpp-dev@lists.fd.io>
> > > > Subject: [vpp-dev] VPP 17.04 released
> > > >
> > > > The images are built, the wiki is updated (let me know if something
> has
> > > been
> > > > missed).
> > > >
> > > > Release notes:
> > > > https://docs.fd.io/vpp/17.04/release_notes_1704.html
> > > >
> > > > Images at:
> > > > https://nexus.fd.io/
> > > >
> > > > Best regards,
> > > > Ole
> > > ___
> > > 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

[vpp-dev] 17.04 Features to highlight in press release

[Ed Warnicke]

The fd.io marketing committee would like to do a press release about the
various
17.04 releases of projects in fd.io (vpp, honeycomb, nsh_sfc, csit, etc).

In order to produce the best press release, we wanted to ask the community
to chime in about what they think the most exciting new features in 17.04
are.  Please speak up :)

Ed
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] VPP 17.04 released

[Ed Warnicke]

Congratulations!

Ed

On Wed, Apr 19, 2017 at 1:46 PM, Luke, Chris  wrote:

> Yay! Great stuff!
>
> But also, eek! I think the 17.01 release notes didn't get dual-committed
> last time around. It's empty.
>
> I'm about to head out; I'll rustle that up when I get home if nobody else
> beats me to it.
>
> Chris.
>
> > -Original Message-
> > From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io]
> On
> > Behalf Of otr...@employees.org
> > Sent: Wednesday, April 19, 2017 4:37 PM
> > To: vpp-dev 
> > Subject: [vpp-dev] VPP 17.04 released
> >
> > The images are built, the wiki is updated (let me know if something has
> been
> > missed).
> >
> > Release notes:
> > https://docs.fd.io/vpp/17.04/release_notes_1704.html
> >
> > Images at:
> > https://nexus.fd.io/
> >
> > Best regards,
> > Ole
> ___
> 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] Add support to CI for openSUSE

[Ed Warnicke]

Looping in a few more folks to help get this moving at various levels.

Vanessa/Andy,

What do we need to do to get OpenSuse Jenkins Minions going?

Ed

On Mon, Apr 10, 2017 at 2:38 AM, Marco Varlese 
wrote:

> Hi,
>
> I would like to ask if it is possible to add openSUSE distribution in the
> CI for
> FD.IO/VPP.
> We are currently packaging it and I think it would be extremely beneficial
> to
> have the CI running on our distribution too.
>
> Is it at all possible? If so would you please advise what would you
> require on
> my side to make this happen so that I can assist?
>
>
> Thanks and regards,
> Marco
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Running VPP on windows (with vagrant)

[Ed Warnicke]

Mathieu,

I routinely build in AWS using  fairly stock Ubuntu/Centos images.

Ed

On Tue, Apr 4, 2017 at 7:38 AM, Mathieu Duperre (mduperre) <
mdupe...@cisco.com> wrote:

> Hi,
>
>
>
> (my apology if that’s not the right forum, not sure where else to ask).
> Was anyone able to build vpp either:
>
>
>
> -in a windows machine running vagrant (ubuntu or centos)? I tried both,
> could not build it properly (Vagrant image not installing few libs, make
> not making, etc.)
>
> -in AWS?  I was able to build, with a few errors here and there, but i got
> a segmentation fault when trying to start vpp.
>
>
>
> I just want to know if that was done before. thanks.
>
>
>
>
>
> [image:
> http://wwwin.cisco.com/c/dam/cec/organizations/gmcc/services-tools/signaturetool/images/logo/logo_Cisco_Blue.png]
>
>
>
> *Mathieu Duperre*
>
> SOFTWARE SYSTEMS ENGINEER.SALES
>
> mdupe...@cisco.com
>
> Tel: *+1 919 927 1296 <(919)%20927-1296>*
>
> *Cisco Systems, Inc.*
>
>
>
>
> Canada
> cisco.com
>
>
>
> [image: http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think
> before you print.
>
> This email may contain confidential and privileged material for the sole
> use of the intended recipient. Any review, use, distribution or disclosure
> by others is strictly prohibited. If you are not the intended recipient (or
> authorized to receive for the recipient), please contact the sender by
> reply email and delete all copies of this message.
>
> Please click here
>  for
> Company Registration Information.
>
>
>
> ___
> 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] Out of Tree Build Failure on vnet/rewrite.h

[Ed Warnicke]

The more interesting (to me) question is... how did it pass verify?

Ed

On Thu, Mar 30, 2017 at 3:25 PM, Neale Ranns (nranns) 
wrote:

>
>
> Hi Jon,
>
>
>
> Sorry about that.
>
>
>
> The files that get copied to /usr/include/bla/bla are specified in vnet.am
> in nobase_include_HEADERS+=.h
>
> IIRC in that commit I removed vnet/rewirte.h from that set. Which was
> evidently a mistake.
>
>
>
> https://gerrit.fd.io/r/#/c/5963/
>
>
>
> regards,
>
> neale
>
>
>
> *From: *Jon Loeliger 
> *Date: *Thursday, 30 March 2017 at 22:25
> *To: *vpp-dev , "Neale Ranns (nranns)" <
> nra...@cisco.com>
> *Subject: *Out of Tree Build Failure on vnet/rewrite.h
>
>
>
> Neale,
>
>
>
> Looks like we have that situation of either:
>
> 1) An include file shouldn't be #including another one,
>
> and perhaps the latter might be needed directly in
>
> a set of .c files,
>
> or
>
> 2) The install target isn't picking up and installing one
>
> of the now-needed include files.
>
>
>
> Actual error:
>
>
>
> CC .c
>
> In file included from /usr/include/vnet/ip/ip.h:51:0,
>
>  from af_packet.c:12:
>
> /usr/include/vnet/ip/lookup.h:58:26: fatal error: vnet/rewrite.h: No such
> file or directory
>
>  #include 
>
>
>
>
>
> And 'git praise' suggests:
>
>
>
> 2e7fbcc0 src/vnet/ip/lookup.h  (Neale Ranns2017-03-15 04:22:25
> -0700  58) #include 
>
>
>
> Any insight here?
>
>
>
> Thanks,
>
> jdl
>
>
>
>
> ___
> 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] Building router plugin

[Ed Warnicke]

You might also look at

https://gerrit.fd.io/r/#/c/5004/ - which introduces memif interfaces...
which I think Damjan eventually wants a library for so that you could
use them for things like taps for routing protocol packets...

Ed

On Mon, Mar 27, 2017 at 2:43 PM, Łukasz Chrustek  wrote:

> Hi,
>
> Ok,  thank You. I will give a try with earlier version of vpp, as Jeff
> suggests.  I  have  running  netlink  plugin,  but as Ole wrote - most
> important is router plugin.
>
> Cheers,
> Luk
>
> >> You basically have two options:
> >> 1. Teach your routing protocol daemon to directly talk to VPP for
> configuring the FIB.
> >> 2. Do not modify the routing daemon and let VPP map routes written in
> the kernel.
> >>
> >> For 1, you will need the router plugin, but for packet punting only.
> >>
> >> For 2., you will need both netlink+router plugins. The netlink plugin
> (which actually more like a library), shouldn't require so much changes
> though.
>
> > With TCP support in VPP I was playing with the idea of integrating
> exaBGP as a VPP plugin.
> > Use the Python API binding to program routes, and receive the BGP
> > stream across a fifo (or even the API).
>
> > Cheers,
> > Ole
>
> >>> Le 26 mars 2017 à 16:31, Łukasz Chrustek  a écrit :
> >>>
> >>> Hello,
> >>>
> >>> thank all of You for clarification of status router plugin.
> >>>
> >>> I'm trying to use vpp+dpdk as bare metal linux ruter with bgp and ospf
> routing protocols, goal is to make very fast router with dynamic routing
> protocols. Can You advice is there any other way to exchange dynamic
> routing information between os and vpp ?
> >>>
> >>> Regards
> >>> Lukasz
> >>>
> >>>
> >>> The mailman did not let my last message go through because it was too
> big so I am removing the previous threads to keep this message under 100KB
> limit.
> >>>
> >>> Hello,
> >>>
> >>> Dave and Pierre are correct, the router plugin is no longer being
> maintained. There was not much interest in the community for this project
> at the time and I have since moved on to other things.  I’d be happy to
> help a new maintainer with any questions they may have.
> >>>
> >>> If you really want to just test it out, I suggest attempting to
> checkout a commit of VPP close to the last commit on the router plugin.
> Somewhere closely following VPP commit 0bfe5d8c792abcdb, “A Protocol
> Independent Hierarchical FIB (VPP-352)” will work (you might have to git
> bisect to get something that compiles right away).
> >>>
> >>> If necessary, I can submit a patch to remove the router plugin from
> the VPP sandbox with a note on the wiki page mentioning the finalization of
> the project. I recall there being an 8-month time limit for these the
> sandbox projects.
> >>>
> >>> -Jeff
> >>>
> >>>
> >>>
> >>
> >> ___
> >> vpp-dev mailing list
> >> vpp-dev@lists.fd.io
> >> https://lists.fd.io/mailman/listinfo/vpp-dev
>
>
>
>
> --
> Pozdrowienia,
>  Łukasz Chrustek
>
> ___
> 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] CFP for fd.io Minisummit at OpenStack Summit, Monday, May 8 Boston

[Ed Warnicke]

Apologies, the last email was sent prematurely, the link to information and
to the CFP form to submit talks is here:

https://fd.io/news/events/2017-05-08/fdio-mini-summit-open-stack-boston-may-8th

On Mon, Mar 27, 2017 at 11:09 AM, Ed Warnicke <hagb...@gmail.com> wrote:

> fd.io is having a minisummit at the OpenStack Summit Monday May 8 in
> Boston, MA.
>
> The Call for Papers (CFP) has opened, and you can find a link to it here:
>
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Building router plugin

[Ed Warnicke]

Luk,

Are you installing the vpp-dev (or vpp-devel if Centos) package?
I would imagine you'd need that for headers etc.

Ed

On Fri, Mar 24, 2017 at 8:14 AM, Łukasz Chrustek 
wrote:

> Hi Dave,
>
> but this plugin isn't part of core vpp code tree, it is from vppsb.
>
> Regards
> Luk
> > Dear Luk,
>
> > The "vpp-install," "install-packags," "install-deb" etc. targets
> > will build the set of plugins configured in src/configure.ac:
>
> > For example:
>
> > $ cd build-root
> > $ make PLATFORM=vpp TAG=vpp vpp-install
>
> > HTH. Dave
>
> > -Original Message-
> > From: vpp-dev-boun...@lists.fd.io
> > [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Lukasz Chrustek
> > Sent: Friday, March 24, 2017 4:55 AM
> > To: vpp-dev@lists.fd.io
> > Subject: [vpp-dev] Building router plugin
>
> > Hi,
>
> > Can You advice what is the proper way for building router plugin now ?
>
> > I'm trying to build this plugin as stated in README, but I get:
>
> > # ./bootstrap.sh
>
> > Saving PATH settings in /git/vpp/build-root/path_setup
> > Source this file later, as needed
> > Compile native tools
> >  Arch for platform 'native' is native 
> >  Finding source for tools 
> >  Makefile fragment found in
> > /git/vpp/build-root/packages/tools.mk 
> >  Source found in /git/vpp/src 
> >  Configuring tools: nothing to do 
> >  Building tools: nothing to do 
> >  Installing tools: nothing to do 
>
> > # make V=0 PLATFORM=vpp TAG=vpp_debug router-install
> >  Arch for platform 'vpp' is native 
> >  Finding source for vppinfra 
> >  Package vppinfra not found with path /git/vpp 
> > Makefile:780: recipe for target 'vppinfra-find-source' failed
> > make: *** [vppinfra-find-source] Error 1
>
> > compilation  of  vpp is working fine, but not from /git/vpp/build-root
> > but from /git/vpp.
>
> > Regards
> > Luk
>
> > ___
> > vpp-dev mailing list
> > vpp-dev@lists.fd.io
> > https://lists.fd.io/mailman/listinfo/vpp-dev
>
>
>
> --
> Pozdrawiam,
>  Łukasz Chrustek
>
> ___
> 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] vpp-plugins RPM dependency

[Ed Warnicke]

Commenting out the dpdk stanza is a great workaround but we may want to
look at bit more closely at the issue... as installing the vpp project
should result in an out of the box runnable vpp.

Ed

On Wed, Mar 22, 2017 at 11:44 AM, Dave Barach (dbarach) 
wrote:

> Simply remove the “dpdk” stanza from /etc/vpp/startup.conf if you want to
> run vpp without the dpdk plugin.
>
>
>
> Thanks… Dave
>
>
>
> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
> Behalf Of *Feng Pan
> *Sent:* Wednesday, March 22, 2017 1:47 PM
> *To:* vpp-dev 
> *Subject:* [vpp-dev] vpp-plugins RPM dependency
>
>
>
> Hi All,
>
>
>
> With latest master builds of VPP (on Centos with rpm repo), it seems like
> it's necessary to install vpp-plugins package for vpp to start, without it,
> I get the following error when running vpp (with default config file):
>
>
>
> vlib_plugin_early_init:360: plugin path /usr/lib/vpp_plugins
>
> vlib_call_all_config_functions: unknown input `dpdk  '
>
>
>
> Looking at the spec file, vpp package depends on vpp-lib only, so it
> appears that we need to add vpp-plugins to the dependency list too.
> However, it also looks like vpp-plugins depends on vpp package, so I'm
> trying to figure out what the right dependency relationship is :)
>
>
>
> Thanks
>
> Feng
>
> ___
> 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] Make pkg-rpm seems to be failing...

[Ed Warnicke]

Jon,

Looking at :  https://git.fd.io/vpp/tree/Makefile#n138

In make bootstrap... for deb packages on Ubuntu its checking to see if
things are missing and failing fast if they are.
I'd suggest we look at doing something similar for rpms.

Anyone interested in submitting a patch?

Ed

On Mon, Mar 20, 2017 at 8:53 AM, Jon Loeliger  wrote:

> Burt and Ole,
>
> On Sun, Mar 19, 2017 at 7:26 AM,  wrote:
>>
>>>
>>> Hmm, so https://gerrit.fd.io/r/#/c/5781/
>>> isn't sufficient?
>>>
>>
> Necessary, yes.  Sufficient?  No.
>
> On the other hand...
>
> On Sun, Mar 19, 2017 at 11:51 AM, Burt Silverman  wrote:
>
>> Ugh, I made a terrible bone head mistake... Possibly I never ran make
>> install-dep. Even if I had, I was unaware that it is a good idea to run it
>> again, just to be sure, in a case like this. I probably thought it was like
>> make bootstrap, where running a 2nd time doesn't help. Apologies to Ed and
>> Ole for misinformation. So, Jon, were you in the same boat with me --
>> didn't do a double check of make install-dep? I guess so, because you still
>> had the problem after Ole's fix.
>>
>> Burt
>>
>
> This was precisely the problem here.  I'll try to say this as
> politely as I can...  Wow.  That's some blind-siding sh*t.
>
> So, let's talk about that a bit.
>
> First, thank you for identifying the issue!  This does indeed
> fix the build locally, and bring us back to online par. Thank you!
>
> Second, the notion of requiring repeated running of the make
> install-dep target as part of our daily build process from our
> CI engine is just not going to happen.  NFW.  We're not running
> anything has root like that.  It's a bad idea for many reasons.
>
> On the flip side, I can make a job that "notices" a change in the
> installed packaged requirement and run that as, say, a daily job
> and incidentally notice that updates are needed.  Sure, polling
> like that sucks; an interrupt here with a simple "Heads up!  The
> install-deps have changed" would have been awesome!
>
> Thanks,
> jdl
>
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Make pkg-rpm seems to be failing...

[Ed Warnicke]

Other things we know are that the merge jobs appear to be failing on
master...

https://jenkins.fd.io/view/vpp/job/vpp-merge-master-centos7/

Ed

On Fri, Mar 17, 2017 at 2:19 PM, Ed Warnicke <hagb...@gmail.com> wrote:

> I just hit that too...
>
> Ed
>
> On Fri, Mar 17, 2017 at 1:56 PM, Burt Silverman <bur...@gmail.com> wrote:
>
>> I am stuck in vnet/mpls/mpls_features.c at line 107. Not getting beyond
>> make build-release. end_node is not recognized here, it seems.
>> ​
>>
>> ___
>> 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] Make pkg-rpm seems to be failing...

[Ed Warnicke]

I just hit that too...

Ed

On Fri, Mar 17, 2017 at 1:56 PM, Burt Silverman  wrote:

> I am stuck in vnet/mpls/mpls_features.c at line 107. Not getting beyond
> make build-release. end_node is not recognized here, it seems.
> ​
>
> ___
> 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] vpp rpms overlaping files

[Ed Warnicke]

Many thanks :)

Ed

On Fri, Mar 17, 2017 at 1:58 AM, <otr...@employees.org> wrote:

> Ed,
>
> Thanks for finding this.
> It should be fixed in: https://gerrit.fd.io/r/#/c/5783/
>
> Best regards,
> Ole
>
>
> > On 16 Mar 2017, at 15:53, Ed Warnicke <hagb...@gmail.com> wrote:
> >
> > OpNFV has discovered that we have overlapping files in vpp-devel and
> vpp-python-api
> > rpms.  It looks like vpp-python-api is being stuffed into vpp-devel.
> Has something changed here recently?
> >
> > Ed
> >
> >
> > Transaction check error:
> >   file /usr/lib/python2.7/site-packages/jvppgen/__init__.py conflicts
> between attempted installs of vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/__init__.pyc conflicts
> between attempted installs of vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/__init__.pyo conflicts
> between attempted installs of vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/callback_gen.py
> conflicts between attempted installs of 
> vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/callback_gen.pyc
> conflicts between attempted installs of 
> vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/callback_gen.pyo
> conflicts between attempted installs of 
> vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/dto_gen.py conflicts
> between attempted installs of vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/dto_gen.pyc conflicts
> between attempted installs of vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/dto_gen.pyo conflicts
> between attempted installs of vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/jni_gen.py conflicts
> between attempted installs of vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/jni_gen.pyc conflicts
> between attempted installs of vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/jni_gen.pyo conflicts
> between attempted installs of vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/jvpp_c_gen.py conflicts
> between attempted installs of vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/jvpp_c_gen.pyc
> conflicts between attempted installs of 
> vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/jvpp_c_gen.pyo
> conflicts between attempted installs of 
> vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/jvpp_callback_facade_gen.py
> conflicts between attempted installs of 
> vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/jvpp_callback_facade_gen.pyc
> conflicts between attempted installs of 
> vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/jvpp_callback_facade_gen.pyo
> conflicts between attempted installs of 
> vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/python2.7/site-packages/jvppgen/jvpp_future_facade_gen.py
> conflicts between attempted installs of 
> vpp-devel-17.04-rc0~440_ge9f929b~b2064.x86_64
> and vpp-api-python-17.04-rc0~440_ge9f929b~b2064.x86_64
> >   file /usr/lib/pyt

Re: [vpp-dev] Fixed offset from UTC meeting time?

[Ed Warnicke]

Ole,

The meeting is on the meeting page and the vpp calendar as 8am PST.
While I share your frustration about DST... it was clearly documented as
such :)

Ed

On Tue, Mar 14, 2017 at 9:11 AM,  wrote:

> All,
>
> It was a very quiet meeting at 1600UTC today... Could we in the future
> have the meeting time set fixed against UTC so that we avoid any confusion
> whenever different regions of the world randomly chooses to move their
> clocks forward or backward?
>
> Best regards,
> Ole
>
> ___
> 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] system func in vpp

[Ed Warnicke]

Why would you do that from within vpp?

Ed

On Mon, Feb 27, 2017 at 8:36 PM, yug...@telincn.com <yug...@telincn.com>
wrote:

> "int system(const char *command)"
>
> I would like to use this func to start another dameon , such as "
>  system("zebra -d")  ".
>
> Regards,
> Ewan
> ------
> yug...@telincn.com
>
>
> *From:* Ed Warnicke <hagb...@gmail.com>
> *Date:* 2017-02-28 11:15
> *To:* yug...@telincn.com
> *CC:* vpp-dev <vpp-dev@lists.fd.io>
> *Subject:* Re: [vpp-dev] system func in vpp
> I'm not quite sure what you mean by the 'func system'...
>
> Ed
>
> On Mon, Feb 27, 2017 at 7:26 PM, yug...@telincn.com <yug...@telincn.com>
> wrote:
>
>> Hi, all
>>
>> Does vpp can't use func  system? Any reason to this or what can i do  if
>> i really need ?
>>
>> --
>> yug...@telincn.com
>>
>> ___
>> 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] sanity check during rpm installation missing

[Ed Warnicke]

If you are in the mood to push a patch... properly speaking it would be
best if the rpm made sure the hugepages was *at least* 1024, set it to that
if its less, and left it alone if its more.

Ed

On Tue, Feb 21, 2017 at 3:12 PM, Burt Silverman  wrote:

> Hi,
>
> I found some excellent error checking in build-root/vagrant/update.sh,
> whereby if vm.nr_hugepages cannot be set to 1024, the script exits
> gracefully.
>
> However, during rpm installation -- I don't know which one at the moment
> -- there is no checking prior to plopping down src/vpp/conf/80-vpp.conf
> into /etc/sysctl.d. That file assumes vm.nr_hugepages can be set to 1024.
>
> I ended up having to use a Live CD to comment out the file in order to be
> able to reboot my VM.
>
> Burt (using intel based laptop now)
>
>
>
>
>
> ___
> 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] VPP Repo status?

[Ed Warnicke]

Also worked for git 1.8.3.1

Ed

On Tue, Feb 14, 2017 at 6:29 AM, Ed Warnicke <hagb...@gmail.com> wrote:

> Hmm... my successful fresh clones worked with git 2.10.1 and 2.7.4...
>
> Ed
>
>
>
> On Tue, Feb 14, 2017 at 5:58 AM, Bill Fischofer <bill.fischo...@linaro.org
> > wrote:
>
>> I just verified that this issue also happens in git 2.12.0.rc1, which
>> is the current git master. So something has clearly changed in
>> git-land of late that doesn't like the repos hosted at gerrit.fd.io
>>
>> On Tue, Feb 14, 2017 at 7:13 AM, Bill Fischofer
>> <bill.fischo...@linaro.org> wrote:
>> > Thanks, Ed. A bit of further digging shows that I get this message
>> > using git 2.11, using git 2.9 (distributed as part of Ubuntu 16.10)
>> > things work just fine. So I assume git is adding some new checks for
>> > https connections?
>> >
>> > On Mon, Feb 13, 2017 at 9:15 PM, Ed Warnicke <hagb...@gmail.com> wrote:
>> >> As a data point, I just did a fresh clone using that URL:
>> >> https://gerrit.fd.io/r/vpp/
>> >> with no hiccups.
>> >>
>> >> Ed
>> >>
>> >> On Mon, Feb 13, 2017 at 7:57 PM, Bill Fischofer <
>> bill.fischo...@linaro.org>
>> >> wrote:
>> >>>
>> >>> Sorry if this has already been answered. I have a clone of the VPP
>> >>> repo from a few months ago that I went to update this evening and got
>> >>> this error message:
>> >>>
>> >>> git pull
>> >>> fatal: unable to access 'https://gerrit.fd.io/r/vpp/': Problem with
>> >>> the SSL CA cert (path? access rights?)
>> >>>
>> >>> Has the repo moved?  The fd.io web page still points to this URL as
>> >>> what should be cloned to get a local dev copy of VPP.
>> >>>
>> >>> Thanks.
>> >>>
>> >>> Bill Fischofer, Linaro
>> >>> ___
>> >>> 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] VPP Repo status?

[Ed Warnicke]

As a data point, I just did a fresh clone using that URL:
https://gerrit.fd.io/r/vpp/
with no hiccups.

Ed

On Mon, Feb 13, 2017 at 7:57 PM, Bill Fischofer 
wrote:

> Sorry if this has already been answered. I have a clone of the VPP
> repo from a few months ago that I went to update this evening and got
> this error message:
>
> git pull
> fatal: unable to access 'https://gerrit.fd.io/r/vpp/': Problem with
> the SSL CA cert (path? access rights?)
>
> Has the repo moved?  The fd.io web page still points to this URL as
> what should be cloned to get a local dev copy of VPP.
>
> Thanks.
>
> Bill Fischofer, Linaro
> ___
> 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] [FD.io Helpdesk #36502] Jenkins jobs are not started

[Ed Warnicke via RT]

Please let the community know when we find out the root cause :)

Ed

On Fri, Feb 10, 2017 at 7:10 AM, Vanessa Valderrama via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> Jan,
>
> This issue has been resolved.  Jenkins minions are building as
> expected.  The minions in a stuck build status have been removed.  The
> vendor is still performing a root cause analysis.  Again we apologize
> for the inconvenience.
>
> Thank you,
> Vanessa
>
> On Fri Feb 10 04:23:41 2017, valderrv wrote:
> > Jan,
> >
> > We are aware of the issue.  There is an issue with the vendor
> > affecting all tenants.  We've opened a high priority ticket with the
> > vendor.  I will update as soon as we have more details.
> >
> > Thank you,
> > Vanessa
> >
> >
> > On Fri Feb 10 03:56:23 2017, jgel...@cisco.com wrote:
> > > Hello,
> > >
> > > No new Jenkins job was not started in the last our and the build
> > > queue
> > > is increasing. Could you, please, have a look on it?
> > >
> > > Thanks,
> > > Jan
>
>
>
> ___
> 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] [nsh_sfc-dev] Publising jvpp rc jars

[Ed Warnicke]

I'd need to take a look to see if we could find a way to make it easier
than what we are currently doing.

We build our jars without maven (not a criticism), and so the normal kinds
of things one would do in order to do this
aren't going to quite work out.

Ed

On Tue, Feb 7, 2017 at 3:30 AM, <otr...@employees.org> wrote:

> Marek, Ed,
>
> Assuming we want to have RC jars, what are the release mechanics required?
>
> Ole
>
> > On 6 Feb 2017, at 18:03, Marek Gradzki -X (mgradzki - PANTHEON
> TECHNOLOGIES at Cisco) <mgrad...@cisco.com> wrote:
> >
> > Hc2vpp also publishes RC debs and rpms. To build them reliably we need
> rc jars.
> > We use maven for build, so most convenient for us would be to have jvpp
> jars in the fd.io.release repo.
> >
> > Marek
> >
> > From: Ed Warnicke (eaw)
> > Sent: 6 lutego 2017 17:51
> > To: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <
> mgrad...@cisco.com>
> > Cc: Ole Troan (otroan) <otr...@cisco.com>; Ni, Hongjun <
> hongjun...@intel.com>; vpp-dev@lists.fd.io; hc2...@lists.fd.io;
> nsh_sfc-...@lists.fd.io
> > Subject: Re: Publising jvpp rc jars
> >
> > Question… why do we need RC jars and not just SNAPSHOTs?
> >
> > Ed
> > On Feb 6, 2017, at 9:30 AM, Marek Gradzki -X (mgradzki - PANTHEON
> TECHNOLOGIES at Cisco) <mgrad...@cisco.com> wrote:
> >
> > The only impediment for 17.01 was that we forgot to mention it on time.
> >
> > We had a chat regarding the topic and,
> > as far as I remember, you mentioned such change
> > could affect all fd.io projects (don’t remember details),
> > so we should move it to next release.
> >
> > In case of 17.04, jvpp jars (at least currently) are part of
> vpp-api-java package,
> > so perhaps it could be easier now…
> >
> > Regards,
> > Marek
> >
> > From: Ed Warnicke (eaw)
> > Sent: 6 lutego 2017 17:22
> > To: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <
> mgrad...@cisco.com>
> > Cc: Ole Troan (otroan) <otr...@cisco.com>; Ni, Hongjun <
> hongjun...@intel.com>; vpp-dev@lists.fd.io; hc2...@lists.fd.io;
> nsh_sfc-...@lists.fd.io
> > Subject: Re: Publising jvpp rc jars
> >
> > What was the impediment for 17.01?
> >
> > Ed
> > On Feb 6, 2017, at 8:50 AM, Marek Gradzki -X (mgradzki - PANTHEON
> TECHNOLOGIES at Cisco) <mgrad...@cisco.com> wrote:
> >
> > Hi,
> >
> > Would it be possible to publish jvpp rc jars in nexus for 17.04?
> >
> > https://nexus.fd.io/content/repositories/fd.io.release/io/fd/vpp/
> >
> > For 17.01 only rc debs and rpms were published.
> >
> > Publishing rc jars would allow publishing rc artifacts by hc2vpp project
> (and also nsh_sfc project we depend on).
> > Currently hc2vpp rc artifacts have to depend on jvpp snapshots which is
> not very reliable.
> >
> > Thanks,
> > Marek
> >
> > ___
> > nsh_sfc-dev mailing list
> > nsh_sfc-...@lists.fd.io
> > https://lists.fd.io/mailman/listinfo/nsh_sfc-dev
>
>
> ___
> nsh_sfc-dev mailing list
> nsh_sfc-...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/nsh_sfc-dev
>
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Committer / Maintainer model.

[Ed Warnicke]

In the frenzy around the 17.01 release, this seems to have died down a
bit.  Seems worth revitalizing the discussion somewhat, as it appears to
have
been productive.

I tend to be something of an incrementalist, and strongly opposed to
layering too much bureaucracy on things, but sometimes finding a way to
restructure input can be helpful without bringing extra weight... so lets
explore it a bit :)

Towards that end, I would suggest:

1)  Let's talk about this in the vpp call tomorrow morning (Dave, if I
could impose, would you add this to the agenda)
2)  Let's look into getting a gerrit to discuss around a MAINTAINER file.
I personally tend to find it is easier to talk around a gerrit in
circumstances like this
3)  Let's look into what it would take to get gerrit to auto assign
reviewers based on that file
4)  Discuss how folks feel about the the vpp committers adopting among
themselves a policy of waiting for and respecting +1/-1 from maintainers
impacted by a patch.  Clearly, committers have to retain the right to
exercise judgment, but maybe something like adding a comment to the gerrit
to provide clarity when they do not wait for a review from an impacted
maintainer would also be a good social expectation to develop.

Basically, let's explore the mechanics that would make it possible to
explore this space, and talk about what would be good social conventions to
try out.

Thoughts?

Ed

On Wed, Dec 21, 2016 at 4:44 PM, Luke, Chris  wrote:

> If the issue is that of plugins, then I would concur, though tangentially
> there still seems to be some work to harmonize how projects produce their
> artifacts. Dividing things into projects has the neat property that those
> whose maintainers become negligent cause the project to wither on the vine
> and naturally die off.
>
>
>
> Not having witnessed the discussion on the VPP call that started this
> though (I’m out this week[1]) what is it that is driving this discussion?
>
>
>
> I really want to avoid protracted hierarchy, which I doubt will solve the
> problem and worse may give the appearance of solving it. I dislike the
> accompanying bureaucracy that, for example, some OpenStack projects
> exhibit. It is my observation that in such projects the discussion becomes
> more the politics of a change than the merit of it. I do not have the time
> for such games.
>
>
>
> Cheers,
>
> Chris.
>
>
>
> [1] Which today involves a story about my arm being up-to-the-elbow in my
> furnace… but a tale of misadventure for another time perhaps. :)
>
>
>
> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
> Behalf Of *Florin Coras
> *Sent:* Wednesday, December 21, 2016 15:44
> *To:* Damjan Marion 
> *Cc:* vpp-dev 
> *Subject:* Re: [vpp-dev] Committer / Maintainer model.
>
>
>
> Wouldn’t it be better to have separate projects for each plugin (or maybe
> groups of them) and thereby have maintainers automatically become
> committers within their respective projects? As far as I can see this
> diminishes load on VPP committers and gives the required ‘power' to the
> interested parties.
>
>
>
> Just my 0.02$
>
>
>
> Florin
>
>
>
> On Dec 21, 2016, at 10:25 AM, Damjan Marion 
> wrote:
>
>
>
>
> On 21 Dec 2016, at 18:49, Kinsella, Ray  wrote:
>
>
>
> If somebody submits plugin change + 3 lines of new
> code in critical ip4 path, I will greatly benefit from +1 received from
> plugin maintainer and i will focus on this 3 lines.
> If I don’t have +1 from plugin maintainer, i will just left whole diff
> in the gerrit, simply because i don't have a clue about that plugin.
>
>
> But really, the committer will have nothing to add about the plugin in
> this case.
>
> A more efficient process would be to let an IPv4 committer review and
> commit the IPv4 change, with the Plugin committer separately doing likewise.
>
> Many open source project require that patches be made separately for
> component.
>
>
> Yes, and hire one guy to bitch with people who are not following that
> rule...
> ___
> 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

Re: [vpp-dev] Publising jvpp rc jars

[Ed Warnicke (eaw)]

What was the impediment for 17.01?

Ed
On Feb 6, 2017, at 8:50 AM, Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES 
at Cisco) > wrote:

Hi,

Would it be possible to publish jvpp rc jars in nexus for 17.04?

https://nexus.fd.io/content/repositories/fd.io.release/io/fd/vpp/

For 17.01 only rc debs and rpms were published.

Publishing rc jars would allow publishing rc artifacts by hc2vpp project (and 
also nsh_sfc project we depend on).
Currently hc2vpp rc artifacts have to depend on jvpp snapshots which is not 
very reliable.

Thanks,
Marek

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] [honeycomb-dev] Honeycomb 1.17.01 Released

[Ed Warnicke]

Congrats!

Ed

On Mon, Jan 30, 2017 at 9:21 AM, Maciek Konstantynowicz (mkonstan) <
mkons...@cisco.com> wrote:

> Congrats All !
>
> -Maciek
>
> On 30 Jan 2017, at 16:00, Marek Gradzki -X (mgradzki - PANTHEON
> TECHNOLOGIES at Cisco)  wrote:
>
> The honeycomb 1.17.01 release is up.
>
> Honeycomb artifacts can be found on nexus:
> https://nexus.fd.io/content/repositories/fd.io.release/io/fd/honeycomb/
>
> Honeycomb is a generic NETCONF/RESTCONF management agent.
> VPP specific distribution of honeycomb was moved to hc2vpp project (also
> to be released today).
>
> More details can be found in release notes:
> https://docs.fd.io/honeycomb/1.17.01/release-notes-
> aggregator/release_notes.html
>
> Many thanks to all contributors and testers,
>
> Marek
>
> ___
> honeycomb-dev mailing list
> honeycomb-...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/honeycomb-dev
>
>
>
> ___
> honeycomb-dev mailing list
> honeycomb-...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/honeycomb-dev
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] igb_uio -> uio_pci_generic

[Ed Warnicke]

Looping in the deb_dpdk and rpm_dpdk guys to see if they have thoughts on
how these things play out in deployment.

Ed

On Tue, Jan 24, 2017 at 9:05 PM, Burt Silverman  wrote:

> Hi Damjan,
>
> My understanding is that CONFIG_VFIO_NOIOMMU will never be set in a stock
> kernel, and you will need to build a custom kernel for that. I understand
> that with this option, the kernel cannot guarantee that applications are
> prevented from creating bugs that normally the kernel can guarantee will
> not occur (outside of a kernel bug.) It therefore violates the fundamental
> Linux system design. That being said, you may wish to accept the risk for
> performance reasons and build a custom kernel. The other strange thing
> would be that MSI or MSI-X style interrupts are not needed for performance.
> The people who developed them have made a lot of noise about how they came
> about for performance reasons. I have no direct experience, but to learn
> that they are not important is a shock.
>
> It seems to me that the Ubuntu 14.04 issue is really a separate one from
> all of this, although I would imagine that the conclusion to stop
> supporting it does not change.
>
> Burt
>
> On Tue, Jan 24, 2017 at 1:07 PM, Damjan Marion (damarion) <
> damar...@cisco.com> wrote:
>
>>
>> > On 24 Jan 2017, at 18:40, Damjan Marion (damarion) 
>> wrote:
>> >
>> >>
>> >> On 24 Jan 2017, at 18:26, Stephen Hemminger <
>> step...@networkplumber.org> wrote:
>> >>
>> >> On Tue, 24 Jan 2017 17:14:42 +
>> >> "Damjan Marion (damarion)"  wrote:
>> >>
>> >>> Is anybody aware of any valid reason why we cannot switch to
>> uio_pci_generic
>> >>> as default PCI uio driver in ubuntu packages?
>> >>>
>> >>> I think generally people don’t like out-of-tree modules, so as long
>> as we are getting
>> >>> the same service from uio_pci_generic we should use it…
>> >>>
>> >>> Thanks,
>> >>>
>> >>> Damjan
>> >
>> >> uio_pci_generic does not support MSI or MSI-X interrupts, only legacy
>> INTX.
>> >
>> > I know but do we really care?
>> >
>> >>
>> >> The preference should always be to use VFIO. Even on systems without
>> IOMMU.
>> >
>> > What is the perf impact?
>> >
>> > Also, I just tried with kernel 4.8 on rangeley ATOM, and i got:
>> >
>> > [536030.250072] vfio-pci: probe of :00:14.0 failed with error -22
>> > [536030.253271] vfio-pci: probe of :00:14.0 failed with error -22
>> >
>> > I guess I’m doing something wrong….
>>
>> This explains:
>>
>> grep VFIO_NOIO /boot/config-4.8.0-34-generic
>> # CONFIG_VFIO_NOIOMMU is not set
>>
>> So vfio is out of the game of being default choice, people can still
>> switch simply with one line change in /etc/vpp/startup.conf.
>>
>>
>> ___
>> 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

[vpp-dev] Ubuntu 14.04 support in vpp 17.04?

[Ed Warnicke]

The question has come up on a different thread as to whether we should
continue to support
Ubuntu 14.04 in vpp 17.04.

What are folks opinions?

Ed
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] igb_uio -> uio_pci_generic

[Ed Warnicke]

I can tell you why we did it to begin with (which I'm hoping is no longer a
valid reason).  We originally did it because ubuntu 14.04 did not have any
appropriate usable packages for uio drivers.  I for one would be overjoyed
to make the shift you are proposing, but we do need to decide what we want
to do about ubuntu 14.04 in the process.

One possible question to ask is: do we want to support ubuntu 1404 in vpp
17.04?

Ed

On Tue, Jan 24, 2017 at 10:14 AM, Damjan Marion (damarion) <
damar...@cisco.com> wrote:

>
> Is anybody aware of any valid reason why we cannot switch to
> uio_pci_generic
> as default PCI uio driver in ubuntu packages?
>
> I think generally people don’t like out-of-tree modules, so as long as we
> are getting
> the same service from uio_pci_generic we should use it…
>
> 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

Re: [vpp-dev] [FD.io Helpdesk #35687] Re: Verify job failure(s)

[Ed Warnicke]

I'd wait to see if Vanessa can shed light on reasoning there.  Sometimes
things that look odd are very smart but obscure.

Ed

On Thu, Jan 19, 2017 at 9:06 PM, Thanh Ha <thanh...@linuxfoundation.org>
wrote:

> If we have consensus that apt-get update during vm init is a bad idea then
> this patch might be a good quick solution [0].
>
> Regards,
> Thanh
>
> [0] https://gerrit.fd.io/r/4797
>
>
> On Thu, Jan 19, 2017 at 10:47 PM, Ed Warnicke <hagb...@gmail.com> wrote:
>
>> Thanh,
>>
>> I'm not quite sure the logic of having it at that particular point
>> either.  Something to investigate.
>>
>> Ed
>>
>> On Thu, Jan 19, 2017 at 8:44 PM, Thanh Ha <thanh...@linuxfoundation.org>
>> wrote:
>>
>>> FWIW in OpenDaylight we don't typically run yum update or apt-get update
>>> in our init-scripts on VM spinup. At the job level we only install
>>> dependencies needed by the build. I'm not sure why fd.io is running
>>> upgrades but it was existing in the script when I looked at it. System
>>> upgrades during VM spinup is not something the OpenDaylight project does at
>>> least.
>>>
>>> Regards,
>>> Thanh
>>>
>>>
>>> On Thu, Jan 19, 2017 at 10:38 PM, Dave Wallace <dwallac...@gmail.com>
>>> wrote:
>>>
>>>> Ed, Thanh, Vanessa,
>>>>
>>>> IMHO, updating the ubuntu packages every time a VM is spun up is a bug
>>>> wrt. being able to reproduce some (hopefully rare) build/test issues.
>>>> Since every VM is potentially running with different versions of OS
>>>> components, when a failure occurs (e.g. in "make test"), then it may be
>>>> necessary to recreate the exact run-time environment in order to reproduce
>>>> the failure. Unless the complete package list is being archived for every
>>>> VM instance that is spun up, this may not be possible.
>>>>
>>>> My experience is that those rare cases where a tool or environment
>>>> issue causes a failure, the cost to find the issue is extraordinarily high
>>>> if you do not have the ability to recreate the EXACT build/run-time
>>>> environment.  This is why CSIT does not update OS components in the VM
>>>> initialization scripts and the VM images are built from a specific package
>>>> list instead of pulling the latest versions from the apt repositories.
>>>>
>>>> My recommendation is that the VM images be updated periodically (weekly
>>>> or whenever a new security update is released) and the package lists
>>>> archived for each VM image version.  Each VM image should also be verified
>>>> against a known good VPP commit version as is done with CSIT branches.
>>>> Ideally we should build a fully automated continuous deployment model to
>>>> reduce the amount of work to update the VM images to running a Jenkins job
>>>> to build/test/deploy a new VM image from the latest packages versions.
>>>>
>>>> With that automation in place, this mechanism could be extended for use
>>>> by CSIT as well as "make test", thus ensuring that all of our testing was
>>>> done with the same OS component version.  Ideally, all projects should be
>>>> using the same OS components to ensure that everything is tested in the
>>>> same run-time environment.
>>>>
>>>> Thanks,
>>>> -daw-
>>>>
>>>> On 1/19/2017 8:31 PM, Thanh Ha via RT wrote:
>>>>
>>>> The issue with the 16.04 Ubuntu image is fixed now (but we may require 
>>>> some additional actions which I'll send to Vanessa to in case this issue 
>>>> comes up again). We fixed this issue tonight by rebuilding ubuntu1604 and 
>>>> deploying the new image.
>>>>
>>>> I'm going to close this ticket as resolved and we'll take the additional 
>>>> task to find a way to ensure this doesn't appear again off of this ticket.
>>>>
>>>> If you're not interested in the detailed analysis you can stop reading now.
>>>>
>>>> For those interested I suspect that the lock issue will appear again 
>>>> (although I could be wrong). The reason I believe so is that our vm init 
>>>> script runs "apt-get update" as an initialization step when the VM boots 
>>>> up at creation time via this script [0]. Ed mentioned that we didn't see 
>>>> this in the past and it only started appear again recently as we deployed

Re: [vpp-dev] [FD.io Helpdesk #35687] Re: Verify job failure(s)

[Ed Warnicke]

e while step 2 is still 
>> running apt-get update in the background because it was a non-blocking 
>> function.
>>
>> A few ideas I have to get around this.
>>
>> a) Allow init-script to continue running apt-get update however have a shell 
>> script at the start of Ubuntu jobs that waits for the lock to get released 
>> before allowing the job to start
>>
>> b) Remove apt-get update from init-script and make the job run apt-get 
>> update at the beginning of it's execution
>>
>> c) Regularly update VMs to ensure that apt-get update always runs quickly
>>
>>  Regards,
>> Thanh
>>
>> [0] 
>> https://git.fd.io/ci-management/tree/jenkins-scripts/basic_settings.sh#n14
>>
>>
>> On Thu Jan 19 19:23:59 2017, hagbard wrote:
>>
>> FYI... helpdesk is on it, and its being worked in #fdio-infra on IRC
>>
>> Ed
>>
>> On Thu, Jan 19, 2017 at 4:31 PM, Ed Warnicke <hagb...@gmail.com> 
>> <hagb...@gmail.com> wrote:
>>
>>
>> Looping in help desk.
>> On Thu, Jan 19, 2017 at 4:16 PM Dave Barach (dbarach) <dbar...@cisco.com> 
>> <dbar...@cisco.com>
>> wrote:
>>
>>
>> Folks,
>>
>>
>>
>> See https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/3378/console
>>
>>
>>
>> 11:00:46 E: Could not get lock /var/lib/dpkg/lock - open (11: Resource
>> temporarily unavailable)
>>
>> 11:00:46 E: Unable to lock the administration directory (/var/lib/dpkg/),
>> is another process using it?
>>
>>
>>
>> I recognize this failure from my own Ubuntu 16.04 system: a cron-job
>> starts “apt-get -q”, which for whatever reason does not terminate. As a
>> workaround, “sudo killall apt-get || true” before trying to acquire build
>> dependencies...
>>
>>
>>
>> HTH... Dave
>>
>>
>> ___
>>
>> vpp-dev mailing list
>> vpp-dev@lists.fd.io
>> https://lists.fd.io/mailman/listinfo/vpp-dev
>>
>> ___
>> 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] [FD.io Helpdesk #35687] [linuxfoundation.org #35687] Re: Verify job failure(s)

[Ed Warnicke via RT]

The issue in the immediate terms should be fixed now.

Ed


On Thu, Jan 19, 2017 at 5:23 PM, Ed Warnicke via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> FYI... helpdesk is on it, and its being worked in #fdio-infra on IRC
>
> Ed
>
> On Thu, Jan 19, 2017 at 4:31 PM, Ed Warnicke <hagb...@gmail.com> wrote:
>
> > Looping in help desk.
> > On Thu, Jan 19, 2017 at 4:16 PM Dave Barach (dbarach) <dbar...@cisco.com
> >
> > wrote:
> >
> >> Folks,
> >>
> >>
> >>
> >> See https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/3378/console
> >>
> >>
> >>
> >> 11:00:46 E: Could not get lock /var/lib/dpkg/lock - open (11: Resource
> >> temporarily unavailable)
> >>
> >> 11:00:46 E: Unable to lock the administration directory
> (/var/lib/dpkg/),
> >> is another process using it?
> >>
> >>
> >>
> >> I recognize this failure from my own Ubuntu 16.04 system: a cron-job
> >> starts “apt-get -q”, which for whatever reason does not terminate. As a
> >> workaround, “sudo killall apt-get || true” before trying to acquire
> build
> >> dependencies...
> >>
> >>
> >>
> >> HTH... Dave
> >>
> >>
> >> ___
> >>
> >> 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

Re: [vpp-dev] [FD.io Helpdesk #35687] [linuxfoundation.org #35687] Re: Verify job failure(s)

[Ed Warnicke]

The issue in the immediate terms should be fixed now.

Ed


On Thu, Jan 19, 2017 at 5:23 PM, Ed Warnicke via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> FYI... helpdesk is on it, and its being worked in #fdio-infra on IRC
>
> Ed
>
> On Thu, Jan 19, 2017 at 4:31 PM, Ed Warnicke <hagb...@gmail.com> wrote:
>
> > Looping in help desk.
> > On Thu, Jan 19, 2017 at 4:16 PM Dave Barach (dbarach) <dbar...@cisco.com
> >
> > wrote:
> >
> >> Folks,
> >>
> >>
> >>
> >> See https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/3378/console
> >>
> >>
> >>
> >> 11:00:46 E: Could not get lock /var/lib/dpkg/lock - open (11: Resource
> >> temporarily unavailable)
> >>
> >> 11:00:46 E: Unable to lock the administration directory
> (/var/lib/dpkg/),
> >> is another process using it?
> >>
> >>
> >>
> >> I recognize this failure from my own Ubuntu 16.04 system: a cron-job
> >> starts “apt-get -q”, which for whatever reason does not terminate. As a
> >> workaround, “sudo killall apt-get || true” before trying to acquire
> build
> >> dependencies...
> >>
> >>
> >>
> >> HTH... Dave
> >>
> >>
> >> ___
> >>
> >> 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

[vpp-dev] [FD.io Helpdesk #35687] [linuxfoundation.org #35687] Re: Verify job failure(s)

[Ed Warnicke via RT]

FYI... helpdesk is on it, and its being worked in #fdio-infra on IRC

Ed

On Thu, Jan 19, 2017 at 4:31 PM, Ed Warnicke <hagb...@gmail.com> wrote:

> Looping in help desk.
> On Thu, Jan 19, 2017 at 4:16 PM Dave Barach (dbarach) <dbar...@cisco.com>
> wrote:
>
>> Folks,
>>
>>
>>
>> See https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/3378/console
>>
>>
>>
>> 11:00:46 E: Could not get lock /var/lib/dpkg/lock - open (11: Resource
>> temporarily unavailable)
>>
>> 11:00:46 E: Unable to lock the administration directory (/var/lib/dpkg/),
>> is another process using it?
>>
>>
>>
>> I recognize this failure from my own Ubuntu 16.04 system: a cron-job
>> starts “apt-get -q”, which for whatever reason does not terminate. As a
>> workaround, “sudo killall apt-get || true” before trying to acquire build
>> dependencies...
>>
>>
>>
>> HTH... Dave
>>
>>
>> ___
>>
>> 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] Verify job failure(s)

[Ed Warnicke]

FYI... helpdesk is on it, and its being worked in #fdio-infra on IRC

Ed

On Thu, Jan 19, 2017 at 4:31 PM, Ed Warnicke <hagb...@gmail.com> wrote:

> Looping in help desk.
> On Thu, Jan 19, 2017 at 4:16 PM Dave Barach (dbarach) <dbar...@cisco.com>
> wrote:
>
>> Folks,
>>
>>
>>
>> See https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/3378/console
>>
>>
>>
>> 11:00:46 E: Could not get lock /var/lib/dpkg/lock - open (11: Resource
>> temporarily unavailable)
>>
>> 11:00:46 E: Unable to lock the administration directory (/var/lib/dpkg/),
>> is another process using it?
>>
>>
>>
>> I recognize this failure from my own Ubuntu 16.04 system: a cron-job
>> starts “apt-get -q”, which for whatever reason does not terminate. As a
>> workaround, “sudo killall apt-get || true” before trying to acquire build
>> dependencies...
>>
>>
>>
>> HTH... Dave
>>
>>
>> ___
>>
>> 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] Plugin for mpls over gre

[Ed Warnicke]

Calvin,

We've had some consumers express interest in MPLS over UDP:
https://tools.ietf.org/html/rfc7510

Would you be interested in working on that?

Ed

On Wed, Jan 18, 2017 at 2:37 PM, Damjan Marion (damarion) <
damar...@cisco.com> wrote:

>
>
>
> > On 18 Jan 2017, at 16:59, Calvin Ference  wrote:
> >
> > Hey VPP community,
> >
> > I was wondering if anyone had coded a plugin to do mpls over gre before?
> I'm  looking at getting my hands dirty in writing a plugin and I was
> thinking this might be a good start, but if someone already did the work
> I'll find something else.
>
> Glad to see that you’re looking to implement some feature.
> Bad news is that we already have mpls over gre implementation in the
> codebase.
>
> Maybe something else?
>
> 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

Re: [vpp-dev] VPP 17.01 Formal Release

[Ed Warnicke]

Whether there is a calendar event or not is up to our fearless Release
Manager for 17.01: Damjan.

I would suggest to him that it can probably be handled async via email/IRC
in a light weight fashion if he so chooses :)

Ed

On Fri, Jan 13, 2017 at 2:58 PM, Vanessa Valderrama <
vvalderr...@linuxfoundation.org> wrote:

> Ed,
>
> Thank you I appreciate it.  Also if there is a calendar event for the
> release please be sure I am included on the invite.
>
> Thanks,
>
> Vanessa
>
> On 01/13/2017 03:43 PM, Ed Warnicke wrote:
>
> Vanessa,
>
> Rather than enumerate the current artifacts here for vpp, I've updated the
> instructions here:
>
> https://wiki.fd.io/view/VPP/CommitterTasks/CutRelease#
> helpdesk_email_template
>
> to instruct the vpp person cutting the release to send a helpdesk email
> from a template that *should* provide you sufficient
> information to carry out the task.  Let me know if the template appears to
> be sufficient :)
>
> Ed
>
>
> On Fri, Jan 13, 2017 at 12:38 AM, Marek Gradzki -X (mgradzki - PANTHEON
> TECHNOLOGIES at Cisco) <mgrad...@cisco.com> wrote:
>
>> Hi,
>>
>> please also include jvpp jars (hc2vpp 17.01 depends on them).
>> For 16.06 and 16.09, they were installed in
>> <https://nexus.fd.io/content/repositories/fd.io.release>
>> https://nexus.fd.io/content/repositories/fd.io.release
>>
>> Regards,
>> Marek
>>
>> -Original Message-
>> From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io]
>> On Behalf Of Vanessa Valderrama
>> Sent: 12 stycznia 2017 20:20
>> To: Dave Barach (dbarach) <dbar...@cisco.com>; vpp-dev@lists.fd.io
>> Subject: Re: [vpp-dev] VPP 17.01 Formal Release
>>
>> Dave,
>>
>> Specifically the artifacts I will be promoting during the release.
>>
>> Thank you,
>>
>> Vanessa
>>
>> On 01/12/2017 01:18 PM, Dave Barach (dbarach) wrote:
>> > Are you interested in a list of .debs and .rpms?
>> >
>> > Thanks… Dave
>> >
>> > -Original Message-
>> > From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io]
>> On Behalf Of Vanessa Valderrama
>> > Sent: Thursday, January 12, 2017 2:11 PM
>> > To: vpp-dev@lists.fd.io
>> > Subject: [vpp-dev] VPP 17.01 Formal Release
>> >
>> > In preparation for the VPP 17.01 formal release, please provide the
>> list of artifacts as soon as possible.
>> >
>> > Thank you,
>> > Vanessa
>> >
>> >
>>
>>
>> ___
>> 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