Hi Tom,
Please find flow which contains the ct_state (match) and resubmit (action).
http://<controller>:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:2/table/85/flow/14
<?xml version="1.0" encoding="UTF-8"?>
<flow xmlns="urn:opendaylight:flow:inventory">
<table_id>85</table_id>
<id>14</id>
<instructions>
<instruction>
<apply-actions>
<action>
<order>0</order>
<nx-resubmit
xmlns="urn:opendaylight:openflowplugin:extension:nicira:action">
<table>4</table>
</nx-resubmit>
</action>
</apply-actions>
<order>0</order>
</instruction>
</instructions>
<match>
<ethernet-match>
<ethernet-type>
<type>2054</type>
</ethernet-type>
</ethernet-match>
<extension-list xmlns="urn:opendaylight:openflowplugin:extension:general">
<extension-key
xmlns:x="urn:opendaylight:openflowplugin:extension:nicira:match">x:nx-ct-state-key</extension-key>
<extension>
<nxm-nx-ct-state
xmlns="urn:opendaylight:openflowplugin:extension:nicira:match">
<ct-state>34</ct-state>
<mask>55</mask>
</nxm-nx-ct-state>
</extension>
</extension-list>
</match>
</flow>
Nxm-resubmit :
http://<controller>:8181/restconf/config/opendaylight-inventory:nodes/node/openflow:2/table/4/flow/2
<?xml version="1.0" encoding="UTF-8" standalone="no"?
<flow xmlns="urn:opendaylight:flow:inventory">
<table_id>0</table_id>
<id>2</id>
<instructions>
<instruction>
<apply-actions>
<action>
<order>0</order>
<nx-resubmit
xmlns="urn:opendaylight:openflowplugin:extension:nicira:action">
<table>4</table>
</nx-resubmit>
</action>
</apply-actions>
<order>0</order>
</instruction>
</instructions>
<match>
<ethernet-match>
<ethernet-type>
<type>2054</type>
</ethernet-type>
</ethernet-match>
</match>
</flow>
Regs,
Sharath
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
[email protected]
Sent: Wednesday, January 11, 2017 2:56 AM
To: [email protected]
Subject: openflowplugin-dev Digest, Vol 43, Issue 24
Send openflowplugin-dev mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific than "Re:
Contents of openflowplugin-dev digest..."
Today's Topics:
1. Re: [openflowplugin-dev] RPC
opendaylight-direct-statistics:get-flow-statistics not working
(Tom?? Slu?n?)
2. Re: [netvirt-dev] important openflowplugin patches for
netvirt (Shuva Kar)
3. Fwd: [release] WEATHER: BUG-7446: Upgrading to Guava 21
(Abhijit Kumbhare)
----------------------------------------------------------------------
Message: 1
Date: Tue, 10 Jan 2017 14:33:02 +0000
From: Tom?? Slu?n? <[email protected]>
To: Somashekar B <[email protected]>,
'openflowplugin-dev' <[email protected]>
Cc: "[email protected]"
<[email protected]>
Subject: Re: [openflowplugin-dev] RPC
opendaylight-direct-statistics:get-flow-statistics not working
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1250"
Hi Somashekar,
We are trying to reproduce your issue, we was not able to succesfully add flow
with ct_state match, because we do not know what to put into ct_state and mask
fields when adding flow via RPC. Can you send us example of mentioned values so
we will be able to reproduce it?
Thanks,
Tomas
________________________________________
Od: Somashekar B [[email protected]]
Odoslan?: 5. janu?ra 2017 16:23
Komu: 'openflowplugin-dev'
K?pia: [email protected]
Predmet: [openflowplugin-dev] RPC
opendaylight-direct-statistics:get-flow-statistics not working
Hi,
I am trying RPC opendaylight-direct-statistics:get-flow-statistics to get
statistics for below flows
cookie=0x6900000, duration=10169.451s, table=41, n_packets=4, n_bytes=300,
priority=62020,ct_state=+inv+trk actions=drop cookie=0x6900000,
duration=10169.456s, table=41, n_packets=0, n_bytes=0,
priority=50,ct_state=+new+trk actions=drop
JSON input below:
{
"input": {
"node":
"/opendaylight-inventory:nodes/opendaylight-inventory:node[opendaylight-inventory:id='openflow:9114073057828']",
"table_id": "41",
"store-stats": "true"
}
}
If the flows doesn?t have ?ct_state? in the match field, it works fine. But
with the above flows, RPC results in exception as shown below (Complete
exception attached in the mail).
I feel this is related to nicira extensions. It fails to serialize flows which
has nicira extensions.
Please help in fixing this issue.
---------------------------
2017-01-04 16:21:03,041 | ERROR | qtp463448082-512 | ContainerResponse
| 97 - com.sun.jersey.jersey-server - 1.17.0 | The RuntimeException could
not be mapped to a response, re-throwing to the HTTP container
org.opendaylight.yangtools.binding.data.codec.impl.IncorrectNestingException:
Child interface
org.opendaylight.yang.gen.v1.urn.opendaylight.openflowplugin.extension.general.rev140714.GeneralAugMatchNotifUpdateFlowStats
is not valid child.
at
org.opendaylight.yangtools.binding.data.codec.impl.IncorrectNestingException.create(IncorrectNestingException.java:28)
at
org.opendaylight.yangtools.binding.data.codec.impl.DataContainerCodecContext.childNonNull(DataContainerCodecContext.java:180)
at
org.opendaylight.yangtools.binding.data.codec.impl.DataObjectCodecContext.streamChild(DataObjectCodecContext.java:143)
at
org.opendaylight.yangtools.binding.data.codec.impl.BindingToNormalizedStreamWriter.enter(BindingToNormalizedStreamWriter.java:74)
at
org.opendaylight.yangtools.binding.data.codec.impl.BindingToNormalizedStreamWriter.startAugmentationNode(BindingToNormalizedStreamWriter.java:139)
at
org.opendaylight.yang.gen.v1.urn.opendaylight.openflowplugin.extension.general.rev140714.GeneralAugMatchNotifUpdateFlowStats$StreamWriter.serialize(DataObjectSerializerPrototype.java)
at
org.opendaylight.yangtools.binding.data.codec.impl.BindingNormalizedNodeCodecRegistry$DataObjectSerializerProxy.serialize(BindingNormalizedNodeCodecRegistry.java:295)
--------------------------
Thanks,
Somashekar
Tom??Slu?n?
Software Developer
S?dlo / Mlynsk? Nivy 56 / 821 05 Bratislava / Slovakia R&D centrum / Janka
Kr??a 9 / 974 01 Bansk? Bystrica / Slovakia
+421 911 083 902 / [email protected]
reception: +421 2 206 65 114 / www.pantheon.tech
[logo]
------------------------------
Message: 2
Date: Tue, 10 Jan 2017 21:00:17 +0530
From: Shuva Kar <[email protected]>
To: "Aizer, Koby" <[email protected]>
Cc: "[email protected]"
<[email protected]>, openflowplugin-dev
<[email protected]>
Subject: Re: [openflowplugin-dev] [netvirt-dev] important
openflowplugin patches for netvirt
Message-ID:
<cag1-a_2kmoujqzcrxpl8y7_w7nkkgornsewcbfxtekd6jvj...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Reviewed, merged and c/p 'd
Hope it helps :)
Br,shuva
On Tue, Jan 10, 2017 at 1:44 PM, Shuva Kar <[email protected]>
wrote:
> Sure will review :)
>
> thanks
> Shuva
>
> Br,shuva
>
> On Tue, Jan 10, 2017 at 1:28 PM, Aizer, Koby <[email protected]> wrote:
>
>> Hi,
>>
>>
>>
>> I can see [3] is merged & cherry-picked to stable/boron, thanks!
>>
>> I?ve rebased [4] to fix the merge conflict..
>>
>>
>>
>> Thanks,
>>
>> Koby
>>
>>
>>
>> *From:* [email protected] [mailto:
>> [email protected]] *On Behalf Of *Aizer,
>> Koby
>> *Sent:* Monday, January 9, 2017 8:40 PM
>> *To:* Shuva Kar <[email protected]>
>> *Cc:* [email protected]; openflowplugin-dev <
>> [email protected]>
>> *Subject:* Re: [netvirt-dev] [openflowplugin-dev] important
>> openflowplugin patches for netvirt
>>
>>
>>
>> Sure no problem, we'll do that as soon as [3] is merged.
>>
>> Thanks!
>> Koby
>>
>>
>> ------------------------------
>>
>> *From:* Shuva Kar <[email protected]>
>> *Sent:* Jan 9, 2017 20:34
>> *To:* Aizer, Koby
>> *Cc:* openflowplugin-dev; [email protected]
>> *Subject:* Re: [openflowplugin-dev] important openflowplugin patches
>> for netvirt
>>
>>
>>
>> Sure Koby.
>>
>>
>>
>> I have rechecked Jenkins so that we have a Jenkins verified build
>> before we can push in patch [3]. I have c/p 'd the change to stable/Boron as
>> well.
>>
>>
>>
>> However since [3] and [4] conflict each other, we would require to
>> rebase [4] after [3] is merged.
>>
>>
>>
>> thanks
>>
>> Shuva
>>
>>
>> Br,shuva
>>
>>
>>
>> On Mon, Jan 9, 2017 at 9:45 PM, Aizer, Koby <[email protected]> wrote:
>>
>> Hi openflowplugin,
>>
>>
>>
>> There are currently two bugs ([1] & [2]) which are critical for netvirt.
>>
>>
>>
>> [1] causes most of the netvirt 3nodes jobs to fail, because it causes
>> creation of rules without the required nicira actions.
>>
>> [2] floods the logs with the exception described in the ticket
>>
>>
>>
>> There are 2 pending patches that fix those bugs ([3] & [4]).
>>
>>
>>
>> Could you please review & get them merged? Also appreciate if we can
>> get them cherry-picked to stable/boron (at least [3] which is quite
>> blocking)
>>
>>
>>
>> Thanks,
>>
>> Koby
>>
>>
>>
>> [1] https://bugs.opendaylight.org/show_bug.cgi?id=7481
>>
>> [2] https://bugs.opendaylight.org/show_bug.cgi?id=7071
>>
>>
>>
>> [3] https://git.opendaylight.org/gerrit/#/c/50029/
>>
>> [4] https://git.opendaylight.org/gerrit/#/c/49665/
>>
>>
>>
>>
>> _______________________________________________
>> openflowplugin-dev mailing list
>> [email protected]
>> https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.opendaylight.org/pipermail/openflowplugin-dev/attachments/20170110/4e0e3e87/attachment-0001.html>
------------------------------
Message: 3
Date: Tue, 10 Jan 2017 13:26:06 -0800
From: Abhijit Kumbhare <[email protected]>
To: "[email protected]"
<[email protected]>
Subject: [openflowplugin-dev] Fwd: [release] WEATHER: BUG-7446:
Upgrading to Guava 21
Message-ID:
<CAHce=85z3sefqrbsenksywcc-eqk7en10yonb6tkgu7dt+f...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Fyi.
---------- Forwarded message ----------
From: Robert Varga <[email protected]>
Date: Tue, Jan 10, 2017 at 11:35 AM
Subject: [release] WEATHER: BUG-7446: Upgrading to Guava 21
To: "[email protected]" <[email protected]>
Cc: "[email protected]" <[email protected]>
Hello everyone,
Google Guava is finally making the step to Java 8 land, allowing better
integration with Java 7/8 features.
Unfortunately this is a jump of three releases since we have last upgraded
Guava -- we are currently using 18.0 -- and there are some API elements which
were both deprecated in 19.0 and removed in 20.0, hence this transition will
not be completely painless and will require a flag day.
The details are available at:
https://google.github.io/guava/releases/19.0/api/diffs/
https://google.github.io/guava/releases/20.0/api/diffs/
https://google.github.io/guava/releases/21.0-rc2/api/diffs/
API changes impact 12 projects, of which ovsdb and mdsal can be fixed ahead of
time.
The steps to perform the upgrade are the following:
1) provide odl-guava-21 feature from odlparent
2) make yangtools pull odl-guava-21 as well as odl-guava-18
3) create a 'switch-to-21' patch in odlparent
4) prepare migration patches to downstream projects
5) validate autorelease with the patches
6) merge the 'switch-to-21' patch in odlparent
7) reverify/merge the migration patches in the project dependency order,
re-merging unaffected projects, as they need to be rebuilt
8) make yangtools not pull odl-guava-18
Steps 1-3 have been executed.
Patches for 4 are available at
https://git.opendaylight.org/gerrit/#/q/topic:guava21 and have been
compile-tested with -Pq.
Step 5 needs to be executed, unfortunately I don't have local resources to do
that.
The flag day part is step 6&7, which is rather unavoidable, as the individual
projects cannot really interoperate if they were compiled with different
versions of Guava. This also means that in steps 6 and 7 integration-level jobs
(like distribution-check, csit) will be out of whack.
To minimize the duration of this breakage, I would like to determine an
acceptable window when when the releng team would be granted powers to merge
the above patches, disregarding distribution-check failures.
We still have some time before 21.0 is out for real, but I would like us to use
this time to discuss and agree on the strategy.
Colin, could you allocate some 5-10 minutes for this topic on the next TSC call?
Thanks,
Robert
P.S.: The changeover could be done by switching to 19.0 and then to 21.0, which
would make step 7 a rebuild only. I do not have the cycles to drive that and
also the disruption would actually be greater, as 6-8 would have to be executed
twice.
_______________________________________________
release mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/release
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.opendaylight.org/pipermail/openflowplugin-dev/attachments/20170110/1a5f090f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL:
<http://lists.opendaylight.org/pipermail/openflowplugin-dev/attachments/20170110/1a5f090f/attachment.sig>
------------------------------
_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
End of openflowplugin-dev Digest, Vol 43, Issue 24
**************************************************
_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
