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

[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 proposed topics

2.   Release milestones update

3.   Ixia license

4.   Ixia modifications for IxNetwork

5.   Test API and Dashboards

6.   IMIX traffic profile

7.   TREX Integration

8.   Latency histograms and PCAP analysis tools

9.   Noisy neighbor tests

10.   Tuning CI POD
Time: Wednesday UTC 15h00, Ireland (UTC/GMT +1) 16h00, PDT 8h00 (UTC/GMT -7) 
... Currently observing daylight saving

IRC: freenode https://freenode.net/ channel: #opnfv-vswitchperf 
http://webchat.freenode.net/?channels=opnfv-vswitchperf

Audio: https://global.gotomeeting.com/join/391235029
You can also dial in using your phone.  United States: +1 (571) 317-3116  
Access Code: 391-235-029
Phone numbers from other countries are here ... 
https://wiki.opnfv.org/display/meetings

/Trevor
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Fds-dev] [APEX] [Euphrates] Euphrates testing - database issues

[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 in your overcloud deployment and see 
if it works?

Thanks,

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco)" 

To: "Tim Rozet" , opnfv-tech-discuss@lists.opnfv.org
Cc: fds-...@lists.opnfv.org
Sent: Friday, August 4, 2017 11:44:16 AM
Subject: RE: [Fds-dev] [APEX] [Euphrates] Euphrates testing - database issues

The box is not OOM – it has more than 200GB spare. One thing I forgot to 
mention was that I let the setup as is for a day or two (without doing anything 
with it) and then the issue appeared.

Juraj

From: Tim Rozet [mailto:tro...@redhat.com]
Sent: Friday, 04 August, 2017 16:09
To: Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco) 
; opnfv-tech-discuss@lists.opnfv.org
Cc: fds-...@lists.opnfv.org
Subject: Re: [Fds-dev] [APEX] [Euphrates] Euphrates testing - database issues

Hi Juraj,
This error looks different than the files limit problem.  This actually looks 
to be an error in the python sqlalchemy call, complaining there isn't enough 
ram to spawn a session thread.  Is your box oom?

You can check the daily job's functest results.  I believe it deployed that 
scenario in the last iteration.  Otherwise ping me Monday with the setup and 
I'll try to debug.



Sent via the Samsung Galaxy S®6 active, an AT 4G LTE smartphone

 Original message 
From: "Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco)" 
>
Date: 8/4/17 8:34 AM (GMT-05:00)
To: 
opnfv-tech-discuss@lists.opnfv.org
Cc: fds-...@lists.opnfv.org
Subject: [Fds-dev] [APEX] [Euphrates] Euphrates testing - database issues

Hi Apex team,

I tried an os-odl-fdio-ha euphrates baremetal deployment and I ran into mariadb 
issues when I ran functest: 
https://paste.fedoraproject.org/paste/R4tBkzeub0N2ksYVMsabNg/raw

I've seen this issue before when the number of open files was too low in 
mariadb, but I seems to be fine:
MariaDB [(none)]> show variables like 'open_files_limit';
+--+---+
| Variable_name| Value |
+--+---+
| open_files_limit | 20485 |
+--+---+

Has anyone seen this with any other scenario?

Juraj
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[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 Fuel@OPNFV was relying on the jump server's "pxebr" bridge
> interface, which is supposed to reach all baremetal nodes, for PXE-booting
> purposes.
> If we want to reuse this interface as-is, we need to make sure "pxebr"
> will also have internet access, one way or another, on all PODs supporting
> Fuel@OPNFV deploys.
>
Julien: no directly internet access is required for "pxebr", but the node
which Fuel master deployed should have internet access.
  During the deployment, Fuel master will the check the internet
accessible through ping during configure stage and fetch packages during
the deployment.
  Usually the deploy the Fuel master as VM and all the response in
the following based on this assumption.

>
> Afaik, each POD is configured differently, the customizations ranging from
> different IP/subnets to totally different layouts.
> E.g. Armband used to have 2 network attached to its old Fuel Master node:
> - 1 x PXE/admin - no external configuration, TFTP/DNS/DHCP was provided by
> Fuel Master node - hooked up to a port in our dumb version of "pxebr";
> - 1 x public - external gateway, no external DHCP - hooked up to jump
> server's "public" bridge;
> However, x86 PODs running Fuel were configured to use only:
> - 1 x PXE/admin interface, hooked to "pxebr", which also had external
> internet access (NAT-ed?), but no external DHCP/DNS in order not to
> conflict with the ones provided by Fuel Master;
>
> Going forward, I would like to align the new network requirements between
> our PODs and the rest of the OPNFV pool, so here are some questions:
> - is PXE/admin interface (connected to "pxebr") supposed to always have
> internet access? If so, how? NAT on the jump server? Or external gateway?
> Can we assume this is going to happen for all PODs, or should we support
> different configurations as well?
>
Julien: Use static route is OK and SNAT should be used for Fuel master.
please also check whether the firewall in the jumpser blocks the packages.

> - is LOM (the network used to access baremetal nodes IPMI interfaces)
> routed to PXE/admin or public, or is it a separate, independent network?
> This seems to vary from POD to POD.
>
Julien: I would prefer a separate network. You can refer the configuration
in securedlab repo.

> - is LOM expected to have external DNS/DHCP, or is this up to the team
> responsible for POD config?
>
Julien: Usually we configure the LOM address statically or we can not keep
consistent relationship with hardware and management IP address.

>
> Thanks,
> Alex
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[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:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="HU, BIN":MAILTO:bh5...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=opnfv-tech
 -disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:https://global.gotomeeting.com/join/819733085\n+
 1 (312) 757-3126 / Access Code: 819-733-085\n\nHello community:\n\nThis is
  our 97th weekly technical discussion at 6am PDT / 9am EDT Thursday August
  10th\, 2017\, which is 13:00 UTC.\n\nWe will discuss a new project propos
 al stor4nfv by Howard Huang.
 \n\nYou can find your local time here http://www.timeanddate.com/worldcloc
 k/fixedtime.html?msg=OPNFV-Technical-Discussion=20170810T13=1.\n\nP
 lease refer to https://wiki.opnfv.org/display/PROJ/Weekly+Technical+Discus
 sion for details of dialing logistics and tentative agenda.\n\nPlease let 
 me know if you want to add anything to agenda for discussion in the commun
 ity.\n\nFor your convenience:\n-   GoTo Meeting: https://global.gotome
 eting.com/join/819733085\n-   You can also dial in using your phone:\n
 o   United States (Long distance): +1 (312) 757-3126 / Access Code: 81
 9-733-085\no   More phone numbers: https://global.gotomeeting.com/8197
 33085/numbersdisplay.html\n\nThanks\nBin\n\n\n
SUMMARY;LANGUAGE=en-US:Weekly Technical Discussion #97
DTSTART;TZID=Pacific Standard Time:20170810T06
DTEND;TZID=Pacific Standard Time:20170810T07
UID:04008200E00074C5B7101A82E00800FCAD1E1610D301000
 010007BEE4C5A22471C438FB14D92CDC2550F
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20170808T141531Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US: +1 (312) 757-3126 / Access Code: 819-733-085
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-OWNERAPPTID:-1234663455
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:0
X-MICROSOFT-DISALLOW-COUNTER:FALSE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [barometer] Update

[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 August 25

  * We are very much in the middle of Apex integration. 2 scenarios are 
created:  os-nosdn-bar-ha and os-nosdn-bar-noha @ 
https://build.opnfv.org/ci/view/apex/job/apex-daily-master/
  * Apex integration for MS5:


Plugin


integration with Apex for OPNFV E


Documentation Review


Comments


Dpdkstats





To be done


No DPDK specific scenario


Dpdkevents





To be done


No DPDK specific scenario


Hugepages


X


To be done





Intel RDT


Requires an RPM fix


To be done





IPMI





To be done


NOT MERGED TO MASTER YET will not make E


Mcelog (memory RAS)


X


To be done


Needs to be updated when pull request gets merged


OvS stats


X


To be done


No multi instance


OvS events


X


To be done





SNMP-Agent


Requires an RPM fix


To be done





Virt


X


To be done





PMU stats


Will see if we can get this in


To be done


MERGED TO MASTER


OvS DPDK PMD





To be done


No DPDK specific scenario


Gnocchi


X


To be done





Aodh


X


To be done





Ceilometer plugin








Deprecated for E - based on Gnocchi availability


PCIe Errors











RAS Other













Please let me know if you have any questions or comments.

BR
Maryam
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[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
TZOFFSETFROM:+
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Tahhan, Maryam":MAILTO:maryam.tah...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Power, Da
 mien":MAILTO:damien.po...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Mcmahon, 
 Tony B":MAILTO:tony.b.mcma...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Campbell,
  Wesley":MAILTO:wesley.campb...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Ray, Bj":M
 AILTO:bj@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Duignan, 
 Andrew":MAILTO:andrew.duig...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Parker, D
 aniel":MAILTO:daniel.par...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Foley, Em
 ma L":MAILTO:emma.l.fo...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Mario To
 rrecillas Rodriguez':MAILTO:mario.rodrig...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Chornyi, 
 TarasX":MAILTO:tarasx.chor...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'GUPTA, A
 LOK'":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'MORTON, 
 ALFRED C (AL)'":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Lawrence
  Lamers':MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Shobhan 
 AyyadevaraSesha (sayyadev)':MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Seiler, G
 lenn (Wind River)":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Scott Ma
 nsfield':MAILTO:scott.mansfi...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Bernier,
  Daniel (520165)'":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Canio Ci
 llis':MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Tomasini
 , Lorenzo'":MAILTO:lorenzo.tomas...@fokus.fraunhofer.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Srinivas
 a Chaganti':MAILTO:schaga...@versa-networks.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Laporte,
  Laurent [CTO]'":MAILTO:laurent.lapo...@sprint.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Ola Lilj
 edahl':MAILTO:ola.liljed...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Jaggi, M
 anish'":MAILTO:manish.ja...@cavium.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Gabor Ha
 lász':MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='杨艳':
 MAILTO:yangya...@chinamobile.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'SULLIVAN
 , BRYAN L'":MAILTO:bs3...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Andrew V
 eitch':MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'DRUTA, D
 AN'":MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Javier A
 rauz':MAILTO:j.javier.ar...@gmail.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Sen, Pro
 dip'":MAILTO:prodip@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Alan McN
 amee':MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Kedalagud
 de, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Gherghe, 
 Calin":MAILTO:calin.gher...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Murthy, K
 rishna J":MAILTO:krishna.j.mur...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Pierre L
 ynch':MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Sun, Ning"
 :MAILTO:ning@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='rgrigar@
 linuxfoundation.org':MAILTO:rgri...@linuxfoundation.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Marco Va
 

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

[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 by default before the possible harmonization.
I would have thought it was an upper decision as for OpenStack.

Cédric

De : Frank Brockners (fbrockne) [mailto:fbroc...@cisco.com]
Envoyé : mardi 8 août 2017 10:10
À : RICHOMME Morgan IMT/OLN; Tim Rozet; narinder.gu...@canonical.com; 'Michal 
Skalski'; Chigang (Justin); hu.zhiji...@zte.com.cn; David McBride; Georg Kunz; 
Tim Irnich; Manuel Buil; Michael Polenchuk; HE Ruan IMT/OLS; Juraj Linkes -X 
(jlinkes - PANTHEON TECHNOLOGIES at Cisco); Feng Pan; Michal Cmarada -X 
(mcmarada - PANTHEON TECHNOLOGIES at Cisco)
Cc : OLLIVIER Cédric IMT/OLN; wangwulin; opnfv-tech-discuss@lists.opnfv.org
Objet : RE: [OPNFV] ODL target Release for Euphrates

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 hand – which drive another version 
dependency.
For FDS, we plan for an effort similar to what we’ve done for Danube: Once 
we’re getting closer to the E-release, we’ll try to harmonize on a single 
version of ODL, i.e. we’ll try to harmonize on a pre-release version of 
Nitrogen – but for the time being, you’ll find different scenarios using 
different versions of ODL (sometimes even dedicated builds, e.g. as used for 
the GBP-Netvirt PoC or for the fdio-dvr scenario), also due to the fact that 
Karaf-4 migration isn’t yet done for all the components.

Regards, Frank

From: morgan.richo...@orange.com 
[mailto:morgan.richo...@orange.com]
Sent: Dienstag, 8. August 2017 09:18
To: Tim Rozet >; 
narinder.gu...@canonical.com; 'Michal 
Skalski' >; Chigang 
(Justin) >; 
hu.zhiji...@zte.com.cn; David McBride 
>; Georg Kunz 
>; Frank Brockners 
(fbrockne) >; Tim Irnich 
>; Manuel Buil 
>; Michael Polenchuk 
>; HE Ruan IMT/OLPS 
>; Frank Brockners (fbrockne) 
>
Cc: OLLIVIER Cédric IMT/OLN 
>; wangwulin 
>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: [OPNFV] ODL target Release for Euphrates

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.
Cedric consolidated Functest in order to manage properly the upstream 
dependencies (including clients/tooling/lib needed for testing relatively to 
upstream components) and introduced a clean packetization, which is key for an 
integration project.

At the moment, the only ODL version reference we found was beryllium-sr4, which 
is pretty old.

According to https://wiki.opnfv.org/display/SWREL/Euphrates+Scenario+Status
scenario owners dealing with ODL are:
- Frank (Apex ∩ Fdio)
- Tim Inrich (Apex ∩ bgpvpn)
- Brady (not sure the page is up to date) / Manuel (Apex ∩ Sfc)
- Georg (not sure it is up to date) Apex ∩ gluon
- Tim Rozet (Other Apex scenarios)
- Ruan He (Compass ∩ moon)
- Justin (Other Compass scenarios)
- Zhiang (Daisy ∩ moon)
- Michael (Fuel/MCP)

could you confirm the target version for ODL?


/Morgan

note: no scenario ODL with joid referenced in the page.

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This 

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

[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 updated 
but I fully agree with Morgan to set a default release.
It will complete all the work we have done on python requirements (OpenStack 
clients, libraries…).

The second question is to switch (or not) to the Netvirt test suite by default 
which seems much relevant (the basic suites seem obsolete and hardcoded for 
Keystone v2).
But it induces to know the set of features considered as default to create 
filters in our testcase config file if needed (e.g. GBP).

I think we could set the current release: Carbon in our containers.

Cédric


De : Manuel Buil [mailto:mb...@suse.com]
Envoyé : mardi 8 août 2017 10:00
À : jason; RICHOMME Morgan IMT/OLN
Cc : OLLIVIER Cédric IMT/OLN; narinder.gu...@canonical.com; opnfv-tech-discuss
Objet : Re: [opnfv-tech-discuss] [OPNFV] ODL target Release for Euphrates

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 OPNFV tests to help them 
find bugs.

Regards,
Manuel

On Tue, 2017-08-08 at 15:29 +0800, jason wrote:
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 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.
Cedric consolidated Functest in order to manage properly the upstream 
dependencies (including clients/tooling/lib needed for testing relatively to 
upstream components) and introduced a clean packetization, which is key for an 
integration project.

At the moment, the only ODL version reference we found was beryllium-sr4, which 
is pretty old.

According to https://wiki.opnfv.org/display/SWREL/Euphrates+Scenario+Status
scenario owners dealing with ODL are:
- Frank (Apex ∩ Fdio)
- Tim Inrich (Apex ∩ bgpvpn)
- Brady (not sure the page is up to date) / Manuel (Apex ∩ Sfc)
- Georg (not sure it is up to date) Apex ∩ gluon
- Tim Rozet (Other Apex scenarios)
- Ruan He (Compass ∩ moon)
- Justin (Other Compass scenarios)
- Zhiang (Daisy ∩ moon)
- Michael (Fuel/MCP)

could you confirm the target version for ODL?


/Morgan

note: no scenario ODL with joid referenced in the page.


_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

___

opnfv-tech-discuss mailing list

opnfv-tech-discuss@lists.opnfv.org

https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information 

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

[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 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of 
morgan.richo...@orange.com
Sent: Tuesday, August 08, 2017 3:18 PM
To: Tim Rozet; narinder.gu...@canonical.com; 'Michal Skalski'; Chigang 
(Justin); hu.zhiji...@zte.com.cn; David McBride; Georg Kunz; Frank Brockners; 
Tim Irnich; Manuel Buil; Michael Polenchuk; HE Ruan IMT/OLPS; Frank Brockners
Cc: OLLIVIER Cédric IMT/OLN; opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [OPNFV] ODL target Release for Euphrates

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.
Cedric consolidated Functest in order to manage properly the upstream 
dependencies (including clients/tooling/lib needed for testing relatively to 
upstream components) and introduced a clean packetization, which is key for an 
integration project.

At the moment, the only ODL version reference we found was beryllium-sr4, which 
is pretty old.

According to https://wiki.opnfv.org/display/SWREL/Euphrates+Scenario+Status
scenario owners dealing with ODL are:
- Frank (Apex ∩ Fdio)
- Tim Inrich (Apex ∩ bgpvpn)
- Brady (not sure the page is up to date) / Manuel (Apex ∩ Sfc)
- Georg (not sure it is up to date) Apex ∩ gluon
- Tim Rozet (Other Apex scenarios)
- Ruan He (Compass ∩ moon)
- Justin (Other Compass scenarios)
- Zhiang (Daisy ∩ moon)
- Michael (Fuel/MCP)

could you confirm the target version for ODL?


/Morgan

note: no scenario ODL with joid referenced in the page.


_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[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
TZOFFSETFROM:+
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Tahhan, Maryam":MAILTO:maryam.tah...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Power, Da
 mien":MAILTO:damien.po...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Mcmahon, 
 Tony B":MAILTO:tony.b.mcma...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Campbell,
  Wesley":MAILTO:wesley.campb...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Ray, Bj":M
 AILTO:bj@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Duignan, 
 Andrew":MAILTO:andrew.duig...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Parker, D
 aniel":MAILTO:daniel.par...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Foley, Em
 ma L":MAILTO:emma.l.fo...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Mario To
 rrecillas Rodriguez':MAILTO:mario.rodrig...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Chornyi, 
 TarasX":MAILTO:tarasx.chor...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'GUPTA, A
 LOK'":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'MORTON, 
 ALFRED C (AL)'":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Lawrence
  Lamers':MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Shobhan 
 AyyadevaraSesha (sayyadev)':MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Seiler, G
 lenn (Wind River)":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Scott Ma
 nsfield':MAILTO:scott.mansfi...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Bernier,
  Daniel (520165)'":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Canio Ci
 llis':MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Tomasini
 , Lorenzo'":MAILTO:lorenzo.tomas...@fokus.fraunhofer.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Srinivas
 a Chaganti':MAILTO:schaga...@versa-networks.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Laporte,
  Laurent [CTO]'":MAILTO:laurent.lapo...@sprint.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Ola Lilj
 edahl':MAILTO:ola.liljed...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Jaggi, M
 anish'":MAILTO:manish.ja...@cavium.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Gabor Ha
 lász':MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='杨艳':
 MAILTO:yangya...@chinamobile.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'SULLIVAN
 , BRYAN L'":MAILTO:bs3...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Andrew V
 eitch':MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'DRUTA, D
 AN'":MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Javier A
 rauz':MAILTO:j.javier.ar...@gmail.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Sen, Pro
 dip'":MAILTO:prodip@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Alan McN
 amee':MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Kedalagud
 de, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Gherghe, 
 Calin":MAILTO:calin.gher...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Murthy, K
 rishna J":MAILTO:krishna.j.mur...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Pierre L
 ynch':MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Sun, Ning"
 :MAILTO:ning@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='rgrigar@
 linuxfoundation.org':MAILTO:rgri...@linuxfoundation.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Marco Va
 

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

[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
TZOFFSETFROM:+
TZOFFSETTO:+0100
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="Tahhan, Maryam":MAILTO:maryam.tah...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-disc...@lists.opnfv.org:MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Power, Da
 mien":MAILTO:damien.po...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Mcmahon, 
 Tony B":MAILTO:tony.b.mcma...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Campbell,
  Wesley":MAILTO:wesley.campb...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Ray, Bj":M
 AILTO:bj@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Duignan, 
 Andrew":MAILTO:andrew.duig...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Parker, D
 aniel":MAILTO:daniel.par...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Foley, Em
 ma L":MAILTO:emma.l.fo...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Mario To
 rrecillas Rodriguez':MAILTO:mario.rodrig...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Chornyi, 
 TarasX":MAILTO:tarasx.chor...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'GUPTA, A
 LOK'":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'MORTON, 
 ALFRED C (AL)'":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Lawrence
  Lamers':MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Shobhan 
 AyyadevaraSesha (sayyadev)':MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Seiler, G
 lenn (Wind River)":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Scott Ma
 nsfield':MAILTO:scott.mansfi...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Bernier,
  Daniel (520165)'":MAILTO:daniel.bern...@bell.ca
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Canio Ci
 llis':MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Tomasini
 , Lorenzo'":MAILTO:lorenzo.tomas...@fokus.fraunhofer.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Srinivas
 a Chaganti':MAILTO:schaga...@versa-networks.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Laporte,
  Laurent [CTO]'":MAILTO:laurent.lapo...@sprint.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Ola Lilj
 edahl':MAILTO:ola.liljed...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Jaggi, M
 anish'":MAILTO:manish.ja...@cavium.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Gabor Ha
 lász':MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='杨艳':
 MAILTO:yangya...@chinamobile.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'SULLIVAN
 , BRYAN L'":MAILTO:bs3...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Andrew V
 eitch':MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'DRUTA, D
 AN'":MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Javier A
 rauz':MAILTO:j.javier.ar...@gmail.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'Sen, Pro
 dip'":MAILTO:prodip@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Alan McN
 amee':MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Kedalagud
 de, Meghashree Dattatri":MAILTO:meghashree.dattatri.kedalagu...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Gherghe, 
 Calin":MAILTO:calin.gher...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Murthy, K
 rishna J":MAILTO:krishna.j.mur...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Pierre L
 ynch':MAILTO:ply...@ixiacom.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="Sun, Ning"
 :MAILTO:ning@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='rgrigar@
 linuxfoundation.org':MAILTO:rgri...@linuxfoundation.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='Marco Va
 

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

[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

From: cedric.olliv...@orange.com [mailto:cedric.olliv...@orange.com]
Sent: Dienstag, 8. August 2017 11:17
To: Frank Brockners (fbrockne) ; RICHOMME Morgan IMT/OLN 
; Tim Rozet ; 
narinder.gu...@canonical.com; 'Michal Skalski' ; Chigang 
(Justin) ; hu.zhiji...@zte.com.cn; David McBride 
; Georg Kunz ; Tim 
Irnich ; Manuel Buil ; 
Michael Polenchuk ; HE Ruan IMT/OLS 
; Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at 
Cisco) ; Feng Pan ; Michal Cmarada -X 
(mcmarada - PANTHEON TECHNOLOGIES at Cisco) 
Cc: wangwulin ; opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [OPNFV] ODL target Release for Euphrates

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 by default before the possible harmonization.
I would have thought it was an upper decision as for OpenStack.

Cédric

De : Frank Brockners (fbrockne) [mailto:fbroc...@cisco.com]
Envoyé : mardi 8 août 2017 10:10
À : RICHOMME Morgan IMT/OLN; Tim Rozet; 
narinder.gu...@canonical.com; 'Michal 
Skalski'; Chigang (Justin); 
hu.zhiji...@zte.com.cn; David McBride; Georg 
Kunz; Tim Irnich; Manuel Buil; Michael Polenchuk; HE Ruan IMT/OLS; Juraj Linkes 
-X (jlinkes - PANTHEON TECHNOLOGIES at Cisco); Feng Pan; Michal Cmarada -X 
(mcmarada - PANTHEON TECHNOLOGIES at Cisco)
Cc : OLLIVIER Cédric IMT/OLN; wangwulin; 
opnfv-tech-discuss@lists.opnfv.org
Objet : RE: [OPNFV] ODL target Release for Euphrates

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 hand – which drive another version 
dependency.
For FDS, we plan for an effort similar to what we’ve done for Danube: Once 
we’re getting closer to the E-release, we’ll try to harmonize on a single 
version of ODL, i.e. we’ll try to harmonize on a pre-release version of 
Nitrogen – but for the time being, you’ll find different scenarios using 
different versions of ODL (sometimes even dedicated builds, e.g. as used for 
the GBP-Netvirt PoC or for the fdio-dvr scenario), also due to the fact that 
Karaf-4 migration isn’t yet done for all the components.

Regards, Frank

From: morgan.richo...@orange.com 
[mailto:morgan.richo...@orange.com]
Sent: Dienstag, 8. August 2017 09:18
To: Tim Rozet >; 
narinder.gu...@canonical.com; 'Michal 
Skalski' >; Chigang 
(Justin) >; 
hu.zhiji...@zte.com.cn; David McBride 
>; Georg Kunz 
>; Frank Brockners 
(fbrockne) >; Tim Irnich 
>; Manuel Buil 
>; Michael Polenchuk 
>; HE Ruan IMT/OLPS 
>; Frank Brockners (fbrockne) 
>
Cc: OLLIVIER Cédric IMT/OLN 
>; wangwulin 
>; 
opnfv-tech-discuss@lists.opnfv.org
Subject: [OPNFV] ODL target Release for Euphrates

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.
Cedric consolidated Functest in order to manage properly the upstream 
dependencies (including clients/tooling/lib needed for 

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

[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 hand – which drive another version 
dependency.
For FDS, we plan for an effort similar to what we’ve done for Danube: Once 
we’re getting closer to the E-release, we’ll try to harmonize on a single 
version of ODL, i.e. we’ll try to harmonize on a pre-release version of 
Nitrogen – but for the time being, you’ll find different scenarios using 
different versions of ODL (sometimes even dedicated builds, e.g. as used for 
the GBP-Netvirt PoC or for the fdio-dvr scenario), also due to the fact that 
Karaf-4 migration isn’t yet done for all the components.

Regards, Frank

From: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com]
Sent: Dienstag, 8. August 2017 09:18
To: Tim Rozet ; narinder.gu...@canonical.com; 'Michal 
Skalski' ; Chigang (Justin) ; 
hu.zhiji...@zte.com.cn; David McBride ; Georg 
Kunz ; Frank Brockners (fbrockne) 
; Tim Irnich ; Manuel Buil 
; Michael Polenchuk ; HE 
Ruan IMT/OLPS ; Frank Brockners (fbrockne) 

Cc: OLLIVIER Cédric IMT/OLN ; wangwulin 
; opnfv-tech-discuss@lists.opnfv.org
Subject: [OPNFV] ODL target Release for Euphrates

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.
Cedric consolidated Functest in order to manage properly the upstream 
dependencies (including clients/tooling/lib needed for testing relatively to 
upstream components) and introduced a clean packetization, which is key for an 
integration project.

At the moment, the only ODL version reference we found was beryllium-sr4, which 
is pretty old.

According to https://wiki.opnfv.org/display/SWREL/Euphrates+Scenario+Status
scenario owners dealing with ODL are:
- Frank (Apex ∩ Fdio)
- Tim Inrich (Apex ∩ bgpvpn)
- Brady (not sure the page is up to date) / Manuel (Apex ∩ Sfc)
- Georg (not sure it is up to date) Apex ∩ gluon
- Tim Rozet (Other Apex scenarios)
- Ruan He (Compass ∩ moon)
- Justin (Other Compass scenarios)
- Zhiang (Daisy ∩ moon)
- Michael (Fuel/MCP)

could you confirm the target version for ODL?


/Morgan

note: no scenario ODL with joid referenced in the page.


_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.



This message and its attachments may contain confidential or privileged 
information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete 
this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.

Thank you.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[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 OPNFV
tests to help them find bugs.

Regards,
Manuel

On Tue, 2017-08-08 at 15:29 +0800, jason wrote:
> > 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 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. 
> > 
> > Cedric consolidated Functest in order to manage properly the
> > upstream dependencies (including clients/tooling/lib needed for
> > > > testing relatively to upstream components) and introduced a
clean
> > packetization, which is key for an integration project.
> > 
> > 
> > 
> > At the moment, the only ODL version reference we found was
> > beryllium-sr4, which is pretty old.
> > 
> > 
> > 
> > According to
> > https://wiki.opnfv.org/display/SWREL/Euphrates+Scenario+Status
> > 
> > scenario owners dealing with ODL are:
> > 
> > - Frank (Apex ∩ Fdio)
> > 
> > - Tim Inrich (Apex ∩ bgpvpn)
> > 
> > > > - Brady (not sure the page is up to date) / Manuel (Apex ∩
Sfc)
> > 
> > - Georg (not sure it is up to date) Apex ∩ gluon
> > 
> > - Tim Rozet (Other Apex scenarios)
> > 
> > - Ruan He (Compass ∩ moon)
> > 
> > - Justin (Other Compass scenarios)
> > 
> > - Zhiang (Daisy ∩ moon)
> > 
> > - Michael (Fuel/MCP)
> > 
> > 
> > 
> > could you confirm the target version for ODL?
> > 
> > 
> > 
> > 
> > 
> >   /Morgan
> > 
> > 
> > 
> > note: no scenario ODL with joid
> > referenced in the page.
> > 
> >   
> > 
> > 
> > 
> > > > > >  
___
__
> > 
> > > > Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
> > > > pas etre diffuses, exploites ou copies sans autorisation. Si vous
avez recu ce message par erreur, veuillez le signaler
> > > > a l'expediteur et le detruire ainsi que les pieces jointes. Les
messages electroniques etant susceptibles d'alteration,
> > > > Orange decline toute responsabilite si ce message a ete altere,
deforme ou falsifie. Merci.
> > 
> > > > This message and its attachments may contain confidential or
privileged information that may be protected by law;
> > > > they should not be distributed, used or copied without
authorisation.
> > > > If you have received this email in error, please notify the sender
and delete this message and its attachments.
> > > > As emails may be altered, Orange is not liable for messages that
have been modified, changed or falsified.
> > Thank you.
> > 
> > 
> > 
> > 
> > ___
> > 
> > opnfv-tech-discuss mailing list
> > 
> > opnfv-tech-discuss@lists.opnfv.org
> > 
> > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
> > 
> > 
> 
> 
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[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 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.
> Cedric consolidated Functest in order to manage properly the upstream
> dependencies (including clients/tooling/lib needed for testing relatively
> to upstream components) and introduced a clean packetization, which is key
> for an integration project.
>
> At the moment, the only ODL version reference we found was beryllium-sr4,
> which is pretty old.
>
> According to https://wiki.opnfv.org/display/SWREL/Euphrates+
> Scenario+Status
> scenario owners dealing with ODL are:
> - Frank (Apex ∩ Fdio)
> - Tim Inrich (Apex ∩ bgpvpn)
> - Brady (not sure the page is up to date) / Manuel (Apex ∩ Sfc)
> - Georg (not sure it is up to date) Apex ∩ gluon
> - Tim Rozet (Other Apex scenarios)
> - Ruan He (Compass ∩ moon)
> - Justin (Other Compass scenarios)
> - Zhiang (Daisy ∩ moon)
> - Michael (Fuel/MCP)
>
> could you confirm the target version for ODL?
>
>
> /Morgan
>
> note: no scenario ODL with joid referenced in the page.
>
>
> _
>
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu 
> ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
> electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou 
> falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged 
> information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete 
> this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been 
> modified, changed or falsified.
> Thank you.
>
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[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.
Cedric consolidated Functest in order to manage properly the upstream 
dependencies (including clients/tooling/lib needed for testing 
relatively to upstream components) and introduced a clean packetization, 
which is key for an integration project.


At the moment, the only ODL version reference we found was 
beryllium-sr4, which is pretty old.


According to https://wiki.opnfv.org/display/SWREL/Euphrates+Scenario+Status
scenario owners dealing with ODL are:
- Frank (Apex ∩ Fdio)
- Tim Inrich (Apex ∩ bgpvpn)
- Brady (not sure the page is up to date) / Manuel (Apex ∩ Sfc)
- Georg (not sure it is up to date) Apex ∩ gluon
- Tim Rozet (Other Apex scenarios)
- Ruan He (Compass ∩ moon)
- Justin (Other Compass scenarios)
- Zhiang (Daisy ∩ moon)
- Michael (Fuel/MCP)

could you confirm the target version for ODL?


/Morgan

note: no scenario ODL with joid referenced in the page.



_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss