Re: [controller-dev] [infrautils-dev] OK to resurrect c/64522 to first move infrautils.DiagStatus integration for datastore from genius to controller, and then improve it for GENIUS-138 ?

2018-06-07 Thread Muthukumaran K
I can think of one case which can fall-flat with the colocation of EOS owner of registered entity with a specific shard is that : When the entity owner starts running txns against another shard which may not be collocated, then we do not get the fullest benefit of colocation. For example, we

[controller-dev] Intermittent "Unable to create cache directory..." failures

2018-06-07 Thread Tom Pantelis
Hello, We've been seeing these intermittent netconf failures on jenkins: Caused by: java.lang.IllegalArgumentException: Unable to create cache directory at cache/schema at com.google.common.base.Preconditions.checkArgument(Preconditions.java:210) at

Re: [controller-dev] OK to resurrect c/64522 to first move infrautils.DiagStatus integration for datastore from genius to controller, and then improve it for GENIUS-138 ?

2018-06-07 Thread Robert Varga
On 07/06/18 19:14, Michael Vorburger wrote: > Robert, > > just to avoid any misunderstandings and unnecessary extra work to throw > away, may we double check and confirm that we correctly understand your > comment in  https://jira.opendaylight.org/browse/GENIUS-138 to mean that > we are past the

Re: [controller-dev] yang notifications to CDS to emit interesting state/status changes

2018-06-07 Thread Tom Pantelis
On Thu, Jun 7, 2018 at 3:38 PM, Faseela K wrote: > > > > > *From:* Tom Pantelis [mailto:tompante...@gmail.com] > *Sent:* Friday, June 08, 2018 1:05 AM > *To:* Faseela K > *Cc:* Michael Vorburger ; controller-dev < > controller-dev@lists.opendaylight.org>; genius-...@lists.opendaylight.org; >

Re: [controller-dev] yang notifications to CDS to emit interesting state/status changes

2018-06-07 Thread Faseela K
From: Tom Pantelis [mailto:tompante...@gmail.com] Sent: Friday, June 08, 2018 1:05 AM To: Faseela K Cc: Michael Vorburger ; controller-dev ; genius-...@lists.opendaylight.org; Robert Varga Subject: Re: yang notifications to CDS to emit interesting state/status changes On Thu, Jun 7, 2018

Re: [controller-dev] yang notifications to CDS to emit interesting state/status changes

2018-06-07 Thread Tom Pantelis
On Thu, Jun 7, 2018 at 3:20 PM, Faseela K wrote: > Yes, we are currently using EOS in such scenarios. But is there a way to > specify that I want my entity owner to be on “default-config shard leader”? > No - EOS and shards are different concepts. But you mentioned there's DTCN's from

Re: [controller-dev] yang notifications to CDS to emit interesting state/status changes

2018-06-07 Thread Robert Varga
On 07/06/18 21:20, Faseela K wrote: > Yes, we are currently using EOS in such scenarios. But is there a way to > specify that I want my entity owner to be on “default-config shard leader”? > > That’s why I was asking whether the new notifications you are going to > add will help in implementing

Re: [controller-dev] yang notifications to CDS to emit interesting state/status changes

2018-06-07 Thread Faseela K
Yes, we are currently using EOS in such scenarios. But is there a way to specify that I want my entity owner to be on “default-config shard leader”? That’s why I was asking whether the new notifications you are going to add will help in implementing such functionalities. Thanks, Faseela From:

Re: [controller-dev] yang notifications to CDS to emit interesting state/status changes

2018-06-07 Thread Tom Pantelis
On Thu, Jun 7, 2018 at 3:05 PM, Faseela K wrote: > [Changed subject] > > > > No, that’s not the point. > > I have event A that can be fired on nodeA, event B fired on node B, both > are DTCNs but on different shard leaders. > > But I want both the events to be processed on same node. > That's

[controller-dev] yang notifications to CDS to emit interesting state/status changes

2018-06-07 Thread Faseela K
[Changed subject] No, that’s not the point. I have event A that can be fired on nodeA, event B fired on node B, both are DTCNs but on different shard leaders. But I want both the events to be processed on same node. Thanks, Faseela From: Tom Pantelis [mailto:tompante...@gmail.com] Sent:

Re: [controller-dev] [infrautils-dev] OK to resurrect c/64522 to first move infrautils.DiagStatus integration for datastore from genius to controller, and then improve it for GENIUS-138 ?

2018-06-07 Thread Faseela K
Btw, I don’t want to divert the topic. ☺ The discussion here was whether it is now OK to resurrect https://git.opendaylight.org/gerrit/#/c/64522/, to first move infrautils.DiagStatus integration for datastore from genius to controller? Thanks, Faseela From:

Re: [controller-dev] [infrautils-dev] OK to resurrect c/64522 to first move infrautils.DiagStatus integration for datastore from genius to controller, and then improve it for GENIUS-138 ?

2018-06-07 Thread Tom Pantelis
On Thu, Jun 7, 2018 at 2:49 PM, Faseela K wrote: > Tom, > > Currently we have certain cases, where we use EOS to ensure that we > process a set of northbound+southbound events on same node. > > (I am not sure whether that is the actual purpose of EOS, but we use it > like that as well. ;)) >

Re: [controller-dev] [infrautils-dev] OK to resurrect c/64522 to first move infrautils.DiagStatus integration for datastore from genius to controller, and then improve it for GENIUS-138 ?

2018-06-07 Thread Faseela K
Tom, Currently we have certain cases, where we use EOS to ensure that we process a set of northbound+southbound events on same node. (I am not sure whether that is the actual purpose of EOS, but we use it like that as well. ;)) This has certain issues that in a 3 node cluster, your entity

Re: [controller-dev] [infrautils-dev] OK to resurrect c/64522 to first move infrautils.DiagStatus integration for datastore from genius to controller, and then improve it for GENIUS-138 ?

2018-06-07 Thread Tom Pantelis
On Thu, Jun 7, 2018 at 2:39 PM, Faseela K wrote: > Not related in this context, but if we can get shard leader change > notification, can we use that to derive an entity owner instead of using > EOS? ;) > Not exactly sure what you mean but shards and EOS are 2 different concepts... > > >

Re: [controller-dev] [infrautils-dev] OK to resurrect c/64522 to first move infrautils.DiagStatus integration for datastore from genius to controller, and then improve it for GENIUS-138 ?

2018-06-07 Thread Faseela K
Not related in this context, but if we can get shard leader change notification, can we use that to derive an entity owner instead of using EOS? ;) Thanks, Faseela From: infrautils-dev-boun...@lists.opendaylight.org [mailto:infrautils-dev-boun...@lists.opendaylight.org] On Behalf Of Tom

Re: [controller-dev] OK to resurrect c/64522 to first move infrautils.DiagStatus integration for datastore from genius to controller, and then improve it for GENIUS-138 ?

2018-06-07 Thread Tom Pantelis
On Thu, Jun 7, 2018 at 1:14 PM, Michael Vorburger wrote: > Robert, > > just to avoid any misunderstandings and unnecessary extra work to throw > away, may we double check and confirm that we correctly understand your > comment in https://jira.opendaylight.org/browse/GENIUS-138 to mean that > we

[controller-dev] OK to resurrect c/64522 to first move infrautils.DiagStatus integration for datastore from genius to controller, and then improve it for GENIUS-138 ?

2018-06-07 Thread Michael Vorburger
Robert, just to avoid any misunderstandings and unnecessary extra work to throw away, may we double check and confirm that we correctly understand your comment in https://jira.opendaylight.org/browse/GENIUS-138 to mean that we are past the "dependency of a mature project on an incubation