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.

Yifei Xue

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of 
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


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?


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

Reply via email to