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;
>
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
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
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
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:
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
[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:
