|
Re: my perspective on where we are with the single controller code base issue
Dave (and other members of the community) -
The folks that work here at BSN are here to make Daylight as successful as we can, but i) we owe transparency about our over-arching concern (that we
Dave (and other members of the community) -
The folks that work here at BSN are here to make Daylight as successful as we can, but i) we owe transparency about our over-arching concern (that we
|
By
Kyle Forster
·
#168
·
|
|
Invitation: OpenDaylight TSC Meeting @ Weekly from 11am to 1pm on Thursday (probb@linuxfoundation.org)
more details »
OpenDaylight TSC Meeting
Meeting URL: https://meetings.webex.com/collabs/meetings/join?uuid=MA3SRND964PIX06V2LS3SXX3RE-9VIB
Access Information
Meeting number: 194 548 370
Meeting
more details »
OpenDaylight TSC Meeting
Meeting URL: https://meetings.webex.com/collabs/meetings/join?uuid=MA3SRND964PIX06V2LS3SXX3RE-9VIB
Access Information
Meeting number: 194 548 370
Meeting
|
By
Phil Robb
·
#165
·
|
|
Canceled Event: OpenDaylight TSC Meeting @ Weekly from 11am to 12pm on Thursday from Thu Apr 18 to Thu May 30 (probb@linuxfoundation.org)
This event has been canceled and removed from your calendar.
OpenDaylight TSC Meeting
OpenDaylight Technical Steering Committee meeting.
Please hold this time for the weekly OpenDaylight TSC
This event has been canceled and removed from your calendar.
OpenDaylight TSC Meeting
OpenDaylight Technical Steering Committee meeting.
Please hold this time for the weekly OpenDaylight TSC
|
By
Phil Robb
·
#164
·
|
|
Changes to the OpenDaylight TSC Meeting Invitation
Hello Everyone:
To provide a clean change to the TSC meeting invitation as we move from 1 hour to 2 hour meetings, I will be canceling the original meeting, and then sending a new invitation for the
Hello Everyone:
To provide a clean change to the TSC meeting invitation as we move from 1 hour to 2 hour meetings, I will be canceling the original meeting, and then sending a new invitation for the
|
By
Phil Robb
·
#166
·
|
|
Re: my perspective on where we are with the single controller code base issue
BTW, it has been pointed out that I mis-attributed the IOCTL idea to
Chris. That was my mistake. That said, the point I was making still
holds, namely, that there exist some ideas (and there will be
BTW, it has been pointed out that I mis-attributed the IOCTL idea to
Chris. That was my mistake. That said, the point I was making still
holds, namely, that there exist some ideas (and there will be
|
By
David Meyer <dmm@...>
·
#163
·
|
|
my perspective on where we are with the single controller code base issue
All,
As you know today (05.14.2013) was the day on which I wanted to
have the single controller code base issue resolved. What I had
said is that if we couldn't get the projects to agree on a
All,
As you know today (05.14.2013) was the day on which I wanted to
have the single controller code base issue resolved. What I had
said is that if we couldn't get the projects to agree on a
|
By
David Meyer <dmm@...>
·
#162
·
|
|
resolving the controller project/code base issues: process going forward
Folks,
As TSC members will recall, I set a date of 05/13/2013 to have
proposals for the single controller project on the table, and Rob
asked a few questions about this on today's TSC call. Now,
Folks,
As TSC members will recall, I set a date of 05/13/2013 to have
proposals for the single controller project on the table, and Rob
asked a few questions about this on today's TSC call. Now,
|
By
David Meyer <dmm@...>
·
#161
·
|
|
Re: Revised merged controller proposal
* Rob Sherwood (rob.sherwood@...) wrote:
No. Discuss is that way -->> discuss@...
* Rob Sherwood (rob.sherwood@...) wrote:
No. Discuss is that way -->> discuss@...
|
By
Chris Wright <chrisw@...>
·
#160
·
|
|
Logistics for today's call
Hello TSC Members:
Here is the meeting access information for today's meeting. This is the same information currently on the wiki:
When it's time, start the meeting from
Hello TSC Members:
Here is the meeting access information for today's meeting. This is the same information currently on the wiki:
When it's time, start the meeting from
|
By
Phil Robb
·
#159
·
|
|
Re: Revised merged controller proposal
And Rob, can you post to discuss? Thnx, --dmm
And Rob, can you post to discuss? Thnx, --dmm
|
By
David Meyer <dmm@...>
·
#158
·
|
|
Re: Revised merged controller proposal
OK, I think the wiki is now fixed (thanks as always to Andrew Grimberg's prompt and expert responses).
Rob, can you try to upload the Layered API proposal again?
Phil.
OK, I think the wiki is now fixed (thanks as always to Andrew Grimberg's prompt and expert responses).
Rob, can you try to upload the Layered API proposal again?
Phil.
|
By
Phil Robb
·
#157
·
|
|
Re: Revised merged controller proposal
Thanks Phil. --dmm
By
David Meyer <dmm@...>
·
#156
·
|
|
Re: Revised merged controller proposal
The proposal was waiting on moderator approval this morning and I released it to both Discuss and TSC lists a little while ago.
The wiki issue seems to be a bug I'm working on right now. The file
The proposal was waiting on moderator approval this morning and I released it to both Discuss and TSC lists a little while ago.
The wiki issue seems to be a bug I'm working on right now. The file
|
By
Phil Robb
·
#155
·
|
|
Re: Revised merged controller proposal
Actually, now I see you only sent your proposal to tsc@ (unless I
can't keep track of what is cross posted where, which has non-zero
probability). Any reason why it can't go to discuss?
--dmm
Actually, now I see you only sent your proposal to tsc@ (unless I
can't keep track of what is cross posted where, which has non-zero
probability). Any reason why it can't go to discuss?
--dmm
|
By
David Meyer <dmm@...>
·
#154
·
|
|
Re: Revised merged controller proposal
BTW, I updated the agenda to give you a slot; I'm thinking now I'm
going to push everything else off so we can discuss moving forward.
Also, thank you for posting your pdf to the discuss list (as you
BTW, I updated the agenda to give you a slot; I'm thinking now I'm
going to push everything else off so we can discuss moving forward.
Also, thank you for posting your pdf to the discuss list (as you
|
By
David Meyer <dmm@...>
·
#153
·
|
|
Re: [OpenDaylight Discuss] Next Hackfest Dates
Yea, I'm online now this morning and I'll get all of this moving guys.
Phil.
Yea, I'm online now this morning and I'll get all of this moving guys.
Phil.
|
By
Phil Robb
·
#150
·
|
|
Re: Revised merged controller proposal
Sure. Let me work on the agenda this AM. --dmm
Sure. Let me work on the agenda this AM. --dmm
|
By
David Meyer <dmm@...>
·
#149
·
|
|
Re: [OpenDaylight Discuss] Next Hackfest Dates
Rob, I see that you tried to add a pdf to the "layered API proposal" that didn't make it (looks like size limitations). Can you work with Phil to get this posted?
Thnx,
--dmm
Rob, I see that you tried to add a pdf to the "layered API proposal" that didn't make it (looks like size limitations). Can you work with Phil to get this posted?
Thnx,
--dmm
|
By
David Meyer <dmm@...>
·
#148
·
|
|
Re: Revised merged controller proposal
On May 9, 2013, at 8:43 AM, "Rob Sherwood" <rob.sherwood@...> wrote:
I'd second that request. lets spend as much time on this as we need to discuss today.
Tom
On May 9, 2013, at 8:43 AM, "Rob Sherwood" <rob.sherwood@...> wrote:
I'd second that request. lets spend as much time on this as we need to discuss today.
Tom
|
By
Thomas Nadeau <tnadeau@...>
·
#147
·
|
|
Revised merged controller proposal
[resending without attachment -- can we please bump up the attachment file limit to something reasonable?]
After looking in depth into the implications of Colin and Dave's proposal, we ran into a
[resending without attachment -- can we please bump up the attachment file limit to something reasonable?]
After looking in depth into the implications of Colin and Dave's proposal, we ran into a
|
By
Rob Sherwood
·
#146
·
|