Date   

Thoughts and request for guidance.

Sitaraman Vilayannur
 

Hi, 
  Hope this an appropriate group to broach this. 
  Is something along the below lines for the controller and management of SDN network and it open source implementation in the works...any pointers,  feedbacks/guidance is much appreciated.
 Thanks much.
Sitaraman


Exploiting SDN Capabilities:

Some thoughts on the controller considerations for exploiting programmable networks with information centric or content based routing. 

 I was listening in to Stanfords Courseera course on PGM and Expander Graphs..and chanced upon Feynmans lectures where he was talking about the relationship to Mathematics and Physics where though Feynman hadnt mentioned  explicitly seemed to touch upon convexity and duality.... ..and attempted to relate this to SDN networks....

Duality between the algorithmic approach and the nature of the optimization problem.

                One convex algorithmic approach could be to resort to viewing the entire problem as a graph and optimize on the nature of such graph.

                One non-convex algorithmic approach could be a  Newton gradient method.

Decomposition of an overall optimization problem into non-convex subcomponents which subcomponents can be treated jointly as a convex problem.  Such decomposition method could be by determining components (Exapander components?) that are well connected.

 

SDN:

Convexity could vary with the time window size of the problem.   At a given time instant or narrow time window, (routing) the problem is a convex one which one or a narrow set of optimum routing decisions, but due to changing traffic conditions, over a period of time individual routing decisions become a non-convex optimization problem. Therefore, an SDN control could possibly have non-convex (greedy?) approach component and a non-greedy component (viewing problem as a graph with expander subcomponets, each of which could in turn apply the greedy method).

When we bring time axis into the picture, the convexity of the problem changes from convex (short time window) to non-convex (large time window, to make decisions based on current and expected traffic pattern). Therefore the algorithmic approach to the control could change from  a non-convex (short time frame) to a convex (large time frame).  One way of doing this could be for the non-convex components to contribute weights (which determination could have a convex nature to it or at least partly determined by a convex component) to the elements of the convex components (a graph)

When one considers the Information based routing capability, ICN or advanced versions of the same. Here for a short time window, the placement of Information is a non-convex problem, and based on typical information demand, over a large time-window (placement and information content of caches ) could be considered a convex one.   Therefore, information superimposes an orthogonal nature on the convexity to the data component of the SDN-ICN combine.

Stochasticity and time window: While routing in any given network necessarily has to be deterministic, the optimal nature of the same introduces stochasticity amongst the possibly multiple options each of which individually yield deterministic routing. 

Here we would then need to consider the same issues as above wherein a general problem could be started off with a PGM and based on expander sections of this graph, now be decomposed into its non-convex (nature of the probabilistic problem) subcomponents.  It appears that information placement and routing could draw heavily on such PGM as semantic connectivity (again to be considered both across space and time as the vanilla version described above) could be probabilistic. Bringing in Content based Routing and Information Centric Routing therefore could be viewed as  bringing in a "placement" component to routing problem, eerily close but probably a lot more complex than what the VLSI folks deal with.  Therefore, the hardware folks probably have nothing to worry Software Defined Networks are going to use Hardware algorithms after all 


Canceled Event: OpenDaylight TSC Meeting @ Thu Jun 6, 2013 11am - 1pm (probb@linuxfoundation.org)

Phil Robb
 

This event has been canceled and removed from your calendar.

OpenDaylight TSC Meeting

Meeting URL: https://meetings.webex.com/collabs/meetings/join?uuid=MA3SRND964PIX06V2LS3SXX3RE-9VIB

Access Information
Meeting number: 194 548 370
Meeting password: This meeting does not require a password.

Audio Connection
1-855-244-8681 Call-in toll-free number (US/Canada)
1-650-479-3207 Call-in toll number (US/Canada)
Access code: 194 548 370

When
Thu Jun 6, 2013 11am – 1pm Mountain Time
Where
+1 650-479-3207 - Additional connection information in event description (map)
Calendar
probb@...
Who
Philip Robb - organizer
tsc@...

Invitation from Google Calendar

You are receiving this courtesy email at the account tsc@... because you are an attendee of this event.

To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar.


Proposal to vote to accept VTN project

Ed Warnicke (eaw) <eaw@...>
 

I would like to propose that we hold the VTN project creation review and vote to accept
it at the next TSC meeting (this coming Thursday June 13).  

The proposal is here:

I believe they are seeking to enter in bootstrap state.

Ed


Proposal to discuss and vote on the Simultaneous Release Plan

Ed Warnicke (eaw) <eaw@...>
 

I would like to propose that we discuss and vote on the Simultaneous Release Plan:


at next Thursdays (June 13) TSC meeting.

I strongly encourage discussion of the plan on the list prior to that time :)

Ed


I won't be able to make the TSC call this week

David Meyer <dmm@...>
 

Folks,

I'll be on an "interesting" trip to Japan so won't be able to make the
call. Chris Wright has graciously agreed to run the call.

Thanks,

--dmm


Re: I won't be able to make the TSC call this week

Thomas Nadeau <tnadeau@...>
 

I will be in the air on Thursday during the call so I cannot make it
either. That reminds me that we have not sorted out the proxy situation
yet.

--Tom

On 6/10/13 8:26 AM, "David Meyer" <dmm@...> wrote:

Folks,

I'll be on an "interesting" trip to Japan so won't be able to make the
call. Chris Wright has graciously agreed to run the call.

Thanks,

--dmm
_______________________________________________
TSC mailing list
TSC@...
https://lists.opendaylight.org/mailman/listinfo/tsc


Code Prep Suggestions for new Projects

Ed Warnicke (eaw) <eaw@...>
 

Guys,
I put together a preliminary page of 'code prep suggestions' for new projects… not binding things,
but rather 'so you are cleaning up your code to open source it… these are good things to think about' things.
I'd love to hear feedback from folks on what's there, and what changes folks think should be there:


Ed


Re: I won't be able to make the TSC call this week

David Meyer <dmm@...>
 

Thnx Tom. --dmm

On Tue, Jun 11, 2013 at 9:14 AM, Thomas Nadeau <tnadeau@...> wrote:

I will be in the air on Thursday during the call so I cannot make it
either. That reminds me that we have not sorted out the proxy situation
yet.

--Tom


On 6/10/13 8:26 AM, "David Meyer" <dmm@...> wrote:

Folks,

I'll be on an "interesting" trip to Japan so won't be able to make the
call. Chris Wright has graciously agreed to run the call.

Thanks,

--dmm
_______________________________________________
TSC mailing list
TSC@...
https://lists.opendaylight.org/mailman/listinfo/tsc



Supported openflow versions ?

Benny Rochwerger <BennyR@...>
 

All,

 

I am not sure which is the right mailing list to post this question, so please forgive me for cross-posting or if these are not the right lists (in which case, I’ll appreciate if someone points to the right place).

 

We are building an application that leverages some of the features in OF 1.3. Our current prototype is built on NOX, but as we adopt ODP, we would like to be able to move all our applications to a single controller.  

 

What are the plans for supporting OF 1.3 ? I assume that by the time of the first official release, OF 1.3 will be included, but will it be available in the repository prior to that ?  

 

Thanks in advance,

 

Benny Rochwerger


Re: [controller-dev] Supported openflow versions ?

Ed Warnicke (eaw) <eaw@...>
 

Benny,
There have been lots of folks who are talking about bringing OF 1.3 support.
As we go into the Simultaneous Release process:

(note: this is the proposal, not quite yet approved by TSC, but slated for discussion in tomorrows
TSC meeting)

Projects will need to put together Release Plans (described in the Project Lifecycle and Releases
section 3: http://www.opendaylight.org/project-lifecycle-releases) that among other things call out
Release Deliverables.  As part of hammering out those plans we should be figuring out who is stepping
forth to work on what, and at what Milestones they will have what.  

Each project participating in the Simultaneous Release has to produce  a candidate release
plan for public comment by M1 (July 22) and finalize it based on that comment by M2 (Aug 19)
(though I expect in most cases work will have commenced long before those dates).

Which is to say… I expect to see OF 1.3 support… and the community is still working out the plans 
for exactly what is going in when and who's stepping forward to do the work.

Does that answer your question?

Ed

P.S.  I do want to be clear that the Milestones and dates listed above are only *proposed* Milestones
and dates and don't become the plan of record until the TSC approves them.

On Jun 12, 2013, at 2:52 AM, Benny Rochwerger <BennyR@...> wrote:

All,
 
I am not sure which is the right mailing list to post this question, so please forgive me for cross-posting or if these are not the right lists (in which case, I’ll appreciate if someone points to the right place).
 
We are building an application that leverages some of the features in OF 1.3. Our current prototype is built on NOX, but as we adopt ODP, we would like to be able to move all our applications to a single controller.  
 
What are the plans for supporting OF 1.3 ? I assume that by the time of the first official release, OF 1.3 will be included, but will it be available in the repository prior to that ?  
 
Thanks in advance,
 
Benny Rochwerger
_______________________________________________
controller-dev mailing list
controller-dev@...
https://lists.opendaylight.org/mailman/listinfo/controller-dev


Re: [controller-dev] Supported openflow versions ?

Ed Warnicke (eaw) <eaw@...>
 

Benny,
There have been lots of folks who are talking about bringing OF 1.3 support.
As we go into the Simultaneous Release process:

(note: this is the proposal, not quite yet approved by TSC, but slated for discussion in tomorrows
TSC meeting)

Projects will need to put together Release Plans (described in the Project Lifecycle and Releases
section 3: http://www.opendaylight.org/project-lifecycle-releases) that among other things call out
Release Deliverables.  As part of hammering out those plans we should be figuring out who is stepping
forth to work on what, and at what Milestones they will have what.  

Each project participating in the Simultaneous Release has to produce  a candidate release
plan for public comment by M1 (July 22) and finalize it based on that comment by M2 (Aug 19)
(though I expect in most cases work will have commenced long before those dates).

Which is to say… I expect to see OF 1.3 support… and the community is still working out the plans 
for exactly what is going in when and who's stepping forward to do the work.

Does that answer your question?

Ed

P.S.  I do want to be clear that the Milestones and dates listed above are only *proposed* Milestones
and dates and don't become the plan of record until the TSC approves them.

On Jun 12, 2013, at 2:52 AM, Benny Rochwerger <BennyR@...> wrote:

All,
 
I am not sure which is the right mailing list to post this question, so please forgive me for cross-posting or if these are not the right lists (in which case, I’ll appreciate if someone points to the right place).
 
We are building an application that leverages some of the features in OF 1.3. Our current prototype is built on NOX, but as we adopt ODP, we would like to be able to move all our applications to a single controller.  
 
What are the plans for supporting OF 1.3 ? I assume that by the time of the first official release, OF 1.3 will be included, but will it be available in the repository prior to that ?  
 
Thanks in advance,
 
Benny Rochwerger
_______________________________________________
controller-dev mailing list
controller-dev@...
https://lists.opendaylight.org/mailman/listinfo/controller-dev


Updated Invitation: OpenDaylight TSC Meeting @ Weekly from 11am to 1pm on Thursday except Thu Jun 6 11am (probb@linuxfoundation.org)

Phil Robb
 

This event has been changed.

OpenDaylight TSC Meeting

Meeting URL: https://meetings.webex.com/collabs/meetings/join?uuid=MA3SRND964PIX06V2LS3SXX3RE-9VIB

Access Information
Meeting number: 194 548 370
Meeting password: This meeting does not require a password.

Audio Connection
1-855-244-8681 Call-in toll-free number (US/Canada)
1-650-479-3207 Call-in toll number (US/Canada)
Access code: 194 548 370

When
Changed: Weekly from 11am to 1pm on Thursday except Thu Jun 6 11am Mountain Time
Where
+1 650-479-3207 - Additional connection information in event description (map)
Calendar
probb@...
Who
Philip Robb - organizer
tsc@...

Going?   All events in this series:   Yes - Maybe - No    more options »

Invitation from Google Calendar

You are receiving this courtesy email at the account tsc@... because you are an attendee of this event.

To stop receiving future notifications for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar.


Call for folks interested in bringing projects for the first Simultaneous Release

Ed Warnicke (eaw) <eaw@...>
 

The TSC today asked that we poll the community for those interested in bringing project they would like to see
included in the first Simultaneous Release. The current proposed Simultaneous Release Plan (here:
https://wiki.opendaylight.org/view/Simultaneous_Release:Simultaneous_Release_Plan_2013 )
requires projects, by M1 on July 22, 2013, to:

1) Declare their intention to join the Simultaneous Release
2) Provide their candidate Release Plan

This has implications for folks who are seeking to bring projects to ODL that they would like to
be in the first Simultaneous Release. It takes 2-3 weeks from proposal to approval (to allow
for public comment on the proposal and IPR Review). So if the July 22 M1 date is
approved by the TSC, projects that wished to join the Simultaneous Release would need to
get project proposals in by early July.

Please note: a project does not have to be part of the Simultaneous Release to be an OpenDaylight
project.

On the TSC call it was suggested that we poll the community to see if there are folks intending to bring
projects they would like to be in the first Simultaneous Release to see if that July 22nd date would
represent an impediment to them.

So please speak up :)

Ed


Your VTN Proposal has been accepted into Bootstrap State

Phil Robb
 

Yamabe-san:

I am pleased to inform you that the OpenDaylight project proposal titled "OpenDaylight Virtual Tenant Network" has been approved by the TSC for entering the BootStrap state.

The next step will be uploading the source code into the OpenDaylight repository.  To do this, you will need to choose a suitable repository name for the project.  You are not required to choose the name "VTN" for your repository, but if you do choose "VTN" it has already been pre-approved by the TSC.  If you wish to use another name, please send email to the TSC requesting approval for the name of your choice.  Please understand that the TSC is not recommending the name "VTN", but rather has pre-approved it on the assumption that "VTN" is the name you will want to use.

From working with the VTN code during the Inbound Code Review process, the admin team has had some difficulty in getting the project to fully build in the Jenkins CI environment.  Can you please indicate a contact for Andrew Grimberg (cc-ed) to work with in troubleshooting and fixing these build issues?

Thanks Yamabe-san, and congratulations on your contribution to the OpenDaylight Project.

Phil.
--
Phil Robb
Director - Networking Solutions
The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb


Re: Your VTN Proposal has been accepted intoBootstrap State

m-kudo@...
 

Phil san,

We are so delighted to hear that our proposal was approved.
As Yamabe san is out of town through this weekend, please let me express
our thankfulness to the TSC for this approval on behalf of him.

Regarding the repository name, we want to use VTN. So, please create
the repository with this name.

Regarding a contact of troubleshooting for full build, please contact
Yamabe san.

Again, thank you very much for the approval, and we are really excited
to work on the OpenDaylight project.

Best regards,
--
M. Kudo

Yamabe-san:

I am pleased to inform you that the OpenDaylight project proposal titled
"OpenDaylight Virtual Tenant Network" has been approved by the TSC for
entering the BootStrap state.

The next step will be uploading the source code into the OpenDaylight
repository. To do this, you will need to choose a suitable repository name
for the project. You are not required to choose the name "VTN" for your
repository, but if you do choose "VTN" it has already been pre-approved by
the TSC. If you wish to use another name, please send email to the TSC
requesting approval for the name of your choice. Please understand that
the TSC is not recommending the name "VTN", but rather has pre-approved it
on the assumption that "VTN" is the name you will want to use.

From working with the VTN code during the Inbound Code Review process, the
admin team has had some difficulty in getting the project to fully build in
the Jenkins CI environment. Can you please indicate a contact for Andrew
Grimberg (cc-ed) to work with in troubleshooting and fixing these build
issues?

Thanks Yamabe-san, and congratulations on your contribution to the
OpenDaylight Project.

Phil.
--
Phil Robb
Director - Networking Solutions
The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb


Re: Your VTN Proposal has been accepted intoBootstrap State

Ed Warnicke (eaw) <eaw@...>
 

Kudo san,

Might I respectfully suggest that we use a lower case convention for repo names? In this case that would be 'vtn' rather than 'VTN'. Would that be acceptable to you?

On Jun 14, 2013, at 11:58 AM, "m-kudo@..." <m-kudo@...> wrote:

Phil san,

We are so delighted to hear that our proposal was approved.
As Yamabe san is out of town through this weekend, please let me express
our thankfulness to the TSC for this approval on behalf of him.

Regarding the repository name, we want to use VTN. So, please create
the repository with this name.

Regarding a contact of troubleshooting for full build, please contact
Yamabe san.

Again, thank you very much for the approval, and we are really excited
to work on the OpenDaylight project.

Best regards,
--
M. Kudo


Yamabe-san:

I am pleased to inform you that the OpenDaylight project proposal titled
"OpenDaylight Virtual Tenant Network" has been approved by the TSC for
entering the BootStrap state.

The next step will be uploading the source code into the OpenDaylight
repository. To do this, you will need to choose a suitable repository name
for the project. You are not required to choose the name "VTN" for your
repository, but if you do choose "VTN" it has already been pre-approved by
the TSC. If you wish to use another name, please send email to the TSC
requesting approval for the name of your choice. Please understand that
the TSC is not recommending the name "VTN", but rather has pre-approved it
on the assumption that "VTN" is the name you will want to use.

From working with the VTN code during the Inbound Code Review process, the
admin team has had some difficulty in getting the project to fully build in
the Jenkins CI environment. Can you please indicate a contact for Andrew
Grimberg (cc-ed) to work with in troubleshooting and fixing these build
issues?

Thanks Yamabe-san, and congratulations on your contribution to the
OpenDaylight Project.

Phil.
--
Phil Robb
Director - Networking Solutions
The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
_______________________________________________
TSC mailing list
TSC@...
https://lists.opendaylight.org/mailman/listinfo/tsc


Re: Your VTN Proposal has been accepted intoBootstrap State

Andrew Grimberg
 

Kudo-san,

I have provisioned the vtn repository (please note the repo name is
lowercase). It is at present only visible to the initial committers
listed on the project proposal page
( https://wiki.opendaylight.org/view/OpenDaylight_Virtual_Tenant_Network_(VTN):Proposal#Initial_Committers ) of note I could not find accounts in the system for the following listed initial committers:

Takayuki Kawagishi (kawagishi-takayuki@...)
Taiki Kondo (kondo-taiki@...)
Kasumi Takeshige (takeshige-kasumi@...)
Shigeru Yasuda (s-yasuda@...)

If initial committers are not able to see the repository in the web
interface while logged into Gerrit they will need to log out and log
back in for Gerrit to pick up the changes to their access.

I can add them to the list ACL once they have created accounts and I'm
notified (I search on the email address when looking them up to add, if
they registered with different addresses I need either their username or
the email address they registered with).

You will want to identify a project committer to do the originating code
submission to Gerrit. I'm available to help walk someone through doing
that. The repository does exist and the first commit is an empty one
attached to my account (this is produced by Gerrit when I initialize the
repository).

Once the code has been loaded into the repository let me know and I will
make it publicly accessible.

On the topic of not getting the source to compile. I finally worked
through the build dependency issues I was having on my test system. I
need to re-run on a clean VM to make sure I've captured them all before
I can get the Jenkins instance setup for automated patch verification.

Please note, that until I have Jenkins configured java assets produced
from merges of patches into master will not be able to show up in the
Nexus repository as we limit pushing to the repository to Jenkins only.
Admittedly, from what I see of the final build, there aren't any that
are eligible for push any way as we only allow pushes of the
org.opendaylight.<project> namespace from a given project. The two jar
objects I see are not of that namespace, they're in objs.jobjs
namespace.

-Andy-

On Fri, 2013-06-14 at 14:24 +0900, m-kudo@... wrote:
Phil san,

We are so delighted to hear that our proposal was approved.
As Yamabe san is out of town through this weekend, please let me express
our thankfulness to the TSC for this approval on behalf of him.

Regarding the repository name, we want to use VTN. So, please create
the repository with this name.

Regarding a contact of troubleshooting for full build, please contact
Yamabe san.

Again, thank you very much for the approval, and we are really excited
to work on the OpenDaylight project.

Best regards,
--
M. Kudo


Yamabe-san:

I am pleased to inform you that the OpenDaylight project proposal titled
"OpenDaylight Virtual Tenant Network" has been approved by the TSC for
entering the BootStrap state.

The next step will be uploading the source code into the OpenDaylight
repository. To do this, you will need to choose a suitable repository name
for the project. You are not required to choose the name "VTN" for your
repository, but if you do choose "VTN" it has already been pre-approved by
the TSC. If you wish to use another name, please send email to the TSC
requesting approval for the name of your choice. Please understand that
the TSC is not recommending the name "VTN", but rather has pre-approved it
on the assumption that "VTN" is the name you will want to use.

From working with the VTN code during the Inbound Code Review process, the
admin team has had some difficulty in getting the project to fully build in
the Jenkins CI environment. Can you please indicate a contact for Andrew
Grimberg (cc-ed) to work with in troubleshooting and fixing these build
issues?

Thanks Yamabe-san, and congratulations on your contribution to the
OpenDaylight Project.

Phil.
--
Phil Robb
Director - Networking Solutions
The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
--
Andrew J Grimberg
Systems Administrator
The Linux Foundation


Minutes and Recording of yesterday's TSC meeting are posted on the Wiki

Phil Robb
 

Hello TSC Members:

A draft of the Minutes and a link to the recording for the TSC meeting that was held yesterday is now posted on the wiki here:  https://wiki.opendaylight.org/view/TSC:Main

Please le me know if you have any comments.

Thanks,

Phil.
--
Phil Robb
Director - Networking Solutions
The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb


Re: Your VTN Proposal has been acceptedintoBootstrap State

m-kudo@...
 

Ed san,

Thank you very much for your suggestion.

Yes, 'vtn' is just fine with us.

Best regards,
--
M. Kudo

「Re: [OpenDaylight TSC] Your VTN Proposal has been acceptedintoBootstrap State」への返事です。

Kudo san,

Might I respectfully suggest that we use a lower case convention for repo names? In this case that would be 'vtn' rather than 'VTN'. Would that be acceptable to you?

On Jun 14, 2013, at 11:58 AM, "m-kudo@..." <m-kudo@...> wrote:

Phil san,

We are so delighted to hear that our proposal was approved.
As Yamabe san is out of town through this weekend, please let me express
our thankfulness to the TSC for this approval on behalf of him.

Regarding the repository name, we want to use VTN. So, please create
the repository with this name.

Regarding a contact of troubleshooting for full build, please contact
Yamabe san.

Again, thank you very much for the approval, and we are really excited
to work on the OpenDaylight project.

Best regards,
--
M. Kudo


Yamabe-san:

I am pleased to inform you that the OpenDaylight project proposal titled
"OpenDaylight Virtual Tenant Network" has been approved by the TSC for
entering the BootStrap state.

The next step will be uploading the source code into the OpenDaylight
repository. To do this, you will need to choose a suitable repository name
for the project. You are not required to choose the name "VTN" for your
repository, but if you do choose "VTN" it has already been pre-approved by
the TSC. If you wish to use another name, please send email to the TSC
requesting approval for the name of your choice. Please understand that
the TSC is not recommending the name "VTN", but rather has pre-approved it
on the assumption that "VTN" is the name you will want to use.

From working with the VTN code during the Inbound Code Review process, the
admin team has had some difficulty in getting the project to fully build in
the Jenkins CI environment. Can you please indicate a contact for Andrew
Grimberg (cc-ed) to work with in troubleshooting and fixing these build
issues?

Thanks Yamabe-san, and congratulations on your contribution to the
OpenDaylight Project.

Phil.
--
Phil Robb
Director - Networking Solutions
The Linux Foundation
(O) 970-229-5949
(M) 970-420-4292
Skype: Phil.Robb
_______________________________________________
TSC mailing list
TSC@...
https://lists.opendaylight.org/mailman/listinfo/tsc


Re: [OpenDaylight Discuss] Call for folks interested in bringingprojects for the first Simultaneous Release

m-kudo@...
 

Ed san,

VTN project (just approved by the TSC :) will join the Simultaneous Release as Offset1.
Regarding the candidate Release Plan, we will send it early next week.

Best regards,
--
M. Kudo

The TSC today asked that we poll the community for those interested in bringing project they would like to see
included in the first Simultaneous Release. The current proposed Simultaneous Release Plan (here:
https://wiki.opendaylight.org/view/Simultaneous_Release:Simultaneous_Release_Plan_2013 )
requires projects, by M1 on July 22, 2013, to:

1) Declare their intention to join the Simultaneous Release
2) Provide their candidate Release Plan

This has implications for folks who are seeking to bring projects to ODL that they would like to
be in the first Simultaneous Release. It takes 2-3 weeks from proposal to approval (to allow
for public comment on the proposal and IPR Review). So if the July 22 M1 date is
approved by the TSC, projects that wished to join the Simultaneous Release would need to
get project proposals in by early July.

Please note: a project does not have to be part of the Simultaneous Release to be an OpenDaylight
project.

On the TSC call it was suggested that we poll the community to see if there are folks intending to bring
projects they would like to be in the first Simultaneous Release to see if that July 22nd date would
represent an impediment to them.

So please speak up :)

Ed

_______________________________________________
Discuss mailing list
Discuss@...
https://lists.opendaylight.org/mailman/listinfo/discuss

201 - 220 of 14323