[opnfv-tech-discuss] [OPNFV] ODL target Release for Euphrates

2017-08-08 Thread morgan.richomme
Hi, I did not find the list of the target versions for the main components integrated in Euphrates version. it would make sense to explicitely reference them on one of the wiki pages dedicated to the release https://wiki.opnfv.org/display/SWREL/Euphrates In functest, we need to know it.

Re: [opnfv-tech-discuss] [OPNFV] ODL target Release for Euphrates

2017-08-08 Thread jason
Hi Morgan, Daisy currently uses Carbon snapshot earlier than SR1 but the target is Carbon SR1. On Aug 8, 2017 15:18, wrote: > Hi, > > I did not find the list of the target versions for the main components > integrated in Euphrates version. > it would make sense to

Re: [opnfv-tech-discuss] [OPNFV] ODL target Release for Euphrates

2017-08-08 Thread Manuel Buil
Hello Morgan, As far as I understood, the OPNFV release is only agreeing on the openstack version. So I assume different projects can use different ODL versions, or? In SFC we are targetting ODL Nitrogen SR0. It will be officially released on the 7th of September and we are currently using our

Re: [opnfv-tech-discuss] [OPNFV] ODL target Release for Euphrates

2017-08-08 Thread Frank Brockners (fbrockne)
Hi Morgan, it might well be that there is no one answer to your question – especially for those scenarios which are leading edge and actively drive development upstream (i.e. in ODL and HoneyComb). In addition, given the sister relationship between ODL and Honeycomb, model updates go hand in

[opnfv-tech-discuss] [vsperf] Agenda for VSPERF weekly meeting - 9 Aug 2017

2017-08-08 Thread Cooper, Trevor
Previous Minutes - Ww31 http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-08-02-14.55.html - ww30 http://ircbot.wl.linuxfoundation.org/meetings/opnfv-vswitchperf/2017/opnfv-vswitchperf.2017-07-26-15.03.html Agenda 1. Opens and

Re: [opnfv-tech-discuss] [OPNFV] ODL target Release for Euphrates

2017-08-08 Thread cedric.ollivier
Hello, I understand your point but Functest requires a default answer to finish the containers and to write the testcase config file (suites and dependencies on scenarii or installers). Then we take the decision about the release (the last one seems fine) and if the NetVirt test suite is ran

Re: [opnfv-tech-discuss] [OPNFV] ODL target Release for Euphrates

2017-08-08 Thread cedric.ollivier
Hello, It’s true if we only consider the Neutron API but we run several dedicated tests to check the ODL Neutron API. Even if the default robot suite is quite basic, we have to know which branch of ODL we should clone. I know that it shouldn’t induce problems because the API has not been

Re: [opnfv-tech-discuss] [OPNFV] ODL target Release for Euphrates

2017-08-08 Thread Frank Brockners (fbrockne)
Hi Cédric, is there a way to have a per-scenario functest config file? We could have a default file, which we’d modify on a case by case basis. Note that e.g. only a subset of the scenarios use NetVirt, hence having Netvirt as a default testsuite probably won’t make sense. Thanks, Frank

Re: [opnfv-tech-discuss] [OPNFV] ODL target Release for Euphrates

2017-08-08 Thread Xueyifei (Yifei Xue)
Hi Morgan Compass currently uses Carbon SR1. Once SR2 of Carbon released, we will use SR2 immediately. For OPNFV E release, we are not going to upgrade odl from Carbon to Nitrogen. Thanks Yifei Xue From: opnfv-tech-discuss-boun...@lists.opnfv.org

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

2017-08-08 Thread Tahhan, Maryam
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

2017-08-08 Thread Tahhan, Maryam
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] [barometer] Update

2017-08-08 Thread Tahhan, Maryam
Hi folks [barometer] Update Congratulations to our new committers: Al Morton, Aaron Smith, Emma Foley, and Calin Gherghe. Maryam OOO till the 29th of August. Please complete any code reviews you are added to for MS5 and MS6. * E Release * MS 5 pushed out to Aug 11, MS6 pushed out to

[opnfv-tech-discuss] Weekly Technical Discussion #97

2017-08-08 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

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

2017-08-08 Thread Tahhan, Maryam
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] [Fds-dev] [APEX] [Euphrates] Euphrates testing - database issues

2017-08-08 Thread Tim Rozet
Juraj, Now I'm thinking this is the same problem as before. I see we had this in Danube: https://github.com/opnfv/apex/blob/stable/danube/build/baremetal-environment.yaml which we are not using in master because this problem was supposed to be fixed upstream. Can you try including this file

Re: [opnfv-tech-discuss] Jump server common configuration for PXE/admin network - questions

2017-08-08 Thread Julien
please refer to my inline comments. Alexandru Avadanii 于2017年8月7日周一 上午3:30写道: > Hi, > I am looking at integrating Fuel@OPNFV/MCP with our OPNFV baremetal PODs > (both x86_64 and aarch64). > Right now I am playing with MaaS and its network configuration. > > The old