ryandgoulding

Uncaught error from thread [opendaylight-cluster-data-akka.actor.default-dispatcher-21] shutting down JVM since 'akka.jvm-exit-on-fatal-error' is enabled for ActorSystem[opendaylight-cluster-data]
java.lang.AbstractMethodError: org.opendaylight.controller.cluster.access.client.AbstractClientActor.getClientActorConfig()Lorg/opendaylight/controller/cluster/access/client/ClientActorConfig;

ryandgoulding

[ERROR] /code/autorelease/controller/opendaylight/md-sal/sal-dom-config/src/main/java/org/opendaylight/yang/gen/v1/urn/opendaylight/params/xml/ns/yang/md/sal/config/impl/cluster/singleton/service/rev160718/ClusterSingletonServiceProviderModule.java:[16,51] cannot find symbol
  symbol:   class ClusterSingletonServiceProvider
  location: package org.opendaylight.mdsal.singleton.common.api
[ERROR] /code/autorelease/controller/opendaylight/md-sal/sal-dom-config/src/main/java/org/opendaylight/yang/gen/v1/urn/opendaylight/params/xml/ns/yang/md/sal/config/impl/cluster/singleton/service/rev160718/ClusterSingletonServiceProviderModule.java:[65,21] cannot find symbol
  symbol:   class ClusterSingletonServiceProvider
  location: class org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.md.sal.config.impl.cluster.singleton.service.rev160718.ClusterSingletonServiceProviderModule
[ERROR] /code/autorelease/controller/opendaylight/md-sal/sal-dom-config/target/generated-sources/config-binding/org/opendaylight/yan

ryandgoulding

Caused by: org.apache.maven.wagon.authorization.AuthorizationException: Access denied to: https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/controller/aaa-karaf/0.4.0-SNAPSHOT/aaa-karaf-0.4.0-20160425.181803-1.pom, ReasonPhrase: Forbidden.
	at org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:618)
	at org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:606)
	at org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:524)
	at org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:505)
	at org.apache.maven.wagon.shared.http4.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:485)
	at org.eclipse.aether.connector.wagon.WagonRepositoryConnector$PutTask.run(WagonRepositoryConnector.java:871)
	... 16 more
[INFO] Deployment failed after 1 min 1 sec
Build step 'Deploy artifacts to Maven repository' changed build re

ryandgoulding

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 46.510 s
[INFO] Finished at: 2016-01-29T15:11:19+00:00
[INFO] Final Memory: 111M/723M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.3:compile (default-compile) on project netconf-util: Compilation failure: Compilation failure:
[ERROR] /code/ar/netconf/opendaylight/netconf/netconf-util/src/main/java/org/opendaylight/netconf/util/OrderedNormalizedNodeWriter.java:[179,63] no suitable method found for leafSetEntryNode(java.lang.Object,java.util.Map<org.opendaylight.yangtools.yang.common.QName,java.lang.String>)
[ERROR] method org.opendaylight.yangtools.yang.data.api.schema.stream.NormalizedNodeStreamAttributeWriter.leafSetEntryNode(org.opendaylight.yangtools.yang.common.QName,java.lang.Object,java.util.Ma

ryandgoulding

High level discussion summary:

* Distinguish between NETCONF protocol issues and YANG schema conformance in the payload.
* Loose mode for both is strongly desirable.
* Especially to support devices that may not yet have a model, or it's known to be incomplete.
* For schema conformance loose mode, consider making it a per-model tweak.
* Loose mode should only apply when violations are not structurally ambiguous. Data that cannot be deserialized by a reasonably tolerant parser should always be rejected. This means bad XML (syntactically broken - unbalanced nesting, missing >'s and so on) should probably not be accepted, but semantic issues (not passing yang schema checks, like elements not passing type tests or whole data structures not being defined in the schema at all) should be tolerable. Likewise NETCONF transport issues that are not ambiguous should be tolerable too.
* ODL northbound should always be well behaved; passthrough must be carefully considered, possibly with a separate endpoint (to make its us

ryandgoulding

[ERROR] Failed to execute goal org.opendaylight.yangtools:yang-maven-plugin:0.8.0-SNAPSHOT:generate-sources (default) on project aaa-authn-mdsal-api: Execution default of goal org.opendaylight.yangtools:yang-maven-plugin:0.8.0-SNAPSHOT:generate-sources failed: An API incompatibility was encountered while executing org.opendaylight.yangtools:yang-maven-plugin:0.8.0-SNAPSHOT:generate-sources: java.lang.ExceptionInInitializerError: null
[ERROR] -----------------------------------------------------
[ERROR] realm =    plugin>org.opendaylight.yangtools:yang-maven-plugin:0.8.0-SNAPSHOT
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/home/ryan/.m2/repository/org/opendaylight/yangtools/yang-maven-plugin/0.8.0-SNAPSHOT/yang-maven-plugin-0.8.0-SNAPSHOT.jar
[ERROR] urls[1] = file:/home/ryan/.m2/repository/org/opendaylight/mdsal/maven-sal-api-gen-plugin/0.8.0-SNAPSHOT/maven-sal-api-gen-plugin-0.8.0-SNAPSHOT.jar
[ERROR] urls[2] = file:/home/ryan/.m2/repository/org/opend

ryandgoulding

#!/usr/bin/env python

import calendar
import time
import sys
import logging
import json
import subprocess
import sqlite3

ryandgoulding

 <rgoulding___> Good Morning Ed
 <edwarnicke> Good morning :)
 <edwarnicke> How may I help you?
 <rgoulding___> I saw your discussion with Flavio and Kyle concerning https://bugs.opendaylight.org/show_bug.cgi?id=3680 .  You had mentioned having something that could make the ODL startup delay a lot better in general.  I was wondering if you were actively working this issue?  I am seeing this as well.
 <edwarnicke> Very actively
 <edwarnicke> Its been what has been occupying my attention the past few days
 <edwarnicke> That said, if you are interested in listening, it would probably be nice to explain the problem and the solution I'm working on :)
 <rgoulding___> Okay, great thanks.  I am definitely not as much of a maven/karaf ninja as you, but I'd love to hear what you are doing!
 <edwarnicke> So here's the root problem:
 <edwarnicke> How do you make sure ODL can startup in 'offline' mode