Date   

Re: [openflowplugin-dev] Switch didn't register to controller in opendaylight controller (Lithium) and Openvswitch 2.4.0?

Abhijit Kumbhare
 

Yes Luis - please do.

On Wed, Oct 14, 2015 at 10:31 PM, Luis Gomez <ecelgp@...> wrote:
How are we doing with this? did anybody open a bug to track this? if not I will do as I think it is important to support latest OVS in ODL.

BR/Luis


On Sep 25, 2015, at 6:29 AM, Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES at Cisco) <mirehak@...> wrote:

Hi Ben,
this is caused by table-features. Please file a bug to openflowjava.
You might workaround this issue by downgrading to 2.3.x version of openvswitch (there are table-features not supported). 

And just to defend ofjava a bit - by cpqd switch there are table-features supported and it works. Ovs-2.4 is the first version of ovs with table-features and message content is probably more complicated.


Regards,
Michal


From: openflowplugin-dev-bounces@... [openflowplugin-dev-bounces@...] on behalf of 鐘晧文 [hnaxiorll@...]
Sent: Friday, September 25, 2015 02:11
To: openflowplugin-dev@...
Subject: [openflowplugin-dev] Switch didn't register to controller in opendaylight controller (Lithium) and Openvswitch 2.4.0?

Hi all,

I use the openvswitch 2.4.0 and opendaylight controller (Lithium).

Then, I install these feature odl-dlux-all, odl-restconf-all, odl-mdsal-apidocs, and odl-openflowplugin-all-li in ODL.

Next, I create a bridge and set controller but I can't see any switch node in web.

The OVS shows that `Controller "tcp:192.168.5.131:6633is_connected: true` (ovs-vsctl show).

The log of ODL shows a lot of warn and some error:

2015-09-24 18:17:02,718 | INFO  | entLoopGroup-8-4 | DeviceManagerImpl                | 279 - org.opendaylight.openflowplugin.impl - 0.1.0.Lithium | Static node Uri [_value=openflow:134303595078473] info: OFPMPGROUPFEATURES collected
2015-09-24 18:17:02,719 | TRACE | entLoopGroup-8-4 | OpenflowProtocolListenerFullImpl | 279 - org.opendaylight.openflowplugin.impl - 0.1.0.Lithium | Multipart Reply with XID: 2
2015-09-24 18:17:02,732 | WARN  | entLoopGroup-8-4 | OFDecoder                        | 276 - org.opendaylight.openflowjava.openflow-protocol-impl - 0.6.0.Lithium | Message deserialization failed
java.lang.IllegalStateException: Deserializer for key: msgVersion: 4 objectClass: org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.oxm.rev150225.match.entries.grouping.MatchEntry msgType: 1 oxm_field: 31 experimenterID: null was not found - please verify that all needed deserializers ale loaded correctly
        at org.opendaylight.openflowjava.protocol.impl.deserialization.DeserializerRegistryImpl.getDeserializer(DeserializerRegistryImpl.java:64)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.util.ListDeserializer.deserializeHeaders(ListDeserializer.java:71)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.deserialization.factories.MultipartReplyMessageFactory.createTableFeaturesProperties(MultipartReplyMessageFactory.java:426)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.deserialization.factories.MultipartReplyMessageFactory.setTableFeatures(MultipartReplyMessageFactory.java:361)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.deserialization.factories.MultipartReplyMessageFactory.deserialize(MultipartReplyMessageFactory.java:216)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.deserialization.factories.MultipartReplyMessageFactory.deserialize(MultipartReplyMessageFactory.java:146)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.deserialization.DeserializationFactory.deserialize(DeserializationFactory.java:53)[276:org.opendaylight.openflowjava.openflow-pr
...
2015-09-24 18:17:03,251 | DEBUG | entLoopGroup-8-4 | RpcContextImpl                   | 279 - org.opendaylight.openflowplugin.impl - 0.1.0.Lithium | Registration of service interface org.opendaylight.yang.gen.v1.urn.opendaylight.flow.statistics.rev130819.OpendaylightFlowStatisticsService for device KeyedInstanceIdentifier{targetType=interface org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node, path=[org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.Nodes, org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node[key=NodeKey [_id=Uri [_value=openflow:134303595078473]]]]}.
2015-09-24 18:17:03,252 | TRACE | entLoopGroup-8-4 | OpenflowProtocolListenerFullImpl | 279 - org.opendaylight.openflowplugin.impl - 0.1.0.Lithium | Multipart Reply with XID: 11
2015-09-24 18:17:03,253 | ERROR | lt-dispatcher-14 | Shard                            | 208 - org.opendaylight.controller.sal-akka-raft - 1.2.0.Lithium | member-1-shard-inventory-operational An exception occurred while preCommitting transaction member-1-chn-15-txn-1
java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: Metadata not available for modification NodeModification [identifier=(urn:opendaylight:flow:inventory?revision=2013-08-19)table[{(urn:opendaylight:flow:inventory?revision=2013-08-19)id=140}], modificationType=TOUCH, childModification={AugmentationIdentifier{childNames=[(urn:opendaylight:flow:table:statistics?revision=2013-12-15)flow-table-statistics]}=NodeModification [identifier=AugmentationIdentifier{childNames=[(urn:opendaylight:flow:table:statistics?revision=2013-12-15)flow-table-statistics]}, modificationType=TOUCH, childModification={(urn:opendaylight:flow:table:statistics?revision=2013-12-15)flow-table-statistics=NodeModification [identifier=(urn:opendaylight:flow:table:statistics?revision=2013-12-15)flow-table-statistics, modificationType=WRITE, childModification={}]}]}]
        at com.google.common.util.concurrent.Futures$ImmediateFailedFuture.get(Futures.java:190)[97:com.google.guava:18.0.0]
        at org.opendaylight.controller.cluster.datastore.ShardCommitCoordinator.doCommit(ShardCommitCoordinator.java:357)[215:org.opendaylight.controller.sal-distributed-datastore:1.2.0.Lithium]
        at org.opendaylight.controller.cluster.datastore.ShardCommitCoordinator.doCanCommit(ShardCommitCoordinator.java:316)[215:org.opend
...
2015-09-24 18:17:06,282 | WARN  | lt-dispatcher-16 | SimpleShardDataTreeCohort        | 215 - org.opendaylight.controller.sal-distributed-datastore - 1.2.0.Lithium | Store Tx member-1-chn-17-txn-1: Data validation failed for path /(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:134303595078473}].
org.opendaylight.yangtools.yang.data.api.schema.tree.ModifiedNodeDoesNotExistException: Node /(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:134303595078473}] does not exist. Cannot apply modification to its children.
        at org.opendaylight.yangtools.yang.data.impl.schema.tree.AbstractNodeContainerModificationStrategy.checkTouchApplicable(AbstractNodeContainerModificationStrategy.java:182)[121:org.opendaylight.yangtools.yang-data-impl:0.7.0.Lithium]
        at org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaAwareApplyOperation.checkApplicable(SchemaAwareApplyOperation.java:125)[121:org.opendaylight.yangtools.yang-data-impl:0.7.0.Lithium]
        at org.opendaylight.yangtools.yang.data.impl.schema.tree.AbstractNodeContainerModificationStrategy.checkChildPreconditions(AbstractNodeContainerModificationStrategy.java:205)[121:org.opendaylight.yangtools.yang-data-impl:0.7.0.Lithium]
        at org.opendaylight.yangtools.yang.data.impl.schema.tree.AbstractNodeContainerModificationStrategy.checkTouchApplicable(AbstractNodeContainerModificationStrategy.java:189)[121:org.opendaylight.yangtools.yang-data-impl:0.7.0.Lithium]
        at org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaAwareApplyOperation.checkApplicable(SchemaAwareApplyOperation.java:125)[121:org.opendaylight.yangtools.yang-data-impl:0.7.0.Lithium]

Does anyone know what problem?
Thanks,
Ben.
_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@...
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev


_______________________________________________
openflowplugin-dev mailing list
openflowplugin-dev@...
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev



Re: [openflowplugin-dev] Switch didn't register to controller in opendaylight controller (Lithium) and Openvswitch 2.4.0?

Luis Gomez <ecelgp@...>
 

How are we doing with this? did anybody open a bug to track this? if not I will do as I think it is important to support latest OVS in ODL.

BR/Luis


On Sep 25, 2015, at 6:29 AM, Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES at Cisco) <mirehak@...> wrote:

Hi Ben,
this is caused by table-features. Please file a bug to openflowjava.
You might workaround this issue by downgrading to 2.3.x version of openvswitch (there are table-features not supported). 

And just to defend ofjava a bit - by cpqd switch there are table-features supported and it works. Ovs-2.4 is the first version of ovs with table-features and message content is probably more complicated.


Regards,
Michal


From: openflowplugin-dev-bounces@... [openflowplugin-dev-bounces@...] on behalf of 鐘晧文 [hnaxiorll@...]
Sent: Friday, September 25, 2015 02:11
To: openflowplugin-dev@...
Subject: [openflowplugin-dev] Switch didn't register to controller in opendaylight controller (Lithium) and Openvswitch 2.4.0?

Hi all,

I use the openvswitch 2.4.0 and opendaylight controller (Lithium).

Then, I install these feature odl-dlux-all, odl-restconf-all, odl-mdsal-apidocs, and odl-openflowplugin-all-li in ODL.

Next, I create a bridge and set controller but I can't see any switch node in web.

The OVS shows that `Controller "tcp:192.168.5.131:6633is_connected: true` (ovs-vsctl show).

The log of ODL shows a lot of warn and some error:

2015-09-24 18:17:02,718 | INFO  | entLoopGroup-8-4 | DeviceManagerImpl                | 279 - org.opendaylight.openflowplugin.impl - 0.1.0.Lithium | Static node Uri [_value=openflow:134303595078473] info: OFPMPGROUPFEATURES collected
2015-09-24 18:17:02,719 | TRACE | entLoopGroup-8-4 | OpenflowProtocolListenerFullImpl | 279 - org.opendaylight.openflowplugin.impl - 0.1.0.Lithium | Multipart Reply with XID: 2
2015-09-24 18:17:02,732 | WARN  | entLoopGroup-8-4 | OFDecoder                        | 276 - org.opendaylight.openflowjava.openflow-protocol-impl - 0.6.0.Lithium | Message deserialization failed
java.lang.IllegalStateException: Deserializer for key: msgVersion: 4 objectClass: org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.oxm.rev150225.match.entries.grouping.MatchEntry msgType: 1 oxm_field: 31 experimenterID: null was not found - please verify that all needed deserializers ale loaded correctly
        at org.opendaylight.openflowjava.protocol.impl.deserialization.DeserializerRegistryImpl.getDeserializer(DeserializerRegistryImpl.java:64)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.util.ListDeserializer.deserializeHeaders(ListDeserializer.java:71)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.deserialization.factories.MultipartReplyMessageFactory.createTableFeaturesProperties(MultipartReplyMessageFactory.java:426)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.deserialization.factories.MultipartReplyMessageFactory.setTableFeatures(MultipartReplyMessageFactory.java:361)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.deserialization.factories.MultipartReplyMessageFactory.deserialize(MultipartReplyMessageFactory.java:216)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.deserialization.factories.MultipartReplyMessageFactory.deserialize(MultipartReplyMessageFactory.java:146)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.deserialization.DeserializationFactory.deserialize(DeserializationFactory.java:53)[276:org.opendaylight.openflowjava.openflow-pr
...
2015-09-24 18:17:03,251 | DEBUG | entLoopGroup-8-4 | RpcContextImpl                   | 279 - org.opendaylight.openflowplugin.impl - 0.1.0.Lithium | Registration of service interface org.opendaylight.yang.gen.v1.urn.opendaylight.flow.statistics.rev130819.OpendaylightFlowStatisticsService for device KeyedInstanceIdentifier{targetType=interface org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node, path=[org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.Nodes, org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node[key=NodeKey [_id=Uri [_value=openflow:134303595078473]]]]}.
2015-09-24 18:17:03,252 | TRACE | entLoopGroup-8-4 | OpenflowProtocolListenerFullImpl | 279 - org.opendaylight.openflowplugin.impl - 0.1.0.Lithium | Multipart Reply with XID: 11
2015-09-24 18:17:03,253 | ERROR | lt-dispatcher-14 | Shard                            | 208 - org.opendaylight.controller.sal-akka-raft - 1.2.0.Lithium | member-1-shard-inventory-operational An exception occurred while preCommitting transaction member-1-chn-15-txn-1
java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: Metadata not available for modification NodeModification [identifier=(urn:opendaylight:flow:inventory?revision=2013-08-19)table[{(urn:opendaylight:flow:inventory?revision=2013-08-19)id=140}], modificationType=TOUCH, childModification={AugmentationIdentifier{childNames=[(urn:opendaylight:flow:table:statistics?revision=2013-12-15)flow-table-statistics]}=NodeModification [identifier=AugmentationIdentifier{childNames=[(urn:opendaylight:flow:table:statistics?revision=2013-12-15)flow-table-statistics]}, modificationType=TOUCH, childModification={(urn:opendaylight:flow:table:statistics?revision=2013-12-15)flow-table-statistics=NodeModification [identifier=(urn:opendaylight:flow:table:statistics?revision=2013-12-15)flow-table-statistics, modificationType=WRITE, childModification={}]}]}]
        at com.google.common.util.concurrent.Futures$ImmediateFailedFuture.get(Futures.java:190)[97:com.google.guava:18.0.0]
        at org.opendaylight.controller.cluster.datastore.ShardCommitCoordinator.doCommit(ShardCommitCoordinator.java:357)[215:org.opendaylight.controller.sal-distributed-datastore:1.2.0.Lithium]
        at org.opendaylight.controller.cluster.datastore.ShardCommitCoordinator.doCanCommit(ShardCommitCoordinator.java:316)[215:org.opend
...
2015-09-24 18:17:06,282 | WARN  | lt-dispatcher-16 | SimpleShardDataTreeCohort        | 215 - org.opendaylight.controller.sal-distributed-datastore - 1.2.0.Lithium | Store Tx member-1-chn-17-txn-1: Data validation failed for path /(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:134303595078473}].
org.opendaylight.yangtools.yang.data.api.schema.tree.ModifiedNodeDoesNotExistException: Node /(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:134303595078473}] does not exist. Cannot apply modification to its children.
        at org.opendaylight.yangtools.yang.data.impl.schema.tree.AbstractNodeContainerModificationStrategy.checkTouchApplicable(AbstractNodeContainerModificationStrategy.java:182)[121:org.opendaylight.yangtools.yang-data-impl:0.7.0.Lithium]
        at org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaAwareApplyOperation.checkApplicable(SchemaAwareApplyOperation.java:125)[121:org.opendaylight.yangtools.yang-data-impl:0.7.0.Lithium]
        at org.opendaylight.yangtools.yang.data.impl.schema.tree.AbstractNodeContainerModificationStrategy.checkChildPreconditions(AbstractNodeContainerModificationStrategy.java:205)[121:org.opendaylight.yangtools.yang-data-impl:0.7.0.Lithium]
        at org.opendaylight.yangtools.yang.data.impl.schema.tree.AbstractNodeContainerModificationStrategy.checkTouchApplicable(AbstractNodeContainerModificationStrategy.java:189)[121:org.opendaylight.yangtools.yang-data-impl:0.7.0.Lithium]
        at org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaAwareApplyOperation.checkApplicable(SchemaAwareApplyOperation.java:125)[121:org.opendaylight.yangtools.yang-data-impl:0.7.0.Lithium]

Does anyone know what problem?
Thanks,
Ben.
_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@...
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev


Re: Questions about usage/documentation of openflow java library

Madhava Bangera, Raksha <raksha.madhava.bangera@...>
 

Hi Michal,

 

Thanks for your help here J.

 

Do you know which library PacketIn object is a part of?

 

Thanks & Regards,

Raksha

 

From: Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES at Cisco) [mailto:mirehak@...]
Sent: Wednesday, October 14, 2015 8:56 AM
To: Madhava Bangera, Raksha; 'integration-dev@...'; 'openflowjava-dev@...'
Subject: Re: [openflowjava-dev] Questions about usage/documentation of openflow java library

 

Hi Raksha,

I am afraid that ofJava is doing exactly the opposite of your goal. However there is PacketIn object defined (with builder to make the creation more comfortable). But ofJava decodes binary wire protocol to PacketIn and I presume you need to encode PacketIn to binary wire protocol. With flowMods it is the other way round.

 

In OfJava repo there is testing project - simple-client. But it is just a simple machine for sending and checking received binary fragments.

 

 

Regards,

Michal

 


From: openflowjava-dev-bounces@... <openflowjava-dev-bounces@...> on behalf of Madhava Bangera, Raksha <raksha.madhava.bangera@...>
Sent: Wednesday, October 14, 2015 01:22
To: 'integration-dev@...'; 'openflowjava-dev@...'
Subject: [openflowjava-dev] Questions about usage/documentation of openflow java library

 

Hi all,

 

I am working on writing a Java based tool that can benchmark SDN controllers on openflow 1.3 (similar to cbench tool). I am at the point where the program can create fakeswitches and connect to controller.  I want to use  openflowjava library to construct packet-ins and receive the respective flow-mods from the controller. Is there any documentation of how I can use openflowjava library APIs to send hello messages, packet-ins and receive flow-mods. Any pointer to OpenDaylight project files that uses openflowjava library for this functionality would also be helpful.

 

Thanks & Regards,

Raksha


Re: [openflowjava-users] When i install "odl-openflowjava-all" feature in karaf in openflowplugin proejct, I found a problem.

Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES@Cisco) <mirehak@...>
 

Hi Shixing,

could you try with this ofJava revision (not merged yet):


https://git.opendaylight.org/gerrit/27172




Regards,

Michal




From: openflowjava-users-bounces@... <openflowjava-users-bounces@...> on behalf of liushixing <liushixing@...>
Sent: Wednesday, October 14, 2015 10:22
To: openflowjava-users@...; openflowjava-dev@...
Subject: [openflowjava-users] [openflowjava-dev] When i install "odl-openflowjava-all" feature in karaf in openflowplugin proejct, I found a problem.
 

Hi All,

 

       I downloaded the openflowplugin project master from github , compiled it and run the karaf,

 

When I install the  "odl-openflowjava-all"  feature in karaf in openflowplugin project,  An error occurred in the log file as following.

 

After that when I install “odl-openflowplugin-flow-services”, there has been no response all the time in karaf. As if program died.

 

Is it a known problem with the mater version of the plugin ? Could someone give me some suggestions about that problem?

 

 

2015-10-14 15:00:51,533 | ERROR | bundle-tracker-0 | ModuleInfoBundleTracker          | 110 - org.opendaylight.controller.config-manager - 0.4.0.SNAPSHOT | Failed to process bundleentry://247.fwk1761849498/META-INF/services/org.opendaylight.yangtools.yang.binding.YangModelBindingProvider for bundle org.opendaylight.openflowjava.openflow-protocol-api_0.7.0.SNAPSHOT [247]

java.lang.IllegalStateException: Error while executing getModuleInfo on org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.$YangModelBindingProvider@51f35fd2

         at org.opendaylight.controller.config.manager.impl.osgi.mapping.ModuleInfoBundleTracker.retrieveModuleInfo(ModuleInfoBundleTracker.java:144)[110:org.opendaylight.controller.config-manager:0.4.0.SNAPSHOT]

         at org.opendaylight.controller.config.manager.impl.osgi.mapping.ModuleInfoBundleTracker.addingBundle(ModuleInfoBundleTracker.java:84)[110:org.opendaylight.controller.config-manager:0.4.0.SNAPSHOT]

         at org.opendaylight.controller.config.manager.impl.osgi.mapping.ModuleInfoBundleTracker.addingBundle(ModuleInfoBundleTracker.java:32)[110:org.opendaylight.controller.config-manager:0.4.0.SNAPSHOT]

         at org.opendaylight.controller.config.manager.impl.osgi.ExtensibleBundleTracker$1$1.execute(ExtensibleBundleTracker.java:86)[110:org.opendaylight.controller.config-manager:0.4.0.SNAPSHOT]

         at org.opendaylight.controller.config.manager.impl.osgi.ExtensibleBundleTracker.forEachAdditionalBundle(ExtensibleBundleTracker.java:131)[110:org.opendaylight.controller.config-manager:0.4.0.SNAPSHOT]

         at org.opendaylight.controller.config.manager.impl.osgi.ExtensibleBundleTracker.access$100(ExtensibleBundleTracker.java:50)[110:org.opendaylight.controller.config-manager:0.4.0.SNAPSHOT]

         at org.opendaylight.controller.config.manager.impl.osgi.ExtensibleBundleTracker$1.call(ExtensibleBundleTracker.java:83)[110:org.opendaylight.controller.config-manager:0.4.0.SNAPSHOT]

         at java.util.concurrent.FutureTask.run(FutureTask.java:262)[:1.7.0_51]

         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_51]

         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_51]

         at java.lang.Thread.run(Thread.java:744)[:1.7.0_51]

Caused by: java.lang.ExceptionInInitializerError

         at org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.$YangModuleInfoImpl.<init>($YangModuleInfoImpl.java:25)

         at org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.$YangModuleInfoImpl.<clinit>($YangModuleInfoImpl.java:10)

         at org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.$YangModelBindingProvider.getModuleInfo($YangModelBindingProvider.java:6)

         at org.opendaylight.controller.config.manager.impl.osgi.mapping.ModuleInfoBundleTracker.retrieveModuleInfo(ModuleInfoBundleTracker.java:142)[110:org.opendaylight.controller.config-manager:0.4.0.SNAPSHOT]

         ... 10 more

Caused by: java.lang.IllegalStateException: Resource '/META-INF/yang/openflow-instruction.yang' is missing

         at org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.instruction.rev130731.$YangModuleInfoImpl.<init>($YangModuleInfoImpl.java:31)[247:org.opendaylight.openflowjava.openflow-protocol-api:0.7.0.SNAPSHOT]

         at org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.instruction.rev130731.$YangModuleInfoImpl.<clinit>($YangModuleInfoImpl.java:10)[247:org.opendaylight.openflowjava.openflow-protocol-api:0.7.0.SNAPSHOT]

         ... 14 more

 

Regards,

Shixing

 


Re: Questions about usage/documentation of openflow java library

Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES@Cisco) <mirehak@...>
 

Hi Raksha,

I am afraid that ofJava is doing exactly the opposite of your goal. However there is PacketIn object defined (with builder to make the creation more comfortable). But ofJava decodes binary wire protocol to PacketIn and I presume you need to encode PacketIn to binary wire protocol. With flowMods it is the other way round.


In OfJava repo there is testing project - simple-client. But it is just a simple machine for sending and checking received binary fragments.



Regards,

Michal



From: openflowjava-dev-bounces@... <openflowjava-dev-bounces@...> on behalf of Madhava Bangera, Raksha <raksha.madhava.bangera@...>
Sent: Wednesday, October 14, 2015 01:22
To: 'integration-dev@...'; 'openflowjava-dev@...'
Subject: [openflowjava-dev] Questions about usage/documentation of openflow java library
 

Hi all,

 

I am working on writing a Java based tool that can benchmark SDN controllers on openflow 1.3 (similar to cbench tool). I am at the point where the program can create fakeswitches and connect to controller.  I want to use  openflowjava library to construct packet-ins and receive the respective flow-mods from the controller. Is there any documentation of how I can use openflowjava library APIs to send hello messages, packet-ins and receive flow-mods. Any pointer to OpenDaylight project files that uses openflowjava library for this functionality would also be helpful.

 

Thanks & Regards,

Raksha


Re: [controller-dev] Integration distribution failing Single Feature test in master

Lori Jakab <lojakab@...>
 

On 10/14/15 3:28 AM, Luis Gomez wrote:
Thanks Tom for your analysis, lisp and ofjava people, would you mind
taking a look at these comments?
Hi Luis, all,

We just pushed a patch to disable the timeout on the blueprint
container, to allow more time for the services to come up. We've seen
this exception in the past for example when a patch slowed down the
config subsystem as a side effect. It means that in the 5 minutes
default timeout the core mappingservice did not initialize, and didn't
register an implementation of IMappingServiceShell with OSGi.

I have no idea how the test environment handles the exception, so I hope
disabling the timeout will help.

From the other analysis on the thread it looks like lisp is only causing
issues in terms of more heap needed after the additional features were
added, but not in terms of functionality.

-Lori


BR/Luis


On Oct 13, 2015, at 2:31 PM, Tom Pantelis <tompantelis@...
<mailto:tompantelis@...>> wrote:

Comparing to the last successful run on Oct 5th, there's a couple
errors now appearing:

2015-10-13 15:41:51,778 | ERROR | bundle-tracker-0 | ModuleInfoBundleTracker | 131 - org.opendaylight.controller.config-manager - 0.4.0.SNAPSHOT | Failed to process bundleentry://188.fwk532513438/META-INF/services/org.opendaylight.yangtools.yang.binding.YangModelBindingProvider for bundle org.opendaylight.openflowjava.openflow-protocol-api_0.7.0.SNAPSHOT [188]
java.lang.IllegalStateException: Error while executing getModuleInfo on org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.$YangModelBindingProvider@4a0236de
...
Caused by: java.lang.IllegalStateException: Resource '/META-INF/yang/openflow-instruction.yang' is missing
at org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.instruction.rev130731.$YangModuleInfoImpl.<init>($YangModuleInfoImpl.java:31)[188:org.opendaylight.openflowjava.openflow-protocol-api:0.7.0.SNAPSHOT]

This one has been happening for a while but it *seems* to be benign.

2015-10-13 15:48:11,064 | ERROR | rint Extender: 3 | BlueprintContainerImpl | 15 - org.apache.aries.blueprint.core - 1.4.2 | Unable to start blueprint container for bundle org.opendaylight.lispflowmapping.mappingservice.shell due to unresolved dependencies [(objectClass=org.opendaylight.lispflowmapping.interfaces.mappingservice.IMappingServiceShell)]
java.util.concurrent.TimeoutException
at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:336)[15:org.apache.aries.blueprint.core:1.4.2]
at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[15:org.apache.aries.blueprint.core:1.4.2]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_85]
at java.util.concurrent.FutureTask.run(FutureTask.java:262)[:1.7.0_85]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)[:1.7.0_85]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)[:1.7.0_85]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_85]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_85]
at java.lang.Thread.run(Thread.java:745)[:1.7.0_85]
This one appears to emanate from lispflowmapping. It's using
blueprint and appears to import an OSGi
service, IMappingServiceShell, that wasn't found. The default timeout
for blueprint is 5 min but I don't know if the test blocks on this
blueprint container and will fail as a result. Either way it seems
this should be looked at by a lispflowmapping contributor.
There may be other stuff going on. It would be useful to run it by
hand and, when/if it appears stuck, use jstack to get a thread dump.
Also it's hard to tell why the OOM errors are occurring - one of the
tests indicates they started to occur after shutdown was started. For
that it would be useful to get a heap dump via jmap or, better yet,
run the test with the -XX:+HeapDumpOnOutOfMemoryError option enabled
if possible.

On Tue, Oct 13, 2015 at 4:43 PM, Luis Gomez <ecelgp@...
<mailto:ecelgp@...>> wrote:

Look in at more failing distribution jobs, there is always a
timeout in the Single Feature, the distribution used to build in
8 mins while now it takes more than 1 hour.

BR/Luis


On Oct 13, 2015, at 12:13 PM, Luis Gomez <ecelgp@...
<mailto:ecelgp@...>> wrote:

Hi all,

I just observed the distribution in master is failing since Oct
6th [1]. Last errors [2] show memory issues like below but I am
not sure this is the root cause for this. Can anyone help
identifying the problem here?

Thanks/Luis

[1] https://jenkins.opendaylight.org/releng/view/yangtools/job/yangtools-distribution-beryllium/
[2]
https://jenkins.opendaylight.org/releng/view/yangtools/job/yangtools-distribution-beryllium/444/testReport/

Exception in thread "qtp1815616686-79" java.lang.OutOfMemoryError: GC overhead limit exceeded
at java.util.HashMap.newKeyIterator(HashMap.java:968)
at java.util.HashMap$KeySet.iterator(HashMap.java:1002)
at java.util.HashSet.iterator(HashSet.java:170)
at sun.nio.ch.Util$2.iterator(Util.java:303)
at org.eclipse.jetty.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:600)
at org.eclipse.jetty.io.nio.SelectorManager$1.run(SelectorManager.java:290)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
at java.lang.Thread.run(Thread.java:745)

Exception in thread "Timer-0" java.lang.OutOfMemoryError: Java heap space
at java.io.BufferedReader.<init>(BufferedReader.java:98)
at java.io.BufferedReader.<init>(BufferedReader.java:109)
at java.io.LineNumberReader.<init>(LineNumberReader.java:72)
at org.apache.felix.utils.properties.Properties$PropertiesReader.<init>(Properties.java:748)
at org.apache.felix.utils.properties.Properties.loadLayout(Properties.java:352)
at org.apache.felix.utils.properties.Properties.load(Properties.java:142)
at org.apache.felix.utils.properties.Properties.load(Properties.java:138)
at org.apache.felix.utils.properties.Properties.load(Properties.java:122)
at org.apache.felix.utils.properties.Properties.<init>(Properties.java:107)
at org.apache.felix.utils.properties.Properties.<init>(Properties.java:96)
at org.apache.karaf.jaas.modules.properties.AutoEncryptionSupport$1.run(AutoEncryptionSupport.java:63)
Exception in thread "INT-2,ISPN,rk-c7-merge-6c0-16483" at java.util.TimerThread.mainLoop(Timer.java:555)
at java.util.TimerThread.run(Timer.java:505)
java.lang.OutOfMemoryError: Java heap space
at org.jgroups.util.Util.readLongSequence(Util.java:2235)
at org.jgroups.util.Digest.readFrom(Digest.java:166)
at org.jgroups.util.Digest.readFrom(Digest.java:154)
at org.jgroups.util.Util.readStreamable(Util.java:1105)
at org.jgroups.util.Util.streamableFromBuffer(Util.java:773)
at org.jgroups.protocols.pbcast.STABLE.readDigest(STABLE.java:695)
at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:237)
at org.jgroups.protocols.UNICAST2.up(UNICAST2.java:448)
at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:636)
at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:147)
at org.jgroups.protocols.FD.up(FD.java:255)
at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:301)
at org.jgroups.protocols.MERGE2.up(MERGE2.java:209)
at org.jgroups.protocols.Discovery.up(Discovery.java:379)
at org.jgroups.protocols.TP.passMessageUp(TP.java:1399)
at org.jgroups.protocols.TP <http://org.jgroups.protocols.tp/>$4.run(TP.java:1327)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Exception in thread "qtp431119273-318" java.lang.OutOfMemoryError: GC overhead limit exceeded
Exception in thread "qtp431119273-85" java.lang.OutOfMemoryError: GC overhead limit exceeded
Exception in thread "RMI RenewClean-[10.30.11.239:44444 <http://10.30.11.239:44444/>]" java.lang.OutOfMemoryError: GC overhead limit exceeded
Exception in thread "Thread-2" java.lang.OutOfMemoryError: Java heap space



_______________________________________________
controller-dev mailing list
controller-dev@...
<mailto:controller-dev@...>
https://lists.opendaylight.org/mailman/listinfo/controller-dev



_______________________________________________
controller-dev mailing list
controller-dev@...
https://lists.opendaylight.org/mailman/listinfo/controller-dev


[openflowjava-users] When i install "odl-openflowjava-all" feature in karaf in openflowplugin proejct, I found a problem.

liushixing
 

Hi All,

 

       I downloaded the openflowplugin project master from github , compiled it and run the karaf,

 

When I install the  "odl-openflowjava-all"  feature in karaf in openflowplugin project,  An error occurred in the log file as following.

 

After that when I install “odl-openflowplugin-flow-services”, there has been no response all the time in karaf. As if program died.

 

Is it a known problem with the mater version of the plugin ? Could someone give me some suggestions about that problem?

 

 

2015-10-14 15:00:51,533 | ERROR | bundle-tracker-0 | ModuleInfoBundleTracker          | 110 - org.opendaylight.controller.config-manager - 0.4.0.SNAPSHOT | Failed to process bundleentry://247.fwk1761849498/META-INF/services/org.opendaylight.yangtools.yang.binding.YangModelBindingProvider for bundle org.opendaylight.openflowjava.openflow-protocol-api_0.7.0.SNAPSHOT [247]

java.lang.IllegalStateException: Error while executing getModuleInfo on org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.$YangModelBindingProvider@51f35fd2

         at org.opendaylight.controller.config.manager.impl.osgi.mapping.ModuleInfoBundleTracker.retrieveModuleInfo(ModuleInfoBundleTracker.java:144)[110:org.opendaylight.controller.config-manager:0.4.0.SNAPSHOT]

         at org.opendaylight.controller.config.manager.impl.osgi.mapping.ModuleInfoBundleTracker.addingBundle(ModuleInfoBundleTracker.java:84)[110:org.opendaylight.controller.config-manager:0.4.0.SNAPSHOT]

         at org.opendaylight.controller.config.manager.impl.osgi.mapping.ModuleInfoBundleTracker.addingBundle(ModuleInfoBundleTracker.java:32)[110:org.opendaylight.controller.config-manager:0.4.0.SNAPSHOT]

         at org.opendaylight.controller.config.manager.impl.osgi.ExtensibleBundleTracker$1$1.execute(ExtensibleBundleTracker.java:86)[110:org.opendaylight.controller.config-manager:0.4.0.SNAPSHOT]

         at org.opendaylight.controller.config.manager.impl.osgi.ExtensibleBundleTracker.forEachAdditionalBundle(ExtensibleBundleTracker.java:131)[110:org.opendaylight.controller.config-manager:0.4.0.SNAPSHOT]

         at org.opendaylight.controller.config.manager.impl.osgi.ExtensibleBundleTracker.access$100(ExtensibleBundleTracker.java:50)[110:org.opendaylight.controller.config-manager:0.4.0.SNAPSHOT]

         at org.opendaylight.controller.config.manager.impl.osgi.ExtensibleBundleTracker$1.call(ExtensibleBundleTracker.java:83)[110:org.opendaylight.controller.config-manager:0.4.0.SNAPSHOT]

         at java.util.concurrent.FutureTask.run(FutureTask.java:262)[:1.7.0_51]

         at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_51]

         at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_51]

         at java.lang.Thread.run(Thread.java:744)[:1.7.0_51]

Caused by: java.lang.ExceptionInInitializerError

         at org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.$YangModuleInfoImpl.<init>($YangModuleInfoImpl.java:25)

         at org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.$YangModuleInfoImpl.<clinit>($YangModuleInfoImpl.java:10)

         at org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.$YangModelBindingProvider.getModuleInfo($YangModelBindingProvider.java:6)

         at org.opendaylight.controller.config.manager.impl.osgi.mapping.ModuleInfoBundleTracker.retrieveModuleInfo(ModuleInfoBundleTracker.java:142)[110:org.opendaylight.controller.config-manager:0.4.0.SNAPSHOT]

         ... 10 more

Caused by: java.lang.IllegalStateException: Resource '/META-INF/yang/openflow-instruction.yang' is missing

         at org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.instruction.rev130731.$YangModuleInfoImpl.<init>($YangModuleInfoImpl.java:31)[247:org.opendaylight.openflowjava.openflow-protocol-api:0.7.0.SNAPSHOT]

         at org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.instruction.rev130731.$YangModuleInfoImpl.<clinit>($YangModuleInfoImpl.java:10)[247:org.opendaylight.openflowjava.openflow-protocol-api:0.7.0.SNAPSHOT]

         ... 14 more

 

Regards,

Shixing

 


Re: [controller-dev] Integration distribution failing Single Feature test in master

Luis Gomez <ecelgp@...>
 

Thanks Tom for your analysis, lisp and ofjava people, would you mind taking a look at these comments?

BR/Luis


On Oct 13, 2015, at 2:31 PM, Tom Pantelis <tompantelis@...> wrote:

Comparing to the last successful run on Oct 5th, there's a couple errors now appearing:

2015-10-13 15:41:51,778 | ERROR | bundle-tracker-0 | ModuleInfoBundleTracker          | 131 - org.opendaylight.controller.config-manager - 0.4.0.SNAPSHOT | Failed to process bundleentry://188.fwk532513438/META-INF/services/org.opendaylight.yangtools.yang.binding.YangModelBindingProvider for bundle org.opendaylight.openflowjava.openflow-protocol-api_0.7.0.SNAPSHOT [188]
java.lang.IllegalStateException: Error while executing getModuleInfo on org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.$YangModelBindingProvider@4a0236de
...
Caused by: java.lang.IllegalStateException: Resource '/META-INF/yang/openflow-instruction.yang' is missing
	at org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.common.instruction.rev130731.$YangModuleInfoImpl.<init>($YangModuleInfoImpl.java:31)[188:org.opendaylight.openflowjava.openflow-protocol-api:0.7.0.SNAPSHOT]
	

This one has been happening for a while but it *seems* to be benign.


2015-10-13 15:48:11,064 | ERROR | rint Extender: 3 | BlueprintContainerImpl           | 15 - org.apache.aries.blueprint.core - 1.4.2 | Unable to start blueprint container for bundle org.opendaylight.lispflowmapping.mappingservice.shell due to unresolved dependencies [(objectClass=org.opendaylight.lispflowmapping.interfaces.mappingservice.IMappingServiceShell)]
java.util.concurrent.TimeoutException
	at org.apache.aries.blueprint.container.BlueprintContainerImpl$1.run(BlueprintContainerImpl.java:336)[15:org.apache.aries.blueprint.core:1.4.2]
	at org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[15:org.apache.aries.blueprint.core:1.4.2]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.7.0_85]
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)[:1.7.0_85]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)[:1.7.0_85]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)[:1.7.0_85]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_85]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_85]
	at java.lang.Thread.run(Thread.java:745)[:1.7.0_85]

This one appears to emanate from lispflowmapping. It's using blueprint and appears to import an OSGi service, IMappingServiceShell, that wasn't found. The default timeout for blueprint is 5 min but I don't know if the test blocks on this blueprint container and will fail as a result. Either way it seems this should be looked at by a lispflowmapping contributor.

There may be other stuff going on. It would be useful to run it by hand and, when/if it appears stuck, use jstack to get a thread dump. Also it's hard to tell why the OOM errors are occurring - one of the tests indicates they started to occur after shutdown was started. For that it would be useful to get a heap dump via jmap or, better yet, run the test with the -XX:+HeapDumpOnOutOfMemoryError option enabled if possible.

On Tue, Oct 13, 2015 at 4:43 PM, Luis Gomez <ecelgp@...> wrote:
Look in at more failing distribution jobs, there is always a timeout in the Single Feature, the distribution used to build in 8 mins while now it takes more than 1 hour.

BR/Luis


On Oct 13, 2015, at 12:13 PM, Luis Gomez <ecelgp@...> wrote:

Hi all,

I just observed the distribution in master is failing since Oct 6th [1]. Last errors [2] show memory issues like below but I am not sure this is the root cause for this. Can anyone help identifying the problem here?

Thanks/Luis 


Exception in thread "qtp1815616686-79" java.lang.OutOfMemoryError: GC overhead limit exceeded
	at java.util.HashMap.newKeyIterator(HashMap.java:968)
	at java.util.HashMap$KeySet.iterator(HashMap.java:1002)
	at java.util.HashSet.iterator(HashSet.java:170)
	at sun.nio.ch.Util$2.iterator(Util.java:303)
	at org.eclipse.jetty.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:600)
	at org.eclipse.jetty.io.nio.SelectorManager$1.run(SelectorManager.java:290)
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
	at java.lang.Thread.run(Thread.java:745)

Exception in thread "Timer-0" java.lang.OutOfMemoryError: Java heap space
	at java.io.BufferedReader.<init>(BufferedReader.java:98)
	at java.io.BufferedReader.<init>(BufferedReader.java:109)
	at java.io.LineNumberReader.<init>(LineNumberReader.java:72)
	at org.apache.felix.utils.properties.Properties$PropertiesReader.<init>(Properties.java:748)
	at org.apache.felix.utils.properties.Properties.loadLayout(Properties.java:352)
	at org.apache.felix.utils.properties.Properties.load(Properties.java:142)
	at org.apache.felix.utils.properties.Properties.load(Properties.java:138)
	at org.apache.felix.utils.properties.Properties.load(Properties.java:122)
	at org.apache.felix.utils.properties.Properties.<init>(Properties.java:107)
	at org.apache.felix.utils.properties.Properties.<init>(Properties.java:96)
	at org.apache.karaf.jaas.modules.properties.AutoEncryptionSupport$1.run(AutoEncryptionSupport.java:63)
Exception in thread "INT-2,ISPN,rk-c7-merge-6c0-16483" 	at java.util.TimerThread.mainLoop(Timer.java:555)
	at java.util.TimerThread.run(Timer.java:505)
java.lang.OutOfMemoryError: Java heap space
	at org.jgroups.util.Util.readLongSequence(Util.java:2235)
	at org.jgroups.util.Digest.readFrom(Digest.java:166)
	at org.jgroups.util.Digest.readFrom(Digest.java:154)
	at org.jgroups.util.Util.readStreamable(Util.java:1105)
	at org.jgroups.util.Util.streamableFromBuffer(Util.java:773)
	at org.jgroups.protocols.pbcast.STABLE.readDigest(STABLE.java:695)
	at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:237)
	at org.jgroups.protocols.UNICAST2.up(UNICAST2.java:448)
	at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:636)
	at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:147)
	at org.jgroups.protocols.FD.up(FD.java:255)
	at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:301)
	at org.jgroups.protocols.MERGE2.up(MERGE2.java:209)
	at org.jgroups.protocols.Discovery.up(Discovery.java:379)
	at org.jgroups.protocols.TP.passMessageUp(TP.java:1399)
	at org.jgroups.protocols.TP$4.run(TP.java:1327)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
Exception in thread "qtp431119273-318" java.lang.OutOfMemoryError: GC overhead limit exceeded
Exception in thread "qtp431119273-85" java.lang.OutOfMemoryError: GC overhead limit exceeded
Exception in thread "RMI RenewClean-[10.30.11.239:44444]" java.lang.OutOfMemoryError: GC overhead limit exceeded
Exception in thread "Thread-2" java.lang.OutOfMemoryError: Java heap space





_______________________________________________
controller-dev mailing list
controller-dev@...
https://lists.opendaylight.org/mailman/listinfo/controller-dev




Questions about usage/documentation of openflow java library

Madhava Bangera, Raksha <raksha.madhava.bangera@...>
 

Hi all,

 

I am working on writing a Java based tool that can benchmark SDN controllers on openflow 1.3 (similar to cbench tool). I am at the point where the program can create fakeswitches and connect to controller.  I want to use  openflowjava library to construct packet-ins and receive the respective flow-mods from the controller. Is there any documentation of how I can use openflowjava library APIs to send hello messages, packet-ins and receive flow-mods. Any pointer to OpenDaylight project files that uses openflowjava library for this functionality would also be helpful.

 

Thanks & Regards,

Raksha


Re: Ordering of multipart reply messages with the same transaction ID

Vitaliy Nazaryants <vinazaryants@...>
 

Thanks a lot for your reply, we'll try to do some hacking before we can migrate to Li.

On Fri, Oct 9, 2015 at 4:32 PM, Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES at Cisco) <mirehak@...> wrote:

Hi Vitaly,


yes - this can happen because notifications are delivered by md-dal and it depends in internal implementation there if multiple threads are involved which could result into random delivery order.


This is covered in Li-codebase of ofPlugin where complete statistics are atomically written into dataStore and apps are expected to listen to dataChangeNotifications.


https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:He_vs_Li_comparison



Regards,

Michal



From: openflowjava-dev-bounces@... <openflowjava-dev-bounces@...> on behalf of Vitaliy Nazaryants <vinazaryants@...>
Sent: Friday, October 9, 2015 11:41
To: openflowplugin-dev@...
Cc: openflowjava-dev@...
Subject: [openflowjava-dev] Ordering of multipart reply messages with the same transaction ID
 
Hello,

   We use flow statistics requests to track the flows currently installed on the switches. When the number of flows on a switch is large, the controller receives several multipart replies for one request, and it turns out that somehow the order of notifications for these replies is not stable. We listen to the FlowsStatisticsUpdate notifications having the necessary transaction ID and track the OFPMPF_REQ_MORE flag to find the last reply in the sequence, but, although the switches send replies in the correct order (if I may say so, but at least OFPMPF_REQ_MORE = 0 is in the last reply), the order of FlowsStatisticsUpdate notifications is such that sometimes the notification with OFPMPF_REQ_MORE = 0 is in the middle of the sequence, and can even become the first one.
  Is this a known problem? Can someone suggest a way to ensure the correct order of replies / notifications in this case, at least the one with OFPMPF_REQ_MORE = 0 always being the last one? Thank you in advance.

--
-- 
Best Regards,
Vitaly Nazaryants
Software Engineer, Mirantis Inc.
Work phone: +7(8452) 674 555
Cell phone: +7917 215 9329
Skype: newalias



--
-- 
Best Regards,
Vitaly Nazaryants
Software Engineer, Mirantis Inc.
Work phone: +7(8452) 674 555
Cell phone: +7917 215 9329
Skype: newalias


Re: Ordering of multipart reply messages with the same transaction ID

Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES@Cisco) <mirehak@...>
 

Hi Vitaly,


yes - this can happen because notifications are delivered by md-dal and it depends in internal implementation there if multiple threads are involved which could result into random delivery order.


This is covered in Li-codebase of ofPlugin where complete statistics are atomically written into dataStore and apps are expected to listen to dataChangeNotifications.


https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:He_vs_Li_comparison



Regards,

Michal



From: openflowjava-dev-bounces@... <openflowjava-dev-bounces@...> on behalf of Vitaliy Nazaryants <vinazaryants@...>
Sent: Friday, October 9, 2015 11:41
To: openflowplugin-dev@...
Cc: openflowjava-dev@...
Subject: [openflowjava-dev] Ordering of multipart reply messages with the same transaction ID
 
Hello,

   We use flow statistics requests to track the flows currently installed on the switches. When the number of flows on a switch is large, the controller receives several multipart replies for one request, and it turns out that somehow the order of notifications for these replies is not stable. We listen to the FlowsStatisticsUpdate notifications having the necessary transaction ID and track the OFPMPF_REQ_MORE flag to find the last reply in the sequence, but, although the switches send replies in the correct order (if I may say so, but at least OFPMPF_REQ_MORE = 0 is in the last reply), the order of FlowsStatisticsUpdate notifications is such that sometimes the notification with OFPMPF_REQ_MORE = 0 is in the middle of the sequence, and can even become the first one.
  Is this a known problem? Can someone suggest a way to ensure the correct order of replies / notifications in this case, at least the one with OFPMPF_REQ_MORE = 0 always being the last one? Thank you in advance.

--
-- 
Best Regards,
Vitaly Nazaryants
Software Engineer, Mirantis Inc.
Work phone: +7(8452) 674 555
Cell phone: +7917 215 9329
Skype: newalias


Ordering of multipart reply messages with the same transaction ID

Vitaliy Nazaryants <vinazaryants@...>
 

Hello,

   We use flow statistics requests to track the flows currently installed on the switches. When the number of flows on a switch is large, the controller receives several multipart replies for one request, and it turns out that somehow the order of notifications for these replies is not stable. We listen to the FlowsStatisticsUpdate notifications having the necessary transaction ID and track the OFPMPF_REQ_MORE flag to find the last reply in the sequence, but, although the switches send replies in the correct order (if I may say so, but at least OFPMPF_REQ_MORE = 0 is in the last reply), the order of FlowsStatisticsUpdate notifications is such that sometimes the notification with OFPMPF_REQ_MORE = 0 is in the middle of the sequence, and can even become the first one.
  Is this a known problem? Can someone suggest a way to ensure the correct order of replies / notifications in this case, at least the one with OFPMPF_REQ_MORE = 0 always being the last one? Thank you in advance.

--
-- 
Best Regards,
Vitaly Nazaryants
Software Engineer, Mirantis Inc.
Work phone: +7(8452) 674 555
Cell phone: +7917 215 9329
Skype: newalias


Re: [OpenDaylight Discuss] Run time error for bundle openflowjava.openflow-protocol-api_0.7.0.SNAPSHOT

Yang, Yi Y
 

Michal, thank you so much for pointing out this gbp workaround, I took some efforts to fix it, but finally I found it is an openflowjava issue :-)

-----Original Message-----
From: openflowjava-dev-bounces@... [mailto:openflowjava-dev-bounces@...] On Behalf Of Michal Polkoráb
Sent: Friday, October 09, 2015 3:28 PM
To: Tony Tkacik -X (ttkacik - PANTHEON TECHNOLOGIES at Cisco); Mahajani, Saket M; discuss@...
Cc: openflowjava-dev@...
Subject: Re: [openflowjava-dev] [OpenDaylight Discuss] Run time error for bundle openflowjava.openflow-protocol-api_0.7.0.SNAPSHOT

Hello,

there is already opened bug for this issue here: https://bugs.opendaylight.org/show_bug.cgi?id=4281.
Openflowjava yang files are hidden intentionally, because of API leak and related problems in DLUX project. The problem occurs if a project has dependency on OFjava (direct or indirect) and the project wants to have junit tests extending AbstractDataBrokerTest. Since more and more projects want to use this functionality, we probably have to find some solution in DLUX project.

In the meantime, one can use workaround similar to the one present in GBP project: https://git.opendaylight.org/gerrit/gitweb?p=groupbasedpolicy.git;a=blob;f=neutron-mapper/src/test/java/org/opendaylight/groupbasedpolicy/neutron/mapper/test/GbpDataBrokerTest.java;h=70de32704cb86467bcd76e3f2c7c620c70b6fa96;hb=refs/heads/stable/lithium

Regards,
Michal Polkorab
________________________________________
From: Tony Tkacik -X (ttkacik - PANTHEON TECHNOLOGIES at Cisco) <ttkacik@...>
Sent: 09 October 2015 08:49
To: Mahajani, Saket M; discuss@...
Cc: openflowjava-dev@...
Subject: Re: [OpenDaylight Discuss] Run time error for bundle openflowjava.openflow-protocol-api_0.7.0.SNAPSHOT

Hi, could you please open bug against openflowjava? Seems they are modifying their bundle manually to not include Yang models (and YangModelBindingPRovider class relies on yang model being resource, since they are both generated And packaged together by design).

Tony

-----Original Message-----
From: discuss-bounces@... [mailto:discuss-bounces@...] On Behalf Of Mahajani, Saket M
Sent: Friday, October 09, 2015 12:43 AM
To: discuss@...
Subject: [OpenDaylight Discuss] Run time error for bundle openflowjava.openflow-protocol-api_0.7.0.SNAPSHOT

Hi guys,
I came across this runtime error today on one of the openflowjava dependencies:

ERROR | bundle-tracker-0 | ModuleInfoBundleTracker | 110 - org.opendaylight.controller.config-manager - 0.4.0.SNAPSHOT | Failed to process bundleentry://241.fwk1700966106/META-INF/services/org.opendaylight.yangtools.yang.binding.YangModelBindingProvider for bundle org.opendaylight.openflowjava.openflow-protocol-api_0.7.0.SNAPSHOT [241]
java.lang.IllegalStateException: Error while executing getModuleInfo on org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.$YangModelBindingProvider@20d3a056

Has anyone come across this today? Seems to be related to Yang tools but I'm not sure.
Thanks,

Saket Mahajani
_______________________________________________
Discuss mailing list
Discuss@...
https://lists.opendaylight.org/mailman/listinfo/discuss
_______________________________________________
Discuss mailing list
Discuss@...
https://lists.opendaylight.org/mailman/listinfo/discuss
MichalPolkoráb
Software Developer

Sídlo / Mlynské Nivy 56 / 821 05 Bratislava / Slovakia R&D centrum / Janka Kráľa 9 / 974 01 Banská Bystrica / Slovakia
+421 918 378 907 / michal.polkorab@...
reception: +421 2 206 65 114 / www.pantheon.sk

[logo]


_______________________________________________
openflowjava-dev mailing list
openflowjava-dev@...
https://lists.opendaylight.org/mailman/listinfo/openflowjava-dev


Re: [OpenDaylight Discuss] Run time error for bundle openflowjava.openflow-protocol-api_0.7.0.SNAPSHOT

Michal Polkorab
 

Hello,

there is already opened bug for this issue here: https://bugs.opendaylight.org/show_bug.cgi?id=4281.
Openflowjava yang files are hidden intentionally, because of API leak and related problems in DLUX project. The problem occurs if a project has dependency on OFjava (direct or indirect) and the project wants to have junit tests extending AbstractDataBrokerTest. Since more and more projects want to use this functionality, we probably have to find some solution in DLUX project.

In the meantime, one can use workaround similar to the one present in GBP project: https://git.opendaylight.org/gerrit/gitweb?p=groupbasedpolicy.git;a=blob;f=neutron-mapper/src/test/java/org/opendaylight/groupbasedpolicy/neutron/mapper/test/GbpDataBrokerTest.java;h=70de32704cb86467bcd76e3f2c7c620c70b6fa96;hb=refs/heads/stable/lithium

Regards,
Michal Polkorab
________________________________________
From: Tony Tkacik -X (ttkacik - PANTHEON TECHNOLOGIES at Cisco) <ttkacik@...>
Sent: 09 October 2015 08:49
To: Mahajani, Saket M; discuss@...
Cc: openflowjava-dev@...
Subject: Re: [OpenDaylight Discuss] Run time error for bundle openflowjava.openflow-protocol-api_0.7.0.SNAPSHOT

Hi, could you please open bug against openflowjava? Seems they are modifying their bundle manually to not include
Yang models (and YangModelBindingPRovider class relies on yang model being resource, since they are both generated
And packaged together by design).

Tony

-----Original Message-----
From: discuss-bounces@... [mailto:discuss-bounces@...] On Behalf Of Mahajani, Saket M
Sent: Friday, October 09, 2015 12:43 AM
To: discuss@...
Subject: [OpenDaylight Discuss] Run time error for bundle openflowjava.openflow-protocol-api_0.7.0.SNAPSHOT

Hi guys,
I came across this runtime error today on one of the openflowjava dependencies:

ERROR | bundle-tracker-0 | ModuleInfoBundleTracker | 110 - org.opendaylight.controller.config-manager - 0.4.0.SNAPSHOT | Failed to process bundleentry://241.fwk1700966106/META-INF/services/org.opendaylight.yangtools.yang.binding.YangModelBindingProvider for bundle org.opendaylight.openflowjava.openflow-protocol-api_0.7.0.SNAPSHOT [241]
java.lang.IllegalStateException: Error while executing getModuleInfo on org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.$YangModelBindingProvider@20d3a056

Has anyone come across this today? Seems to be related to Yang tools but I'm not sure.
Thanks,

Saket Mahajani
_______________________________________________
Discuss mailing list
Discuss@...
https://lists.opendaylight.org/mailman/listinfo/discuss
_______________________________________________
Discuss mailing list
Discuss@...
https://lists.opendaylight.org/mailman/listinfo/discuss
MichalPolkoráb
Software Developer

Sídlo / Mlynské Nivy 56 / 821 05 Bratislava / Slovakia
R&D centrum / Janka Kráľa 9 / 974 01 Banská Bystrica / Slovakia
+421 918 378 907 / michal.polkorab@...
reception: +421 2 206 65 114 / www.pantheon.sk

[logo]


Re: [OpenDaylight Discuss] Run time error for bundle openflowjava.openflow-protocol-api_0.7.0.SNAPSHOT

Tony Tkacik
 

Hi, could you please open bug against openflowjava? Seems they are modifying their bundle manually to not include
Yang models (and YangModelBindingPRovider class relies on yang model being resource, since they are both generated
And packaged together by design).

Tony

-----Original Message-----
From: discuss-bounces@... [mailto:discuss-bounces@...] On Behalf Of Mahajani, Saket M
Sent: Friday, October 09, 2015 12:43 AM
To: discuss@...
Subject: [OpenDaylight Discuss] Run time error for bundle openflowjava.openflow-protocol-api_0.7.0.SNAPSHOT

Hi guys,
I came across this runtime error today on one of the openflowjava dependencies:

ERROR | bundle-tracker-0 | ModuleInfoBundleTracker | 110 - org.opendaylight.controller.config-manager - 0.4.0.SNAPSHOT | Failed to process bundleentry://241.fwk1700966106/META-INF/services/org.opendaylight.yangtools.yang.binding.YangModelBindingProvider for bundle org.opendaylight.openflowjava.openflow-protocol-api_0.7.0.SNAPSHOT [241]
java.lang.IllegalStateException: Error while executing getModuleInfo on org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.$YangModelBindingProvider@20d3a056

Has anyone come across this today? Seems to be related to Yang tools but I'm not sure.
Thanks,

Saket Mahajani
_______________________________________________
Discuss mailing list
Discuss@...
https://lists.opendaylight.org/mailman/listinfo/discuss


Re: How to acquire a SwitchConnectionProvider instance

Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES@Cisco) <mirehak@...>
 

Hi Arthur,

wiring between nicira extension is defined here:

<openFlowPlugin>/extension/openflowplugin-extension-nicira-config/src/main/resources/initial/43-openflowjava-nx-config.xml


There are ofJava and ofPlugin parts. OfJava consists of 2 modules (1 service, 1 module using this service) and ofPlugin is 1 module.



Regards,

Michal



From: openflowjava-dev-bounces@... <openflowjava-dev-bounces@...> on behalf of Arthur Castonguay <arthur@...>
Sent: Tuesday, October 6, 2015 16:23
To: openflowjava-dev@...
Subject: [openflowjava-dev] How to acquire a SwitchConnectionProvider instance
 
Hey all,

Looking to add a custom serializer/deserializer.  I've managed to get that code done by following a page in the wiki:

https://wiki.opendaylight.org/view/Openflow_Protocol_Library:Openflow_Protocol_Library's_extensibility:Basic_Principle_%26_Example.

One of the last paragraphs mentions the methods to call but completely ignores how to get a handle to one of these switch connection provider instances.  I've been digging around to no avail.  Any guidance on this would be appreciated.

/a


How to acquire a SwitchConnectionProvider instance

Arthur Castonguay <arthur@...>
 

Hey all,

Looking to add a custom serializer/deserializer.  I've managed to get that code done by following a page in the wiki:

https://wiki.opendaylight.org/view/Openflow_Protocol_Library:Openflow_Protocol_Library's_extensibility:Basic_Principle_%26_Example.

One of the last paragraphs mentions the methods to call but completely ignores how to get a handle to one of these switch connection provider instances.  I've been digging around to no avail.  Any guidance on this would be appreciated.

/a


Arbitrary mask matching

John Schistos <jschistos@...>
 

Hello, I want to make a contribution to the open source project.I want to implement the arbitrary mask matching of incoming packets.I want help on finding where this match happens.Any ideas?


Re: [openflowplugin-dev] Switch didn't register to controller in opendaylight controller (Lithium) and Openvswitch 2.4.0?

Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES@Cisco) <mirehak@...>
 

Hi Ben,
this is caused by table-features. Please file a bug to openflowjava.
You might workaround this issue by downgrading to 2.3.x version of openvswitch (there are table-features not supported).

And just to defend ofjava a bit - by cpqd switch there are table-features supported and it works. Ovs-2.4 is the first version of ovs with table-features and message content is probably more complicated.


Regards,
Michal


From: openflowplugin-dev-bounces@... [openflowplugin-dev-bounces@...] on behalf of 鐘晧文 [hnaxiorll@...]
Sent: Friday, September 25, 2015 02:11
To: openflowplugin-dev@...
Subject: [openflowplugin-dev] Switch didn't register to controller in opendaylight controller (Lithium) and Openvswitch 2.4.0?

Hi all,

I use the openvswitch 2.4.0 and opendaylight controller (Lithium).

Then, I install these feature odl-dlux-all, odl-restconf-all, odl-mdsal-apidocs, and odl-openflowplugin-all-li in ODL.

Next, I create a bridge and set controller but I can't see any switch node in web.

The OVS shows that `Controller "tcp:192.168.5.131:6633is_connected: true` (ovs-vsctl show).

The log of ODL shows a lot of warn and some error:

2015-09-24 18:17:02,718 | INFO  | entLoopGroup-8-4 | DeviceManagerImpl                | 279 - org.opendaylight.openflowplugin.impl - 0.1.0.Lithium | Static node Uri [_value=openflow:134303595078473] info: OFPMPGROUPFEATURES collected
2015-09-24 18:17:02,719 | TRACE | entLoopGroup-8-4 | OpenflowProtocolListenerFullImpl | 279 - org.opendaylight.openflowplugin.impl - 0.1.0.Lithium | Multipart Reply with XID: 2
2015-09-24 18:17:02,732 | WARN  | entLoopGroup-8-4 | OFDecoder                        | 276 - org.opendaylight.openflowjava.openflow-protocol-impl - 0.6.0.Lithium | Message deserialization failed
java.lang.IllegalStateException: Deserializer for key: msgVersion: 4 objectClass: org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.oxm.rev150225.match.entries.grouping.MatchEntry msgType: 1 oxm_field: 31 experimenterID: null was not found - please verify that all needed deserializers ale loaded correctly
        at org.opendaylight.openflowjava.protocol.impl.deserialization.DeserializerRegistryImpl.getDeserializer(DeserializerRegistryImpl.java:64)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.util.ListDeserializer.deserializeHeaders(ListDeserializer.java:71)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.deserialization.factories.MultipartReplyMessageFactory.createTableFeaturesProperties(MultipartReplyMessageFactory.java:426)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.deserialization.factories.MultipartReplyMessageFactory.setTableFeatures(MultipartReplyMessageFactory.java:361)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.deserialization.factories.MultipartReplyMessageFactory.deserialize(MultipartReplyMessageFactory.java:216)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.deserialization.factories.MultipartReplyMessageFactory.deserialize(MultipartReplyMessageFactory.java:146)[276:org.opendaylight.openflowjava.openflow-protocol-impl:0.6.0.Lithium]
        at org.opendaylight.openflowjava.protocol.impl.deserialization.DeserializationFactory.deserialize(DeserializationFactory.java:53)[276:org.opendaylight.openflowjava.openflow-pr
...
2015-09-24 18:17:03,251 | DEBUG | entLoopGroup-8-4 | RpcContextImpl                   | 279 - org.opendaylight.openflowplugin.impl - 0.1.0.Lithium | Registration of service interface org.opendaylight.yang.gen.v1.urn.opendaylight.flow.statistics.rev130819.OpendaylightFlowStatisticsService for device KeyedInstanceIdentifier{targetType=interface org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node, path=[org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.Nodes, org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node[key=NodeKey [_id=Uri [_value=openflow:134303595078473]]]]}.
2015-09-24 18:17:03,252 | TRACE | entLoopGroup-8-4 | OpenflowProtocolListenerFullImpl | 279 - org.opendaylight.openflowplugin.impl - 0.1.0.Lithium | Multipart Reply with XID: 11
2015-09-24 18:17:03,253 | ERROR | lt-dispatcher-14 | Shard                            | 208 - org.opendaylight.controller.sal-akka-raft - 1.2.0.Lithium | member-1-shard-inventory-operational An exception occurred while preCommitting transaction member-1-chn-15-txn-1
java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: Metadata not available for modification NodeModification [identifier=(urn:opendaylight:flow:inventory?revision=2013-08-19)table[{(urn:opendaylight:flow:inventory?revision=2013-08-19)id=140}], modificationType=TOUCH, childModification={AugmentationIdentifier{childNames=[(urn:opendaylight:flow:table:statistics?revision=2013-12-15)flow-table-statistics]}=NodeModification [identifier=AugmentationIdentifier{childNames=[(urn:opendaylight:flow:table:statistics?revision=2013-12-15)flow-table-statistics]}, modificationType=TOUCH, childModification={(urn:opendaylight:flow:table:statistics?revision=2013-12-15)flow-table-statistics=NodeModification [identifier=(urn:opendaylight:flow:table:statistics?revision=2013-12-15)flow-table-statistics, modificationType=WRITE, childModification={}]}]}]
        at com.google.common.util.concurrent.Futures$ImmediateFailedFuture.get(Futures.java:190)[97:com.google.guava:18.0.0]
        at org.opendaylight.controller.cluster.datastore.ShardCommitCoordinator.doCommit(ShardCommitCoordinator.java:357)[215:org.opendaylight.controller.sal-distributed-datastore:1.2.0.Lithium]
        at org.opendaylight.controller.cluster.datastore.ShardCommitCoordinator.doCanCommit(ShardCommitCoordinator.java:316)[215:org.opend
...
2015-09-24 18:17:06,282 | WARN  | lt-dispatcher-16 | SimpleShardDataTreeCohort        | 215 - org.opendaylight.controller.sal-distributed-datastore - 1.2.0.Lithium | Store Tx member-1-chn-17-txn-1: Data validation failed for path /(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:134303595078473}].
org.opendaylight.yangtools.yang.data.api.schema.tree.ModifiedNodeDoesNotExistException: Node /(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:134303595078473}] does not exist. Cannot apply modification to its children.
        at org.opendaylight.yangtools.yang.data.impl.schema.tree.AbstractNodeContainerModificationStrategy.checkTouchApplicable(AbstractNodeContainerModificationStrategy.java:182)[121:org.opendaylight.yangtools.yang-data-impl:0.7.0.Lithium]
        at org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaAwareApplyOperation.checkApplicable(SchemaAwareApplyOperation.java:125)[121:org.opendaylight.yangtools.yang-data-impl:0.7.0.Lithium]
        at org.opendaylight.yangtools.yang.data.impl.schema.tree.AbstractNodeContainerModificationStrategy.checkChildPreconditions(AbstractNodeContainerModificationStrategy.java:205)[121:org.opendaylight.yangtools.yang-data-impl:0.7.0.Lithium]
        at org.opendaylight.yangtools.yang.data.impl.schema.tree.AbstractNodeContainerModificationStrategy.checkTouchApplicable(AbstractNodeContainerModificationStrategy.java:189)[121:org.opendaylight.yangtools.yang-data-impl:0.7.0.Lithium]
        at org.opendaylight.yangtools.yang.data.impl.schema.tree.SchemaAwareApplyOperation.checkApplicable(SchemaAwareApplyOperation.java:125)[121:org.opendaylight.yangtools.yang-data-impl:0.7.0.Lithium]

Does anyone know what problem?
Thanks,
Ben.


Re: [openflowplugin-dev] Can anybody propose a better solution for this https://bugs.opendaylight.org/show_bug.cgi?id=4281?

Michal Rehak -X (mirehak - PANTHEON TECHNOLOGIES@Cisco) <mirehak@...>
 

Hi all,
the reason for removing yang files with rpcs inside is:
https://bugs.opendaylight.org/show_bug.cgi?id=2926

This bug emerged in dlux project as it is not possible there to distinguish between real service (exposed in md-sal) and API description (never exposed, polluting dlux UI).

Reverting that change will help testing but will damage dlux. I believe that solution should be based on more informations:

 - @Tony: when will be the support for yang exclusion ready?
 - @dlux-dev: can you guys live with having that bug reappeared till end of Beryllium?


Regards,
Michal



From: openflowplugin-dev-bounces@... [openflowplugin-dev-bounces@...] on behalf of Yang, Yi Y [yi.y.yang@...]
Sent: Monday, September 21, 2015 14:02
To: Tony Tkacik -X (ttkacik - PANTHEON TECHNOLOGIES at Cisco); openflowplugin-dev@...
Cc: dev@...; openflowjava-dev@...
Subject: Re: [openflowplugin-dev] Can anybody propose a better solution for this https://bugs.opendaylight.org/show_bug.cgi?id=4281?

Thanks Tony, so can openflowjava guys help get it fixed in master tree?

 

From: Tony Tkacik -X (ttkacik - PANTHEON TECHNOLOGIES at Cisco) [mailto:ttkacik@...]
Sent: Monday, September 21, 2015 2:27 PM
To: Yang, Yi Y; openflowplugin-dev@...
Cc: dev@...
Subject: RE: [openflowplugin-dev] Can anybody propose a better solution for this https://bugs.opendaylight.org/show_bug.cgi?id=4281?

 

Hi,

The fix is acceptable, since original pom file was messing with MD-SAL packaging, whichj may lead to incorrect behaviour if someone

used this models in their models.

 

Tony

 

From: openflowplugin-dev-bounces@... [mailto:openflowplugin-dev-bounces@...] On Behalf Of Yang, Yi Y
Sent: Monday, September 21, 2015 4:50 AM
To: openflowplugin-dev@...
Cc: dev@...
Subject: Re: [openflowplugin-dev] Can anybody propose a better solution for this https://bugs.opendaylight.org/show_bug.cgi?id=4281?

 

Hi, all

 

I encountered this bug https://bugs.opendaylight.org/show_bug.cgi?id=4281
 
Caused by: java.lang.IllegalStateException: Resource '/META-INF/yang/openflow-instruction.yang' is missing
 
in https://jenkins.opendaylight.org/releng/job/openflowplugin-verify-beryllium/jdk=openjdk7,nodes=dynamic_verify/1706/console.
 
The issue is fixed after I applied this patch https://git.opendaylight.org/gerrit/#/c/27172/, I'm not sure if it is acceptable, or do you have any better way to fix this?
 
I wonder why other openflowplugin unit tests didn’t encounter such issues although they also used AbstractDataBrokerTest.