Definitely the singleton in Carbon introduced changes in the entity-owner API,
this is what it was before (for a single instance):
{
"entity-owners": {
"entity-type": [
{
"type": "openflow",
"entity": [
{
"id": "/general-entity:entity[general-entity:name='openflow:1']",
"candidate": [
{
"name": "member-1"
}
],
"owner": "member-1"
}
]
}
]
}
}
And this is what I see now:
{
"entity-owners": {
"entity-type": [
{
"type": "org.opendaylight.mdsal.ServiceEntityType",
"entity": [
{
"id":
"/odl-general-entity:entity[odl-general-entity:name='openflow:1']",
"candidate": [
{
"name": "member-1"
}
],
"owner": "member-1"
}
]
},
{
"type": "org.opendaylight.mdsal.AsyncServiceCloseEntityType",
"entity": [
{
"id":
"/odl-general-entity:entity[odl-general-entity:name='openflow:1']",
"candidate": [
{
"name": "member-1"
}
],
"owner": "member-1"
}
]
}
]
}
}
Question: Which device type should I look at to extract the owner?
org.opendaylight.mdsal.ServiceEntityType or
org.opendaylight.mdsal.AsyncServiceCloseEntityType or does not matter?
BR/Luis
_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
