integration-dev@lists.opendaylight.org | Adding ovsdb.neutron bundle to SP Edition

Home Messages Hashtags Subgroups

Date Date 1 - 7 of 7

Adding ovsdb.neutron bundle to SP Edition

Madhu Venugopal #1013 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 https://git.opendaylight.org/gerrit/#/c/390/ <version>0.1.2</version> </dependency> + <!--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. Thanks, Madhu
More All Messages By This Member
Ed Warnicke (eaw) <eaw@...> #1080 Madhu, Here’s a distro that is precisely ServiceProvider plus ovsdb.neutron: https://git.opendaylight.org/gerrit/6908 Ed toggle quoted message Show quoted text 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 https://git.opendaylight.org/gerrit/#/c/390/ <version>0.1.2</version> </dependency> + <!--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. Thanks, Madhu _______________________________________________ integration-dev mailing list integration-dev@... https://lists.opendaylight.org/mailman/listinfo/integration-dev
More All Messages By This Member
Luis Gomez #1081 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: https://lists.opendaylight.org/pipermail/discuss/2014-May/002320.html BR/Luis toggle quoted message Show quoted text On May 12, 2014, at 10:46 AM, Ed Warnicke (eaw) <eaw@...> wrote: Madhu, Here’s a distro that is precisely ServiceProvider plus ovsdb.neutron: https://git.opendaylight.org/gerrit/6908 Ed 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 https://git.opendaylight.org/gerrit/#/c/390/ <version>0.1.2</version> </dependency> + <!--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. Thanks, Madhu _______________________________________________ integration-dev mailing list integration-dev@... https://lists.opendaylight.org/mailman/listinfo/integration-dev _______________________________________________ integration-dev mailing list integration-dev@... https://lists.opendaylight.org/mailman/listinfo/integration-dev
More All Messages By This Member
Madhu Venugopal #1087 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 :-) -Madhu toggle quoted message Show quoted text 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: https://lists.opendaylight.org/pipermail/discuss/2014-May/002320.html BR/Luis On May 12, 2014, at 10:46 AM, Ed Warnicke (eaw) <eaw@...> wrote: Madhu, Here’s a distro that is precisely ServiceProvider plus ovsdb.neutron: https://git.opendaylight.org/gerrit/6908 Ed 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 https://git.opendaylight.org/gerrit/#/c/390/ <version>0.1.2</version> </dependency> + <!--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. Thanks, Madhu _______________________________________________ integration-dev mailing list integration-dev@... https://lists.opendaylight.org/mailman/listinfo/integration-dev _______________________________________________ integration-dev mailing list integration-dev@... https://lists.opendaylight.org/mailman/listinfo/integration-dev
More All Messages By This Member
Luis Gomez #1091 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)? BR/Luis toggle quoted message Show quoted text 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 :-) -Madhu 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: https://lists.opendaylight.org/pipermail/discuss/2014-May/002320.html BR/Luis On May 12, 2014, at 10:46 AM, Ed Warnicke (eaw) <eaw@...> wrote: Madhu, Here’s a distro that is precisely ServiceProvider plus ovsdb.neutron: https://git.opendaylight.org/gerrit/6908 Ed 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 https://git.opendaylight.org/gerrit/#/c/390/ <version>0.1.2</version> </dependency> + <!--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. Thanks, Madhu _______________________________________________ integration-dev mailing list integration-dev@... https://lists.opendaylight.org/mailman/listinfo/integration-dev _______________________________________________ integration-dev mailing list integration-dev@... https://lists.opendaylight.org/mailman/listinfo/integration-dev
More All Messages By This Member
Ed Warnicke (eaw) <eaw@...> #1092 Luis, I think we already addressed this question last week and decided that the proper mechanism for considering such things was the Helium Release Vehicle process as already outlined in the Helium Release plan (as you noted) or the cutting of a custom distro in integration (which could then be tested with the integration infra if that made sense). I think this is the... third time this question has been brought to the TSC now... and I believe we have been clearly consistent about it the previous two times. Ed P.S. Per our request I have pushed a new patchset moving it to distributions/extra/ https://git.opendaylight.org/gerrit/#/c/6908/2 ________________________________________ From: Luis Gomez [ecelgp@...] Sent: Wednesday, May 14, 2014 3:25 PM To: tsc@... Cc: Ed Warnicke (eaw); Madhu Venugopal; integration-dev@... Subject: Re: [integration-dev] Adding ovsdb.neutron bundle to SP Edition 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)? BR/Luis 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 :-) -Madhu 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: https://lists.opendaylight.org/pipermail/discuss/2014-May/002320.html BR/Luis On May 12, 2014, at 10:46 AM, Ed Warnicke (eaw) <eaw@...> wrote: Madhu, Here’s a distro that is precisely ServiceProvider plus ovsdb.neutron: https://git.opendaylight.org/gerrit/6908 Ed 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 https://git.opendaylight.org/gerrit/#/c/390/ <version>0.1.2</version> </dependency> + <!--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. Thanks, Madhu _______________________________________________ integration-dev mailing list integration-dev@... https://lists.opendaylight.org/mailman/listinfo/integration-dev _______________________________________________ integration-dev mailing list integration-dev@... https://lists.opendaylight.org/mailman/listinfo/integration-dev
More All Messages By This Member
Luis Gomez #1095 Sorry Ed, I might not have well understood this decision then because after the call I was writing a proposal where I said changes to current “official” distributions will be addressed to TSC, should I remove that and say instead changes to “official” distributions are only considered during release vehicle process (one time every release)? Thanks/Luis toggle quoted message Show quoted text On May 14, 2014, at 2:48 PM, Ed Warnicke (eaw) <eaw@...> wrote: Luis, I think we already addressed this question last week and decided that the proper mechanism for considering such things was the Helium Release Vehicle process as already outlined in the Helium Release plan (as you noted) or the cutting of a custom distro in integration (which could then be tested with the integration infra if that made sense). I think this is the... third time this question has been brought to the TSC now... and I believe we have been clearly consistent about it the previous two times. Ed P.S. Per our request I have pushed a new patchset moving it to distributions/extra/ https://git.opendaylight.org/gerrit/#/c/6908/2 ________________________________________ From: Luis Gomez [ecelgp@...] Sent: Wednesday, May 14, 2014 3:25 PM To: tsc@... Cc: Ed Warnicke (eaw); Madhu Venugopal; integration-dev@... Subject: Re: [integration-dev] Adding ovsdb.neutron bundle to SP Edition 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)? BR/Luis 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 :-) -Madhu 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: https://lists.opendaylight.org/pipermail/discuss/2014-May/002320.html BR/Luis On May 12, 2014, at 10:46 AM, Ed Warnicke (eaw) <eaw@...> wrote: Madhu, Here’s a distro that is precisely ServiceProvider plus ovsdb.neutron: https://git.opendaylight.org/gerrit/6908 Ed 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 https://git.opendaylight.org/gerrit/#/c/390/ <version>0.1.2</version> </dependency> + <!--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. Thanks, Madhu _______________________________________________ integration-dev mailing list integration-dev@... https://lists.opendaylight.org/mailman/listinfo/integration-dev _______________________________________________ integration-dev mailing list integration-dev@... https://lists.opendaylight.org/mailman/listinfo/integration-dev
More All Messages By This Member

1 - 7 of 7

1

Previous Topic Next Topic

Home Hashtags Subgroups Terms