Hi Suchi, happy new year.

 

I have a question regarding the system test for Affinity: We will be testing Affinity application during SP edition system test, however for Virtualization edition given that we have 3 deliveries: VTN, OVSDB and OpenDove and as far as I understand none of them actually supports or interacts with Affinity (at least in this first release), does it make sense to include Affinity test cases in any of these 3 editions system test? also for release understanding: if a user wants to work with Affinity application, which ODL edition would you recommend to use?

 

Thanks/Luis

 

Hi Luis,

Happy New Year to you! 

I've made several of the changes that Anees and others recommended, and have a version that does not rely exclusively on l2agent. 

However: 

 (1) Yes, it is true that affinity API does not have any meaningful integration with other projects in the virt. edn. 

 (2) The dependency in OSGI is still there, since that seems to be the only mechanism for service discovery in controller/OSGi. 

 

I do think it is useful to have affinity project in the base edition -- we would certainly welcome any air time this API can get. I only have script examples, no formal APIdocs. 

These are in the scripts/ directory in the project repo. 

Suchi

On Mon, Jan 6, 2014 at 3:38 PM, Luis Gomez <luis.gomez@...> wrote:

Hi Suchi, happy new year.

 

I have a question regarding the system test for Affinity: We will be testing Affinity application during SP edition system test, however for Virtualization edition given that we have 3 deliveries: VTN, OVSDB and OpenDove and as far as I understand none of them actually supports or interacts with Affinity (at least in this first release), does it make sense to include Affinity test cases in any of these 3 editions system test? also for release understanding: if a user wants to work with Affinity application, which ODL edition would you recommend to use?

 

Thanks/Luis

 

I forgot to mention that the affinity version to be used is 0.4.1 (not 0.4.0) as currently listed in the integration repo. 

I am on tap to push a small change to correct this in the affinity repo. I'll get this done by end of day Tuesday, or if you need it earlier let me know. 

On Mon, Jan 6, 2014 at 4:02 PM, Suchi Raman <suchi.raman@...> wrote:

Hi Luis,

Happy New Year to you! 

I've made several of the changes that Anees and others recommended, and have a version that does not rely exclusively on l2agent. 

However: 

 (1) Yes, it is true that affinity API does not have any meaningful integration with other projects in the virt. edn. 

 (2) The dependency in OSGI is still there, since that seems to be the only mechanism for service discovery in controller/OSGi. 

 

I do think it is useful to have affinity project in the base edition -- we would certainly welcome any air time this API can get. I only have script examples, no formal APIdocs. 

These are in the scripts/ directory in the project repo. 

Suchi

On Mon, Jan 6, 2014 at 3:38 PM, Luis Gomez <luis.gomez@...> wrote:

Hi Suchi, happy new year.

 

I have a question regarding the system test for Affinity: We will be testing Affinity application during SP edition system test, however for Virtualization edition given that we have 3 deliveries: VTN, OVSDB and OpenDove and as far as I understand none of them actually supports or interacts with Affinity (at least in this first release), does it make sense to include Affinity test cases in any of these 3 editions system test? also for release understanding: if a user wants to work with Affinity application, which ODL edition would you recommend to use?

 

Thanks/Luis

 

Hi Suchi, I have merged 4051 but please fix 4052 as I think you changed the wrong project in the Virtualization POM (OpenDove instead of Affinity)

 

BR/Luis

 

 

From: Suchi Raman [mailto:suchi.raman@...]
Sent: Tuesday, January 07, 2014 7:07 AM
To: Luis Gomez; Madhu Venugopal
Cc: Nils Swart; integration-dev@...
Subject: Re: Affinity test in Virt edition

 

These are now in: 

http://git.opendaylight.org/gerrit/4051

http://git.opendaylight.org/gerrit/4052

 

Could either Luis or Madhu merge these after review. 

 

Thanks

Suchi

 

 

On Mon, Jan 6, 2014 at 5:14 PM, Suchi Raman <suchi.raman@...> wrote:

I forgot to mention that the affinity version to be used is 0.4.1 (not 0.4.0) as currently listed in the integration repo. 

 

I am on tap to push a small change to correct this in the affinity repo. I'll get this done by end of day Tuesday, or if you need it earlier let me know. 

 

On Mon, Jan 6, 2014 at 4:02 PM, Suchi Raman <suchi.raman@...> wrote:

Hi Luis,

 

Happy New Year to you! 

 

I've made several of the changes that Anees and others recommended, and have a version that does not rely exclusively on l2agent. 

 

However: 

 

 (1) Yes, it is true that affinity API does not have any meaningful integration with other projects in the virt. edn. 

 (2) The dependency in OSGI is still there, since that seems to be the only mechanism for service discovery in controller/OSGi. 

 

I do think it is useful to have affinity project in the base edition -- we would certainly welcome any air time this API can get. I only have script examples, no formal APIdocs. 

These are in the scripts/ directory in the project repo. 

 

Suchi

 

 

On Mon, Jan 6, 2014 at 3:38 PM, Luis Gomez <luis.gomez@...> wrote:

Hi Suchi, happy new year.

 

I have a question regarding the system test for Affinity: We will be testing Affinity application during SP edition system test, however for Virtualization edition given that we have 3 deliveries: VTN, OVSDB and OpenDove and as far as I understand none of them actually supports or interacts with Affinity (at least in this first release), does it make sense to include Affinity test cases in any of these 3 editions system test? also for release understanding: if a user wants to work with Affinity application, which ODL edition would you recommend to use?

 

Thanks/Luis