Re: [opnfv-tech-discuss] [OPNFV] ODL target Release for Euphrates
Hello Franck, The basic test suite is hardcoded for keystone v2 (and other limitations) what becomes an issue. We must sync with ODL test community regarding that point if it makes sense to continue on updating this suite. Yes our config file already allows defining multiple ODL testcases according to installers or scenarii (see dependencies). For the latest release, we implemented 3 cases testing ODL (odl, odl_netvirt and fds). Only the robot suites specified as args differ in the config. Cédric De : Frank Brockners (fbrockne) [mailto:fbroc...@cisco.com] Envoyé : mardi 8 août 2017 11:34 À : OLLIVIER Cédric IMT/OLN; 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 Objet : RE: [OPNFV] ODL target Release for Euphrates 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> [mailto:cedric.olliv...@orange.com] Sent: Dienstag, 8. August 2017 11:17 To: Frank Brockners (fbrockne) <fbroc...@cisco.com<mailto:fbroc...@cisco.com>>; RICHOMME Morgan IMT/OLN <morgan.richo...@orange.com<mailto:morgan.richo...@orange.com>>; Tim Rozet <tro...@redhat.com<mailto:tro...@redhat.com>>; narinder.gu...@canonical.com<mailto:narinder.gu...@canonical.com>; 'Michal Skalski' <mskal...@mirantis.com<mailto:mskal...@mirantis.com>>; Chigang (Justin) <chig...@huawei.com<mailto:chig...@huawei.com>>; hu.zhiji...@zte.com.cn<mailto:hu.zhiji...@zte.com.cn>; David McBride <dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>>; Georg Kunz <georg.k...@ericsson.com<mailto:georg.k...@ericsson.com>>; Tim Irnich <tim.irn...@ericsson.com<mailto:tim.irn...@ericsson.com>>; Manuel Buil <manuel.b...@ericsson.com<mailto:manuel.b...@ericsson.com>>; Michael Polenchuk <mpolenc...@mirantis.com<mailto:mpolenc...@mirantis.com>>; HE Ruan IMT/OLS <ruan...@orange.com<mailto:ruan...@orange.com>>; Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco) <jlin...@cisco.com<mailto:jlin...@cisco.com>>; Feng Pan <f...@redhat.com<mailto:f...@redhat.com>>; Michal Cmarada -X (mcmarada - PANTHEON TECHNOLOGIES at Cisco) <mcmar...@cisco.com<mailto:mcmar...@cisco.com>> Cc: wangwulin <wangwu...@huawei.com<mailto:wangwu...@huawei.com>>; opnfv-tech-discuss@lists.opnfv.org<mailto: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<mailto:narinder.gu...@canonical.com>; 'Michal Skalski'; Chigang (Justin); hu.zhiji...@zte.com.cn<mailto: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<mailto: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 f
Re: [opnfv-tech-discuss] [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> [mailto:morgan.richo...@orange.com] Sent: Dienstag, 8. August 2017 09:18 To: Tim Rozet <tro...@redhat.com<mailto:tro...@redhat.com>>; narinder.gu...@canonical.com<mailto:narinder.gu...@canonical.com>; 'Michal Skalski' <mskal...@mirantis.com<mailto:mskal...@mirantis.com>>; Chigang (Justin) <chig...@huawei.com<mailto:chig...@huawei.com>>; hu.zhiji...@zte.com.cn<mailto:hu.zhiji...@zte.com.cn>; David McBride <dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>>; Georg Kunz <georg.k...@ericsson.com<mailto:georg.k...@ericsson.com>>; Frank Brockners (fbrockne) <fbroc...@cisco.com<mailto:fbroc...@cisco.com>>; Tim Irnich <tim.irn...@ericsson.com<mailto:tim.irn...@ericsson.com>>; Manuel Buil <manuel.b...@ericsson.com<mailto:manuel.b...@ericsson.com>>; Michael Polenchuk <mpolenc...@mirantis.com<mailto:mpolenc...@mirantis.com>>; HE Ruan IMT/OLPS <ruan...@orange.com<mailto:ruan...@orange.com>>; Frank Brockners (fbrockne) <fbroc...@cisco.com<mailto:fbroc...@cisco.com>> Cc: OLLIVIER Cédric IMT/OLN <cedric.olliv...@orange.com<mailto:cedric.olliv...@orange.com>>; wangwulin <wangwu...@huawei.com<mailto:wangwu...@huawei.com>>; opnfv-tech-discuss@lists.opnfv.org<mailto: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 ain
Re: [opnfv-tech-discuss] [OPNFV] ODL target Release for Euphrates
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, <morgan.richo...@orange.com<mailto:morgan.richo...@orange.com>> 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<mailto: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<mailto: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
Re: [opnfv-tech-discuss] [OPNFV] ODL target Release for Euphrates
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
Re: [opnfv-tech-discuss] [OPNFV] ODL target Release for Euphrates
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) <fbroc...@cisco.com>; RICHOMME Morgan IMT/OLN <morgan.richo...@orange.com>; Tim Rozet <tro...@redhat.com>; narinder.gu...@canonical.com; 'Michal Skalski' <mskal...@mirantis.com>; Chigang (Justin) <chig...@huawei.com>; hu.zhiji...@zte.com.cn; David McBride <dmcbr...@linuxfoundation.org>; Georg Kunz <georg.k...@ericsson.com>; Tim Irnich <tim.irn...@ericsson.com>; Manuel Buil <manuel.b...@ericsson.com>; Michael Polenchuk <mpolenc...@mirantis.com>; HE Ruan IMT/OLS <ruan...@orange.com>; Juraj Linkes -X (jlinkes - PANTHEON TECHNOLOGIES at Cisco) <jlin...@cisco.com>; Feng Pan <f...@redhat.com>; Michal Cmarada -X (mcmarada - PANTHEON TECHNOLOGIES at Cisco) <mcmar...@cisco.com> Cc: wangwulin <wangwu...@huawei.com>; 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<mailto:narinder.gu...@canonical.com>; 'Michal Skalski'; Chigang (Justin); hu.zhiji...@zte.com.cn<mailto: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<mailto: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> [mailto:morgan.richo...@orange.com] Sent: Dienstag, 8. August 2017 09:18 To: Tim Rozet <tro...@redhat.com<mailto:tro...@redhat.com>>; narinder.gu...@canonical.com<mailto:narinder.gu...@canonical.com>; 'Michal Skalski' <mskal...@mirantis.com<mailto:mskal...@mirantis.com>>; Chigang (Justin) <chig...@huawei.com<mailto:chig...@huawei.com>>; hu.zhiji...@zte.com.cn<mailto:hu.zhiji...@zte.com.cn>; David McBride <dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>>; Georg Kunz <georg.k...@ericsson.com<mailto:georg.k...@ericsson.com>>; Frank Brockners (fbrockne) <fbroc...@cisco.com<mailto:fbroc...@cisco.com>>; Tim Irnich <tim.irn...@ericsson.com<mailto:tim.irn...@ericsson.com>>; Manuel Buil <manuel.b...@ericsson.com<mailto:manuel.b...@ericsson.com>>; Michael Polenchuk <mpolenc...@mirantis.com<mailto:mpolenc...@mirantis.com>>; HE Ruan IMT/OLPS <ruan...@orange.com<mailto:ruan...@orange.com>>; Frank Brockners (fbrockne) <fbroc...@cisco.com<mailto:fbroc...@cisco.com>> Cc: OLLIVIER Cédric IMT/OLN <cedric.olliv...@orange.com<mailto:cedric.olliv...@orange.com>>; wangwulin <wangwu...@huawei.com<mailto:wangwu...@huawei.com>>; opnfv-tech-discuss@lists.opnfv.org<mailto: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 s
Re: [opnfv-tech-discuss] [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 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
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
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