<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:33:03 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[OPNFLWPLUG-660] Li Migration: Problems to detect the removal of flow entries</title>
                <link>https://jira.opendaylight.org/browse/OPNFLWPLUG-660</link>
                <project id="10155" key="OPNFLWPLUG">OpenFlowPlugin</project>
                    <description>&lt;p&gt;Target&lt;br/&gt;
------&lt;/p&gt;

&lt;p&gt;Target source code: master branch of March of 2016&lt;br/&gt;
Target feature: OFP-Li (OpenFlow Plugin Lithium design)&lt;br/&gt;
Target data: flow-node-inventory:table in the operational DS&lt;br/&gt;
Related OpenFlow message: FLOW_REMOVED&lt;/p&gt;


&lt;p&gt;Problems&lt;br/&gt;
--------&lt;/p&gt;

&lt;p&gt;With the OFP-Li, applications need to use operational DS (flow-node-inventory:table) to get information about flow entries installed in OpenFlow switches.&lt;/p&gt;

&lt;p&gt;In my understanding, when statistics manager of the OPF-Li is installed, the flow entry information on the operational DS is updated only by the statistics manager.&lt;br/&gt;
And, the statistics manager does not use FLOW_REMOVED to update the flow entry information in the DS.&lt;/p&gt;

&lt;p&gt;As a result, with the current implementation of the OFP-Li, applications face the following two problems to detect the removal of flow entries.&lt;/p&gt;

&lt;p&gt; 1. It takes so long time (several seconds) to detect the removal.&lt;br/&gt;
 2. It is possible that applications fail to detect the removal.&lt;/p&gt;


&lt;p&gt;First, when the statics manager is installed, the OFP-Li does not update the operational DS on the event of FLOW_REMOVED.&lt;br/&gt;
Instead, the statistics manager updates (removes the flow entry from) the operational DS only based on the statistics information which the statistics manager gets from switch.&lt;br/&gt;
However, by default, the statistics manager gets the statistics information from the switch at intervals of several seconds.&lt;br/&gt;
Therefore, it takes several seconds for applications which listen data change on the operational DS to detect the removal of a flow entry after the flow entry is actually removed from the switch.&lt;/p&gt;


&lt;p&gt;Second, when an application installs a flow entry whose timeout is a few seconds, it is possible that the statistics manager could not be aware of the installation and removal of the flow entry.&lt;br/&gt;
That&apos;s because the statistics manager does not use the notification of FLOW_REMOVED to update the operational DS.&lt;br/&gt;
As a result, the application would fail to detect the removal of the flow entry.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="27928">OPNFLWPLUG-660</key>
            <summary>Li Migration: Problems to detect the removal of flow entries</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="Hideyuki1985">Hideyuki Tai</reporter>
                        <labels>
                    </labels>
                <created>Thu, 24 Mar 2016 20:53:01 +0000</created>
                <updated>Mon, 27 Sep 2021 09:01:46 +0000</updated>
                            <resolved>Thu, 21 Jul 2016 15:34:10 +0000</resolved>
                                                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>8</watches>
                                                                                                                <comments>
                            <comment id="57754" author="hideyuki.tai@necam.com" created="Thu, 24 Mar 2016 20:54:39 +0000"  >&lt;p&gt;VTN project requests the OpenFlow Plugin project to provide a way which does not have the above two problems in Boron.&lt;/p&gt;


&lt;p&gt;We think one candidate solution for the problems is that the OFP-Li implements a YANG notification which notifies its applications of the removal of a flow entry on the event of receiving FLOW_REMOVED message from a switch.&lt;/p&gt;</comment>
                            <comment id="57755" author="kramesha@cisco.com" created="Mon, 11 Apr 2016 16:38:13 +0000"  >&lt;p&gt;From the code, the FlowRemoved message is processed by OFP and the same is removed from the operational.&lt;/p&gt;

&lt;p&gt;I dont see any notification raised to be consumed by the apps.&lt;/p&gt;</comment>
                            <comment id="57756" author="shuva.jyoti.kar.87@gmail.com" created="Tue, 10 May 2016 16:30:18 +0000"  >&lt;p&gt;Hi Kamal and folks, &lt;/p&gt;

&lt;p&gt;can we publish a flowremoved notification from the place where we receive the flowremoved message and intimate the listeners.&lt;/p&gt;

&lt;p&gt;Its taken that notifications will not be guaranteed, but just as experimenters and packet-in s can we shoot up an notification ?&lt;/p&gt;</comment>
                            <comment id="57757" author="shuva.jyoti.kar.87@gmail.com" created="Tue, 10 May 2016 16:43:41 +0000"  >&lt;p&gt;A patch for the same:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/38639&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/38639&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="57758" author="hideyuki.tai@necam.com" created="Wed, 8 Jun 2016 16:48:19 +0000"  >&lt;p&gt;I&apos;ve submitted an additional patch for this problem.&lt;br/&gt;
&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/39906/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/39906/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Could a committer review and merge the patch?&lt;/p&gt;</comment>
                            <comment id="57759" author="shuva.jyoti.kar.87@gmail.com" created="Thu, 9 Jun 2016 15:14:49 +0000"  >&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/39552&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/39552&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="57760" author="abhijit2511" created="Thu, 21 Jul 2016 15:34:10 +0000"  >&lt;p&gt;This has been added/fixed.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="27973">OPNFLWPLUG-705</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5602</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=5602]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10202" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Priority</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10312"><![CDATA[High]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i032iv:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>