Hi, This is to propose Messaging4Transport [1] as a new project under OpenDaylight. This project proposal is based on the initial work currently done starting from the OpenDaylight summer internship 2

Hi, I have just posted a project proposal for project creation review. Here is the link https://wiki.opendaylight.org/view/Project_Proposals:FaaS Thanks Xingjun Chu IP solutions Huawei Technologies Ca

Hi ODL Team, We would like to share our project proposal - ODL Controller Security project. The wiki page detailing out the same is https://wiki.opendaylight.org/view/Project_Proposals:Controller_Shie

Hi all; i am a developer and new to yang world.i want to know what exactly are the methods possible by which i can convert a given yang file to corresponding xml schema.. like- leaf hello{ type string

Colin, Comments inline... It should actually reduce the cross patch issue as things get moved into more logical groupings. It should make it a fair bit easier, as you will have distinct logical compon

I'm also cc'ing the project-proposals list to archive this in the appropriate location. --Colin

Dear All, Please find attached OpenDaylight project proposal: SDNApp-SDK (Software Development Kit - SDK for SDN Applications) Project Wiki page link as follows: https://wiki.opendaylight.org/view/Pro

Hi, Colin, Do you think we still have time to do NEMO creation review tomorrow? Thanks, Helen Chen

Hi, A new proposal has been posted for reviewing: https://wiki.opendaylight.org/view/Project_Proposals:NEMO Thanks, Helen Chen

Its also important to map out which projects will depend on this one and how. One problem with some changes is that it can affect an "upstream" project that consumes another. When say a public API cha

Hi All, Added a Project Proposal for “OpenFlow Extensions in support of Circuit Switching” at - https://wiki.opendaylight.org/view/Project_Proposals:Openflowplugin-extension-circuitsw Please review it

I agree with Colin's comment. We face the similar issue with Openflowplugin project, where NSF/Models were living in controller and their implementation was in openflowplugin project. Everytime we pus

As part of a previous TSC meeting [0], I was asked to provide candidate dates for service releases beyond SR2 for Lithium. The tentative plan was: A.) Have the first two service releases spaced 6 week

Just a heads up, I've added this project to the list of project proposals pending review here: https://wiki.opendaylight.org/view/Project_Proposals:Main#Proposals_Submitted_For_Review --Colin

Just a heads up, I've added this project to the list of project proposals pending review here: https://wiki.opendaylight.org/view/Project_Proposals:Main#Proposals_Submitted_For_Review --Colin

Just a heads up, I've added this project to the list of project proposals pending review here: https://wiki.opendaylight.org/view/Project_Proposals:Main#Proposals_Submitted_For_Review --Colin

Just a heads up, I've added this project to the list of project proposals pending review here: https://wiki.opendaylight.org/view/Project_Proposals:Main#Proposals_Submitted_For_Review --Colin

So, I think it makes a lot of sense to move the NETCONF SB plugin to it's own project, but moving RESTCONF out seems... odd to me. It's as critical to the use of the MD-SAL (if not more so) than the D

I'm curious how much of this could be done by having logical sub-projects that are well-organized and well-separated within the YANG tools repository. I understand that we'd like to factor apart the v

Guys, Quick point of order. Today is M3 for offset 0, and thus it is to late for this split to happen for Lithium. Is this just an ultra-early launch of the discussion for Beryllium? Ed