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

scurtis's profile - activity

2015-06-29 23:15:51 -0700 received badge  Famous Question (source)
2015-05-05 04:48:55 -0700 received badge  Notable Question (source)
2014-12-16 07:43:22 -0700 received badge  Notable Question (source)
2014-12-16 07:43:22 -0700 received badge  Famous Question (source)
2014-12-10 23:39:48 -0700 received badge  Popular Question (source)
2014-12-05 21:02:28 -0700 received badge  Famous Question (source)
2014-12-05 02:07:23 -0700 received badge  Popular Question (source)
2014-12-04 03:58:57 -0700 asked a question What Does It Take To Get New Devices To Show In Topology View

I've created a very simple data definition of a device and am programatticaly pushing this into the ODL DataStore.

It would be useful to be able to see these in the DLUX topology viewer, Is there a way to either:

(1) hook my simple definition to the topology viewer.

or

(2) enhance the DLUX console to display my devices.

2014-11-26 07:34:03 -0700 received badge  Enthusiast
2014-11-25 12:44:59 -0700 received badge  Notable Question (source)
2014-11-25 07:56:17 -0700 commented question shrunken dlux topology view

I'm seeing the same thing on my environment. I'm running Helium-SR1 and have observed it both in IE11 and Chrome 39.0.2171.65 m It does make the topology view a lot less useful than it should be.

2014-11-17 05:56:03 -0700 commented question ODL takes quite a long time to start

Yes I see similar timings whether or not debug is enabled. I'm assuming it's something to do with the "!MESSAGE Bundle reference:file:../lib/logging.bridge-0.5.0-SNAPSHOT@1:start not found." statement and the OSGI container is waiting on a timeout firing before continuing.

2014-11-17 05:54:25 -0700 commented answer What is the best way to use ODL to manage both discoverable and non-discoverable devices together

How would ODL become aware of NETCONF enabled devices? Can it self-discover or does the logical inventory need to be statically loaded into ODL somehow (via a new plugin probably) before the NETCONF transactions can be run?

2014-11-14 11:33:31 -0700 received badge  Popular Question (source)
2014-11-13 08:40:25 -0700 commented question Creating node in the inventory is error under clustering mode, while fine under single mode

Is DataBroker the correct way to do something like this, are nodes added this way automatically pushed into the SwitchManager/TopologyManager services? I was trying to do somethign similar by using the IPluginOutTopologyService.edgeUpdate method.

2014-11-13 06:28:36 -0700 received badge  Famous Question (source)
2014-11-13 01:39:55 -0700 received badge  Popular Question (source)
2014-11-13 01:39:55 -0700 received badge  Notable Question (source)
2014-11-12 07:24:38 -0700 commented question What is the best way to use ODL to manage both discoverable and non-discoverable devices together

Thanks lori, hope it's a little clearer now. Essentially I'm looking into what ODL can do from an OSS perspective. I'd be looking at how to manage a network estate that isn't able to tell ODL about itself alongside OF-enabled devices so I can create custom business processes across both.

2014-11-12 07:22:41 -0700 received badge  Editor (source)
2014-11-12 04:36:08 -0700 asked a question ODL takes quite a long time to start

I'm running ODL from the latest git version but it regularly takes quite a long time to load:

Setting maximum memory to 1G.
"C:\Program Files\Java\jdk1.8.0_25\bin\java.exe" -Dopendaylight.controller  -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=8000  -Xmx1G -Djava.io.tmpdir="C:\Users\700608667\Projects\SITB\ODL\controller\opendaylight\distribution\opendaylight\target\distribution.opendaylight-osgipackage\opendaylight\work\tmp" -Djava.awt.headless=true -Dosgi.install.area=C:\Users\700608667\Projects\SITB\ODL\controller\opendaylight\distribution\opendaylight\target\distribution.opendaylight-osgipackage\opendaylight\ -Dosgi.configuration.area="C:\Users\700608667\Projects\SITB\ODL\controller\opendaylight\distribution\opendaylight\target\distribution.opendaylight-osgipackage\opendaylight\configuration" -Dosgi.frameworkClassPath="file:\C:\Users\700608667\Projects\SITB\ODL\controller\opendaylight\distribution\opendaylight\target\distribution.opendaylight-osgipackage\opendaylight\lib\org.eclipse.osgi-3.8.1.v20120830-144521.jar,file:\C:\Users\700608667\Projects\SITB\ODL\controller\opendaylight\distribution\opendaylight\target\distribution.opendaylight-osgipackage\opendaylight\lib\org.eclipse.virgo.kernel.equinox.extensions-3.6.0.RELEASE.jar,file:\C:\Users\700608667\Projects\SITB\ODL\controller\opendaylight\distribution\opendaylight\target\distribution.opendaylight-osgipackage\opendaylight\lib\org.eclipse.equinox.launcher-1.3.0.v20120522-1813.jar" -Dosgi.framework="file:\C:\Users\700608667\Projects\SITB\ODL\controller\opendaylight\distribution\opendaylight\target\distribution.opendaylight-osgipackage\opendaylight\lib\org.eclipse.osgi-3.8.1.v20120830-144521.jar" -classpath "C:\Users\700608667\Projects\SITB\ODL\controller\opendaylight\distribution\opendaylight\target\distribution.opendaylight-osgipackage\opendaylight\lib\org.eclipse.osgi-3.8.1.v20120830-144521.jar;C:\Users\700608667\Projects\SITB\ODL\controller\opendaylight\distribution\opendaylight\target\distribution.opendaylight-osgipackage\opendaylight\lib\org.eclipse.virgo.kernel.equinox.extensions-3.6.0.RELEASE.jar;C:\Users\700608667\Projects\SITB\ODL\controller\opendaylight\distribution\opendaylight\target\distribution.opendaylight-osgipackage\opendaylight\lib\org.eclipse.equinox.launcher-1.3.0.v20120522-1813.jar" org.eclipse.equinox.launcher.Main -console -consoleLog
Listening for transport dt_socket at address: 8000
!SESSION 2014-11-12 12:17:01.574 -----------------------------------------------

eclipse.buildId=unknown
java.version=1.8.0_25
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_GB
Command-line arguments:  -console -consoleLog

!ENTRY org.eclipse.osgi 4 0 2014-11-12 12:17:03.729
!MESSAGE Bundle reference:file:../lib/logging.bridge-0.5.0-SNAPSHOT@1:start not found.
2014-11-12 12:21:09.155 GMT [Start Level Event Dispatcher] INFO  o.a.sshd.common.util.SecurityUtils - Trying to register BouncyCastle as a JCE provider
2014-11-12 12:21:09.893 GMT [Start Level Event Dispatcher] INFO  o.a.sshd.common.util.SecurityUtils - Registration succeeded
2014-11-12 12:21:10.664 GMT [ControllerI/O Thread] INFO  o.o.c.p.o.c.internal.ControllerIO - Controller is now listening on any:6633
2014-11-12 12:21:35.546 GMT [Start Level Event Dispatcher] INFO  o.o.c.c.s.internal.ClusterManager - I'm a GossipRouter will listen on port 12001

You can see that this takes nearly seven minutes to startup. Is this normal or is there something that can be done to speed this up? Something to do with the "logging.bridge-0.5.0-SNAPSHOT@1:start not found" message perhaps?

Note I have seen this consistently happen across multiple developer machines and operating systems.

Thanks in advance

2014-11-11 13:07:19 -0700 asked a question How do I programatically load new switches into ODL so they are visible in the console

I'm trying to programatically create switches in a custom plugin that loads some set inventory so it is visible in the ODL console. The code doing the work makes use of the switch manager service as follows:

try {
    Node node = new Node(Node.NodeIDType.OPENFLOW, Long.valueOf(1L));
    Switch newSwitch = new Switch(node);
    switchManager.getNetworkDevices().add(newSwitch);
} catch (ConstructionException e) {
    e.printStackTrace();
}

I don't get any exceptions thrown but I also don't get any switches visible. When I print the contents of the devices out after the fact the new switch does not appear in the list.

Is this the correct way to do something like this or am I bypassing some internal caching somewhere.

When I get this working I'd also like to programatically create host devices as well.

Thanks in advance.

2014-11-11 12:59:18 -0700 asked a question What is the best way to use ODL to manage both discoverable and non-discoverable devices together

I'd like to use ODL as a single application to manage both discoverable devices and non-discoverable devices.

Note by non-discoverable devices, I mean those that do not proactively advertise their presence and will need to be loaded into ODL via a custom plugin.

First of all does this sound like a good idea, secondly is there any documentation/good practice around how to programatically load non-SDN/OF switches into the ODL topology services?

Thanks in advance.