Ask is moving to Stack Overflow and Serverfault.com! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode

adetalhouet's profile - activity

2016-11-30 11:59:38 -0700 commented answer Feature install error

You are pulling the artifacts from ODL Nexus repo, right?

2016-11-30 11:58:48 -0700 commented answer Feature install error

I compiled up to commit cf2fbb06d10ac7932e2915a079b926942967bddf

2016-11-30 11:58:27 -0700 commented answer Feature install error

I have just recompile your whole project again, using the command in the answer, and it is working fine for me. It has to be a cache issue (~/.m2/repository) or your github repo doesn't have latest modification.

2016-11-30 11:51:33 -0700 commented answer Feature install error

-Pq it to use the "quite" profile, which make the compilation way faster. Regarding the change, a patch was merged in Beryllium code base, the one you're using. And your error is related to that, as the change make use of a different version of the artifact java-concurrent-hash-trie-map.

2016-11-29 13:23:34 -0700 commented answer Feature install error

I edited my answer, it's working fine for me.

2016-11-29 13:06:37 -0700 commented answer How to register for event notifications?

See answers in the asked question.

2016-11-29 13:05:12 -0700 answered a question Feature install error

Can you try to mvn clean install -Pq -U because some change occurred for that dependency recently.

Also, you don't need to install all those features, based on your repo, you have the default feature getting installed by default: https://github.com/Pawash-Ahuja/pahuj... It should install all you need.

I just pulled in your repo, compiled it, and ran it without issue. Maybe you should clean your local cache: rm -r ~/.m2/repository/org/opendaylight

Hope this helps, Alexis

2016-11-23 05:59:48 -0700 commented answer How to register for event notifications?

[0]: https://github.com/opendaylight/openflowplugin/blob/stable/beryllium/features/src/main/features/features.xml#L45
With that feature you will be able to leverage a majority of the OpenFlowPlugin components.

2016-11-23 05:58:56 -0700 commented answer How to register for event notifications?

To connect OpenFlow-capable switches to your ODL instance, you have to install the odl-openflowplugin-flow-services feature [0]. Based on your repo, I would add such feature here: https://github.com/Pawash-Ahuja/pahujaOpenDaylight/blob/master/features/src/main/features/features.xml#L33

2016-11-22 08:50:05 -0700 commented answer How to register for event notifications?

You have different issues, see https://github.com/adetalhouet/pahujaOpenDaylight/commit/1ca318640fa44649d33ddbdfc1b58e49abfcc628 It doesn't solve the whole thing. You're using PacketProcessingListener from the openflowpluign model, hence you need to add the appropriate feature in the feature file.

2016-11-22 07:33:17 -0700 commented answer How to register for event notifications?

Based on all this, I'm not actually sure to see what you're missing, can you elaborate on that?

2016-11-22 07:32:27 -0700 commented answer How to register for event notifications?

Forget that last comment, I've spoken too fast. You got that right l47 (I was tricked by the indentation)

2016-11-22 07:30:58 -0700 commented answer How to register for event notifications?

@ahuja, The issue you're facing has nothing to do with the notification registration itself; you haven't registered the provider within the config system registry. You're missing `getBrokerDependency().registerProvider(provider);` in your *Module#createInstance() before the return statement.

2016-11-22 07:10:52 -0700 commented answer how to fix bug 7073 ?

Yes, either you wait, either you can pull the patch locally. To do so, you will have to clone the DLUX project for the boron branch, then apply the patch, build, so local artifact contain the fix. If you need step by step process let me know, I could help.

2016-11-22 07:07:44 -0700 commented answer Adding CORS support for my Plugin

@icehong, the patch I've linked is just an example of how to add that functionality. You would have to do the same in your project's configuration. There is an existing wiki page but it's pretty much outdated so I'd rather not linking it here.

2016-11-22 06:42:41 -0700 answered a question MD-SAL Data Remains after restarting karaf clean

Hello,

Using ./bin/karaf clean will start the container without any previously installed features, only with the default ones.

To completely clean the MD-SAL data, you should use this command at the root of the karaf directory: rm -rf data/* journal/* snapshots/*

The journal is event source based where each entry contains the affects of a transaction. On startup, the journal entries are played back to rebuild the data tree. Snapshots are taken periodically to avoid the journal getting too large.

A snapshot is just a flat file containing the serialized data tree. When a snapshot is taken, the journal entries are deleted. On startup, akka first plays back the last snapshot and then the journal entries.

Hope this helps, Alexis

2016-11-22 06:37:53 -0700 answered a question How to register for event notifications?

Hello @ahuja,

What ODL version do you want to use? If using Boron or master, I strongly recommend not using the config system to inject dependencies, as you're doing in the code shown. Instead you should use blueprint, which is way easier.

Beryllium and previous:

  1. You need to add the NotificationService in the default-config.xml file to inject its instance in the *Module#createInstance() See this example - pretty much the same as your, but using the new interface, not the deprecated one.
  2. In the *Module#createInstance() get the NotificationService dependency See this example - You've done the same thing already
  3. In the provider, use the #registerNotificationListener() from the NotificationService.
  4. Hold the Registration element to close it in the #close() funtion

Boron and after:

To register a notification listener using blueprint, see this wiki

Here is a concrete example with blueprint: 1. Create the bean (that will instantiate your class implementing the *Listener interface) 2. Register the listener using odl:notification-listener

If you really need to be tied to Beryllium or previous version, I'll edit that response with appropriate information.

Hope this helps. Alexis

2016-11-09 11:00:27 -0700 answered a question Training at summit 2016

Hello,

That wiki has a presentation of the OpenDaylight archetype to create an application from scratch. It will also guide you through some basic functionality, such as defining and implementing an RPC. The archetype works well with the mentioned version. That wiki is 75% up-to-date and everything works, the 25% missing is missing information.

Hope this helps, Alexis

2016-11-08 15:22:34 -0700 commented answer Register for topology change events

From the archetype, you'll get a project structure. Create your yang model. Then in the impl/ you have to create a class implementing DataTreeChangeListener. Once done, in the provider class, using the DataBroker, register the listener. Then you can use RESTCONF to play with your YANG model.

2016-11-08 15:18:40 -0700 commented answer Register for topology change events

There is currently some changes in OpenFlowPlugin, to change former topology_id from flow:1 to openflow.
as ref, I would recommend using the archetype to create your app.

2016-11-08 15:03:55 -0700 answered a question how to fix bug 7073 ?

Hello,

The bug is resolved and will be fixed in Boron SR2.

If you want to see the code, patch is here: https://git.opendaylight.org/gerrit/#...

Hope this helps, Alexis

2016-11-08 09:36:41 -0700 answered a question Register for topology change events

Hello,

If I'm understanding correctly, you're trying to gather the steps required to be able to interact with a given topology. You're steps are pretty much correct. Here are the one I have in mind anyway:

  1. Create the YANG model When the model will be loaded, if the model has a root container, this will be the root of your topology.
  2. Create the implementation for this YANG model 2.a. Register a listener on the config store for the topology created by your YANG model
  3. Use RESTCONF or ODL's internal to write to the config store
  4. Intercept the change in the listener, and appropriately update whatever the YANG is modeling (e.g. using SB protocol) and then write the result in the Operational store

hence config store has the desired state and operational has the current state.

This is not a prolific answer, but at least provide guidelines (very similar as what you already said).

Hope this helps, Alexis

2016-11-08 09:17:08 -0700 answered a question Restconf instance identifier

Hello,

Here is how the openflow node instance identifier should look like, based on your node:

/opendaylight-inventory:nodes/opendaylight-inventory:node[opendaylight-inventory:id=\"openflow:8796758018911\"]

Hope that helps, Alexis

2016-11-08 09:12:39 -0700 commented question Training at summit 2016

What training are you talking about? The NETCONF/YANG, the BGP/PCEP, the Application development,...?

2016-11-04 05:21:39 -0700 answered a question Adding CORS support for my Plugin

Hello,

I've done that in the UniMgr project of ODL. I would suggest looking at this gerrit.

Hope this helps, Alexis

2016-11-04 05:19:19 -0700 commented answer How to delete ovs bridge using OVSDB northbound API?

Any reason why you're using Helium. I would advice upgrading to a newer version. As the postman collection I postman collection I pointed you at is not compatible with Helium. Helium has a different design.

2016-11-01 07:05:42 -0700 answered a question A problem about opendaylight dlux_ui

This is a BUG in current Boron release, track by this bugzilla

See associated mail-thread about it.

Thanks, Alexis

2016-11-01 07:00:10 -0700 answered a question releases Boron nodes can't show on the web

This is a BUG in current Boron release, track by this bugzilla

See associated mail-thread about it.

Thanks, Alexis

2016-11-01 07:00:00 -0700 answered a question there is no nodes information in my odl user interface

This is a BUG in current Boron release, track by this bugzilla

See associated mail-thread about it.

Thanks, Alexis

2016-11-01 06:59:52 -0700 answered a question No node is detected in Nodes tab in boron UI ?

This is a BUG in current Boron release, track by this bugzilla

See associated mail-thread about it.

Thanks, Alexis

2016-11-01 06:59:32 -0700 answered a question Nodes in WebUI for ODL(Boron) always be empty

This is a BUG in current Boron release, track by this bugzilla

See associated mail-thread about it.

Thanks, Alexis