Hi Abhijit, FaaS team has tested out the “Li” Migration. The only thing we found out is that after the FaaS features are installed, it takes about 20 secs to see all the registered openflow nodes some how. Based on our analysis it probably is NOT related to openflow plugin, we will figure it out later. So for FaaS, it is no blocking issue found .
Thanks Xingjun FaaS PTL From: [email protected] [mailto:[email protected]] On Behalf Of Abhijit Kumbhare Sent: Monday, April 04, 2016 2:41 PM To: Colin Dixon; Release; <[email protected]> Cc: [email protected]; [email protected]; [email protected]; An Ho; <[email protected]>; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected]; [email protected] Subject: [groupbasedpolicy-dev] PLEASE READ: OpenFlow Plugin default design migration to Lithium Hi folks, Since in today's TWS there were not many project leads and committers of the dependent projects attending - the action item for me was to send an email summarizing the plan for migration and send it to release & discuss. So I would like to provide (repeat) the rough plan: 1. Have the projects test out the new design and report issues. The OpenFlow Plugin release plan would be dependent on that. The already extended deadline for this was April 7 so that OFP has inputs to decide what major issues need to be addressed - and be incorporated in the OpenFlow Plugin release plan (due April 21). * The issues should be filed as blocker bugs for OpenFlow Plugin with the title starting with the string "Li Migration: ". This will make it easy to search for the issues in bugzilla. * So far we have received reports from VTN (3 issues - 4671, 5432 & 5602), GBP (no blocking issues reported). In the past L2 switch had responded saying they already support the Lithium design natively. Need reports from the remaining projects & I think we will need to track these in the Boron spreadsheet. 1. The OFP target for fixing the issues and actually changing the default plugin would likely be dependent offset 2 projects M2 / OpenFlow Plugin M3 - depending on the complexity of the issues identified. * I have reflected this in the OpenFlow Plugin release plan under M3. Again please be aware of this plan and please report the corresponding issues as soon as possible (deadline April 7). We can discuss the issues in the next week TWS call. I will try to reach out individually to you all the next few days. Thanks, Abhijit On Thu, Mar 24, 2016 at 9:02 AM, Colin Dixon <[email protected]<mailto:[email protected]>> wrote: I've added it here: https://wiki.opendaylight.org/view/Tech_Work_Stream:Main#Upcoming_Meeting_Agendas --Colin On Thu, Mar 24, 2016 at 11:34 AM, Abhijit Kumbhare <[email protected]<mailto:[email protected]>> wrote: Sounds good to me. On Thu, Mar 24, 2016 at 7:53 AM, An Ho <[email protected]<mailto:[email protected]>> wrote: Could we schedule a meeting during TWS for projects affected by OpenFlowPlugin to meet on 4/4 for dependant projects to share their feedback or concerns? Dependant projects should provide feedback either by email or at the meeting. I will start reaching out to projects to get representatives to the meeting. Best Regards, An Ho From: Abhijit Kumbhare [mailto:[email protected]<mailto:[email protected]>] Sent: Wednesday, March 23, 2016 10:45 AM To: Colin Dixon; An Ho Cc: Release; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: Re: [L2switch-dev] Weather report: Unmerged Patch for projects to test OpenFlow Plugin default design to Lithium Folks, The OpenFlow Plugin project has not received any reports from you (the dependent projects) about using this patch to try and test the issues. Have you had a chance to try out the patch? And you have not run into issues? Or is it that you have not tried it at all? I suspect it is the latter. In order to get more realistic feedback /identify major issues after you folks have tried the new plugin & to incorporate that into the OpenFlow Plugin release plan - we can extend the deadline for the feedback by a bit - but not a lot. Working backwards from our M2 date (April 21) when we have to finalize our release plan - my guess is we would need the feedback by at least two weeks before to incorporate any changes/requirements to our release plan. That would put it to April 7. Please sure that the feedback/major issues that you have identified with the Lithium design is available by April 7. An - can we have the release IRC meeting next Wednesday the usual time? Thanks, Abhijit On Mon, Mar 14, 2016 at 8:15 AM, Abhijit Kumbhare <[email protected]<mailto:[email protected]>> wrote: Yes. We should also discuss this in the next IRC release meeting. On Mon, Mar 14, 2016 at 6:37 AM, Colin Dixon <[email protected]<mailto:[email protected]>> wrote: We should probably add this to the milestone readouts for Beryllium. --Colin On Friday, March 11, 2016, Abhijit Kumbhare <[email protected]<mailto:[email protected]>> wrote: Hi folks, We need all the dependent projects of OpenFlow Plugin (OFP) to move to the Lithium design for the Boron release. To help in this process OpenFlow Plugin has created an unmerged patch which swaps the default design to the new Lithium design. The patch is: https://git.opendaylight.org/gerrit/#/c/35892. The purpose of this patch is for projects to identify issues in the migration and help OpenFlow Plugin fix them. To use this patch projects should: 1. clone the openflowplugin and then checkout this patch it locally and build 2. t est their project with the locally swapped new plugin We would like this activity to identify issues to conclude in the next 2 weeks or so (say March 24 - which happens to be the current offset 2 projects M1 date in the provisional traditional release plan ). That way OpenFlow Plugin can factor the gaps needed to fix in the OpenFlow Plugin release plan which is due by M2 for us (current date in the provisional traditional release plan for OFP is April 21). The OFP target for fixing the issues and actually changing the default plugin would likely be either OFP M2 or M3 - depending on the complexity of the issues identified. The issues which cannot be worked around and blocking development of the project should be raised as blocker issues on OpenFlow Plugin. Again as I mentioned - please try this patch out and let us know the issues by March 24. If there is an issue in providing this info - please let us know as well. Thanks, Abhijit
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
