[opnfv-tech-discuss] 答复: OPERA is calling for developers for Open-O integration

2016-12-02 Thread Chigang (Justin)
Hi Yingjun, Glad to hear OPREA integrating with Compass. We have finished OpenStack Newton release integation in Danube MS3. In next step, it is planning to support feature project integrating. Huangxiangyu is good at Compass integration, I recommend him as the cross liaison between Com

[opnfv-tech-discuss] OpenStack contribution: Gets easier over time (blog)

2016-12-02 Thread Dave Neary
Hi all, A colleague of mine, Assaf Muller, did a brief study on time to patch acceptance compared on various axes: number of patches, number of reviews, time since first patch, size of patch, etc. He found, unsurprisingly, that the more patches you propose, the quicker the patches are accepted, o

Re: [opnfv-tech-discuss] [Apex] [Fdio]deployment error

2016-12-02 Thread Tim Rozet
Ah sorry. I was confusing with ovs-dpdk, where we install dpdk rpms separately. Do we also want to support this for that scenario? We could get OVS4NFV to rebuild dpdk rpms for us. Tim Rozet Red Hat SDN Team - Original Message - From: "Feng Pan" To: "Tim Rozet" Cc: "Daniel Bernier (

Re: [opnfv-tech-discuss] [Apex] [Fdio]deployment error

2016-12-02 Thread Feng Pan
Tim, I don't believe we can just use a mlx pmd driver, since support for mlx nic requires DPDK rebuild. This will need to be resolved from VPP side as Daniel point out because vpp packages its own DPDK. Thanks, Feng On Fri, Dec 2, 2016 at 3:39 PM, Tim Rozet wrote: > Hey sorry Patrick. I misse

Re: [opnfv-tech-discuss] Discussion on UTC vs. Pacific Time

2016-12-02 Thread Dave Neary
Hi Ray, On 12/02/2016 01:33 PM, Raymond Paik wrote: > Over the past couple of years, we've had discussions on whether meetings > like TSC or Release call times should be based on Pacific Time (as has > been the tradition since OPNFV started) or if the community should move > to UTC. > > UTC obvio

Re: [opnfv-tech-discuss] [Apex] [Fdio]deployment error

2016-12-02 Thread Tim Rozet
Hey sorry Patrick. I missed your earlier question. +Feng who also has done a great deal of work on the VPP side. We allow passing the UIO driver to use in the deploy settings. So if we had a package with the Mellanox driver installed on Overcloud image, we should be able to use it. Is that

Re: [opnfv-tech-discuss] Discussion on UTC vs. Pacific Time

2016-12-02 Thread Ashlee Young
It doesn't matter to me. The issue is making sure the info is up to date, especially if calendar invites are used. Also, I really wish we could discuss stuff via email or discussion forum first. My preference has and continues to be for Discourse. But I think we are trying to have too complex of

[opnfv-tech-discuss] Discussion on UTC vs. Pacific Time

2016-12-02 Thread Raymond Paik
All, Another follow-up from the TSC... Over the past couple of years, we've had discussions on whether meetings like TSC or Release call times should be based on Pacific Time (as has been the tradition since OPNFV started) or if the community should move to UTC. UTC obviously has the benefit of

Re: [opnfv-tech-discuss] Feedback requested on test documentation example from Models

2016-12-02 Thread David McBride
Bryan, In general, I like this approach. My only comment is that I think that the "Post-State" criteria should be more specific and detailed. For example, "Tacker is installed and active in a docker container". Specifically, how is this determined? OS commands? Docker commands? Something else?

Re: [opnfv-tech-discuss] OPERA is calling for developers for Open-O integration

2016-12-02 Thread Yingjun Li
Huabing Thanks for your consistent support for the Open-O integration with OPNFV. Which integration part are your team particularly interested in? I will collect all the replies and mitigate the tasks and resources. Best Yingjun From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn] Se

[opnfv-tech-discuss] Single recurring meetings for the two GTM accounts

2016-12-02 Thread Raymond Paik
All, As discussed in the TSC call, I created single recurring meetings for each of the GTM accounts we have for calls. You can find the info below (and I also added this to the main meetings wiki page at https://wiki.opnfv.org/display/meetings/Meetings). For people who were not on the TSC call,

[opnfv-tech-discuss] [IPv6] Project Meeting #53

2016-12-02 Thread HU, BIN
BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Pacific Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:-0700 TZOFFSETTO:-0800 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02000

[opnfv-tech-discuss] [IPv6] IPv6 meeting summary today Dec 2

2016-12-02 Thread HU, BIN
Hello community, We had a very good team discussion of IPv6 today. Minutes is captured in https://wiki.opnfv.org/display/ipv6/Minutes+20161202. One of our focus is upstream IPv6 support in ODL. Sridhar has been focusing on driving IPv6 in ODL. Currently east-west traffic routing is supported

Re: [opnfv-tech-discuss] OPERA is calling for developers for Open-O integration

2016-12-02 Thread David McBride
Yingjun, Thanks for the update. In order to meet MS6 (test case implementation) for Danube, you will need to complete items 1, 2, and 3 in the next 7 weeks. Do you feel confident about doing that? Thanks. David On Thu, Dec 1, 2016 at 10:38 AM, Yingjun Li wrote: > Dear All > > > > OPERA proj

Re: [opnfv-tech-discuss] [Apex] [Fdio]deployment error

2016-12-02 Thread Bernier, Daniel (520165)
FYI, Issue is that the Mellanox PMD driver is not compiled by default with DPDK since it requires proprietary libs. Without it, VPP cannot bind to these NICs. There is a thread regarding this in vpp-...@lists.fd.io -Original Message- From: Patrick Lemay Date: Friday, November 25, 2016

[opnfv-tech-discuss] Discussion for OpenRetriever

2016-12-02 Thread jiaxuan
Hi All Thanks for the discussion for the new project proposal OpenRetriever. I answer these questions we have discussed in the last meeting. If I have something misunderstood, please let me know. 1. If there is a baremetal deployment, in case of COE, regarding networking part, do you intend to