Bug 8074 - actor name [test-device] is not unique! 73/54873/7
authormiroslav.kovac <miroslav.kovac@pantheon.tech>
Mon, 3 Apr 2017 12:39:19 +0000 (14:39 +0200)
committermiroslav.kovac <miroslav.kovac@pantheon.tech>
Wed, 10 May 2017 15:09:37 +0000 (17:09 +0200)
commitbd80e01f1967880fdd85f49d75b2186d728d18b5
treeeb8634afab61f46367f91d8aaa99fa902884cc56
parent228c46e1e7e00444ea60bbb98c86cdcce607b78e
Bug 8074 - actor name [test-device] is not unique!

When creating a new actor with same name as an old one, it might fail
becuase old actor might not be completely gone at this point.

This creates a slaveActor which will never be closed, but instead
every time that mountpoint is closed or master is changed, it would
update NetconfNodeActor data and keep the same actor.

Only time that actor is closed is when node was deleted. Or slave
became a master

The name of the actor is removed - letting akka to handle that -
log the akka created name.

Change-Id: I6d10db7b8902048632e336fb5a9701a797b363c6
Signed-off-by: miroslav.kovac <miroslav.kovac@pantheon.tech>
netconf/netconf-topology-singleton/src/main/java/org/opendaylight/netconf/topology/singleton/impl/NetconfNodeManager.java
netconf/netconf-topology-singleton/src/main/java/org/opendaylight/netconf/topology/singleton/impl/actors/NetconfNodeActor.java
netconf/netconf-topology-singleton/src/main/java/org/opendaylight/netconf/topology/singleton/messages/RefreshSlaveActor.java [new file with mode: 0644]