package org.opendaylight.openflowplugin.api.openflow.device;
+import javax.annotation.CheckForNull;
+import com.google.common.util.concurrent.ListenableFuture;
import io.netty.util.Timeout;
import java.math.BigInteger;
import java.util.List;
+
+import io.netty.util.Timeout;
import org.opendaylight.controller.md.sal.binding.api.NotificationPublishService;
import org.opendaylight.controller.md.sal.binding.api.NotificationService;
-import org.opendaylight.controller.md.sal.binding.api.ReadTransaction;
+import org.opendaylight.controller.md.sal.binding.api.ReadOnlyTransaction;
import org.opendaylight.controller.md.sal.common.api.data.LogicalDatastoreType;
import org.opendaylight.openflowplugin.api.openflow.OpenFlowPluginTimer;
import org.opendaylight.openflowplugin.api.openflow.connection.ConnectionContext;
import org.opendaylight.openflowplugin.api.openflow.rpc.RpcContext;
import org.opendaylight.openflowplugin.api.openflow.statistics.ofpspecific.MessageSpy;
import org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.MultipartReply;
+import org.opendaylight.yang.gen.v1.urn.opendaylight.role.service.rev150727.OfpRole;
import org.opendaylight.yangtools.yang.binding.DataObject;
import org.opendaylight.yangtools.yang.binding.InstanceIdentifier;
*/
DeviceState getDeviceState();
+ /**
+ * Method has to activate (MASTER) or deactivate (SLAVE) TransactionChainManager.
+ * TransactionChainManager represents possibility to write or delete Node subtree data
+ * for actual Controller Cluster Node. We are able to have an active TxManager only if
+ * newRole is {@link OfpRole#BECOMESLAVE}.
+ * Parameters are used as marker to be sure it is change to SLAVE from MASTER or from
+ * MASTER to SLAVE and the last parameter "cleanDataStore" is used for validation only.
+ * @param role - NewRole expect to be {@link OfpRole#BECOMESLAVE} or {@link OfpRole#BECOMEMASTER}
+ */
+ ListenableFuture<Void> onClusterRoleChange(@CheckForNull OfpRole role);
+
/**
* Method creates put operation using provided data in underlying transaction chain.
*/
* represented by this context. This read only transaction has a fresh dataStore snapshot.
* There is a possibility to get different data set from DataStore
* as write transaction in this context.
+ * @return readOnlyTransaction - Don't forget to close it after finish reading
*/
- ReadTransaction getReadTransaction();
+ ReadOnlyTransaction getReadTransaction();
/**
RpcContext getRpcContext();
- /**
- * Callback when confirmed that device is disconnected from cluster
- */
- void onDeviceDisconnectedFromCluster();
+ @Override
+ void close();
}