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 <[email protected]> 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 <[email protected]> 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 <[email protected]> >> 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 >> / [email protected] >> reception: +421 2 206 65 114 / www.pantheon.sk >> >> [logo] >> >> > _______________________________________________ openflowplugin-dev mailing list [email protected] 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 / [email protected] reception: +421 2 206 65 114 / www.pantheon.sk [logo] _______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
