Re: liblldp project proposal

Colin Dixon

It just seems easier to me to put the code in OpenFlow plugin than to pull a new project out of a hat that somehow doesn't behave like normal projects. If we can move it to OpenFlow plugin for now, that seems right.


On Wed, Jul 26, 2017 at 4:53 PM, Anil Vishnoi <vishnoianil@...> wrote:
As a openflow committer hat on, I also don't have any strong objection here.

On Wed, Jul 26, 2017 at 4:24 PM, Abhijit Kumbhare <abhijitkoss@...> wrote:
I believe it was more of a library that could be used by any project for LLDP protocol packets - even though it's currently used only by OpenFlow Plugin. Hence we thought a central place would be better. Otherwise I don't see much problem in putting it into OpenFlow Plugin.

On Wed, Jul 26, 2017 at 2:55 PM Colin Dixon <colin@...> wrote:
I'm happy either way. The fact that lldp "is a protocol" doesn't seem like a compelling argument for why it can't go in the OpenFlow plugin project to me, but maybe I'm missing something. 

Abhijit, is there something I'm missing for why it shouldn't go in OpenFlow plugin?


On Wed, Jul 26, 2017 at 2:08 PM Sam Hague <shague@...> wrote:
On Wed, Jul 26, 2017 at 8:50 AM, Colin Dixon <colin@...> wrote:
Thanks! I take it the conclusion was that this shouldn't be part of the OpenFlow plugin project?
The discussion leaned to a new project. I think moving to openflowplugin would be easiest, but lldp is a protocol and doesn't make sense to be there.


On Sat, Jul 22, 2017 at 11:57 AM Sam Hague <shague@...> wrote:
Hello TSC,

I have included the liblldp to the list of project proposals. I would like to start the two week discussion.

This proposal is contingent on the plan to spin out the liblldp project from the controller. The goal was to get this started so we can get this started if we wanted it in for the nitrogen release.

Thanks, Sam

project-proposals mailing list

project-proposals mailing list


Join { to automatically receive all group messages.