|
Re: [E] Re: Next TSC meeting
Luis Gomez
Happy holidays everyone 🍾🥂🥳
toggle quoted messageShow quoted text
|
||||||||||||||
|
|
||||||||||||||
|
Re: [E] Re: Next TSC meeting
Sangwook Ha
Sorry, I missed the meeting - I didn't realize it's past 9am, and joined the meeting late but nobody was there. Merry Christmas and Happy New Year! See you next year 🙂 Thanks, Sangwook
On Thu, Dec 16, 2021 at 9:09 AM Casey Cain <ccain@...> wrote:
|
||||||||||||||
|
|
||||||||||||||
|
Re: Next TSC meeting
Casey Cain
Sorry we couldn't get a chance to talk before the end of the year.
Sorry we couldn't get a chance to talk before the end of the year. Merry Christmas and Happy New Year! I hope everyone stays safe and we see you in early '22! Best, Casey Cain Senior Technical Community Architect Linux Foundation _________________ WeChat: okaru6 WhatsApp: +1.503.779.4519
On Wed, Dec 15, 2021 at 1:11 PM Daniel de la Rosa <ddelarosa0707@...> wrote:
|
||||||||||||||
|
|
||||||||||||||
|
TSC Meeting for December 16, 2021 at 9 am Pacific
Guillaume Lambert
Hello OpenDaylight Community,
Next TSC meeting is December 16, 2021 at 9 am Pacific Time.
If you need to add anything, please let me know or add it there.The agenda proposal and the connection details for this meeting are available at the following URL: The meeting minutes will be at the same location after the meeting is over. Best Regards Guillaume _________________________________________________________________________________________________________________________ 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.
|
||||||||||||||
|
|
||||||||||||||
|
Re: Next TSC meeting
Luis and I won’t be able to make it either. Merry Christmas and Happy New Year to all of you
On Wed, Dec 15, 2021 at 8:40 AM Ghazisaidi, Navid <navid.ghazisaidi@...> wrote:
--
Daniel de la Rosa ODL Release Manager
|
||||||||||||||
|
|
||||||||||||||
|
Next TSC meeting
Ghazisaidi, Navid
Hi All, I won't be able to attend tomorrow's meeting. Sangwook will proxy me. Merry Christmas and Happy New Year everyone! Regards, Navid
|
||||||||||||||
|
|
||||||||||||||
|
Re: TSC Meeting for December 9, 2021 at 10 pm Pacific
Venkatrangan Govindarajan
Hi All, Sorry!! I have a conflict with another meeting today. I will miss today;'s meeting. Regards, Rangan வியா., 9 டிச., 2021, பிற்பகல் 5:54 அன்று, Guillaume Lambert via lists.opendaylight.org <guillaume.lambert=orange.com@...> எழுதியது:
--
Venkatrangan Govindarajan ( When there is no wind...Row )
|
||||||||||||||
|
|
||||||||||||||
|
TSC Meeting for December 9, 2021 at 10 pm Pacific
Guillaume Lambert
Hello OpenDaylight Community, Next TSC meeting is December 9 , 2021 at 10 pm Pacific Time. The agenda proposal and the connection details for this meeting are available at the following URL: If you need to add anything, please let me know or add it there. The meeting minutes will be at the same location after the meeting is over. Best Regards Guillaume _________________________________________________________________________________________________________________________ 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.
|
||||||||||||||
|
|
||||||||||||||
|
[OpenDaylight Infrastructure] Gerrit update at 4:00pm PST Monday Dec 6
Jessica Wagantall <jwagantall@...>
Dear ODL community, An update to IT-23302 will be performed today at 4:00pm PST No services would be paused but you might experience a small Gerrit glitch which will be under control. Thanks so much for your patience! Jess
|
||||||||||||||
|
|
||||||||||||||
|
Functest Xena is out!
#release
#announcement
Cedric Ollivier
Hi,
I eagerly announce the release of Functest Xena.
Here is the full verification job in success, running both the classical IaaS verification and Reference Conformance suite for OpenStack (RC1): https://build.opnfv.org/ci/view/functest/job/functest-xena-daily/23/
At the time of writing, all Functest CNTT-specific containers consider any new Feature brought by OpenStack Xena as skipped because Anuket RA1 only asks for Wallaby features. The test case descriptions would be updated according to any new mandatory feature in RA1 Chapter 5. But the less we can write is that RC1 is already in a good shape for N+1.
It’s worth mentioning that Functest continuously updates all libraries and all linters too. For instance, the code was hugely updated to match the latest Pylint rules (Functest asks for a perfect rating in gates).
Please note that all releases from Jerma are still very well maintained.
Cédric
_________________________________________________________________________________________________________________________ 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.
|
||||||||||||||
|
|
||||||||||||||
|
Re: FOSDEM 2022 Network Devroom CFP
Charles Eckel <eckelcu@...>
Great idea and please do. I help run the Network devroom. Proposals related to OpenDaylight would be most welcome.
toggle quoted messageShow quoted text
Cheers, Charles
On Dec 2, 2021, at 9:36 AM, Robert Varga <nite@...> wrote:
|
||||||||||||||
|
|
||||||||||||||
|
FOSDEM 2022 Network Devroom CFP
Robert Varga
Hey everyone,
I just got the attached invitation to present something at the upcoming FOSDEM. If we can come up with some tech-focused topics, I think this could improve our visibility and perhaps get a few causal hands-on contributors. The CFP deadline is December 12th, so we have just a hair over a week to throw some proposals together. Regards, Robert
|
||||||||||||||
|
|
||||||||||||||
|
Re: [integration-dev] [opendaylight-dev][release] OpenDaylight - Phosphorus SR1
Great, thanks! all we are missing is to update downloads page.. @LAMBERT Guillaume TGI/OLN can you help us with that? Thanks
On Wed, Dec 1, 2021 at 9:01 PM Luis Gomez <ecelgp@...> wrote:
--
Daniel de la Rosa ODL Release Manager
|
||||||||||||||
|
|
||||||||||||||
|
Re: [integration-dev] [opendaylight-dev][release] OpenDaylight - Phosphorus SR1
Luis Gomez
OK, I just released the distribution with the old job name, we can fix the name for the next release:
toggle quoted messageShow quoted text
BR/Luis
|
||||||||||||||
|
|
||||||||||||||
|
Re: [integration-dev] [opendaylight-dev][release] OpenDaylight - Phosphorus SR1
Luis Gomez
I have just realized there is a typo in the distribution stage job:
toggle quoted messageShow quoted text
If anyone can review & merge, I can release the distribution tomorrow morning. BR/Luis
|
||||||||||||||
|
|
||||||||||||||
|
Luis and Daniel will join tsc meeting on 12/2, 30 min later
Hello TSC and all We have a conflict and we will need to join 30 min late. Hope that's not a problem -- Thanks Daniel de la Rosa ODL Release Manager
|
||||||||||||||
|
|
||||||||||||||
|
proxy for next TSC meeting
Ghazisaidi, Navid
Hi All, I won't be able to attend tomorrow's meeting. Sangwook will proxy me. Thanks, Navid
|
||||||||||||||
|
|
||||||||||||||
|
Re: Openflowplugin PTL nomination - Sangwook Ha
d.arunprakash@...
Hi TSC Members, I will be officially stepping down as Openflowplugin PTL and Sangwook Ha will be taking over the PTL role of openflowplugin.
All the best Regards, Arun
From: D Arunprakash
Hi, Sangwook Ha has shown interest in taking over OpenflowPlugin PTL role and I would like to step down as I’m not active in the project currently. So, would like to nominate Sangwook as OpenflowPlugin PTL.
Regards, Arun
|
||||||||||||||
|
|
||||||||||||||
|
Re: TSC Meeting for December 2, 2021 at 9 am Pacific
Guillaume Lambert
Hello OpenDaylight Community,
https://wiki.opendaylight.org/x/qScEAQ
_________________________________________________________________________________________________________________________ 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.
|
||||||||||||||
|
|
||||||||||||||
|
Old RESTCONF northbound scheduled for removal
Robert Varga
Hello everyone,
as you might be aware, OpenDaylight ships two versions of RESTCONF northbound. The first is the all-familiar implementation of draft-bierman-netconf-restconf-02, available at localhost:8181/restconf. The second is the implementation of RFC8040, available at localhost:8181/rests. TL;DR of this email is that we plan to completely remove the first implementation in our 2022.09 Chlorine release. If it is a problem for you, please speak out now. There are multiple reasons driving this decision: 1. The old interface does not (and cannot) support YANG 1.1 action statements, i.e. there is no way to invoke them. 2. RFC8040 implementation is considered now considered a fully-maintained and production-ready equivalent. 3. The implementation is effectively frozen, receiving only minimal updates required for it to remain working in face of upstream API changes. 4. Bringing the implementation into a shape which is maintainable in the long term requires a large-scale refactor with the associated risk of introducing regressions. 5. The implementation is the only user of a number of pieces of upstream code, preventing that code from being removed. The tracker issue for the removal is https://jira.opendaylight.org/browse/NETCONF-837 and the plan of action is as follows: 1. Phosphorus SR2, due out 2022-01-27, will issue a single (mild) warning on startup. We will continue to install the implementation as part of the 'odl-restconf' feature. 2. 2022.03 Sulfur, due out 2022-03-17, will not install the old implementation by default. Users will be required to explicitly install the 'odl-restconf-nb-bierman02' feature. The warning introduced in step 1. will be updated to warn about the fact the feature is no longer supported and scheduled for removal in the next major release. 3. Old implementation will be removed from the netconf git repository's master branch as soon as the 3.0.x stability branch for Sulfur is created -- i.e. March/April 2022. 4. 2022.09 Chlorine, due out in September 2022, will not include the old implementation. Unless serious objections to this are raised by 2022-01-10 we will execute it exactly as outlined above. Regards, Robert
|
||||||||||||||
|
|