Luiz,

we did the same test:


3 cluster nodes, 1 switch, switch connected to 1 cluster node

entity ownership dump 
(/restconf/operational/entity-owners:entity-owners<http://${odlAddress}:${odlPort}/restconf/operational/entity-owners:entity-owners>)show

entity "ServiceEntityType" is registered in all cluster nodes


I  checked the logs and we are ok. We are cleaning after disconnect.


It is time to ask guys from controller if it is normal behavior or it is a bug.


Jozef


P.S.: Added controller mailing list

________________________________
Od: Jozef Bacigál <jozef.baci...@pantheon.tech>
Odoslané: 23. augusta 2016 8:16
Komu: Anil Vishnoi; Luis Gomez
Kópia: openflowplugin-dev
Predmet: Re: [openflowplugin-dev] Changes in entity-owner


Luis is there a chance to see logs from test ?


Jozef

________________________________
Od: Anil Vishnoi <vishnoia...@gmail.com>
Odoslané: 22. augusta 2016 22:15
Komu: Luis Gomez
Kópia: openflowplugin-dev
Predmet: Re: [openflowplugin-dev] Changes in entity-owner

This seems like a bug to me. Hopefully it's not a stale entry that was not 
cleaned up in a scenario where the device was connected to all the cluster node 
and then you disconnect and connect the same device to only one node. But even 
in this scenario it's a bug.

On Mon, Aug 22, 2016 at 9:51 AM, Luis Gomez 
<ece...@gmail.com<mailto:ece...@gmail.com>> wrote:
I mean if I connect a switch to just 1 member in the cluster, I see the other 2 
as candidates. Is this a bug? for your comments it seems like it is.

BR/Luis


On Aug 22, 2016, at 3:13 AM, Andrej Leitner 
<andrej.leit...@pantheon.tech<mailto:andrej.leit...@pantheon.tech>> wrote:

Just to clarify, my entity-owners GET was performed with 3 switches connected 
to all 3 cluster nodes (3 candidates are present in ServiceEntityType section).

________________________________
From: Jozef Bacigál
Sent: Monday, August 22, 2016 10:55 AM
To: Luis Gomez; Andrej Leitner
Cc: openflowplugin-dev
Subject: Re: [openflowplugin-dev] Changes in entity-owner

Hi Luis,

I don't fully understand what do you mean "regardless of switch connection". 
You mean if the switch is not connected to the cluster node you still see 
registered entity ?
EOS behavior does work the same per cluster node as singleton approach. (At 
least it should :) The switch has to be connected to cluster node: to create an 
entity candidate in EOS as a registration of service in singleton provider in 
singleton approach.

Jozef
________________________________________
Od: Luis Gomez <ece...@gmail.com<mailto:ece...@gmail.com>>
Odoslané: 19. augusta 2016 18:22
Komu: Andrej Leitner
Kópia: openflowplugin-dev
Predmet: Re: [openflowplugin-dev] Changes in entity-owner

Hi all,

I actually found a difference in the entity owner behavior so before I make a 
change in the test I want to make sure this is expected behavior (not a bug): 
in normal cluster implementation candidates are those that the OF switch 
connects to, in singleton the candidate is any member in the cluster regardless 
of switch connections. Is this expected?

Thanks/Luis


> On Aug 19, 2016, at 12:21 AM, Luis Gomez 
> <ece...@gmail.com<mailto:ece...@gmail.com>> wrote:
>
> Thanks Andrej,
>
> FYI, a patch for entity-owner API changes for Singleton is ready:
>
> https://git.opendaylight.org/gerrit/#/c/44380/
>
> Unfortunately current infra issues are preventing the patch verification.
>
> BR/Luis
>
>
>> On Aug 19, 2016, at 12:16 AM, Andrej Leitner 
>> <andrej.leit...@pantheon.tech<mailto:andrej.leit...@pantheon.tech>> wrote:
>>
>> Hi Luis,
>> my adjusted GET of entity-owners for stable/boron:
>>
>> --- TYPE [ofTransaction]
>>     ID : /a:entity[a:name='openflow:1']
>>     +-- OWNER: member-3
>>         candidate: member-3
>>     ID : /a:entity[a:name='openflow:3']
>>     +-- OWNER: member-1
>>         candidate: member-1
>>     ID : /a:entity[a:name='openflow:2']
>>     +-- OWNER: member-1
>>         candidate: member-1
>>
>> --- TYPE [openflow]
>>     ID : /a:entity[a:name='openflow:1']
>>     +-- OWNER: member-3
>>         candidate: member-3
>>         candidate: member-2
>>         candidate: member-1
>>     ID : /a:entity[a:name='openflow:3']
>>     +-- OWNER: member-1
>>         candidate: member-1
>>         candidate: member-2
>>         candidate: member-3
>>     ID : /a:entity[a:name='openflow:2']
>>     +-- OWNER: member-1
>>         candidate: member-1
>>         candidate: member-2
>>         candidate: member-3
>>
>> ... and for master:
>>
>> --- TYPE [org.opendaylight.mdsal.AsyncServiceCloseEntityType]
>>     ID : /a:entity[a:name='openflow:3']
>>     +-- OWNER: member-1
>>         candidate: member-1
>>     ID : /a:entity[a:name='openflow:2']
>>     +-- OWNER: member-1
>>         candidate: member-1
>>     ID : /a:entity[a:name='openflow:1']
>>     +-- OWNER: member-1
>>         candidate: member-1
>>
>> --- TYPE [org.opendaylight.mdsal.ServiceEntityType]
>>     ID : /a:entity[a:name='openflow:3']
>>     +-- OWNER: member-1
>>         candidate: member-1
>>         candidate: member-2
>>         candidate: member-3
>>     ID : /a:entity[a:name='openflow:2']
>>     +-- OWNER: member-1
>>         candidate: member-1
>>         candidate: member-2
>>         candidate: member-3
>>     ID : /a:entity[a:name='openflow:1']
>>     +-- OWNER: member-1
>>         candidate: member-1
>>         candidate: member-2
>>         candidate: member-3
>>
>> So it means that only entity types of double candidate approach are 
>> different using Singleton
>>
>> openflow -> ServiceEntityType
>> ofTransaction -> AsyncServiceCloseEntityType
>>
>> Regards.
>> -al-
>> AndrejLeitner
>> Software Developer
>>
>> Sídlo / Mlynské Nivy 56 / 821 05 Bratislava / Slovakia
>> R&D centrum / Janka Kráľa 9 /  974 01 Banská Bystrica / Slovakia
>> / andrej.leit...@pantheon.tech<mailto:andrej.leit...@pantheon.tech>
>> reception: +421 2 206 65 114 / www.pantheon.sk<http://www.pantheon.sk/>
>>
>> [logo]
>>
>>
>

_______________________________________________
openflowplugin-dev mailing list
openflowplugin-...@lists.opendaylight.org<mailto:openflowplugin-...@lists.opendaylight.org>
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
JozefBacigál
Software Engineer

Sídlo / Mlynské Nivy 56 / 821 05 Bratislava / Slovakia
R&D centrum / Janka Kráľa 9 /  974 01 Banská Bystrica / Slovakia
+421 908 766 972<tel:%2B421%20908%20766%20972> / jozef.baci...@pantheon.tech
reception: +421 2 206 65 114 / www.pantheon.sk<http://www.pantheon.sk/>

[logo]


AndrejLeitner
Software Developer

Sídlo / Mlynské Nivy 56 / 821 05 Bratislava / Slovakia
R&D centrum / Janka Kráľa 9 /  974 01 Banská Bystrica / Slovakia
/ andrej.leit...@pantheon.tech<mailto:andrej.leit...@pantheon.tech>
reception: +421 2 206 65 114 / www.pantheon.sk<http://www.pantheon.sk/>
[logo]




_______________________________________________
openflowplugin-dev mailing list
openflowplugin-...@lists.opendaylight.org<mailto:openflowplugin-...@lists.opendaylight.org>
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev




--
Thanks
Anil
JozefBacigál
Software Engineer

Sídlo / Mlynské Nivy 56 / 821 05 Bratislava / Slovakia
R&D centrum / Janka Kráľa 9 /  974 01 Banská Bystrica / Slovakia
+421 908 766 972 / jozef.baci...@pantheon.tech
reception: +421 2 206 65 114 / www.pantheon.sk

[logo]


JozefBacigál
Software Engineer

Sídlo / Mlynské Nivy 56 / 821 05 Bratislava / Slovakia
R&D centrum / Janka Kráľa 9 /  974 01 Banská Bystrica / Slovakia
+421 908 766 972 / jozef.baci...@pantheon.tech
reception: +421 2 206 65 114 / www.pantheon.sk

[logo]


_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev

Reply via email to