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

danielZt's profile - activity

2017-05-09 08:12:00 -0700 received badge  Notable Question (source)
2017-04-24 02:02:33 -0700 received badge  Popular Question (source)
2017-01-26 01:39:06 -0700 received badge  Popular Question (source)
2017-01-26 01:39:06 -0700 received badge  Notable Question (source)
2017-01-17 15:29:16 -0700 asked a question Flow(config DS) is not reinstalled

I would like to know if this is the normal behaviour of the Forwarding Rules Synchronizer (FRS) or Forwarding Rules Manager (FRM)

Test scenario(ODL Boron & mininet):

  1. Added a flow in the config data store.
  2. The flow is successfully installed in the switch.
  3. Deleted the flow from the switch using ovs-ofctl.
  4. The flow fails to be reinstalled in the switch unless I restart mininet.

I got the same result with both FRM and FRS.

I was expecting the flow to be reinstalled because the config flows reign over operational flows.

2016-10-24 01:56:38 -0700 commented answer distribution fails to start in both stable/beryllium and stable/boron

as I already commented the question, the next day the issue was fixed.

2016-10-13 04:22:09 -0700 received badge  Famous Question (source)
2016-09-21 01:35:06 -0700 commented question distribution fails to start in both stable/beryllium and stable/boron

I had this problem even after I deleted the ~/.m2/ folder and build. Luckily the frozen controller has been fixed the day after I noticed it. God job ODL!

2016-09-20 10:03:29 -0700 asked a question distribution fails to start in both stable/beryllium and stable/boron

I cloned the l2switch from https://github.com/opendaylight/l2switch , checked-out the stable/beryllium and built successfully this project. The problems is the controller fails to start and it is stuck after few log lines. Here are the last ones I see:

2016-09-20 17:45:21,419 | INFO  | Event Dispatcher | core                             | 58 - org.apache.aries.jmx.core - 1.1.2 | Registering org.osgi.jmx.framework.ServiceStateMBean to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name osgi.core:type=serviceState,version=1.7,framework=org.eclipse.osgi,uuid=f0b30b9c-517f-0016-14e3-f0e8ee69b9df
2016-09-20 17:45:21,423 | INFO  | Event Dispatcher | core                             | 58 - org.apache.aries.jmx.core - 1.1.2 | Registering org.osgi.jmx.framework.BundleStateMBean to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name osgi.core:type=bundleState,version=1.7,framework=org.eclipse.osgi,uuid=f0b30b9c-517f-0016-14e3-f0e8ee69b9df
2016-09-20 17:45:21,424 | INFO  | Event Dispatcher | core                             | 58 - org.apache.aries.jmx.core - 1.1.2 | Registering org.osgi.jmx.framework.PackageStateMBean to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name osgi.core:type=packageState,version=1.5,framework=org.eclipse.osgi,uuid=f0b30b9c-517f-0016-14e3-f0e8ee69b9df
2016-09-20 17:45:21,424 | INFO  | Event Dispatcher | core                             | 58 - org.apache.aries.jmx.core - 1.1.2 | Registering org.osgi.jmx.framework.FrameworkMBean to MBeanServer com.sun.jmx.mbeanserver.JmxMBeanServer@5e481248 with name osgi.core:type=framework,version=1.7,framework=org.eclipse.osgi,uuid=f0b30b9c-517f-0016-14e3-f0e8ee69b9df

This was working last Friday, but it doesn't anymore. It might be because one of the bundles has been updated.

Do you know exactly what causes this issue?

Here it is the tail of the log I see when I set the logging level to TRACE:

2016-09-20 17:58:45,456 | DEBUG | ion(2)-127.0.0.1 | tcp                              |  -  -  | RMI TCP Connection(2)-127.0.0.1: (port 44444) connection closed
2016-09-20 17:58:45,456 | DEBUG | RMI Scheduler(0) | tcp                              |  -  -  | RMI Scheduler(0): wake up
2016-09-20 17:58:45,457 | DEBUG | ion(2)-127.0.0.1 | tcp                              |  -  -  | RMI TCP Connection(2)-127.0.0.1: close connection
2016-09-20 17:58:45,457 | DEBUG | RMI Scheduler(0) | tcp                              |  -  -  | RMI Scheduler(0): connection timeout expired
2016-09-20 17:58:45,457 | DEBUG | RMI Scheduler(0) | tcp                              |  -  -  | RMI Scheduler(0): close connection
2016-09-20 17:58:45,459 | DEBUG | ion(1)-127.0.0.1 | tcp                              |  -  -  | RMI TCP Connection(1)-127.0.0.1: (port 1099) connection closed
2016-09-20 17:58:45,459 | DEBUG | ion(1)-127.0.0.1 | tcp                              |  -  -  | RMI TCP Connection(1)-127.0.0.1: close connection
2016-09-20 08:48:46 -0700 commented question After integrating OpenStack with ODL, vms ping fails after live migration

I haven't tried odl + openstack...but can you please check if you are using the l2switch app in odl. anyway the problem I found in the l2switch is that it installs flows (srcMac,dstMac -> port) and they are not removed/updated when a host migrates.

2016-09-20 07:37:24 -0700 commented question After integrating OpenStack with ODL, vms ping fails after live migration

I have seen that the l2 switch does not support host mobility, it might be the same issue.

2016-08-19 08:20:45 -0700 received badge  Citizen Patrol (source)
2016-08-12 11:37:32 -0700 received badge  Notable Question (source)
2016-08-11 09:47:58 -0700 received badge  Supporter (source)
2016-08-11 09:17:38 -0700 received badge  Student (source)
2016-08-11 05:33:31 -0700 answered a question configuration/logback.xml does not become effective

In Beryllium target/assembly/etc/org.ops4j.pax.logging.cfg is the file in which the logging levels can be set.

The logging levels set using log:set <level> [logger] are saved there.

2016-08-11 05:03:57 -0700 received badge  Popular Question (source)
2016-08-10 02:41:49 -0700 commented answer Deploy a bundle without restarting the controller

Also the bundle:install command you have suggested produces this ERROR org.eclipse.osgi.framework.internal.core.Framework$DuplicateBundleException: Bundle "org.opendaylight.<bundle>" version "1.1.3.SNAPSHOT" has already been installed from: mvn:org.opendaylight.<maven_repo>

2016-08-10 01:34:30 -0700 commented answer Deploy a bundle without restarting the controller

I tried to uninstall the bundle and then to deploy the updated one but I get a `WARN | /assembly/deploy | fileinstall | 7 - org.apache.felix.fileinstall - 3.4.2 | Failed to update bundle: <bundle name=""> with ID 194. The bundle has been uninstalled` and it does not work.

2016-08-09 03:41:09 -0700 asked a question Deploy a bundle without restarting the controller

One of the good things about OSGi is that it allows to update and deploy bundles without restarting Karaf.

During development I would like to update the bundle without having to restart Karaf.

I tried to deploy several updated bundles by placing them in the deploy folder. The problem is the new code is never executed if I do not reboot Karaf.

The error is:

Failed to remove bundle org.opendaylight.hello.impl_1.0.0.SNAPSHOT [195]
java.lang.IllegalStateException: Error while copying old configuration from ModuleInternalInfo [name=ModuleIdentifier{factoryName='hello', instanceName='hello-default'}] to org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.hello.impl.rev141210.HelloModuleFactory@50e77f8f

After a restart everything is fine.

Is there something I am missing? Are there java methods I have to change to facilitate the hot-installation?

Context: Beryllium

2016-08-09 03:19:51 -0700 asked a question ask.opendaylight search box

The search button is one of the most important functions in this community. The search box is way too small. I tried both Chrome and Firefox. This issue has not be fixed in the last 2 months.

I do care about this because these small things do not help to promote OpenDaylight.

Do you know any way to contact the web developers of this website? I asked the same question on IRC but none answered.

I am sorry for OT. I suggest to delete this question as soon as the problem is solved.

2016-07-22 10:45:10 -0700 answered a question target/generated-sources/mdsal-binding

I have found a solution:

replacing:

<parent>
<groupId>org.opendaylight.mdsal</groupId>
<artifactId>binding-parent</artifactId>
<version>0.8.3-SNAPSHOT</version>
<relativePath/>
</parent>

with:

<parent>
<groupId>org.opendaylight.controller</groupId>
<artifactId>config-parent</artifactId>
<version>0.4.3-SNAPSHOT</version>
<relativePath />
</parent>

in hello/api/pom.xml

2016-07-22 10:42:59 -0700 asked a question target/generated-sources/mdsal-binding

Hi there,

Could you please explain what triggers the generation of the target/generated-sources/mdsal-binding ? I know it is generated by the yang tools but I would like to know more.

I am following the https://wiki.opendaylight.org/view/Op...Controller:MD-SAL:StartupProject_Archetype and I have no problem building and running the project but eclipse complains about a missing class:

import org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.hello.rev150105.HelloService;

I think this is because the generated classes are not stored anywhere in the hello-api.

2016-07-13 01:40:56 -0700 received badge  Enthusiast
2016-07-08 07:27:02 -0700 received badge  Editor (source)
2016-07-06 12:07:10 -0700 received badge  Popular Question (source)
2016-07-06 02:19:50 -0700 received badge  Scholar (source)
2016-07-06 02:19:49 -0700 commented answer FlowCapableNode yang model

Thanks. It is defined in the `flow-node-inventory.yang`

2016-07-05 02:13:28 -0700 answered a question Topology Manager and Inventory Manager

The Inventory Manager stores only information about nodes while the Topology Manager stores links as well.

Checkout these two models:

org.opendaylight.controller.model.model-inventory/src/main/yang/opendaylight-inventory.yang org.opendaylight.controller.model.model-topology/src/main/yang/opendaylight-topology.yang

2016-07-05 02:02:05 -0700 asked a question FlowCapableNode yang model

Hello,

Could you please point me to the location where the FlowCapableNode is defined(I mean its yang model)?

In the org.opendaylight.openflowplugin.applications.topology.manager this class is used but Eclipse is not able to find it.

The import org.opendaylight.yang.gen.v1.urn.opendaylight.flow.inventory cannot be resolved

This does not affect the build. It builds successfully using:

mvn -nsu clean install -DskipTests