Re: [controller-dev] [netvirt-dev] [bgpcep-dev] [OpenDaylight TSC] TSC Vote to release latest build # 326 as Sodium SR2

FYI, we just reverted the offending patch with the help of Robert: https://git.opendaylight.org/gerrit/#/c/controller/+/87277/ We can go ahead and pick the next green sodium AR. BR/Luis > On Feb 1, 2020, at 6:53 AM, Robert Varga w

Re: [controller-dev] [netvirt-dev] [bgpcep-dev] [OpenDaylight TSC] TSC Vote to release latest build # 326 as Sodium SR2

FYI, here is the ticket: https://jira.opendaylight.org/browse/CONTROLLER-1928 <https://jira.opendaylight.org/browse/CONTROLLER-1928> > On Jan 29, 2020, at 1:50 PM, Jamo Luhrsen wrote: > > good work, Luis. inline... > > On 1/29/20 1:35 PM, Luis Gomez wrote: >> Ye

Re: [controller-dev] [bgpcep-dev] [OpenDaylight TSC] TSC Vote to release latest build # 326 as Sodium SR2

/controller/job/controller-csit-3node-clustering-tell-all-magnesium/ Anyway this last is in the cluster tell-based suite so probably not blocking considering this is not default cluster setting. BR/Luis > On Jan 29, 2020, at 9:05 AM, Luis Gomez wrote: > > Regarding the controller test

Re: [controller-dev] [bgpcep-dev] [OpenDaylight TSC] TSC Vote to release latest build # 326 as Sodium SR2

Regarding the controller test, I saw 2 regressions happening at the same time: Ask based perf test does not pass: https://jenkins.opendaylight.org/releng/job/controller-csit-3node-rest-clust-cars-perf-ask-only-sodium/

Re: [controller-dev] [bgpcep-dev] [OpenDaylight TSC] TSC Vote to release latest build # 326 as Sodium SR2

OK, it turned out the issue is nothing to do with global-jjb update but a change in 3rd party python library setuptools. We will try a patch to pin the working version. BR/Luis > On Jan 28, 2020, at 3:47 PM, Luis Gomez wrote: > > FYI I took a look and BGPCEP job is failing because

Re: [controller-dev] [bgpcep-dev] [OpenDaylight TSC] TSC Vote to release latest build # 326 as Sodium SR2

FYI I took a look and BGPCEP job is failing because it is not possible to install exabgp 3.4.16: pip install exabgp==3.4.16 ERROR: Package 'setuptools' requires a different Python: 2.7.12 not in '>=3.5'' should be empty. I believe this started to happen after last global-jjb update: ht

Re: [controller-dev] [openflowplugin-dev] Can't make it today's meeting. Please continue if there is topic to discuss.

No topic from me, only question is whether we should move issue https://jira.opendaylight.org/browse/OPNFLWPLUG-1074 to controller project after last comment from Somashekhar. BR/Luis > On Jan 27, 2020, at 8:18 AM, Arunprakash D via Lists.Opendaylight.Org > wrote: > > > > Get Outlook for

Re: [controller-dev] [OpenDaylight TSC] Micro-distribution: Follow Up from TWS

I missed Monday call, but I still have hard time to understand why we have not made any progress in this topic in Magnesium: first reason "not clear scope/use case" was addressed by just targeting Netconf micro-distribution in this release, second reason "lack of people" is not valid as there ar

Re: [controller-dev] [OpenDaylight Discuss] Migrating inventory/topology models

I think in the case of OFP the work can be split in 2: - Update topology model to last RFC (same as other projects in ODL). To me the sooner we can do this the better. This also may have reduced impact in OFP apps because the topology model contains very few data (e.g. no specific OFP extension

Re: [controller-dev] [release] CDS serialization format in Neon SR2/Sodium

a Neon SR2 member? > On Jul 18, 2019, at 2:29 PM, Robert Varga wrote: > > On 18/07/2019 20:52, Luis Gomez wrote: >> >> >>> On Jul 18, 2019, at 10:53 AM, Robert Varga wrote: >>> >>> On 18/07/2019 19:14, Luis Gomez wrote: >>>> Am I

[controller-dev] Sodium cluster regression

The blocker bug I was talking in the TSC call: https://jira.opendaylight.org/browse/CONTROLLER-1906 BR/Luis ___ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.open

Re: [controller-dev] [release] CDS serialization format in Neon SR2/Sodium

Also, are these changes already merged in the stable branch? > On Jul 18, 2019, at 11:52 AM, Luis Gomez wrote: > > > >> On Jul 18, 2019, at 10:53 AM, Robert Varga wrote: >> >> On 18/07/2019 19:14, Luis Gomez wrote: >>> Am I understanding we are i

Re: [controller-dev] [release] CDS serialization format in Neon SR2/Sodium

> On Jul 18, 2019, at 10:53 AM, Robert Varga wrote: > > On 18/07/2019 19:14, Luis Gomez wrote: >> Am I understanding we are introducing a non-compatible change in a Service >> Release? > > If you define non-compatible as 'you cannot just downgrade software&#

Re: [controller-dev] [release] CDS serialization format in Neon SR2/Sodium

Am I understanding we are introducing a non-compatible change in a Service Release? If so what is the reason for this? I hope there is good one because otherwise this is not a good practice. BR/Luis > On Jul 18, 2019, at 8:01 AM, Robert Varga wrote: > > Hello everyone, > > this is a notice

Re: [controller-dev] org/iq80/leveldb/DBFactory, shutting down JVM since 'akka.jvm-exit-on-fatal-error' is enabled for ActorSystem[opendaylight-cluster-data]

Have you tried without -r option? > On Apr 8, 2019, at 12:48 AM, sivashankar ravishankar > wrote: > > Hi All, > > I am facing this error in Neon, Fluorine releases in my Ubuntu 18.04 VM when > i try to install "feature:install -v -r odl-mdsal-all". Did anyone came > across this issue ? Pleas

Re: [controller-dev] Help me

Hi Chaco, In order to help, can you please specify the following: - ODL version - Features you are installing in ODL. - Full URL you are trying in your browser. BR/Luis > On Apr 8, 2019, at 12:55 PM, CHACO MUKADI wrote: > > Good evening organization, > I'm a finalist in the second year of co

Re: [controller-dev] Cluster problem

> On Mar 8, 2019, at 1:42 AM, Robert Varga wrote: > > On 08/03/2019 09:05, Luis Gomez wrote: >> Hi controller experts, >> >> I see sporadically this problem in one of our cluster deployments (Fluorine >> SR1): >> >> 1) Operational DS gets lo

[controller-dev] Cluster problem

Hi controller experts, I see sporadically this problem in one of our cluster deployments (Fluorine SR1): 1) Operational DS gets locked in member-1 (leader of shard-default-operational) after stopping member-2: 2019-03-01T14:49:05,189 | INFO | opendaylight-cluster-data-akka.actor.default-dis

Re: [controller-dev] OFP cluster test with "tell-based"

etconf/job/netconf-csit-3node-clustering-only-sodium/21/ <https://jenkins.opendaylight.org/releng/view/netconf/job/netconf-csit-3node-clustering-only-sodium/21/> BR/Luis > On Feb 26, 2019, at 1:01 PM, Robert Varga wrote: > > On 26/02/2019 21:52, Luis Gomez wrote: >>

Re: [controller-dev] OFP cluster test with "tell-based"

:35 AM, Robert Varga wrote: > > On 19/02/2019 19:50, Luis Gomez wrote: >> >> >>> On Feb 19, 2019, at 6:16 AM, Robert Varga >> <mailto:n...@hq.sk>> wrote: >>> >>> On 19/02/2019 02:11, Luis Gomez wrote: >>>> >>&g

Re: [controller-dev] OFP cluster test with "tell-based"

> On Feb 19, 2019, at 6:16 AM, Robert Varga wrote: > > On 19/02/2019 02:11, Luis Gomez wrote: >> >> >>> On Feb 13, 2019, at 2:22 AM, Robert Varga wrote: >>> >>> On 12/02/2019 19:44, Luis Gomez wrote: >>>> Hi everybody, >&g

Re: [controller-dev] OFP cluster test with "tell-based"

> On Feb 13, 2019, at 2:22 AM, Robert Varga wrote: > > On 12/02/2019 19:44, Luis Gomez wrote: >> Hi everybody, >> >> FYI I have just tried OFP cluster test with "tell-based" protocol: >> >> https://logs.opendaylight.org/releng/vex-yul-odl-je

[controller-dev] OFP cluster test with "tell-based"

Hi everybody, FYI I have just tried OFP cluster test with "tell-based" protocol: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/openflowplugin-csit-3node-clustering-only-neon/180/robot-plugin/log.html.gz My observations: 1) node/port down events do not clear links in topology, this

Re: [controller-dev] Kernel Project weekly meeting minutes

Thanks Michael for the summary, for some reason my mic did not work in the call. Anyway happy holidays to everybody (I guess there will be no call until next year). BR/Luis > On Dec 18, 2018, at 9:42 AM, Michael Vorburger wrote: > > Hello, > > (06:37:02 CET) odl_meetbot: Meeting ended Tue De

Re: [controller-dev] [release] fluorine-sr1 respin build is finished and successful

OFP is also updated now. > On Nov 18, 2018, at 6:19 AM, Tom Pantelis wrote: > > > > On Sun, Nov 18, 2018 at 7:35 AM Ariel Adam > wrote: > Hi everyone. > To complete the Fluorine SR1 #273 sign off process we are still missing > inputs for the controller and Openflowpl

Re: [controller-dev] Signing Off

Ryan, 4 years is long time and a lot of contribution. Thanks for that, we will definitively miss you. Also I wish you the best in your new endeavor, lets keep in touch. BR/Luis > On Aug 27, 2018, at 12:49 PM, Ryan Goulding wrote: > > Hi ODL Community, > > I have decided to make a career tr

[controller-dev] Circuit breaker problem

Hi Brian, Is the problem you talked during TWS today related to this one: https://jira.opendaylight.org/browse/CONTROLLER-1789 From the ticket it seems this occurs when there is high number of disk transactions and the disk happens to be a

Re: [controller-dev] Sprint to talk at today's TWS

> difference being persistence and upgraded transport (and the > application/service in question of course!). > > > > > > From: Luis Gomez [mailto:ece...@gmail.com <mailto:ece...@gmail.com>] > Sent: Monday, July 09, 2018 2:08 PM > To: Casey Cain &

Re: [controller-dev] Sprint to talk at today's TWS

Hi, It just occurred to me after the presentation today, the FPC agent use case may have some resemblance with the Honeycomb agent running in fd.io : https://wiki.fd.io/view/Honeycomb So I just leave the link in case Sprint is interested in loo

Re: [controller-dev] Which Release is the Most Recent in Stable State That Compiles

so no point to store that unless you want to build offline or similar. > > Sorry for going too details. I am just trying to avoid making mistakes in > such areas. It’s kind critical to me. > > > Thank you very much! > > Harry > > > From: Luis Gomez [mailt

Re: [controller-dev] Which Release is the Most Recent in Stable State That Compiles

stion but you could save the entire git repo or just the changes you did. > > > Best Regards, > > Harry > > > > From: Luis Gomez [mailto:ece...@gmail.com] > Sent: Tuesday, June 19, 2018 3:49 PM > To: Zhang, Harry > Cc: controller-dev@lists.opendaylight

Re: [controller-dev] Which Release is the Most Recent in Stable State That Compiles

Hi Harry, stable/oxygen is the latest stable release. > On Jun 19, 2018, at 1:46 PM, harry.zh...@us.fujitsu.com wrote: > > Hi Everybody, > > I am trying to find a recent stable branch to compile the controller and > Netconf projects. I did, > > git clone https://git.opendaylight.org/gerrit/p

Re: [controller-dev] [integration-dev] custom_shard_config.txt

I guess you have to use this file in combination with https://github.com/opendaylight/integration-distribution/blob/master/karaf/src/main/assembly/bin/configure_cluster.sh , af

Re: [controller-dev] Controller High CPU

> On Jun 12, 2018, at 7:06 PM, Tom Pantelis wrote: > > > > On Tue, Jun 12, 2018 at 10:01 PM, Luis Gomez <mailto:ece...@gmail.com>> wrote: > OK, then we just wait for the fix. > > > There's more work to do to before removing the all CSS code compl

Re: [controller-dev] Controller High CPU

OK, then we just wait for the fix. > On Jun 12, 2018, at 6:54 PM, Tom Pantelis wrote: > > > > On Tue, Jun 12, 2018 at 9:47 PM, Luis Gomez <mailto:ece...@gmail.com>> wrote: > Hi all, > > Today I noticed unusual high CPU in controller, so I installed sim

[controller-dev] Controller High CPU

Resending... (attachment does not pass max size) > On Jun 12, 2018, at 6:47 PM, Luis Gomez wrote: > > Hi all, > > Today I noticed unusual high CPU in controller, so I installed simple feature > "odl-restconf" and attached a profiler I saw below class uses

Re: [controller-dev] [yangtools-dev] patch-test triggers to run csit on patches

project? > On Jun 6, 2018, at 8:28 AM, Robert Varga wrote: > > On 06/06/18 17:15, Luis Gomez wrote: >> Couple of notes here: the "test--" framework used to >> trigger CSIT on a patch only works in Snapshot integrated projects (mdsal, >> controller, etc…)

Re: [controller-dev] [yangtools-dev] patch-test triggers to run csit on patches

Couple of notes here: the "test--" framework used to trigger CSIT on a patch only works in Snapshot integrated projects (mdsal, controller, etc…) and it does not build any downstream project apart from distribution. So this makes me wonder for this and also MRI project like odlparent, yangtools

Re: [controller-dev] [openflowplugin-dev] [release] Carbon SR4 - stable/carbon branch locked

ing in any other branch where the above patch is already merged. BR/Luis > On Apr 25, 2018, at 9:15 AM, Luis Gomez wrote: > > FYI I have just detected a recent feature conflict in Carbon through this > job: > > https://jenkins.opendaylight.org/releng/job/openflowplugin-csit

Re: [controller-dev] [openflowplugin-dev] [release] Carbon SR4 - stable/carbon branch locked

FYI I have just detected a recent feature conflict in Carbon through this job: https://jenkins.opendaylight.org/releng/job/openflowplugin-csit-1node-flow-services-all-carbon/ It seems like when al

Re: [controller-dev] [integration-dev] odl-restconf feature missing

; > Then launch the karaf from the local build karaf distribution directory under > faas ->districtuion-karaf/target/assembly/bin/karaf. > > feature:list | grep odl-restconf, there is no such feature anymore L. > > Thanks > XIngjun > > From: Luis Gomez [mai

Re: [controller-dev] [integration-dev] odl-restconf feature missing

Hi Xingjun, We have plenty of jobs building a patch and distribution just after and we have not noticed this problem. Maybe if you describe more the problem you have: does distribution works fine if built without faas? are other ODL features present in the resulting distribution? does your patc

Re: [controller-dev] accessing flow tables in ODL

cc-ing ofp list, OF tables are normally available through the inventory API described below: http://docs.opendaylight.org/en/stable-nitrogen/user-guide/openflow-plugin-project-user-guide.html#ofp-e2e-inv

[controller-dev] Fwd: [Opendaylight-users] More Nitrogen weirdness

Adding controller devs for the archetype question. > Begin forwarded message: > > From: Ryan Dietrich > Subject: [Opendaylight-users] More Nitrogen weirdness > Date: December 12, 2017 at 3:15:57 PM PST > To: opendaylight-us...@lists.opendaylight.org > > I ran into some issues with my southbound

Re: [controller-dev] [integration-dev] ODL crashing in CSIT jobs

which is "slower RAM" > > JamO > > On 11/29/2017 09:13 AM, Luis Gomez wrote: >> I do not remember all the issues related with memory but at least swap is >> required in the robot VM to generate the log.html >> when output.xml file is big. &g

Re: [controller-dev] [integration-dev] ODL crashing in CSIT jobs

see how things go. If we find it really useful we can move > it into 2 or 3. > > Regards, > Thanh > > On Mon, Nov 13, 2017 at 6:19 PM, Luis Gomez <mailto:ece...@gmail.com>> wrote: > +1, adding Andy: is it possible to get swap space in the VM from the cloud > p

Re: [controller-dev] [integration-dev] ODL crashing in CSIT jobs

ap = 0kB > > > > > > On Thu, Nov 9, 2017 at 1:39 AM, Stephen Kitt > <mailto:sk...@redhat.com>> wrote: > > > > > On Thu, 9 Nov 2017 10:28:14 +0100 > > > Robert Varga mailto:n...@hq.sk>> wrote: > > > > On 02/11/17 23:02,

Re: [controller-dev] ODL crashing in CSIT jobs

So from the time I was debugging the issue with Jamo and Thanh, it seems there is a memory leak but: 1) JVM does not kill itself, the OS does instead after the java process grows to 3.7G in a VM of 4G RAM (note Xmx is set to 2G but still the jvm goes far beyond that). 2) The issue happens so f

Re: [controller-dev] [unimgr-dev] SingleFeatureTest (SFT) failure on odl-integration-compatible-with-all due to ConflictingModificationAppliedException: Node was created by other transaction.

OK, I aborted without reading the last mail, anyway lets wait for next verity to see if this is transient or permanent problem in this patch. > On Oct 27, 2017, at 8:50 AM, Jamo Luhrsen wrote: > > > > On 10/27/2017 06:33 AM, Donald Hunter (donaldh) wrote: >> I pushed this patch but the Jenkin

Re: [controller-dev] SingleFeatureTest (SFT) failure on odl-integration-compatible-with-all due to ConflictingModificationAppliedException: Node was created by other transaction.

+1, otherwise we can always grep for the offending features in the distribution and remove them from the distribution-check. > On Oct 25, 2017, at 7:14 AM, Tomas Cere -X (tcere - PANTHEON TECHNOLOGIES at > Cisco) wrote: > > This is caused by some project that is still pulling in the old featur

Re: [controller-dev] SingleFeatureTest (SFT) failure on odl-integration-compatible-with-all due to ConflictingModificationAppliedException: Node was created by other transaction.

Vratko, I think we talked about this in the last integration call: if netconf project (or any other) has 2 or more features that are incompatible (e.g. produce SFT failures) but still required (e.g. for netconf device notifications xor netconf cluster use case), the project should select 1 as pr

Re: [controller-dev] [release] Controller/Clustering Carbon SR2 Blocker Bug

> > For the patch set to integration/distribution, should we push a patch set to > Oxegen or Nitrogen? > > Thanks, > > YuLing > > On Thu, Aug 17, 2017 at 1:08 PM, Luis Gomez <mailto:ece...@gmail.com>> wrote: > YuLing, > > Today TSC decided to give T

Re: [controller-dev] [release] Controller/Clustering Carbon SR2 Blocker Bug

): rovarga <>, skitt <>, anipbu <>, > LuisGomez <>, shague <>, jamoluhrsen <>, zxiiro <>, vishnoianil <> > [10:37am] odl_meetbot <>: friday (1): abhijitkumbhare <> > [10:38am] colindixon <>: #agreed <> we will drop TSD

Re: [controller-dev] [release] Controller/Clustering Carbon SR2 Blocker Bug

YuLing, Today TSC decided to give TSDR until EOD tomorrow (8/18) to get patches for autorelease and int/dist. I would suggest to push the patches today if you can to avoid last minute surprises. BR/Luis > On Aug 17, 2017, at 12:47 PM, YuLing Chen wrote: > > Hi An and Colin, > > We really w

Re: [controller-dev] [L2switch-dev] [l2switch] Regarding link discovery

duration=77972.554s, table=0, n_packets=0, > n_bytes=0, priority=2,in_port=2 actions=output:1,CONTROLLER:65535 > cookie=0x2b01, duration=78057.189s, table=0, n_packets=0, > n_bytes=0, priority=0 actions=drop > > Regards, > Amit > > > On Wed, Aug 16, 2017 a

Re: [controller-dev] [L2switch-dev] [l2switch] Regarding link discovery

Can you please post the flows you see in the OF switches? > On Aug 16, 2017, at 3:02 AM, Amit Kumar wrote: > > Hi Luis, > > I have installed odl-l2switch-switch and odl-restconf-all features apart from > odl-dlux-core. > > Regards, > Amit > > On A

Re: [controller-dev] [L2switch-dev] [l2switch] Regarding link discovery

Hi Amit, which features do you install in controller? > On Aug 15, 2017, at 5:19 AM, Amit Kumar wrote: > > Hello All, > > Could you guys provide your response, is it an expected behavior? I am facing > this behavior in both Beryllium and Carbon. > > Regards, > Amit > > On Mon, Aug 14, 2017 a

Re: [controller-dev] [openflowplugin-dev] Any takers for liblldp?

> On Jul 20, 2017, at 3:43 PM, Robert Varga wrote: > > On 21/07/17 00:32, Sam Hague wrote: >> What was the reasoning not to absorb liblldp into the openflow project? >> Because lldp isn't part of openflow? That makes sense and I don't think >> we will find a project as this really is it's own pr

Re: [controller-dev] [OpenDaylight Discuss] TWS Call on Monday 7/17

Jesus, can you please add me to the bug group and send me over bug link? > On Jul 18, 2017, at 9:06 AM, Thanh Ha wrote: > > On Tue, Jul 18, 2017 at 11:24 AM, Luis Gomez <mailto:ece...@gmail.com>> wrote: > Thanks this is clear, we need the JSON file structured by project

Re: [controller-dev] [OpenDaylight Discuss] TWS Call on Monday 7/17

Thanks this is clear, we need the JSON file structured by projects. Thanh, will you file this bug or you want me to do it? > On Jul 18, 2017, at 2:43 AM, Jesus M. Gonzalez-Barahona > wrote: > > On Mon, 2017-07-17 at 13:21 -0700, Luis Gomez wrote: >> I am sure Thanh has

Re: [controller-dev] [OpenDaylight Discuss] TWS Call on Monday 7/17

I am sure Thanh has already a list of issues, for me I think it is important to show per-project contribution given that, as mentioned in the call, the project name can be extracted from the git repo name (e.g. controller, integration/test, etc). BR/Luis > On Jul 17, 2017, at 11:21 AM, Thanh H

Re: [controller-dev] LLDP and ODL

openflowplugin does not install any LLDP rule by default, you have to either use table miss flow app [1] or l2switch [2] features to get LLDP packets automatically forwarded to controller. [1] http://docs.opendaylight.org/en/stable-carbon/getting-started-guide/project-release-notes/openflowplug

Re: [controller-dev] LLDP specification for SDN controller

BTW, from my traces ODL is using chassis type 4 (MAC) and port type 7 (logical assign). > On Jun 12, 2017, at 8:28 AM, Luis Gomez wrote: > > Well, I am not sure who wrote the LLDP wiki, if you read the IEEE standard > below we are using accepted values for these parameter

Re: [controller-dev] LLDP specification for SDN controller

2017, at 10:24 PM, sothy shan wrote: > > Thanks Luis. This document gives an idea for destination MAC addresss. What > about LLDP Data types. Chassis? Port? TTL? > > > On Mon, Jun 12, 2017 at 3:46 AM, Luis Gomez <mailto:ece...@gmail.com>> wrote: > This is because

Re: [controller-dev] LLDP specification for SDN controller

This is because OpenFlow uses a variant of the standard LLDP protocol called OpenFlow Discovery protocol: http://groups.geni.net/geni/wiki/OpenFlowDiscoveryProtocol BR/Luis > On Jun 9, 2017, at 10:55 PM, sothy shan wrote: > > > H

Re: [controller-dev] build failure when 'mvn archetype:generate' using '-DarchetypeCatalog'

It worked for me, I just updated: https://wiki.opendaylight.org/view/Controller_Core_Functionality_Tutorials:Main with '-DarchetypeCatalog=remote'. > On Apr 22, 2017, at 2:35 AM, Sam wrote: > > Some one on st

Re: [controller-dev] [integration-dev] CSIT test bugs

I added cluster logs to the bug. > On Apr 20, 2017, at 12:00 AM, Jozef Bacigál > wrote: > > Luis can you send me the karaf logs you made with DEBUG ? > > Jozef > Od: Luis Gomez mailto:ece...@gmail.com>> > Odoslané: štvrtok, 20. apríla 2017 3:01:56 > Kom

Re: [controller-dev] [integration-dev] CSIT test bugs

ins. This behavior is not observed in Boron where RPC works very quickly after OF device owner is killed. Current bug: https://bugs.opendaylight.org/show_bug.cgi?id=8185 BR/Luis > On Apr 19, 2017, at 5:28 PM, Luis Gomez wrote: > > I activated DEBUG for openflow and again I do not see

Re: [controller-dev] [opendaylight.org #40000] [integration-dev] Time sync between CSIT nodes

9.14.110, stratum 2, offset 0.020222, delay 0.02615 03:44:02 19 Apr 03:44:02 ntpdate[11411]: adjust time server 10.29.14.110 offset 0.020222 sec I can also push some patch to monitor this for a while. BR/luis > On Apr 18, 2017, at 5:52 PM, Luis Gomez wrote: > > Thank

[controller-dev] WARN message during OF cluster test (carbon)

Hi cluster experts, I am finding below message very often in karaf log during OpenFlow cluster test in carbon [1]: 2017-04-17 12:32:22,296 | WARN | lt-dispatcher-20 | FrontendClientMetadataBuilder| 196 - org.opendaylight.controller.sal-distributed-datastore - 1.5.0.SNAPSHOT | Unknown his

Re: [controller-dev] [opendaylight.org #40000] [integration-dev] Time sync between CSIT nodes

://stackoverflow.com/questions/26005056/synchronizing-clock-time-in-host-and-guest-under-kvm > On Apr 18, 2017, at 10:09 AM, Andrew Grimberg via RT > wrote: > > On 04/18/2017 09:52 AM, Luis Gomez via RT wrote: >> Forwarding the sync question helpdesk as I am not sure how the VM

Re: [controller-dev] [integration-dev] Clustering acceptance tests

aylight.org/show_bug.cgi?id=7901> Unfortunately last week we realized of a new issue in carbon: https://bugs.opendaylight.org/show_bug.cgi?id=7884 <https://bugs.opendaylight.org/show_bug.cgi?id=7884> BR/Luis > On Feb 9, 2017, at 5:32 PM, Luis Gomez wrote: > > Hi Vratko, >

Re: [controller-dev] [integration-dev] Clustering acceptance tests

openflow or cluster related, all bugs are now in openflow queue and I would expect openflow devs to move to cluster queue if that is where they belong to. BR/Luis > On Feb 7, 2017, at 10:34 AM, Luis Gomez wrote: > > >> On Feb 7, 2017, at 10:03 AM, Vratko Polak -X (vrp

Re: [controller-dev] [integration-dev] Clustering acceptance tests

/jenkins092/openflowplugin-csit-3node-clustering-only-carbon/470/archives/log.html.gz> > > From: Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco) > Sent: 7 February, 2017 15:05 > To: 'Luis Gomez' mailto:ece...@gmail.com>> > Cc: integration-

Re: [controller-dev] [integration-dev] Clustering acceptance tests

Here is what I know from OpenFlow plugin (cc-ing ofplugin devs): > * Does your project have a test plan mentioning specific cluster scenarios? Not written test plan but we are running a bunch of cluster tests. > * Do you have any of such scenarios implemented as Robot suites? 1) https://jenkin

Re: [controller-dev] [integration-dev] [int/test] Cluster testing

> On Feb 2, 2017, at 10:46 AM, Jamo Luhrsen wrote: > > > > On 02/02/2017 10:38 AM, Luis Gomez wrote: >> So I see 3 actions from integration today’s call: >> >> 1) Find out what documentation is relevant for test end users (e.g. >> developers

Re: [controller-dev] [integration-dev] [int/test] Cluster testing

So I see 3 actions from integration today’s call: 1) Find out what documentation is relevant for test end users (e.g. developers, integration people). This may include: - Feature/functionality description. - High level test plan. - Detailed test cases description. 2) Look at what of the above c

Re: [controller-dev] [int/test] Cluster testing

+1, looking forward to hear more about this idea :) > On Jan 30, 2017, at 8:50 AM, Jamo Luhrsen wrote: > > This is good, Vratko. We'll move to this topic after a quick round table. > > making cluster as stable as possible is important. > > JamO > > On 01/30/2017 07:59 AM, Vratko Polak -X (vr

Re: [controller-dev] [mdsal-dev] [integration-dev] 3node cluster regression in Carbon - since Jan 5th

.org > [mailto:mdsal-dev-boun...@lists.opendaylight.org] On Behalf Of Mainzer, Gal > Sent: יום ג 10 ינואר 2017 06:34 > To: Robert Varga > Cc: netvirt-...@lists.opendaylight.org; genius-...@lists.opendaylight.org; > Luis Gomez ; Jamo Luhrsen ; > mdsal-...@lists.opendaylight.org

Re: [controller-dev] [mdsal-dev] 3node cluster regression in Carbon - since Jan 5th

ndaylight/md-sal/sal-clustering-config/src/main/resources/initial/akka.conf > > Vratko. > > -Original Message- > From: controller-dev-boun...@lists.opendaylight.org > [mailto:controller-dev-boun...@lists.opendaylight.org] On Behalf Of Luis Gomez > Sent: 9 January,

Re: [controller-dev] [mdsal-dev] 3node cluster regression in Carbon - since Jan 5th

Patch looks good but in future I would ask controller people to inform broadly the community when you do these changes specially if they impact the cluster configuration. BR/Luis > On Jan 9, 2017, at 5:28 AM, Peretz, Ravit wrote: > > CSIT uses configure_cluster.sh to configure 3node jobs whi

Re: [controller-dev] [integration-dev] Looking for a co-mentor for internship project

+1, this project if still alive could leverage the intern work. > On Dec 13, 2016, at 5:56 AM, Alexis de Talhouët > wrote: > > >> On Dec 13, 2016, at 8:55 AM, Lori Jakab > > wrote: >> >> On 12/13/16 3:53 PM, Lori Jakab wrote: >>> Thanks Alexis, this is useful informa

Re: [controller-dev] Locating a Controller in a Network Topology

Hi Sean, AFAIK OpenFlow topologies do not include controllers but dataplane devices and links between them. I guess this is because: 1) controllers do not normally forward traffic (they control the forwarding) so connection topology is not very relevant; and 2) I do not remember anything in the

[controller-dev] Fwd: [OpenDaylight Infrastructure] how to set up an odl-clustering

fwd-ing to the appropriate list. I think you need at least 3 cluster nodes to elect a leader. > Begin forwarded message: > > From: gehe <13269178...@163.com> > Subject: [OpenDaylight Infrastructure] how to set up an odl-clustering > Date: October 8, 2016 at 1:14:37 AM PDT > To: odl-structure >

[controller-dev] OpenFlow Device connection bounce issue

Hi cluster devs, In case you have some time, maybe you can take a look at this: https://bugs.opendaylight.org/show_bug.cgi?id=6672 BR/Luis ___ controller-dev mailing list controller-dev@lists.opend

Re: [controller-dev] Regression in OF cluster test

the test? > > Best Regards, > An Ho > > [1] https://git.opendaylight.org/gerrit/#/c/45271/ > <https://git.opendaylight.org/gerrit/#/c/45271/> > [2] https://bugs.opendaylight.org/show_bug.cgi?id=6540 > <https://bugs.opendaylight.org/show_bug.cgi?id=6540>

Re: [controller-dev] Regression in OF cluster test

Most of the test regression seems to be related with entity-owner API behavior. Repair the test and retest everything is going to cost us one day, so should we go ahead or we revert the patch? BR/Luis > On Sep 7, 2016, at 9:42 AM, Luis Gomez wrote: > > I am not sure this was

[controller-dev] Regression in OF cluster test

I am not sure this was intended (cluster behavior change) but this patch: https://git.opendaylight.org/gerrit/#/c/45271/ introduced regression in the OpenFlow cluster test: https://jenkins.opendaylight.org/releng/view/CSIT-3node/job/openflowplugi

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

> On Wed, Aug 31, 2016 at 6:52 PM, Alexis de Talhouët <mailto:adetalho...@inocybe.com>> wrote: > > > On Wednesday, August 31, 2016, Luis Gomez <mailto:ece...@gmail.com>> wrote: > In any case it would be good to clarify in documentation or somewhere which

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

In any case it would be good to clarify in documentation or somewhere which port should be primarily used in ODL as I think many people (including me) thought it was 8181 as I can see in many user guides and even in our system test. BR/Luis > On Aug 31, 2016, at 3:50 PM, Luis Gomez wr

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

Correction, you are right both ports are open :) > On Aug 31, 2016, at 3:30 PM, Luis Gomez wrote: > > OK, then something happened after because today 8181 is the port everybody > uses and 8080 is not even open. > > >> On Aug 31, 2016, at 12:18 PM, Edward Warnicke >

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

git.opendaylight.org/gerrit/#/c/13546/> > > (a lot of work actually went into moving RESTCONF to 8080, because for > backward compatibility it also meant making neutron work with jetty.xml, > because neutron northbound wasn't being deprecated :) ). > > Ed > > On We

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

STCONF originally went on > 8181... once ADSAL was deprecated, *then* RESTCONF shifted to the 8080 port, > with 8181 retained for backward compatibility (I *think* I was the one to do > all that work... but its a bit murky in my mind). > > Ed > > On Wed, Aug 31, 201

Re: [controller-dev] etc/jetty.xml port 8080 and 8181

I think it is the other way around: 8181 is the "official" RESTCONF port and 8080 was used before in ADSAL and kept for API backwards compatibility reasons. > On Aug 31, 2016, at 5:57 AM, Edward Warnicke wrote: > > 8080 is the primary port... 8181 was a historical artifact. > > Ed > > On Wed,

[controller-dev] Cluster test regression in Boron

FYI, I logged this bug, I tested with RC2: https://bugs.opendaylight.org/show_bug.cgi?id=6587 BR/Luis ___ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight

Re: [controller-dev] [openflowplugin-dev] Changes in entity-owner

opened this bug to track this issue: https://bugs.opendaylight.org/show_bug.cgi?id=6554 <https://bugs.opendaylight.org/show_bug.cgi?id=6554> BR/Luis > On Aug 24, 2016, at 6:42 PM, Luis Gomez wrote: > > Actually it was only that run that did not show the registration issue, I >

Re: [controller-dev] [openflowplugin-dev] Changes in entity-owner

Actually it was only that run that did not show the registration issue, I believe we still have it: https://logs.opendaylight.org/releng/jenkins092/openflowplugin-csit-3node-clustering-only-boron/581/archives/log.html.gz BR/Luis > On Aug 23, 2016, at 10:06 AM, Luis Gomez wrote: > >

Re: [controller-dev] [openflowplugin-dev] Changes in entity-owner

gt; Od: Jozef Bacigál <mailto:jozef.baci...@pantheon.tech>> > Odoslané: 23. augusta 2016 11:18 > Komu: Anil Vishnoi; Luis Gomez; controller-dev@lists.opendaylight.org > <mailto:controller-dev@lists.opendaylight.org> > Kópia: openflowplugin-dev > Predmet: Re: [openflowplugin-d

Re: [controller-dev] Opendaylight support for Presto

In that case I think it is better to address the project mail list directly. > On Aug 16, 2016, at 5:24 AM, Aliza Nagauker > wrote: > > Hi, > > I refer to MEF 55 Open LSO Presto protocol for service configuration. > > We found the project https://wiki.opendaylight.org/view/Unimgr:Documentat

Re: [controller-dev] Change in mdsal[master]: Implimented checkStyleViolation errors in mdsal-common-api m...

Should be good now. > On Aug 2, 2016, at 11:56 AM, Brinda Jana (AM) > wrote: > > > > Hello dev team, > > I think > > https://jenkins.opendaylight.org/releng/job/mdsal-distribution-check-boron/ > > 1039/ : FAILURE

  1   2   >