Thanks for letting us know.

Hello TSC members: Thanh has agreed to proxy me during the TSC calls on Nov 14th and 28th, since I would not be able to join the call during these days. Thanks, Anil

Hello, I have updated the proposal to spell out gaps in our knowledge of the problem/solution domains here: https://wiki.opendaylight.org/view/Project_Proposals:Lighty#Open_questions We will need

Hello everyone, Tejas, thank you for your feedback. Regarding your comments: Yes, we will upstream all lighty.io modules from our lighty.io github repository [1]. Yes, I agree with you. I would like

Yes, we could do that if that if folks want us to. -Andy- -- Andrew J Grimberg Manager Release Engineering The Linux Foundation

This was discussed in the TSC call, forwarding to the list below. ---------- Forwarded message --------- From: Casey Cain <ccain@...> Date: Thu, Aug 29, 2019, 12:22 Subject: Re: [infrawg] Meeting

+1

+1 We have a +1 vote from the following TSC members: Faseela, Hema, Luis, Tejas, Jamo, Abhijit Hence this carries as that is 6 out of 11. Congratulations Achuth for being approved as the Neutron

BTW, I forgot to mention this effort of checking yang models per-project is also available for Self-Managed projects (use merge-full vs merge-managed in the job

Nothing to add, I agree on the 3 bullets.

+1 On 11/8/19 9:34 AM, Tejas Nevrekar wrote:

+1

+1

Sure Abhijit. I will pose my comments/suggestions here then: 1. Will this project upstream the existing lighty components for the SB plugins like netconf, openflowplugin? 2. From an implementation

+1

+1

+1 -- Faseela.K

Also this should not be that hard, Stephen already prepared a patch: https://git.opendaylight.org/gerrit/#/c/netvirt/+/84369/ You can merge this and later fix the CSIT. BR/Luis

I couldn't spend time later on that activity, Abhinav, do we have anyone who can work on it?

OK, thanks for clarifying. Any ETA for SFC removal?