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

jeffcavalcante's profile - activity

2015-08-13 00:34:28 -0700 received badge  Famous Question (source)
2015-06-25 19:41:55 -0700 answered a question How to slice topology in topomanager in opendaylight?thanks.

The network-topology database loaded by TopologyManager carries a list of topologies. You could create a topology for each slice.

Hope I've helped.

2015-06-25 19:35:23 -0700 answered a question How do I programatically load new switches into ODL so they are visible in the console

You have to save them on the network-topology container of ODL's database.

Create an InstanceIdentifier to the network-topology/topology, then create a WriteOnly transaction and save the Node object you've created.

Hope I've helped.

2015-06-25 19:32:03 -0700 answered a question How to Write own REST API

In MD-SAL, you create a YANG model with the data you want to expose and it will be available for REST calls, then set up your features plugin to install the feature through karaf.

Check this example on how to generate a simple set of modules, including a model and a provider:

https://wiki.opendaylight.org/view/OpenDaylightToolkit:MD-SAL-SimpleArchetype#WhatdoestheMD-SALArchetypeProvidefor_us.3F

Hope I've helped.

2015-06-25 19:20:34 -0700 answered a question How to put cost-value on link in MD-SAL Helium.

You can create an YANG module which augments the network-topology data tree with a leaf for the link's cost.

Create a yang file like this on your provider plugin:

module link-cost{
/* put all the required things for a module here like namespace and revision */

    augment "network-topology/topology/link"{
        leaf cost{
            type whatever-you-need; //I would recommend an enumeration
        }
    }
}
2015-06-25 19:03:54 -0700 commented question New Rpc implementation
2015-06-25 18:50:55 -0700 answered a question Fault recovery link down

Maybe You can implement some intelligence in the ODL controller to handle this.

You could create a plugin which gets notified when a link is down and configures flows to restore connectivity between all hosts.

Hope I've helped.

2015-06-19 14:56:09 -0700 received badge  Notable Question (source)
2015-06-18 10:42:16 -0700 commented answer Why recompile opendaylight-karaf for changes in another plugin to take effect?

Unfortunatelly, none of these seemed to update the recently compiled JARs, and I had to replace them manually. However, I noticed that if we change the POM (eg. add a dependency), cleaning the data directory after replacing the JAR is also necessary. Thanks for this.

2015-06-18 10:35:17 -0700 answered a question Why recompile opendaylight-karaf for changes in another plugin to take effect?

Here's the 2 steps that worked for me:

1- Manually copy the updated JARs from local maven repository to karaf's system (controller/karaf/opendaylight-karaf/target/assembly/system) directory. This allows the updated code to be installed. Before replacing the JARs, I uninstall the feature (feature:uninstal) and restart karaf. If dependencies change, for example, the step 2 is required.

2- Cleaning the karaf's data (controller/karaf/opendaylight-karaf/target/assembly/data) directory. Thanks to grmontpetit for this.

Bundle watch didn't work properly for me (I noticed when debugging), that's why I'm replacing JARs manually.

2015-06-18 10:21:13 -0700 received badge  Popular Question (source)
2015-06-11 12:43:31 -0700 received badge  Editor (source)
2015-06-11 12:42:40 -0700 asked a question Why recompile opendaylight-karaf for changes in another plugin to take effect?

I have now a set of plugins. When I change code in one of them, i have to recompile it and recompile the opendaylight-karaf (my bundles are in its set of dependencies) for changes to take effect.

It was not like that weeks ago. Is there a way to avoid recompiling the entire karaf for changes in plugins to take effect?