z.archive.alto-dev@lists.opendaylight.org | [release] Boron autorelease fails: alto, l2switch, blueprint

Home Messages Hashtags Subgroups

This group is locked. No changes can be made to the group while it is locked.

Date Date 1 - 3 of 3

[release] Boron autorelease fails: alto, l2switch, blueprint

Gao Kai <gaok12@...> #381 Vratko, The current patch might do now, at least for Boron. Currently we can work around it but in the long run we may still need to enable reactive routing. Actually we don't care much about ARP packets so it's OK to flood them. But if I'm not mistaken when that option is enabled, l2switch will flood other packets as well (see [1]). It will be great to know how we can change the options automatically, so we may disable flooding when our module is installed and re-enable it when removed. Thanks! Regards, Kai [1] https://github.com/opendaylight/l2switch/blob/fc88da4024fa83b440b4176f90d88b077052c20d/arphandler/src/main/java/org/opendaylight/l2switch/arphandler/core/ProactiveFloodFlowWriter.java On 04/07/16 23:29, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) wrote: toggle quoted message Show quoted text L2switch has been converted to blueprint [0], so *-config artifacts are no longer defined. Alto was depending on them. Possible fix for the autorelease build: [1]. But even after that fix, the new value [2] for is-proactive-flood-mode will NOT get applied. Is there a way for downstream feature to override the default value [3]? Vratko. [0] https://git.opendaylight.org/gerrit/40707 [1] https://git.opendaylight.org/gerrit/41285 [2] https://git.opendaylight.org/gerrit/gitweb?p=alto.git;a=blob;f=alto-extensions/simple-pce/network-tracker/config/src/main/config/default-config.xml;h=954c068ca890942e061de81fd6eb7ff4fcbcd69b;hb=refs/heads/master#l28 [3] https://git.opendaylight.org/gerrit/#/c/40707/3/arphandler/src/main/yang/arp-handler-config.yang@54 _______________________________________________ release mailing list release@... https://lists.opendaylight.org/mailman/listinfo/release

Thanh Ha <thanh.ha@...> #382 What's the plan here? the alto patch is still unapplied and boron still broken. Regards, Thanh toggle quoted message Show quoted text On 4 July 2016 at 12:19, Gao Kai <gaok12@...> wrote: Vratko, The current patch might do now, at least for Boron. Currently we can work around it but in the long run we may still need to enable reactive routing. Actually we don't care much about ARP packets so it's OK to flood them. But if I'm not mistaken when that option is enabled, l2switch will flood other packets as well (see [1]). It will be great to know how we can change the options automatically, so we may disable flooding when our module is installed and re-enable it when removed. Thanks! Regards, Kai [1] https://github.com/opendaylight/l2switch/blob/fc88da4024fa83b440b4176f90d88b077052c20d/arphandler/src/main/java/org/opendaylight/l2switch/arphandler/core/ProactiveFloodFlowWriter.java On 04/07/16 23:29, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) wrote: L2switch has been converted to blueprint [0], so *-config artifacts are no longer defined. Alto was depending on them. Possible fix for the autorelease build: [1]. But even after that fix, the new value [2] for is-proactive-flood-mode will NOT get applied. Is there a way for downstream feature to override the default value [3]? Vratko. [0] https://git.opendaylight.org/gerrit/40707 [1] https://git.opendaylight.org/gerrit/41285 [2] https://git.opendaylight.org/gerrit/gitweb?p=alto.git;a=blob;f=alto-extensions/simple-pce/network-tracker/config/src/main/config/default-config.xml;h=954c068ca890942e061de81fd6eb7ff4fcbcd69b;hb=refs/heads/master#l28 [3] https://git.opendaylight.org/gerrit/#/c/40707/3/arphandler/src/main/yang/arp-handler-config.yang@54 _______________________________________________ release mailing list release@... https://lists.opendaylight.org/mailman/listinfo/release _______________________________________________ release mailing list release@... https://lists.opendaylight.org/mailman/listinfo/release

Gao Kai #383 Thanh, I've contacted the committers to accept the patch. It should be done within minutes. Sorry for the trouble. Regards, Kai On 06/07/16 22:08, Thanh Ha wrote: toggle quoted message Show quoted text What's the plan here? the alto patch is still unapplied and boron still broken. Regards, Thanh On 4 July 2016 at 12:19, Gao Kai <gaok12@...> wrote: Vratko, The current patch might do now, at least for Boron. Currently we can work around it but in the long run we may still need to enable reactive routing. Actually we don't care much about ARP packets so it's OK to flood them. But if I'm not mistaken when that option is enabled, l2switch will flood other packets as well (see [1]). It will be great to know how we can change the options automatically, so we may disable flooding when our module is installed and re-enable it when removed. Thanks! Regards, Kai [1] https://github.com/opendaylight/l2switch/blob/fc88da4024fa83b440b4176f90d88b077052c20d/arphandler/src/main/java/org/opendaylight/l2switch/arphandler/core/ProactiveFloodFlowWriter.java On 04/07/16 23:29, Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) wrote: L2switch has been converted to blueprint [0], so *-config artifacts are no longer defined. Alto was depending on them. Possible fix for the autorelease build: [1]. But even after that fix, the new value [2] for is-proactive-flood-mode will NOT get applied. Is there a way for downstream feature to override the default value [3]? Vratko. [0] https://git.opendaylight.org/gerrit/40707 [1] https://git.opendaylight.org/gerrit/41285 [2] https://git.opendaylight.org/gerrit/gitweb?p=alto.git;a=blob;f=alto-extensions/simple-pce/network-tracker/config/src/main/config/default-config.xml;h=954c068ca890942e061de81fd6eb7ff4fcbcd69b;hb=refs/heads/master#l28 [3] https://git.opendaylight.org/gerrit/#/c/40707/3/arphandler/src/main/yang/arp-handler-config.yang@54 _______________________________________________ release mailing list release@... https://lists.opendaylight.org/mailman/listinfo/release _______________________________________________ release mailing list release@... https://lists.opendaylight.org/mailman/listinfo/release _______________________________________________ alto-dev mailing list alto-dev@... https://lists.opendaylight.org/mailman/listinfo/alto-dev

1 - 3 of 3

1

Previous Topic Next Topic

Home Hashtags Subgroups Terms