Thank you all. So I have picked Magnesium AR 491 and here is the updated tracksheet to review...

Hi, I am fine with 9 AM PST or 10 PM PST.

Here is a dooble pool to cite your time preference. https://doodle.com/poll/yadxuiusngcus6eg

Hello all, I'm ok with anytime between 6am - 11pm AEST time. Thanks, Anil

Infra is better now and missing BGPCEP patch is merged so I think we can pick next AR build as RC. BR/Luis

Hello Team Any updates on the Magnesium SR3 issues? Thanks On Wed, Dec 2, 2020 at 8:01 PM Daniel de la Rosa via lists.opendaylight.org <ddelarosa0707=gmail.com@...> wrote:

I feel, any time between 8:00 AM to 9:00 AM PST should be convenient to most of the attendees in almost all timezones. Current TSC schedule of 9:00 AM PST should be OK or we can move it to a little

In the interest of supporting cross-community engagement, attracting continued participation of new organizations, and regular updates from marketing team experts I would recommend that we keep a

My suggestion is to do it at a time that all current TSC members can attend, which is probably around 10 pm pst, if Robert and Guillaume are ok with that so Anil can join every single meeting.

A correction about this: >> The TSC Chairperson has also filled the role of TAC and SPC representative unless otherwise declined. The elections for both the TAC and SPC representatives always have to

Hello, everyone. I would again like to congratulate our newly elected TSC Members and thank the outgoing members for their amazing contributions to the OpenDalight Community! The TSC Chair nomination

I think, like in the past, it will be hard to find a time suiting everyone. So even when it is messy in the calendar we might want to continue with the bi-weekly morning-night schedule. So far my

Hello everyone, with the new TSC along with new community participants, we have an opportunity to adjust out TSC call schedule. To that effect, I would like to get some basic information on

@Anil Belur i know you can't join next TSC at 9 am pst, so can you let us know if increasing the vexhost is going to be your long term solution? I'd like to be able to release Magnesium SR3 this week

OK, it seems like this has to be fixed in order: - First we need to fix any issue with vexhost not cleaning images. - Second, if the CSIT still fails, we can look at reducing the robot minions even if

I can see there's some orphaned servers that don't appear to be getting deleted, from the Jenkins UI: Online since Nov 10th 2020

Please review https://git.opendaylight.org/gerrit/c/releng/builder/+/94012

Hello Luis: The max no of instances for the robot node type is set to 25, let's decrease the value to 20 going forward? This would imply that the dist-test would take a bit longer to

Next ODL TSC meeting is December 3, 2020 at 9 am Pacific Time. The zoom session for the meeting is: https://zoom.us/j/219174946?pwd=aW9uSXl0KzJpcjRXY3l1bWIwdG9KZz09. Agenda for this meeting is

Hi Anil, I think increasing the vexhost quota might not be the right solution here because: 1) it may impact the vexhost bill (this is why you added a quota in first place) and 2) it is hard to adjust