Re: Adding ovsdb.neutron bundle to SP Edition

Luis Gomez

Hi TSC members,

We are currently in a transition stage where we have passed Hydrogen release but have not decided yet about Helium editions. I think Madhu’s proposal to change SP edition at this moment poses another more global question to TSC: Can we change current “official” distributions components in master to temporarily fulfill developer/end-user/customer needs or should we wait until TSC decides on release vehicles for Helium by M3 (7/7/2014)?


On May 14, 2014, at 12:41 AM, Madhu Venugopal <mavenugo@...> wrote:

Thanks Luis & Yes, as explained in my original email & discussed in detail during TSC, the request was to include the ovsdb in SP edition.
If the need was to create a new "extra" edition, I hope I know how to create a new distribution :-)


On 5/12/14, 12:05 PM, Luis Gomez wrote:
Hi Ed, I thought this request was to modify the existing SP edition instead of creating a new one. New editions that are not “official” should go under “extra” folder as we discussed here:


On May 12, 2014, at 10:46 AM, Ed Warnicke (eaw) <eaw@...> wrote:

Here’s a distro that is precisely ServiceProvider plus ovsdb.neutron:

On May 2, 2014, at 2:04 PM, Madhu Venugopal <mavenugo@...> wrote:

Hi TSC members,

Post Hydrogen, we have received a few requests from the end-user/customer community to include the ovsdb.neutron
functionality into the SP edition.

am sending this email based on the discussion we had in TSC meeting (05/01/2014) & seeking your approval.

Thanks to the modular nature of our projects, the following fix to the integration project will take care of it
with no negative impact to any of the SP edition functionality, but will enhance it with the requested functionality.

--- a/distributions/serviceprovider/pom.xml
+++ b/distributions/serviceprovider/pom.xml
@@ -444,6 +444,13 @@ see

+ <!--OVSDB neutron-->
+ <dependency>
+ <groupId>org.opendaylight.ovsdb</groupId>
+ <artifactId>ovsdb.neutron</artifactId>
+ <version>0.5.1-SNAPSHOT</version>
+ </dependency>

Based on your input, I will push the change to integration project.

integration-dev mailing list
integration-dev mailing list

Join { to automatically receive all group messages.