1. Topics
  2. [release] Weather report: Unmerged Patch for projects to test OpenFlow Plugin default design to Lithium

[release] Weather report: Unmerged Patch for projects to test OpenFlow Plugin default design to Lithium

Gao Kai <gaok12@...>
 

We might want to test OpenFlow Plugin as well and declare our dependency on that too from the Boron release.


-------- Forwarded Message --------
Subject: [release] Weather report: Unmerged Patch for projects to test OpenFlow Plugin default design to Lithium
Date: Thu, 10 Mar 2016 21:53:48 -0800
From: Abhijit Kumbhare <abhijitkoss@...>
To: Release <release@...>, faas-dev@..., GroupBasedPolicy-dev@... <groupbasedpolicy-dev@...>, l2switch-dev@... <l2switch-dev@...>, lacp-dev@..., nemo-dev@..., nic-dev@... <nic-dev@...>, Sdninterfaceapp-dev@..., netide-dev@..., <ovsdb-dev@...> <ovsdb-dev@...>, sfc-dev@... <sfc-dev@...>, vpnservice-dev@..., vtn-dev@... <vtn-dev@...>


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



?
Attached Message Part

1 - 1 of 1