Hi, Abhijit I am sorry.About the present in the TSC meeting, August 16 may be inconvenient for us. The time may conflict for some of my team members. So Ineed to discuss with them about the

Hi, Daya We plan to use netconf to configure otherdevices and some private api for special third party devices in the future. Current netconf is not implementedin our HNI module and it

Hi,Anil (1)Current we are not considering Kubernetes networking support/extension. Butyour suggestion is a good idea. We can put it in the next step. (2)The netconf、privateapi Is the

Thanks sam. Glend, a few more questions from me. ODL has the netvirt service today which can configure a hwvtep today via ovsdb based on openstack l2gw configuration. It looks like semantically,

Adding Daya to thread.

Added the TSC as well.

Glend, There is a 2 week review period for project proposals so that folks can ask questions over the email and after which you can come and present the project to the TSC for approval. Since you

Hi Glend, Thanks for the project proposal. I have few quick questions (1) Although it's not mentioned in the project proposal, but are you considering Kubernetes networking support/extension also as a

Hi: we propose a project to the opendaylight committee. Here is the reference https://wiki.opendaylight.org/view/Project_Proposals:HNI I am looking forwards your replay. Thanks.

Hi: we propose a project to the opendaylight committee. Here is the reference https://wiki.opendaylight.org/view/Project_Proposals:HNI I am looking forwards your replay. Thanks. Best

Hi TSC members, For a new project proposal , the TSC review is supposed to be two weeks after it has been proposed so that the TSC members have a chance to review it first. In this case, this was

Hi, As discussed in last TSC call, we presented the scope of the SRM feature which is currently in GENIUS, at TWS. The decision was to spin off a separate project, starting with SRM, and

I would strongly recommend that the repo and package name line up. Not doing so breaks all of the other standards we've got in ODL around artifact naming. -Andy- -- Andrew J Grimberg Lead, IT

Agreed. When looking at ODL's Gerrit system it's obvious that this is an ODL project however when looking from PyPi that wouldn't be obvious at all. We could have supporttools as the repo name, but

Can we stay with odltools? These tools are installed via pip install odltools so it is better if it has odl in the package name. Adding support doesnt add much as tools implies the same.

I'm good with 'supporttools' JamO

+1 to supporttools, that's more specific than "[odl]tools" which could be anything and everything.

Since odl is kind of implicit... supporttools or somesuch?

ODL Support Tools sounds good. I would prefer the smaller odltools for the repo name.