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

Denis's profile - activity

2016-03-21 09:48:08 -0700 commented question How to register salFlowService, to prevent DOMRpcImplementationNotAvailableException: No implementation of RPC AbsoluteSchemaPath{path=[(urn:opendaylight:flow:service?revision=2013-08-19)add-flow]} available

@karthik330: Not sure about it, but i would guess you look for `<groupid>org.opendaylight.openflowplugin.model</groupid> <artifactid>model-flow-service</artifactid>` At least, there are the impls for salFlowService..

2016-03-21 09:47:40 -0700 commented question How to register salFlowService, to prevent DOMRpcImplementationNotAvailableException: No implementation of RPC AbsoluteSchemaPath{path=[(urn:opendaylight:flow:service?revision=2013-08-19)add-flow]} available

@g_trelos, mahanare: no but i have to admit, that i stopped working with odl, due its complexity and lack of community support

2016-02-20 23:55:03 -0700 received badge  Notable Question (source)
2015-12-04 01:49:09 -0700 received badge  Famous Question (source)
2015-11-23 16:43:56 -0700 received badge  Popular Question (source)
2015-11-23 16:43:56 -0700 received badge  Notable Question (source)
2015-11-23 16:43:56 -0700 received badge  Famous Question (source)
2015-10-10 08:28:38 -0700 asked a question How to register salFlowService, to prevent DOMRpcImplementationNotAvailableException: No implementation of RPC AbsoluteSchemaPath{path=[(urn:opendaylight:flow:service?revision=2013-08-19)add-flow]} available

Hi,

I get this error msg in karaf, whenever i try to use the salFlowService in my self developed application, Googling pointed out, that I've to register the salFlowService, to prevent this. But i dont know, how to do this properly in my app. Also, the salFlowService works in l2switch, and I cant see any relevant difference from my code to l2switch/main-impl - code. Also i cannot found there any registering of the salFlowService.

some excerpts of my code (only the relevant parts): FlowBuilderModule - create instance:

   public java.lang.AutoCloseable createInstance() {
       ...
       SalFlowService salFlowService = rpcRegistryDependency
            .getRpcService(SalFlowService.class);
       final FlowBuilder fb = new FlowBuilder(getDataBrokerDependency(), provider);
       fb.setSalFlowService(salFlowService);
       ...
   }

Flowbuilders code:

  public class FlowBuilder {
     ...
     private SalFlowService salFlowService;
     ...


     private void addFlows(List<Flow> flows, NodeConnectorRef destRef) {
        for (Flow f: flows)
           InstanceIdentifier<Flow> flowId = getInstanceIdentifier(flow, destRef);
           AddFlowInput addFlow = new AddFlowInputBuilder(f).setFlowRef(new FlowRef(flowId)).build();
           Future<RpcResult<AddFlowOutput>> futRpc = salFlowService.addFlow(addFlow);
           while (!futRpc.isDone())
              log.debug("flowbuilder: waiting for future rpc");

           if (futRpc.isDone()) {
              try {
                  RpcResult<AddFlowOutput> rpc = futRpc.get();
                  log.debug("flowbuilder: rpc successful : "+rpc.isSuccessful());
            } catch (InterruptedException | ExecutionException e) {
                // TODO Auto-generated catch block
                e.printStackTrace();
            }
        }
     }

     private InstanceIdentifer<Flow> getInstanceIdentifier(Flow flow, NodeConnectorRef destRef) {
          return InstanceIdentifier
                .builder(Nodes.class)
                .child(Node.class,
                        new NodeKey(destRef.getValue()
                                .firstKeyOf(Node.class, NodeKey.class)))
                .augmentation(FlowCapableNode.class)
                .child(Table.class, new TableKey((short) 0))
                .child(Flow.class, f.getKey()).build();
     }
  }

yang file - implementation part:

 ...
 augment "/config:modules/config:module/config:configuration" {
 case flowbuilder-impl {
    when "/config:modules/config:module/config:type = 'flowbuilder-impl'";
    ...
     container rpc-registry {
        uses config:service-ref {
          refine type {
            mandatory true;
            config:required-identity mdsal:binding-rpc-registry;
          }
        }
    }
    ...

yang file - config part (48-flowbuilder.xml):

  <snapshot>
     <configuration>
       <data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
         <modules xmlns="urn:opendaylight:params:xml:ns:yang:controller:config">
           <module>
               <type xmlns:prefix="urn:opendaylight:medqos:flowbuilder-impl">
        prefix:flowbuilder-impl
               </type>
               <name>flowbuilder-impl</name>
               <notification-service>
                  <type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">
                    binding:binding-notification-service
                  </type>
                 <name>binding-notification-broker</name>
               </notification-service>
               <data-broker>
                  <type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-async-data-broker</type>
                  <name>binding-data-broker</name>
               </data-broker>
               <rpc-registry>
                     <type xmlns:binding="urn:opendaylight:params:xml:ns:yang:controller:md:sal:binding">binding:binding-rpc-registry</type>
                   <name>binding-rpc-broker</name>
              </rpc-registry>
       </module>
  </modules>
  </data>
  </configuration>
  <required-capabilities>
      <capability>urn:opendaylight:medqos:flowbuilder-impl?module=flowbuilder-impl&revision=2015-07-09</capability>
   </required-capabilities>
</snapshot>

My application is organized like the l2switch project. Working on Lithium (latest stable/ also tested on built controller from master) In another mailing from your list, i saw that also a possible disconnect of a device can be a factor to raise that exception. But i dont believe this is the point here, as l2switch works. Can anybody point me in the right direction, what I am missing / doing wrong ?

2015-10-06 15:33:48 -0700 commented question ODL controller project not building fine

try with jdk 1.7 - there was an issue some months ago, that odl works only with jdk 1.7. Dont know, wheter the issue with java 8 has been fixed.

2015-10-05 05:11:43 -0700 received badge  Popular Question (source)
2015-10-03 03:15:39 -0700 commented answer Where to find MeterIdInstruction in openflow-protocol-api

Yeah the point was, i was looking in a old version of testcode.. there MeterIdInstruction was used for this case. In newer versions MeterCase is used, just like in your example. Thanks anyway!

2015-10-03 03:13:29 -0700 received badge  Supporter (source)
2015-10-01 05:22:20 -0700 received badge  Popular Question (source)
2015-10-01 05:22:20 -0700 received badge  Notable Question (source)
2015-10-01 05:22:20 -0700 received badge  Famous Question (source)
2015-09-22 03:37:19 -0700 asked a question Where to find MeterIdInstruction in openflow-protocol-api

I'm missing the MeterIdInstruction class in openflow-protocol-api (0.7.0-SNAPSHOT). In openflow-protocol-api (0.5.4-SNAPSHOT) the file exists. Does anyone know, where it has been moved, or was it replaced by another class ? If it was replaced by another, how can I assign a meter to a flow, if not using MeterIdInstruction. Any pointer to updated tutorials (for odl-lithium) and dealing with meters and flows are greatly appreciated.

2015-09-21 03:46:43 -0700 answered a question Checkstyle violations for the empty project

Correct the code so that it fits the checkstyle rules. The error message shows, where to find the typo..

 [ERROR] src/main/java/org/opendaylight/yang-push/impl/Yang-pushProvider.java[23:5]

Check line 23 in the mentioned class

2015-09-19 10:44:45 -0700 asked a question not able to augment instruction with MeterIdInstruction

Im trying to add per-flow meters. Adding the meter itself works fine, but assigning the meter to flow is not working. I'm not able to add the augmentation of MeterIdInstruction on a instruction.

ODL-Version: stable / helium (1.4.6-snapshot) Switch: cpqd

Here's my code:

imports:

   import org.opendaylight.yang.gen.v1.urn.opendaylight.flow.types.rev131026.instruction.list.Instruction;
   import org.opendaylight.yang.gen.v1.urn.opendaylight.flow.types.rev131026.instruction.list.InstructionBuilder;
   import org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.augments.rev131002.MeterIdInstruction;
   import org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.augments.rev131002.MeterIdInstructionBuilder;

relevant code:

    long meterId = meter.getMeterId();
    MeterIdInstructionBuilder medBuilder = new MeterIdInstructionBuilder();
    medBuilder.setMeterId(meterId);
    new InstructionBuilder().addAugmentation(MeterIdInstruction.class, medBuilder.build()); //

When trying to compile, there occurs this error:

The method addAugmentation(Class<? extends Augmentation<Instruction>>, Augmentation<Instruction>) in the type InstructionBuilder is not applicable for the arguments (Class<MeterIdInstruction>, MeterIdInstruction)

Dont know, how to go from here. Does anyone know, how to solve this ?

2015-09-15 23:14:44 -0700 received badge  Famous Question (source)
2015-09-12 08:07:29 -0700 received badge  Notable Question (source)
2015-09-05 12:30:10 -0700 received badge  Notable Question (source)
2015-09-05 08:39:07 -0700 commented answer Added flow to operational datastore has other id, than specified

Thank you very much, you provided very useful information regarding how config/operational ds really works, however as i am novice in odl, couldnt find that kind of details in wiki. Any pointer where i can read such things to get a better insight ?

2015-09-05 08:35:09 -0700 received badge  Scholar (source)
2015-09-05 06:17:38 -0700 answered a question Added flow to operational datastore has other id, than specified

@Mandeep: I believe your answer is correct, but actually your suggestion is not working for me. When i try to add the flow manually to config datastore, it shows me the exception': Caused by:

org.opendaylight.yangtools.yang.data.api.schema.tree.ModifiedNodeDoesNotExistException: Node /(urn:opendaylight:inventory?revision=2013-08-19)nodes does not exist. Cannot apply modification to its children.

Im a bit confused, as my whole config datastore seems to be empty.. When i query via curl:

curl -X GET -H "Content-Type: application/json" -H "Accept: application/json" --user admin:admin http://localhost:8181/restconf/config/opendaylight-inventory:nodes/

It shows nothing. When i query the operational datastore, i get a normal output. Can you give me some advice, whats going wrong in my case ?

2015-09-02 15:42:23 -0700 received badge  Popular Question (source)
2015-08-31 11:10:07 -0700 asked a question Added flow to operational datastore has other id, than specified

ODL-Version: Helium (1.4.6-Snapshot)

Switch: Mininet 2.2.1

I have to add manually flows to md sal operational data store, as using the salFlowService doesnt store them in md sal. So what im basically doing is writing the flows to switches via salFlowService and additionally storing them in md sal operational datastore. The flows are present in the ovs switches (checked per ovs-ofctl) However i'm able to write the flows to md sal, but curiously the specified id in instance identifier is not used.

This is my hardcoded instance-identifier (for testing)

 InstanceIdentifier<Flow> flowId = InstanceIdentifier
            .builder(Nodes.class)
            .child(Node.class, new NodeKey(new NodeId("openflow:1")))
            .augmentation(FlowCapableNode.class)
            .child(Table.class, new TableKey((short) 0))
            .child(Flow.class, new FlowKey(new FlowId("1"))).build();

When i query the REST api ( http://localhost:8181/restconf/operational/opendaylight-inventory:nodes/node/openflow:1/table/0 ), i can see my flow (identified by name), but the id is not the same as specified in instance identifier

Inrelevant lines ommited:

...
<flow><id>694266177</id><instructions><instruction>
...

Can anyone explain this behaviour ? Do I miss some basic stuff ? Is this maybe an issue in ODL-Helium and was fixed in Lithium ? Just didnt manage to migrate my application to lithium, yet

edit: i dont see any errors or warnings in karaf log

2015-08-05 03:25:54 -0700 received badge  Famous Question (source)
2015-05-29 08:43:28 -0700 received badge  Enthusiast
2015-05-28 07:08:15 -0700 received badge  Notable Question (source)
2015-05-23 04:49:28 -0700 received badge  Popular Question (source)
2015-05-23 04:48:45 -0700 received badge  Popular Question (source)
2015-05-16 11:41:11 -0700 asked a question NullPointerException when generating java source code from yang model

Hi,

I'm following the steps of Toaster:Step-By-Step tutorial. At generating java source code from yang model, npe gets thrown.. (full stack trace, some parts ommitted)

[ERROR] yang-to-sources: Unable to parse yang files from /home/luna/Desktop/odl-testapp/MedQos/MedQos/src/main/yang
java.lang.NullPointerException
at org.opendaylight.yangtools.yang.parser.impl.YangParserImpl.resolveIdentity(YangParserImpl.java:1039)
at org.opendaylight.yangtools.yang.parser.impl.YangParserImpl.resolveIdentities(YangParserImpl.java:1019)
at org.opendaylight.yangtools.yang.parser.impl.YangParserImpl.build(YangParserImpl.java:711)

.....

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8.466 s
[INFO] Finished at: 2015-05-16T20:29:01+02:00
[INFO] Final Memory: 15M/331M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.opendaylight.yangtools:yang-maven-plugin:0.6.5-Helium-SR3:generate-sources (default) on project MedQos: yang-to-sources: Unable to parse yang files from /home/luna/Desktop/odl-testapp/MedQos/MedQos/src/main/yang: NullPointerException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.opendaylight.yangtools:yang-maven-plugin:0.6.5-Helium-SR3:generate-sources (default) on project MedQos: yang-to-sources: Unable to parse yang files from /home/luna/Desktop/odl-testapp/MedQos/MedQos/src/main/yang
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

....

Caused by: org.apache.maven.plugin.MojoExecutionException: yang-to-sources: Unable to parse yang files from /home/luna/Desktop/odl-testapp/MedQos/MedQos/src/main/yang
at org.opendaylight.yangtools.yang2sources.plugin.YangToSourcesProcessor.processYang(YangToSourcesProcessor.java:177)
at org.opendaylight.yangtools.yang2sources.plugin.YangToSourcesProcessor.execute(YangToSourcesProcessor.java:82)
at org.opendaylight.yangtools.yang2sources.plugin.YangToSourcesMojo.execute(YangToSourcesMojo.java:122)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 20 more
Caused by: java.lang.NullPointerException
at org.opendaylight.yangtools.yang.parser.impl.YangParserImpl.resolveIdentity(YangParserImpl.java:1039)
at org.opendaylight.yangtools.yang.parser.impl.YangParserImpl.resolveIdentities(YangParserImpl.java:1019)
at org.opendaylight.yangtools.yang.parser.impl.YangParserImpl.build(YangParserImpl.java:711)
at org.opendaylight.yangtools.yang.parser.impl.YangParserImpl.parseYangModelSources(YangParserImpl.java:354)
at org.opendaylight.yangtools.yang.parser.impl.YangParserImpl.parseYangModelsFromStreamsMapped(YangParserImpl.java:308)
at org.opendaylight.yangtools.yang2sources.plugin.YangToSourcesProcessor.processYang(YangToSourcesProcessor.java:151)
... 24 more

Does anyone know, how to resolve this ?

Heres my pom.xml:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
  <artifactId>MedQos-parent</artifactId>
  <groupId>com.mygroup.own</groupId>
  <version>0.0.1-SNAPSHOT</version>
  <relativePath>../</relativePath>
</parent>

<artifactId>MedQos</artifactId>
<packaging>jar</packaging>

<build>
  <plugins>
     <plugin>
         <groupId>org.opendaylight.yangtools</groupId>
         <artifactId>yang-maven-plugin</artifactId>
         <version>${yangtools.version}</version>
     <executions>
       <execution>
          <goals>
             <goal>generate-sources</goal>
          </goals>
          <configuration>
             <yangFilesRootDir>src/main/yang</yangFilesRootDir>
          <codeGenerators>
             <generator>
                 <codeGeneratorClass>org.opendaylight.yangtools.maven.sal.api.gen.plugin.CodeGeneratorImpl</codeGeneratorClass>
             <outputBaseDir>${salGeneratorPath}</outputBaseDir>
           </generator>
         </codeGenerators>
         <inspectDependencies>true</inspectDependencies>
       </configuration>
     </execution>
   </executions>
   <dependencies>
     <dependency>
       <groupId>org.opendaylight.yangtools</groupId>
       <artifactId>maven-sal-api-gen-plugin</artifactId>
       <version>${yangtools ...
(more)
2015-05-14 06:57:43 -0700 asked a question Maven: Cant build project like Toaster Tutorial

Hi,

Im trying to build a md-sal application,following the instructions of the toaster tutorial.

Kind of newbie to maven. Project names and so on are changed according to my projects name

When the first mvn clean install occurs (in section: Generate the Toaster yang data model source) , maven fails with follwing error:

Some problems were encountered while processing the POMs:
[FATAL] 'version' is missing. @ de.tu-berlin.cit:MedQos-parent:[unknown-version], /home/denis/Schreibtisch/odl-testapp/MedQos/pom.xml, line 1, column 204
@ 
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project de.tu-berlin.cit:MedQos:[unknown-version] (/home/denis/Schreibtisch/odl-testapp/MedQos/MedQos/pom.xml) has 1 error
[ERROR]     'version' is missing. @ de.tu-berlin.cit:MedQos-parent:[unknown-version], /home/denis/Schreibtisch/odl-testapp/MedQos/pom.xml, line 1, column 204

After adding a version tag to the root pom file, following error occurs:

[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[WARNING] 'build.plugins.plugin.version' for org.opendaylight.yangtools:yang-maven-plugin is missing. @ de.tu-berlin.cit:MedQos:[unknown-version], /home/denis/Schreibtisch/odl-testapp/MedQos/MedQos/pom.xml, line 15, column 14
[ERROR] Unknown packaging: bundle @ de.tu-berlin.cit:MedQos:[unknown-version], /home/denis/Schreibtisch/odl-testapp/MedQos/MedQos/pom.xml, line 11, column 13
[ERROR] 'modelVersion' is missing. @ de.tu-berlin.cit:MedQos:[unknown-version], /home/denis/Schreibtisch/odl-testapp/MedQos/MedQos/pom.xml, line 2, column 114
[ERROR] 'dependencies.dependency.version' for org.opendaylight.yangtools:yang-binding:jar is missing. @ de.tu-berlin.cit:MedQos:[unknown-version], /home/denis/Schreibtisch/odl-testapp/MedQos/MedQos/pom.xml, line 48, column 16
[ERROR] 'dependencies.dependency.version' for org.opendaylight.yangtools:yang-common:jar is missing. @ de.tu-berlin.cit:MedQos:[unknown-version], /home/denis/Schreibtisch/odl-testapp/MedQos/MedQos/pom.xml, line 52, column 16
[ERROR] 'build.plugins.plugin[org.opendaylight.yangtools:yang-maven-plugin].dependencies.dependency.version' for org.opendaylight.yangtools:maven-sal-api-gen-plugin:jar must be a valid version but is '${yangtools.version}'. @ de.tu-berlin.cit:MedQos:[unknown-version], /home/denis/Schreibtisch/odl-testapp/MedQos/MedQos/pom.xml, line 39, column 21
@ 
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project de.tu-berlin.cit:MedQos:0.0.1-SNAPSHOT (/home/denis/Schreibtisch/odl-testapp/MedQos/MedQos/pom.xml) has 5 errors
[ERROR]     Unknown packaging: bundle @ de.tu-berlin.cit:MedQos:[unknown-version], /home/denis/Schreibtisch/odl-testapp/MedQos/MedQos/pom.xml, line 11, column 13
[ERROR]     'modelVersion' is missing. @ de.tu-berlin.cit:MedQos:[unknown-version], /home/denis/Schreibtisch/odl-testapp/MedQos/MedQos/pom.xml, line 2, column 114
[ERROR]     'dependencies.dependency.version' for org.opendaylight.yangtools:yang-binding:jar is missing. @ de.tu-berlin.cit:MedQos:[unknown-version], /home/denis/Schreibtisch/odl-testapp/MedQos/MedQos/pom.xml, line 48, column 16
[ERROR]     'dependencies.dependency.version' for org.opendaylight.yangtools:yang-common:jar is missing. @ de.tu-berlin.cit:MedQos:[unknown-version], /home/denis/Schreibtisch/odl-testapp/MedQos/MedQos/pom.xml, line 52, column 16
[ERROR]     'build.plugins.plugin[org.opendaylight.yangtools:yang-maven-plugin].dependencies.dependency.version' for org.opendaylight.yangtools:maven-sal-api-gen-plugin:jar must be a valid version but is '${yangtools.version}'. @ de.tu-berlin.cit:MedQos:[unknown-version], /home/denis/Schreibtisch/odl-testapp/MedQos/MedQos/pom ...
(more)
2015-05-07 08:53:16 -0700 answered a question Can't install l2-learning-switch sample

had an similiar issue with odl, maven and ubuntu. check this

create a file, named settings.xml in your local maven repository: usually on windows, you find it:

C:\Documents and Settings\{your-username}\.m2\

copy the content to settings.xml, mentioned in the above link and save it. Maybe this will resolve your issue.

2015-05-07 08:00:19 -0700 asked a question cpu consumption odl controller helium release

Hi,

On this board there is a similar question, but its about hydrogen release. This question is about helium release. I have some issues with the opendaylight controller and relatively high cpu usage. I installed the opendaylight controller, by using the tutorial provided on sdnhub. After compiling the tutorial and starting the controller, cpu usage raises to 100% and stays for a short while, and going down to "normal" cpu usage. After starting mininet with a simple topology, one switch, and three nodes, the cpu usage raises to nearly 50-60%. Do some sort of pinging, everything is fine..after stopping mininet, the controllers cpu usage is not going down to "few" %, it stays at 50%. Okay thought, maybe the tutorial application may be not working fully, i stopped the osgi bundle, but the controller still has a high consumption. Is this a normal behaviour ? I had expected, the usage will go down, if the controller has nothing to do. There were no other applications loaded, than the standard ones.

osgi> ss
"Framework is launched."


id  State       Bundle
0   ACTIVE      org.eclipse.osgi_3.8.1.v20120830-144521
1   ACTIVE      org.apache.felix.fileinstall_3.1.6
2   ACTIVE      org.eclipse.jdt.core.compiler.batch_3.8.0.I20120518-2145
3   ACTIVE      org.eclipse.equinox.ds_1.4.0.v20120522-1841
4   ACTIVE      org.eclipse.equinox.util_1.0.400.v20120522-2049
5   ACTIVE      org.eclipse.osgi.services_3.3.100.v20120522-1822
6   ACTIVE      org.eclipse.equinox.console_1.0.0.v20120522-1841
7   ACTIVE      slf4j.api_1.7.2
8   ACTIVE      ch.qos.logback.classic_1.0.9
9   ACTIVE      ch.qos.logback.core_1.0.9
10  ACTIVE      org.opendaylight.controller.logging.bridge_0.4.2.Helium
11  ACTIVE      com.sun.jersey.core_1.17.0
12  ACTIVE      com.sun.jersey.jersey-server_1.17.0
13  ACTIVE      org.apache.felix.gogo.shell_0.8.0.v201110170705
14  ACTIVE      javax.persistence_2.0.4.v201112161009
15  ACTIVE      org.springframework.web.servlet_3.1.3.RELEASE
16  ACTIVE      org.opendaylight.controller.topologymanager_0.4.2.Helium
17  ACTIVE      org.opendaylight.controller.usermanager.northbound_0.0.2.Helium
18  ACTIVE      org.springframework.beans_3.1.3.RELEASE
19  ACTIVE      javax.xml.rpc_1.1.0.v201005080400
20  ACTIVE      io.netty.codec_4.0.2.Final
21  ACTIVE      javax.annotation_1.1.0.v201209060031
22  ACTIVE      org.opendaylight.controller.configuration_0.4.3.Helium
23  RESOLVED    org.sdnhub.odl.tutorial.adsal_L2_forwarding_0.5.0.SNAPSHOT
24  ACTIVE      com.fasterxml.jackson.jaxrs.jackson-jaxrs-base_2.3.2
25  ACTIVE      org.opendaylight.controller.forwarding.staticrouting_0.5.2.Helium
26  RESOLVED    org.apache.coyote_7.0.53.v201406070630
                Master=39
27  ACTIVE      org.springframework.context.support_3.1.3.RELEASE
28  ACTIVE      org.apache.commons.lang_2.6.0
29  ACTIVE      org.opendaylight.controller.hosttracker_0.5.2.Helium
30  RESOLVED    org.apache.jasper_7.0.53.v201406070630
                Master=39
31  ACTIVE      org.springframework.core_3.1.3.RELEASE
32  ACTIVE      org.opendaylight.controller.arphandler_0.5.2.Helium
33  ACTIVE      org.opendaylight.controller.forwarding.staticrouting.northbound_0.4.2.Helium
34  ACTIVE      jcl.over.slf4j_1.7.2
35  ACTIVE      org.opendaylight.controller.appauth_0.4.2.Helium
36  ACTIVE      javax.portlet_0.0.0
37  ACTIVE ...
(more)
2015-04-28 11:49:57 -0700 edited question Maven fails when building odl controller

Hi,

I used this video to setup the odl controller. When I try to compile it, as shown in video, maven complains about following:

[ERROR]   The project org.opendaylight.controller:config-parent:0.4.0-SNAPSHOT (/home/denis/Schreibtisch/controller/controller/opendaylight/config/config-parent/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM: Could not find artifact org.opendaylight.yangtools:binding-parent:pom:0.8.0-SNAPSHOT and 'parent.relativePath' points at no local POM @ line 11, column 11 -> [Help 2]
org.apache.maven.model.resolution.UnresolvableModelException: Could not find artifact org.opendaylight.yangtools:binding-parent:pom:0.8.0-SNAPSHOT
  at org.apache.maven.project.ProjectModelResolver.resolveModel(ProjectModelResolver.java:159)
at org.apache.maven.model.building.DefaultModelBuilder.readParentExternally(DefaultModelBuilder.java:813)
at org.apache.maven.model.building.DefaultModelBuilder.readParent(DefaultModelBuilder.java:664)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:310)
at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:232)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:410)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:379)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:495)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:379)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:495)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:379)
at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:343)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:636)
at org.apache.maven.DefaultMaven.getProjectsForMavenReactor(DefaultMaven.java:585)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:234)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could not find artifact org.opendaylight.yangtools:binding-parent:pom:0.8.0-SNAPSHOT
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:538)
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:216)
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:193)
at org.sonatype.aether.impl.internal.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:286)
at org.apache.maven.project.ProjectModelResolver.resolveModel(ProjectModelResolver.java:155)
... 26 more
 Caused by: org.sonatype.aether.transfer.ArtifactNotFoundException: Could not find artifact org.opendaylight.yangtools:binding-parent:pom:0.8.0-SNAPSHOT
at org.sonatype.aether.impl.internal.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:528)
... 30 more

Am i missing some dependencies, the error messages says me, that there is some error in the pom file, dont know how to resolve hit. Help is appreciated.

My system: Ubuntu 14 ... (more)

2015-04-28 11:49:57 -0700 received badge  Editor (source)