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:[email protected]] Envoyé : mardi 8 août 2017 10:00 À : jason; RICHOMME Morgan IMT/OLN Cc : OLLIVIER Cédric IMT/OLN; [email protected]; 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, <[email protected]<mailto:[email protected]>> 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 [email protected]<mailto:[email protected]> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss _______________________________________________ opnfv-tech-discuss mailing list [email protected]<mailto:[email protected]> 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 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 [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
