|
Re: TSC Meeting for October 21, 2021 at 9 am Pacific
Brandon Wick
Thank you Guillaume. How does this look? Once final, I'll add it to main navigation and we can start promoting on social/email, etc. Best, Brandon On Tue, Oct 26, 2021 at 8:08 AM <guillaume.lambert@...> wrote:
Brandon Wick
|
|
|
|
Re: TSC Meeting for October 21, 2021 at 9 am Pacific
Guillaume Lambert
Thank you Brandon and Filip.
"[TransportPCE]
end-to-end connectivity management of high rates (400G) and otn service improvements" De : Brandon Wick <bwick@...>
Envoyé : mardi 26 octobre 2021 03:54:04 À : Filip Čúzy Cc : LAMBERT Guillaume INNOV/NET; TSC; Daniel de la Rosa; Casey Cain Objet : Re: [OpenDaylight TSC] TSC Meeting for October 21, 2021 at 9 am Pacific Thank you Filip for pulling this together. It's exactly what we were looking for.
Guillaume, I agree the Phosphorus release page would benefit from a quote with your perspective. In the page copy, Filip has proposed some key points that you could incorporate and put into your own words. We'd like to get the page published this week
so please propose your short quote as soon as possible. If you'd like to
discuss the quote, feel free to reach out. Thanks!
Best,
Brandon
On Mon, Oct 25, 2021 at 6:27 AM Filip Čúzy
<filip.cuzy@...> wrote:
Brandon Wick
_________________________________________________________________________________________________________________________ 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: TSC Meeting for October 21, 2021 at 9 am Pacific
Brandon Wick
Thank you Filip for pulling this together. It's exactly what we were looking for. Guillaume, I agree the Phosphorus release page would benefit from a quote with your perspective. In the page copy, Filip has proposed some key points that you could incorporate and put into your own words. We'd like to get the page published this week so please propose your short quote as soon as possible. If you'd like to discuss the quote, feel free to reach out. Thanks! Best, Brandon On Mon, Oct 25, 2021 at 6:27 AM Filip Čúzy <filip.cuzy@...> wrote:
Brandon Wick
|
|
|
|
ODL Twitter Account Status
Brandon Wick
Hi All, Here's the status on the ODL Twitter account. ################# Unfortunately, due to some staffing changes in the past we are unable to access the ODL Twitter account. (The recovery email associated with the account is not a Linux Foundation email address). We have made multiple formal requests via Twitter Help Center to recover this data and have, so far, been unsuccessful. We just made another formal request last week and will explore other recovery options if this time is again unsuccessful. Best, Brandon Wick
|
|
|
|
Re: TSC Meeting for October 21, 2021 at 9 am Pacific
Filip Čúzy
Hi everyone,
I was out of office during the last call. We tried creating a spin on the release notes/announcement, which would incorporate a technical view, as well as some more easy-going and more story-telling approach to changes in the latest release.
I realize there is a Google doc available for changes, but since we overwrote most of it, here is a PDF of it attached.
Also, Guillaume as the chair could add some ca. two sentences as a direct quote about the latest release – please.
Let me know what all of you are thinking.
Filip Čúzy Marketing Specialist
PANTHEON .tech Mlynské Nivy 56, 821 05 Bratislava Slovakia Tel / +421 220 665 111
MAIL / filip.cuzy@... WEB / https://pantheon.tech
From:
TSC@... <TSC@...> On Behalf Of Guillaume Lambert via lists.opendaylight.org
Sent: Wednesday, October 20, 2021 9:39 PM
To: TSC <tsc@...> Cc: Daniel de la Rosa <ddelarosa0707@...>; Casey Cain <ccain@...> Subject: [OpenDaylight TSC] TSC Meeting for October 21, 2021 at 9 am Pacific
Hello OpenDaylight Community,
Next TSC meeting is October 21, 2021 at 9 am Pacific Time.
If you need to add anything, please let me know or add it there. _________________________________________________________________________________________________________________________ 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: TSC Meeting for October 21, 2021 at 9 am Pacific
HI Robert On Thu, Oct 21, 2021 at 9:20 AM Robert Varga <nite@...> wrote: On 21/10/2021 15:51, Daniel de la Rosa wrote: no worries
ok good to know. I'll keep SR1 schedule as it is then. Please keep us posted
|
|
|
|
Re: [E] [OpenDaylight TSC] Moderating mailinglists
Robert Varga
On 21/10/2021 19:48, Ghazisaidi, Navid wrote:
Hi Robert,The way this works is you get those emails to a mailbox of your choosing. How to set it up -- I have no idea, but I bet Casey does know exactly what to do :) Thanks so very much, Robert Thanks,
|
|
|
|
Re: [E] [OpenDaylight TSC] Moderating mailinglists
Ghazisaidi, Navid
Hi Robert, I'll take care of it. Can you send me the credentials and links to the mailbox(es)? Thanks, Navid
On Thu, Oct 21, 2021 at 10:26 AM Robert Varga <nite@...> wrote: Hello everyone,
|
|
|
|
Moderating mailinglists
Robert Varga
Hello everyone,
we sorely need people moderating our mailing lists. The jobs description is simple: 1) setup filters to redirect approvals to a separate folder 2) look at that folder at least once a day, doing: 2a) delete spam 2b) send an empty reply to valid emails Step 1) is required because groups.io just does not have any spam filter, so you get all sorts of offers. S2N is probably around 0.05. The good thing about is you know how most favorite spams on the internet look like. This is a critical job, as it makes our conversations with potential new members fluid, as oftentimes they do not subscribe and ignore the message groups.io sends them. Any immediate takers or persons willing to find volunteers, please? Thanks, Robert P.S.: Just a data point: in last 8 hours I got one new subscriber notification and 7 spam messages in that folder.
|
|
|
|
Re: TSC Meeting for October 21, 2021 at 9 am Pacific
Robert Varga
On 21/10/2021 15:51, Daniel de la Rosa wrote:
Hello allHey Daniel, Sorry for not replying to your previous email. Luis and I won't be able to attend this week's meeting. I have requested a code freeze for Silicon in preparation for SR3. i'll be updating checklist for Phosphorus SR1 shortlySo BGPCEP should be now fine for SR3. I am rolling MRI projects for both SR3 and SR1 (as you might have noticed). I will need tomorrow to finish up with NETCONF for SR3, so we should be good to roll on Monday. For SR1, we should be okay to freeze by the end of next week -- depending what the outstanding items are in NETCONF. Thanks, Robert
|
|
|
|
Re: TSC Meeting for October 21, 2021 at 9 am Pacific
Hello all Luis and I won't be able to attend this week's meeting. I have requested a code freeze for Silicon in preparation for SR3. i'll be updating checklist for Phosphorus SR1 shortly Thanks
On Wed, Oct 20, 2021 at 12:38 PM <guillaume.lambert@...> wrote:
|
|
|
|
Silicon code freeze for SR3
Hello TSC and all We are going to code freeze Silicon for all Managed Projects ( cut and lock release branches ) on Monday October 25th at 10 am pst Please remember that we only allow blocker bug fixes in release branch after code freezes Daniel de la Rosa ODL Release Manager Thanks ps. Release schedule and checklist for your reference Thanks Daniel de la Rosa ODL Release Manager
|
|
|
|
TSC Meeting for October 21, 2021 at 9 am Pacific
Guillaume Lambert
Hello OpenDaylight Community,
Next TSC meeting is October 21, 2021 at 9 am Pacific Time.
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: Update Release schedule for Silicon SR3 and Phosphorus SR1
Robert and team, can we proceed with Silicon code freeze as scheduled? Thanks
On Mon, Oct 11, 2021 at 8:00 AM Daniel de la Rosa <ddelarosa0707@...> wrote:
|
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Phosphorus release status
Hello Guillaume Yes this looks great to me so this basically concludes everything in phosphorus formal release Thank you all
On Sat, Oct 16, 2021 at 2:59 AM <guillaume.lambert@...> wrote:
|
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Phosphorus release status
Guillaume Lambert
Hello
FYI download pages and documentation were updated yesteday evenig (CEST time zone).
I removed the Aluminium release from the fly-panel and put the default page to the new phosphorus documentation. Let me know if this is OK for you Daniel.
Hope this helps
BR
Guillaume
De : Daniel de la Rosa [ddelarosa0707@...]
Envoyé : jeudi 14 octobre 2021 06:45 À : Luis Gomez Cc : LAMBERT Guillaume INNOV/NET; Andrew Grimberg; Anil Belur; Casey Cain; OpenDaylight Discuss; Release; THOUENON Gilles INNOV/NET; TSC; integration-dev@...; navid.ghazisaidi@... Objet : Re: [opendaylight-dev][release] OpenDaylight - Phosphorus release status Thanks Luis and Guillaume. Indeed only downloads and branch documentation is all we have left to do
_________________________________________________________________________________________________________________________ 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.
|
|
|
|
Recent change to CI management
Greetings folks,
Yesterday we merged a major change to how Jenkins is managed. Unfortunately, due to how the change had to go in, it was a massive review and a few things got missed during it causing some issues over the last ~12 hours or so as we worked that all out. From what I'm seeing we're back on track for the environment to be working. So, what's changed? The way we do the managed config files, that is, all the files that are stored in Jenkins with credentials for use in the jobs. Historically, this have been hand managed, or as we rolled out our self-service bits, we've had some scripting in place to push in the standard configuration files as new repositories were built. There's been several downsides to this system: 1) The community had no idea what was actually in the files 2) The community has had no easy way to influence what the files are 3) It was very easy for something to be applied to the production system, but not the sandbox system 4) It was very easy for things to be misconfigured Late last year we started work on moving to Jenkins Configuration as Code (JCasC) as much as possible for things. Internally at LF, that has meant better puppet based management of Jenkins for non-community tunables, but it didn't completely resolve other areas that are supported by JCasC but would be something that the community would like to at least know how it was configured, or even influence it. As such, when we were designing our puppet conversion to using JCasC we made sure to make it possible to also incorporate community managed bits. So, here's what this means to the community: The environment variables and cloud configuration continue to be managed the same way (files in the jenkins-config directory of releng/builder), the way that those get pushed into Jenkins has changed though and we now take those files and convert them into JCasC yaml and put them where they belong on system. At the same time, we've also written a system to allow the community to influence the managed config files [0]. You will find in the jenkins-config directory another couple of directories: managed-config-files managed-config-templates These are the directories and files that are now driving the manged config files. They were also the cause of why the system wasn't working so well after the merge. This is due to how JCasC operates. It works in an all-or-nothing setup for the parts of Jenkins that it takes under management. As such, this meant we had to port _all_ of the managed files in at the exact same time, generating a very, very large change that ended up causing the reviews to miss on parts. We should be all good now after having worked through the issues. This new system has a few benefits and one negative: Benefits: * The configuration, upon merge, will be applied within 5 minutes. * The community now has better visibility into how the systems are managed and can influence them * We have fully versioned configuration for the parts under management this way, making it easier to roll back a problem change, or even (re)build a new system more quickly * The cloud configuration is now _less_ brittle than when we were using the jenkins-cfg-merge job which then translated our cloud configuration files into the needed format to be inserted via a on-the-fly built groovy script. This tended to be very brittle and minor version changes of the OpenStack cloud plugin could easily break our system. JCasC is both more, and less forgiving in this respect as it's a yaml rendering of how the parts are configured and is far less concerned with object design. * We now also support Nomad clouds (this was built for FD.io) and will in the future also provide community support for static builder management as well as AWS / EC2 cloud management The negative: The jenkins-cfg-merge job has been removed from the system as it conflicts with using JCasC management. This means that failures in the configuration being applied will not be visible to the community and only to LF staff that receive the cron job output (yes, cron job) that is actually applying the changes. We believe that this minor negative is far outweighed by the speed of which these configurations get applied and the ability for the community to actually see how things are configured and provide input on them. -Andy- [0] https://docs.releng.linuxfoundation.org/en/latest/jenkins.html#managed-config-files -- Andrew J Grimberg Manager Release Engineering The Linux Foundation
|
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Phosphorus release status
Thanks Luis and Guillaume. Indeed only downloads and branch documentation is all we have left to do
On Wed, Oct 13, 2021 at 2:18 PM Luis Gomez <ecelgp@...> wrote:
|
|
|
|
Re: [opendaylight-dev][release] OpenDaylight - Phosphorus release status
Luis Gomez
FYI Phosphorus distribution has been released:
toggle quoted messageShow quoted text
BR/Luis
|
|
|
|
TSC Meeting for October 14, 2021 at 10 pm Pacific
Guillaume Lambert
Hello OpenDaylight Community,
Next TSC meeting is September 30, 2021 at 10 pm Pacific Time.
If you need to add anything, please let me know or add it there. _________________________________________________________________________________________________________________________ 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.
|
|
|