Extensibility support ?


Madhu Venugopal
 

Can someone please clarify the current status of the extensibility support in openflowplugin and openflowjava ?
and overall end-to-end status ?

I see 10+ open gerrits relating to the extensibility support and am confused on what the current status of it is.
M4 is gone and we are still stuck on getting this support so as to make progress in the ovsdb project.

Thanks,
-Madhu


Abhijit Kumbhare
 

Unfortunately looks like its not completely working. Ed is looking at it while Michal Rehak is out - and is trying to make it work.


On Tue, Aug 5, 2014 at 7:09 PM, Madhu Venugopal <mavenugo@...> wrote:

Can someone please clarify the current status of the extensibility support in openflowplugin and openflowjava ?
and overall end-to-end status ?

I see 10+ open gerrits relating to the extensibility support and am confused on what the current status of it is.
M4 is gone and we are still stuck on getting this support so as to make progress in the ovsdb project.

Thanks,
-Madhu


Madhu Venugopal
 


Abhijit,

Please take a look @ https://wiki.opendaylight.org/view/OpenDaylight_OVSDB:Helium_Release_Plan
and you will notice that we are blocked because of this right off-the-bat for Helium (after M1).

am not sure how this situation should be handled when a project depends on the deliverables from
others and the priorities dont align (certainly not due to lack of communication. We have been requesting
for it from March' 2014).

Should we bring it up in TSC, though I seriously doubt anything useful will come out of it...

Thanks,
-Madhu


On 8/5/14, 7:59 PM, Abhijit Kumbhare wrote:

Unfortunately looks like its not completely working. Ed is looking at it while Michal Rehak is out - and is trying to make it work.


On Tue, Aug 5, 2014 at 7:09 PM, Madhu Venugopal <mavenugo@...> wrote:

Can someone please clarify the current status of the extensibility support in openflowplugin and openflowjava ?
and overall end-to-end status ?

I see 10+ open gerrits relating to the extensibility support and am confused on what the current status of it is.
M4 is gone and we are still stuck on getting this support so as to make progress in the ovsdb project.

Thanks,
-Madhu



Abhijit Kumbhare
 

Yes - I understand that. Unfortunately - the extensibility framework was not going to be ready before M4 (not because of priorities not aligning) - and we thought it was working when Michal pushed the code around 10 days back. Ed is working to help you guys get unblocked - we can discuss the latest status in tomorrow's daily OpenFlow plugin IRC meeting at 7 am Pacific.


On Tue, Aug 5, 2014 at 8:43 PM, Madhu Venugopal <mavenugo@...> wrote:

Abhijit,

Please take a look @ https://wiki.opendaylight.org/view/OpenDaylight_OVSDB:Helium_Release_Plan
and you will notice that we are blocked because of this right off-the-bat for Helium (after M1).

am not sure how this situation should be handled when a project depends on the deliverables from
others and the priorities dont align (certainly not due to lack of communication. We have been requesting
for it from March' 2014).

Should we bring it up in TSC, though I seriously doubt anything useful will come out of it...

Thanks,
-Madhu



On 8/5/14, 7:59 PM, Abhijit Kumbhare wrote:
Unfortunately looks like its not completely working. Ed is looking at it while Michal Rehak is out - and is trying to make it work.


On Tue, Aug 5, 2014 at 7:09 PM, Madhu Venugopal <mavenugo@...> wrote:

Can someone please clarify the current status of the extensibility support in openflowplugin and openflowjava ?
and overall end-to-end status ?

I see 10+ open gerrits relating to the extensibility support and am confused on what the current status of it is.
M4 is gone and we are still stuck on getting this support so as to make progress in the ovsdb project.

Thanks,
-Madhu




Madhu Venugopal
 

When I said priorities I meant the reality that we requested for it as early as March'2014 and we don't have it even now that is more than 12 weeks. I think it is because it was prioritized for M4 in openflow projects.  Also we are right next door to M5 code freeze now with no end in sight. 

-Madhu

On Aug 5, 2014, at 9:33 PM, Abhijit Kumbhare <abhijitkoss@...> wrote:

Yes - I understand that. Unfortunately - the extensibility framework was not going to be ready before M4 (not because of priorities not aligning) - and we thought it was working when Michal pushed the code around 10 days back. Ed is working to help you guys get unblocked - we can discuss the latest status in tomorrow's daily OpenFlow plugin IRC meeting at 7 am Pacifi c.


On Tue, Aug 5, 2014 at 8:43 PM, Madhu Venugopal <mavenugo@...> wrote:

Abhijit,

Please take a look @ https://wiki.opendaylight.org/view/OpenDaylight_OVSDB:Helium_Release_Plan
and you will notice that we are blocked because of this right off-the-bat for Helium (after M1).

am not sure how this situation should be handled when a project depends on the deliverables from
others and the priorities dont align (certainly not due to lack of communication. We have been requesting
for it from March' 2014).

Should we bring it up in TSC, though I seriously doubt anything useful will come out of it...

Thanks,
-Madhu



On 8/5/14, 7:59 PM, Abhijit Kumbhare wrote:
Unfortunately looks like its not completely working. Ed is looking at it while Michal Rehak is out - and is trying to make it work.


On Tue, Aug 5, 2014 at 7:09 PM, Madhu Venugopal <mavenugo@...> wrote:

Can someone please clarify the current status of the extensibility support in openflowplugin and openflowjava ?
and overall end-to-end status ?

I see 10+ open gerrits relating to the extensibility support and am confused on what the current status of it is.
M4 is gone and we are still stuck on getting this support so as to make progress in the ovsdb project.

Thanks,
-Madhu




Abhijit Kumbhare
 

Well - it was not put to M4 because we wanted to slow you guys down - but rather that's what we thought could be achieved. The problem is not that it was slated for M4 but that its not quite ready at M4 - which we apologize for. Hopefully we can fix it soon enough.


On Tue, Aug 5, 2014 at 9:55 PM, Madhu Venugopal <mavenugo@...> wrote:
When I said priorities I meant the reality that we requested for it as early as March'2014 and we don't have it even now that is more than 12 weeks. I think it is because it was prioritized for M4 in openflow projects.  Also we are right next door to M5 code freeze now with no end in sight. 

-Madhu

On Aug 5, 2014, at 9:33 PM, Abhijit Kumbhare <abhijitkoss@...> wrote:

Yes - I understand that. Unfortunately - the extensibility framework was not going to be ready before M4 (not because of priorities not aligning) - and we thought it was working when Michal pushed the code around 10 days back. Ed is working to help you guys get unblocked - we can discuss the latest status in tomorrow's daily OpenFlow plugin IRC meeting at 7 am Pacific.


On Tue, Aug 5, 2014 at 8:43 PM, Madhu Venugopal <mavenugo@...> wrote:

Abhijit,

Please take a look @ https://wiki.opendaylight.org/view/OpenDaylight_OVSDB:Helium_Release_Plan
and you will notice that we are blocked because of this right off-the-bat for Helium (after M1).

am not sure how this situation should be handled when a project depends on the deliverables from
others and the priorities dont align (certainly not due to lack of communication. We have been requesting
for it from March' 2014).

Should we bring it up in TSC, though I seriously doubt anything useful will come out of it...

Thanks,
-Madhu



On 8/5/14, 7:59 PM, Abhijit Kumbhare wrote:
Unfortunately looks like its not completely working. Ed is looking at it while Michal Rehak is out - and is trying to make it work.


On Tue, Aug 5, 2014 at 7:09 PM, Madhu Venugopal <mavenugo@...> wrote:

Can someone please clarify the current status of the extensibility support in openflowplugin and openflowjava ?
and overall end-to-end status ?

I see 10+ open gerrits relating to the extensibility support and am confused on what the current status of it is.
M4 is gone and we are still stuck on getting this support so as to make progress in the ovsdb project.

Thanks,
-Madhu