Hi Robert, What we found that thesetests fail on local set up when we run mvn clean install with integration profile as follows mvn clean install -Dmaven.repo.local=<our local repo>

Andy Great to know that infra is going to employ those tools. Zuul will sure qualify for pipelining jobs and even cross project integration. Also nodepool will be a great tool for Jenkins slave

Andy Great to know that infra is going to employ those tools. Zuul will sure qualify for pipelining jobs and even cross project integration. Also nodepool will be a great tool for Jenkins slave

Greetings Luis, The Jenkins queue is by default a FIFO queue. There are circumstances that re-order the execution though. The CSIT jobs are a prime example of things getting a bit funny

Hi, I am running into issue where 3 of the ListProcessingAndOrderingTest tests from sal-binding-dom-it are failing with following error [main] ERROR

Hi LF people, I have a question on Jenkins: I have observed that when we pile up an amount of test (CSIT) jobs in the build queue, these jobs are not executed in the coming order (FIFO). Is this

Thanks Carol. Surekha and I will be joining the Hackfest on both days. Thanks, Vaishali From: Carol Sanders <carol.sanders@...> Date: Thursday, May 29, 2014 7:04 PM To: "'integration-dev@...'

+1 FRM (configuration model) should be more abstract, high-level then plugin level definition of flow, Since capabilities and functionality may yeld different use-cases (e.g. FRM configuration

Makes sense (FRM level having a more abstract rule - which is broken down into multiple specific rules in the plugin). At least theoretically - implementation wise how complicated this will be remains

I’m talking about a lot more than just setting defaults. To give a simple example, let’s say I want to match on all HTTP traffic. With OpenFlow today I need to add two separate rules: one for

Hi devs, I have just added Jenkins ofplugin mail "openflowplugin-jenkins@..." to the OF13 system test notification, so now those subscribed to this list will receive 2 kind of

OMG yes! This! This is an extension of ‘provide good defaults’. Currently the OpenFlow plugin provides defaults for many parameters (very open to discussion about what the correct defaults

Totally agree. Only issue I have heard from some is that the implementations can vary between hardware implementations. I tend to regard OVS as the reference implementation purely due to the

Sorry for the delay, meant to get this done Friday night, I’ve been grinding through some sticking points this weekend on trying to extend OXMs. Here is a rough draft for a start hacking on the

Now there is: https://bugs.opendaylight.org/show_bug.cgi?id=1121 BR/Luis

Luis, I should be able to present it. 60 min or 90 mins slot would be good. I will see if I can pull in ON-LAB folks as well, if possible. I will not be able to join both days of hackfest , but can

Do we have a bug opened for this? I just want to make sure it doesn't fall off our radar. --Colin

Zoltan, That's a fair point - especially the following: forcing the same prerequisite rules on the abstract FlowCapable nodes is only one possibility. But it is also possible not to enforce those,

Hi, Sanity checking is indeed a great idea. But I think it would be important to clearly understand what needs to be sanity checked and what rather needs to be sanitized, or treated otherwise.

Prashanth, since we are building the documentation for this test, which information will you find more useful: - Existing flowmods that are verified as part of the integration system test - How to