https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/OPNFLWPLUG-628 OpenFlowPlugin <p>VTN project needs the "get-flow-statistics-from-flow-table" RPC by default in OpenFlow Plugin Lithium design.</p> <p>The discussion has been already occurred in the openflowplugin-dev ML.</p> <p>The request for the stats RPC in the OFP-Li:<br/> <a href="https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-January/004562.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-January/004562.html</a></p> <p>The explanation why the VTN project needs the "get-flow-statistics-from-flow-table" RPC:<br/> <a href="https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-January/004571.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-January/004571.html</a></p> <p>Michal's comment about this topic.<br/> <a href="https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-January/004572.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-January/004572.html</a></p> <p>Operating System: All<br/> Platform: All</p> OPNFLWPLUG-628

Li Migration: Enabled "get-flow-statistics-from-flow-table" RPC by default.

Improvement Resolved Duplicate Hideyuki Tai Hideyuki Tai Fri, 26 Feb 2016 00:50:34 +0000 Mon, 27 Sep 2021 09:01:44 +0000 Mon, 18 Apr 2016 14:00:24 +0000 General 0 5 <p>Hideyuki how do you continue with this ? </p> <p>Are you able use OFP Li design only with "is-statistics-rpc-enabled" or should we discuss more about it ? </p> <p>Like Michal said we wont make "get-flow-statistics-from-flow-table" default in Boron release and I am not sure if it's good idea to make it default either in Beryllium release. </p> <p>Just let us know. Meantime I lower the bug from major to enhancement.</p> <p>Jozef</p> <p>(In reply to Jozef Bacigal from comment #1)<br/> &gt; Hideyuki how do you continue with this ? <br/> &gt; <br/> &gt; Are you able use OFP Li design only with "is-statistics-rpc-enabled" or<br/> &gt; should we discuss more about it ? </p> <p>Hi Jozef,</p> <p>Thank you for checking the report!</p> <p>VTN project needs the "get-flow-statistics-from-flow-table" RPC by default in Boron.</p> <p>&gt; Like Michal said we wont make "get-flow-statistics-from-flow-table" default<br/> &gt; in Boron release and I am not sure if it's good idea to make it default<br/> &gt; either in Beryllium release. <br/> &gt; </p> <p>I don't think Michal said that.</p> <p>He said "I think it makes more sense to cowardly give up on Li-design purity for Be release and enable it by default."<br/> <a href="https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-January/004572.html" class="external-link" target="_blank" rel="nofollow noopener">https://lists.opendaylight.org/pipermail/openflowplugin-dev/2016-January/004572.html</a></p> <p>Here, I think "Be release" means "Beryllium release".</p> <p>So he didn't say that OFP project won't make it default in Boron release, in my understanding.</p> <p>And, I couldn't find any bad reasons to make it default.<br/> Therefore, I would like the OFP project to make it default in Boron.</p> <p>&gt; Just let us know. Meantime I lower the bug from major to enhancement.<br/> &gt; <br/> &gt; Jozef</p> <p>Hi all,<br/> sorry for latency. There were definitely some misunderstandings. </p> <p>We have rpc implementation for reading stats with notification side effect in Li-design ready and configurable via config subsystem. Present in Beryllium and master (current Boron). And disabled by default.</p> <p>This backward compatibility API+implementation will be deprecated in Boron and replaced by notifications-free implementation probably with option to update DS/operational in order to support user-driven selective DS/operational synchronization. That's why these "old" rpcs can not be enabled by default in Boron.</p> <p>But in Beryllium these "old" rpc can be enabled by default. Or at least I am not aware of any strong reason why not. There would be another routed rpc implementation available. This would not affect projects relying on DS/operational. And projects like VTN would get the compatibility support out of the box (in Beryllium) without adapting config xml files and providing customized karaf distro.</p> <p>Hideyuki+JozefB: If we all agree on this then I can submit the change in config in Beryllium and Jozef - please file a bug for new rpcs with target milestone = Boron.</p> <p>Hi Michal and Jozef,</p> <p>Thank you for your comments.</p> <p>VTN project doesn't use the Li-design in Beryllium. Therefore, we don't need the change in config in Beryllium.</p> <p>In Boron, VTN project plans to use the Li-design, and needs a way to want <b>latest</b> information about flow entries in OpenFlow switches.<br/> And, I think what you mentioned could be what we want.</p> <p>"notifications-free implementation probably with option to update DS/operational in order to support user-driven selective DS/operational synchronization."</p> <p>Jozef, could you give me the URL of the bug report in the bugzilla for the new RPC after you filed it?</p> <p>VTN project wants the new RPC before the OFP project change the default plugin to the Li-design in the master branch.</p> <p><a href="https://bugs.opendaylight.org/show_bug.cgi?id=5692" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=5692</a></p> Duplicate OPNFLWPLUG-672 Development External issue ID 5432 External issue URL Rank 0|i032br: