Re: [controller-dev] [release] [OpenDaylight TSC] Moving lldp code from controller

Just to play devil's advocate, new projects for such things have a significant set of additional overheads: * during releases, release engineering staff have to track it * added periodic merge jobs and integration jobs with spinup time that adds more load to our infra * higher risk of abandonment

Re: [controller-dev] 401 unauthorized error for a new proect

I'm on PTO at the moment, so I'll read through this in some more detail later, but wanted to chime in now to say that the TSC agreed a long time ago to support bug fixes in service releases for the previous release, e.g., Carbon while working toward releasing Nitrogen, and then off-cycle releases

[controller-dev] jmx mbeans to track transaction queue length

Hi controller devs, I know we have some really nice beans for looking at datastore stats: https://github.com/opendaylight/controller/tree/master/opendaylight/md-sal/sal-distributed-datastore/src/main/java/org/opendaylight/controller/cluster/datastore/jmx/mbeans However, I don't see a good way to

Re: [controller-dev] [release] Autorelease nitrogen failed to build sal-distributed-datastore from controller

Snippet: Running org.opendaylight.controller.cluster.datastore.DistributedDataStoreRemotingIntegrationTest Tests run: 36, Failures: 0, Errors: 1, Skipped: 3, Time elapsed: 263.336 sec <<< FAILURE! - in org.opendaylight.controller.cluster.datastore.DistributedDataStoreRemotingIntegrationTest

Re: [controller-dev] [release] Autorelease carbon failed to build sal-distributed-datastore from controller

Here's the snippet: 14:08:34 Running org.opendaylight.controller.cluster.datastore.entityownership.DistributedEntityOwnershipIntegrationTest 14:09:42 Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 69.662 sec <<< FAILURE! - in

Re: [controller-dev] hangs in SFT in autorelease

-api/0.10.0-Carbon > > mvn:org.opendaylight.mdsal/mdsal-binding-generator-api/0.10.0-Carbon > > > On Mon, May 1, 2017 at 4:15 PM, Colin Dixon <co...@colindixon.com> wrote: > >> That seems to be the root of the issues with our SFT hangs. Between SFT >> hangs a

Re: [controller-dev] hangs in SFT in autorelease

ries.blueprint.core:1.7.1] > > > On Mon, May 1, 2017 at 4:11 PM, Colin Dixon <co...@colindixon.com> wrote: > >> It seems like there's something wrong with who sal-binding-broker-impl >> comes up and doesn't get the ClassLoadingStrategy and then SFT hangs. So >>

Re: [controller-dev] hangs in SFT in autorelease

issue we were having before, but it's not AAA. --Colin On Mon, May 1, 2017 at 4:03 PM, Colin Dixon <co...@colindixon.com> wrote: > So, Luis told me to go look at the surefire results for some of the SFT > failures and I'm finding things like this: > > = failnever job #4 = > re

Re: [controller-dev] [release] Autorelease boron failed to build sal-distributed-datastore from controller

I know we're working on Carbon, but if we could pay some attention here as well, that would be great. Thanks, --Colin On Sun, Apr 30, 2017 at 11:00 PM, Jenkins < jenkins-dontre...@opendaylight.org> wrote: > Attention controller-devs, > > Autorelease boron failed to build

Re: [controller-dev] [release] Autorelease carbon failed to build sal-distributed-datastore from controller

failures don't kill autorelease. --Colin On Mon, Apr 24, 2017 at 11:19 AM, Tom Pantelis <tompante...@gmail.com> wrote: > Most likely timing issue in the test. This was added pretty recently by > Tomas Cere I believe - perhaps he could comment. > > On Mon, Apr 24, 2017 at 10:59 A

Re: [controller-dev] [release] Autorelease carbon failed to build sal-distributed-datastore from controller

This is the error. My guess is a timing issue. Others? --Colin Tests run: 4, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 212.104 sec <<< FAILURE! - in org.opendaylight.controller.cluster.sharding.DistributedShardedDOMDataTreeRemotingTest

Re: [controller-dev] [release] Autorelease carbon failed to build sal-distributed-datastore from controller

be fixed if it is) since my > rebuild [0] has built past the point of this failure. > > Regards, > Thanh > > [0] https://jenkins.opendaylight.org/releng/job/ > autorelease-release-carbon/243/ > > On Thu, Apr 13, 2017 at 9:58 PM, Colin Dixon <co...@colindixon.com> wrote:

Re: [controller-dev] [release] Autorelease carbon failed to build sal-distributed-datastore from controller

Tom, do you think you can take a look at this to see if it's a real failure? --Colin On Thu, Apr 13, 2017 at 5:54 PM, Jenkins wrote: > Attention controller-devs, > > Autorelease carbon failed to build sal-distributed-datastore from > controller in build >

Re: [controller-dev] bundle "org.opendaylight.controller.blueprint_0.6.0.SNAPSHOT [260]" could not be resolved. Reason: Missing Constraint: Import-Package: org.opendaylight.controller.config.facade.xm

Did we ever get a fix for this? --Colin On Mon, Mar 6, 2017 at 10:25 AM, Michael Vorburger wrote: > Hello controller-dev, > > do you know what could be causing this new SingleFeatureTest (SFT) failure? > > java.lang.IllegalStateException: Can't install feature >

Re: [controller-dev] [documentation] [int/test] [int/dist] Official clustering configuration

+100,000 to that. Really, almost everything on the wiki should have a big warning at the top that says: "this is likely out of date! check docs.opendaylight.org for information that's more likely to be up-to-date." --Colin On Fri, Feb 3, 2017 at 6:33 PM, Jamo Luhrsen wrote:

Re: [controller-dev] deprecating the config subsystem in Carbon?

That sounds good to me. What's the right way for us to "deprecate" the config subsystem. I guess the simplest thing would be add an @deprecated decorator to the relevant classes that get generated with a pointer to the docs on how to migrate. --Colin On Tue, Nov 15, 2016 at 5:07 PM, FREEMAN,

Re: [controller-dev] deprecating the config subsystem in Carbon?

> controller-dev-boun...@lists.opendaylight.org] *On Behalf Of *Colin Dixon > *Sent:* Tuesday, November 15, 2016 12:14 PM > *To:* controller-dev > *Subject:* [controller-dev] deprecating the config subsystem in Carbon? > > > > During last week's Kernel projects call [0], I

[controller-dev] deprecating the config subsystem in Carbon?

During last week's Kernel projects call [0], I asked if and when we wanted to deprecate the config subsystem. During the conversation, I think everyone agreed that we should strongly discourage people from building new projects based on it and encourage people to move toward Blueprint, which

Re: [controller-dev] [release] Memory leaks on blueprint restart

I realize I'm getting here late, but did we get an issue opened. Have we made any progress? --Colin On Tue, Oct 18, 2016 at 7:34 AM, Robert Varga wrote: > On 10/18/2016 12:38 PM, Martin Dindoffer wrote: > > So what's the status on this? Should I open an issue in controller's > >

[controller-dev] Some DDF notes from 9/29/2016

See attached files for raw notes. --Colin --Replacing-- Adding an option for MD-SAL Eventing with an off-the-shelf message bus The MD-SAL provides many kinds of events including RPCs, YANG notifications, and data change notifications. It does so using a custom eventing system which has

Re: [controller-dev] First shot at serializing data tree entities using the Binding Independent level

(FlowCapableStatisticsGatheringStatus.class, > null); > > List ncList = node.getNodeConnector(); > > List newNcList = new ArrayList<>(); > > if (ncList != null) { > > for (NodeConnector nc : ncList) { > > NodeConnectorBuilder ncBuilder = new NodeConnectorBuilder