[opnfv-tech-discuss] [dovetail]dovetail weekly meeting 12/9

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:China Standard Time BEGIN:STANDARD DTSTART:16010101T00 TZOFFSETFROM:+0800 TZOFFSETTO:+0800 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T00 TZOFFSETFROM:+0800 TZOFFSETTO:+0800 END:DAYLIGHT

[opnfv-tech-discuss] [qtip] Sprint QTIP-D4 started

QTIP runners, Ready for the fourth sprint in Danube? Let's go! In this sprint, we shall focus on 1. YardStick integration 2. CLI evolution (intern project) 3. Runner module refactoring Check the active sprint page[1] for details [1]: https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=135

[opnfv-tech-discuss] [Compass4nfv] Colorado 3.0 artifacts for Compass4nfv

Hi David, Aric, Here is the artifacts for Compass4nfv Colorado 3.0 release. http://artifacts.opnfv.org/compass4nfv/colorado/opnfv-2016-12-05_08-17-18.iso Thanks, Justin ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org

[opnfv-tech-discuss] [qtip] Sprint Report QTIP-D3

Thanks to all contributors' effort, we accomplished many goals in this sprint 1. kicked off the first internship program in QTIP 2. completed the compute QPI design specification 3. resumed verification job is after framework refactoring Though there is some delay on YardStick integration spec

[opnfv-tech-discuss] Canceled: [VSPERF] Weekly Call

BEGIN:VCALENDAR METHOD:CANCEL 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

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

Hi Yingjun, Does OPERA and Open-O have regular meetings? we can discuss some further detail about the integration. Regards HuangXiangyu From: zhao.huab...@zte.com.cn [mailto:zhao.huab...@zte.com.cn] Sent: Tuesday, December 06, 2016 9:45 AM To: Yingjun Li Cc: Chigang (Justin); Yunxia

[opnfv-tech-discuss] [doctor] performance profiler

Doctors, Please find the slides[1] for the background of performance profiler[2] as requested in gerrit review[3] and last meeting[4]. Feel free to give comments. [1]: https://goo.gl/98Osig [2]: https://jira.opnfv.org/browse/DOCTOR-72 [3]: https://gerrit.opnfv.org/gerrit/#/c/25081/ [4]:

[opnfv-tech-discuss] [Apex] C3.0 artifacts for Apex

Hey Aric, David, Here are the artifacts built for release: http://artifacts.opnfv.org/apex/colorado/opnfv-2016-12-05.iso http://artifacts.opnfv.org/apex/colorado/opnfv-apex-3.0-20161205.noarch.rpm http://artifacts.opnfv.org/apex/colorado/opnfv-apex-common-3.0-20161205.noarch.rpm http

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

I fully agree with Gerald – especially regarding his point that it is simpler to calculate the local meeting time based on UTC. The recent change has caused quite some confusion in the NetReady meeting schedule… Some of you have noticed. ;-) Georg From:

[opnfv-tech-discuss] Colorado 3.0 release TODAY!

If you haven't already done so, please tag your project. Also, make sure that your documentation links have been updated. Instructions here . This should be done no later than 12 p.m. (PST). We are having our final Colorado 3.0 daily

[opnfv-tech-discuss] Canceled: [barometer] Weekly Call

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:GMT Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:+0100 TZOFFSETTO:+ RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T01

[opnfv-tech-discuss] Invitation: Colorado retrospective @ Thu Dec 8, 2016 2pm - 4pm (EST) (opnfv-tech-discuss@lists.opnfv.org)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20161208T19Z DTEND:20161208T21Z DTSTAMP:20161205T145102Z ORGANIZER;CN=dmcbr...@linuxfoundation.org:mailto:dmcbride@linuxfoundation.o rg

[opnfv-tech-discuss] Canceled: [barometer] Weekly Call

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:GMT Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:+0100 TZOFFSETTO:+ RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T01

[opnfv-tech-discuss] Canceled: [barometer] Weekly Call

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:GMT Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:+0100 TZOFFSETTO:+ RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T01

[opnfv-tech-discuss] Canceled: [barometer] Weekly Call

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:GMT Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:+0100 TZOFFSETTO:+ RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T01

Re: [opnfv-tech-discuss] [OVSNFV] Sharing the priority path result

Hi Chunghan, Pls find attached. From: Lee, Chunghan [mailto:lee.chung...@jp.fujitsu.com] Sent: Monday, December 5, 2016 1:11 AM To: opnfv-tech-discuss@lists.opnfv.org Cc: O Mahony, Billy ; Gray, Mark D ; therb...@redhat.com; Lee, Chunghan

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

+1 for UTC /Morgan Le 05/12/2016 à 10:11, Kunzmann, Gerald a écrit : > > Hi everyone, > > > > Independent on which timezone we use, this will result in conflicts in > some regions. I agree with Bob that for US/EU this would mean a shift > in meeting time for months and might lead to meeting

Re: [opnfv-tech-discuss] [SDNVPN test Case fail criteria

So make all test cases require 100% success and only do separation testing in a specific test that will be disabled? From: Nikolas Hermanns [mailto:nikolas.herma...@ericsson.com] Sent: Monday, December 05, 2016 10:49 AM To: Skiadas Romanos; BV Guravareddy; opnfv-tech-discuss@lists.opnfv.org

[opnfv-tech-discuss] [multisite][netready]networking for application geo-redundancy

Hello, Tricircle plans to provide L2 network across Neutron to ease supporting application geo-redundancy: For example, in the following figure, the application is consisted of instance1 and instance2, these two instances will be deployed into two OpenStack. Intance1 will provide service

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

Hi everyone, Independent on which timezone we use, this will result in conflicts in some regions. I agree with Bob that for US/EU this would mean a shift in meeting time for months and might lead to meeting clashes with other non-OPNFV meetings. However, at the moment this problem is with Asia

[opnfv-tech-discuss] [SDNVPN test Case fail criteria

1. We need to change the 75% test criteria for all test. That just makes thing more complicated. Can we copy the tests we have an rewrite them so that we don't need the criteria? Then we disable the first test and run them when the bug is fixed upstream. 2. I think we should add a