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
