<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:32:14 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-353] Buckets in groups are not ordered.</title>
                <link>https://jira.opendaylight.org/browse/OPNFLWPLUG-353</link>
                <project id="10155" key="OPNFLWPLUG">OpenFlowPlugin</project>
                    <description>&lt;p&gt;According to spec 1.3.x the action buckets are &quot;an ordered list of action buckets, where each action bucket contains a set of&lt;br/&gt;
actions to execute and associated parameters&quot;. The problem is that these buckets are not ordered, thus when designing an app that involves multiple buckets for, say, fast fail-over, the result is not predictable. This http request:&lt;/p&gt;

&lt;p&gt;&amp;lt;group xmlns=&quot;urn:opendaylight:flow:inventory&quot;&amp;gt;&lt;br/&gt;
	&amp;lt;group-type&amp;gt;group-ff&amp;lt;/group-type&amp;gt;&lt;br/&gt;
	&amp;lt;buckets&amp;gt;&lt;br/&gt;
		&amp;lt;bucket&amp;gt;&lt;br/&gt;
			&amp;lt;action&amp;gt;&lt;br/&gt;
				&amp;lt;output-action&amp;gt;&lt;br/&gt;
					&amp;lt;output-node-connector&amp;gt;openflow:1:2&amp;lt;/output-node-connector&amp;gt;&lt;br/&gt;
				&amp;lt;/output-action&amp;gt;&lt;br/&gt;
				&amp;lt;order&amp;gt;0&amp;lt;/order&amp;gt;&lt;br/&gt;
			&amp;lt;/action&amp;gt;&lt;br/&gt;
			&amp;lt;bucket-id&amp;gt;1&amp;lt;/bucket-id&amp;gt;&lt;br/&gt;
			&amp;lt;watch_port&amp;gt;2&amp;lt;/watch_port&amp;gt;&lt;br/&gt;
		&amp;lt;/bucket&amp;gt;&lt;br/&gt;
		&amp;lt;bucket&amp;gt;&lt;br/&gt;
			&amp;lt;action&amp;gt;&lt;br/&gt;
				&amp;lt;output-action&amp;gt;&lt;br/&gt;
					&amp;lt;output-node-connector&amp;gt;openflow:1:3&amp;lt;/output-node-connector&amp;gt;&lt;br/&gt;
				&amp;lt;/output-action&amp;gt;&lt;br/&gt;
				&amp;lt;order&amp;gt;0&amp;lt;/order&amp;gt;&lt;br/&gt;
			&amp;lt;/action&amp;gt;&lt;br/&gt;
			&amp;lt;bucket-id&amp;gt;2&amp;lt;/bucket-id&amp;gt;&lt;br/&gt;
			&amp;lt;watch_port&amp;gt;3&amp;lt;/watch_port&amp;gt;&lt;br/&gt;
		&amp;lt;/bucket&amp;gt;&lt;br/&gt;
	&amp;lt;/buckets&amp;gt;&lt;br/&gt;
	&amp;lt;group-name&amp;gt;Foo&amp;lt;/group-name&amp;gt;&lt;br/&gt;
	&amp;lt;group-id&amp;gt;1&amp;lt;/group-id&amp;gt;&lt;br/&gt;
&amp;lt;/group&amp;gt;&lt;/p&gt;

&lt;p&gt;produces this data in the configuration tree:&lt;/p&gt;

&lt;p&gt;&amp;lt;group xmlns=&quot;urn:opendaylight:flow:inventory&quot;&amp;gt;&lt;br/&gt;
	&amp;lt;group-id&amp;gt;1&amp;lt;/group-id&amp;gt;&lt;br/&gt;
	&amp;lt;buckets&amp;gt;&lt;br/&gt;
		&amp;lt;bucket&amp;gt;&lt;br/&gt;
			&amp;lt;bucket-id&amp;gt;2&amp;lt;/bucket-id&amp;gt;&lt;br/&gt;
			&amp;lt;watch_port&amp;gt;3&amp;lt;/watch_port&amp;gt;&lt;br/&gt;
			&amp;lt;action&amp;gt;&lt;br/&gt;
				&amp;lt;order&amp;gt;0&amp;lt;/order&amp;gt;&lt;br/&gt;
				&amp;lt;output-action&amp;gt;&lt;br/&gt;
					&amp;lt;output-node-connector&amp;gt;openflow:1:3&amp;lt;/output-node-connector&amp;gt;&lt;br/&gt;
				&amp;lt;/output-action&amp;gt;&lt;br/&gt;
			&amp;lt;/action&amp;gt;&lt;br/&gt;
		&amp;lt;/bucket&amp;gt;&lt;br/&gt;
		&amp;lt;bucket&amp;gt;&lt;br/&gt;
			&amp;lt;bucket-id&amp;gt;1&amp;lt;/bucket-id&amp;gt;&lt;br/&gt;
			&amp;lt;watch_port&amp;gt;2&amp;lt;/watch_port&amp;gt;&lt;br/&gt;
			&amp;lt;action&amp;gt;&lt;br/&gt;
				&amp;lt;order&amp;gt;0&amp;lt;/order&amp;gt;&lt;br/&gt;
				&amp;lt;output-action&amp;gt;&lt;br/&gt;
					&amp;lt;output-node-connector&amp;gt;openflow:1:2&amp;lt;/output-node-connector&amp;gt;&lt;br/&gt;
				&amp;lt;/output-action&amp;gt;&lt;br/&gt;
			&amp;lt;/action&amp;gt;&lt;br/&gt;
		&amp;lt;/bucket&amp;gt;&lt;br/&gt;
	&amp;lt;/buckets&amp;gt;&lt;br/&gt;
	&amp;lt;group-type&amp;gt;group-ff&amp;lt;/group-type&amp;gt;&lt;br/&gt;
	&amp;lt;group-name&amp;gt;Foo&amp;lt;/group-name&amp;gt;&lt;br/&gt;
	&amp;lt;barrier&amp;gt;false&amp;lt;/barrier&amp;gt;&lt;br/&gt;
&amp;lt;/group&amp;gt;&lt;/p&gt;

&lt;p&gt;and the message send to the switch contains the buckets as in the data store. This way we cannot create proper paths in a network using groups as we don&apos;t know which bucket will be used when.&lt;/p&gt;

&lt;p&gt;I suggest a change in the model so that each bucket has an &quot;order&quot; field, much like actions have an order field. Then the OpenFlow pluggin should respect this order and create the proper OF message.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="27621">OPNFLWPLUG-353</key>
            <summary>Buckets in groups are not ordered.</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="iosam@intracom-telecom.com">Ioakeim Samaras</assignee>
                                    <reporter username="ckaidos@intracom-telecom.com">Charalampos Kaidos</reporter>
                        <labels>
                    </labels>
                <created>Tue, 3 Feb 2015 10:22:39 +0000</created>
                <updated>Mon, 27 Sep 2021 09:01:25 +0000</updated>
                            <resolved>Fri, 9 Oct 2015 17:14:44 +0000</resolved>
                                                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                                                                <comments>
                            <comment id="56462" author="abhijit2511" created="Tue, 24 Feb 2015 15:40:03 +0000"  >&lt;p&gt;Kamal,&lt;/p&gt;

&lt;p&gt;Did you work on a bug related to ordering? This is not the most pressing bug at the moment but if you have a chance sometime - please look at it. &lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Abhijit&lt;/p&gt;</comment>
                            <comment id="56463" author="kramesha@cisco.com" created="Wed, 3 Jun 2015 05:31:42 +0000"  >&lt;p&gt;I can work on this one, but this one would probably need a yang/api change.&lt;/p&gt;

&lt;p&gt;Too late for Lithium i guess&lt;/p&gt;</comment>
                            <comment id="56464" author="shuva.jyoti.kar.87@gmail.com" created="Wed, 5 Aug 2015 15:22:13 +0000"  >&lt;p&gt;The issue becomes even more complex and inexplicable in case we decide to add a few more buckets, the ordering gets really scrambled&lt;/p&gt;</comment>
                            <comment id="56465" author="iosam@intracom-telecom.com" created="Fri, 21 Aug 2015 07:00:40 +0000"  >&lt;p&gt;Hello,&lt;/p&gt;

&lt;p&gt;I would like to ask if there is any progress regarding this bug.&lt;/p&gt;

&lt;p&gt;Thanks in advance.&lt;/p&gt;</comment>
                            <comment id="56466" author="iosam@intracom-telecom.com" created="Fri, 21 Aug 2015 15:12:54 +0000"  >&lt;p&gt;Please check the following thread in mailing list:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://lists.opendaylight.org/pipermail/openflowplugin-dev/2015-August/003723.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://lists.opendaylight.org/pipermail/openflowplugin-dev/2015-August/003723.html&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="56467" author="kramesha@cisco.com" created="Sun, 23 Aug 2015 06:37:46 +0000"  >&lt;p&gt;I am not getting the time to pick this up as clustering is going to take a bulk.&lt;br/&gt;
If there are any takers for this one, please go ahead.&lt;br/&gt;
If not then i will jump onto this one, after Li-SR2.&lt;/p&gt;

&lt;p&gt;Resetting owner to default.&lt;/p&gt;</comment>
                            <comment id="56468" author="ecelgp" created="Fri, 25 Sep 2015 18:09:26 +0000"  >&lt;p&gt;This bug makes FF groups unusable.&lt;/p&gt;</comment>
                            <comment id="56469" author="ecelgp" created="Fri, 25 Sep 2015 20:32:10 +0000"  >&lt;p&gt;Hi Samaras, any ETA for the fix?&lt;/p&gt;</comment>
                            <comment id="56470" author="iosam@intracom-telecom.com" created="Tue, 29 Sep 2015 06:25:27 +0000"  >&lt;p&gt;Hello, we have just pushed our solution to ODL gerrit. We are waiting for the review process.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/27544/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/27544/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="56471" author="vishnoianil@gmail.com" created="Tue, 29 Sep 2015 07:33:30 +0000"  >&lt;p&gt;Patch is merged in master and also to stable/lithium.&lt;/p&gt;</comment>
                            <comment id="56472" author="abhijit2511" created="Fri, 9 Oct 2015 17:14:44 +0000"  >&lt;p&gt;As per Anil&apos;s comment has been fixed and just needs verification&lt;/p&gt;</comment>
                    </comments>
                    <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>2664</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=2664]]></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|i030mn:</customfieldvalue>

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