org.opendaylight.controller.clustering.it.provider

Class MdsalLowLevelTestProvider

java.lang.Object

org.opendaylight.controller.clustering.it.provider.MdsalLowLevelTestProvider

All Implemented Interfaces:

OdlMdsalLowlevelControlService, org.opendaylight.yangtools.yang.binding.RpcService

public class MdsalLowLevelTestProvider
extends Object
implements OdlMdsalLowlevelControlService

Constructor Summary

Constructors

Constructor and Description

MdsalLowLevelTestProvider(RpcProviderRegistry rpcRegistry, DOMRpcProviderService domRpcService, org.opendaylight.mdsal.singleton.common.api.ClusterSingletonServiceProvider singletonService, org.opendaylight.mdsal.dom.api.DOMSchemaService schemaService, org.opendaylight.mdsal.binding.dom.codec.api.BindingNormalizedNodeSerializer bindingNormalizedNodeSerializer, NotificationPublishService notificationPublishService, NotificationService notificationService, DOMDataBroker domDataBroker, org.opendaylight.mdsal.dom.api.DOMDataTreeService domDataTreeService, DistributedShardFactory distributedShardFactory, DistributedDataStoreInterface configDataStore, ActorSystemProvider actorSystemProvider)

Method Summary

Modifier and Type	Method and Description
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<AddShardReplicaOutput>>	addShardReplica(AddShardReplicaInput input) A specialised copy of cluster-admin:add-shard-replica.FIXME: Is this really needed for prefix shards, or even module shards(or is the cluster-admin RPC sufficient)?
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<BecomePrefixLeaderOutput>>	becomePrefixLeader(BecomePrefixLeaderInput input) Upon receiving this, the member shall ask the appropriate APIto become Leader of the given shard (presumably the llt:list-ints one,created by produce-transactions) and return immediatelly.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<CheckPublishNotificationsOutput>>	checkPublishNotifications(CheckPublishNotificationsInput input) Upon receiving this, the member shall immediatelly returnthe current tracking data related to the current (or previous) taskstarted by start-publish-notifications with this id.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<CreatePrefixShardOutput>>	createPrefixShard(CreatePrefixShardInput input) Upon receiving this, the member creates a prefix shard at the instance-identifier, with replicason the required members.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<DeconfigureIdIntsShardOutput>>	deconfigureIdIntsShard(DeconfigureIdIntsShardInput input) Upon receiving this, the member shall ask the appropriate APIto remove the llt:id-ints shard (presumably created by produce-transactions)and return immediatelly.It is expected the data would move to the root prefix shard seamlessly.TODO: Make shard name configurable by input?
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<IsClientAbortedOutput>>	isClientAborted(IsClientAbortedInput input) Return state of cds-access-client.FIXME: Is an input needed?
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<ProduceTransactionsOutput>>	produceTransactions(ProduceTransactionsInput input) Upon receiving this, the member shall make sure the outer list itemof llt:in-ints exists for the given id, make sure a shard forthe whole (config) id-ints is created (by creating and closing producerfor the whole id-ints), and create a DOMDataTreeProducer for that item (using that shard).FIXME: Is the above the normal way of creating prefix-based chards?Then start creating (one by one) and submitting transactionsto randomly add or delete items on the inner list for that id.To ensure balanced number of deletes, the first write can createa random set of random numbers.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<RegisterBoundConstantOutput>>	registerBoundConstant(RegisterBoundConstantInput input) Upon receiving this, the member has to create and registera bound llt:get-contexted-constant implementation (routed RPC).If the registration fails for any reason, propagate the corresponding error.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<RegisterConstantOutput>>	registerConstant(RegisterConstantInput input) Upon receiving this, the member has to create llt:get-constantimplementation (global RPC).
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<RegisterDefaultConstantOutput>>	registerDefaultConstant(RegisterDefaultConstantInput input) Upon receiving this, the member has to create and registera default llt:get-contexted-constant implementation (routed RPC).If the registration fails for any reason, propagate the corresponding error.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<RegisterFlappingSingletonOutput>>	registerFlappingSingleton(RegisterFlappingSingletonInput input) Upon receiving this, the member checks whether it has already createda 'flapping' application implementation and 'active' flag is set, and fails if yes.If no, the member (creates a flapping application implementation,)sets the active flag, initializes local variable flap-count to 0,and registers the implementation as a singleton application.If the registration fails for any reason, propagate the corresponding error.If the application is instantiated, it immediatelly un-registers itself.When the application instance is closed, it increments flap-countand if active flag is set, re-registers the application implementation as a singleton.If either un-registration or re-registration fails, 'active' flag is unset,flap-count is set to negative of its previous value (minus one in case of un-registration)to signal a failure has happened.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<RegisterSingletonConstantOutput>>	registerSingletonConstant(RegisterSingletonConstantInput input) Upon receiving this, the member checks whether it has already registereda singleton application, and fails if yes.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<RemovePrefixShardOutput>>	removePrefixShard(RemovePrefixShardInput input) Upon receiving this, the member removes the prefix based shard identifier by this prefix.This must be called from the same node that created the shard.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<RemoveShardReplicaOutput>>	removeShardReplica(RemoveShardReplicaInput input) A specialised copy of cluster-admin:remove-shard-replica.FIXME: Is this really needed for prefix shards, or even module shards(or is the cluster-admin RPC sufficient)?
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<ShutdownPrefixShardReplicaOutput>>	shutdownPrefixShardReplica(ShutdownPrefixShardReplicaInput input) Upon receiving this, the member will try to gracefully shutdown local configurationdata store prefix-based shard replica.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<ShutdownShardReplicaOutput>>	shutdownShardReplica(ShutdownShardReplicaInput input) Upon receiving this, the member will try to gracefully shutdown local configurationdata store module-based shard replica.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<StartPublishNotificationsOutput>>	startPublishNotifications(StartPublishNotificationsInput input) Upon receiving this, the member checks whether it is already in the middle of publishing,for this id, and fails if yes.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<SubscribeDdtlOutput>>	subscribeDdtl(SubscribeDdtlInput input) Upon receiving this, the member checks whether it has already subscribedand fails if yes.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<SubscribeDtclOutput>>	subscribeDtcl(SubscribeDtclInput input) Upon receiving this, the member checks whether it has already subscribedand fails if yes.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<SubscribeYnlOutput>>	subscribeYnl(SubscribeYnlInput input) Upon receiving this, the member checks whether it has already subscribeda yang listener for the given id, and fails if yes.If no, the member subscribes a Yang notification listener to listen forllt:id-sequence notifications.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<UnregisterBoundConstantOutput>>	unregisterBoundConstant(UnregisterBoundConstantInput input) Upon receiving this, the member has to unregisterany llt:get-contexted-constant implementations bound to the context.If no bound implementation for the context has been registered, do nothing.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<UnregisterConstantOutput>>	unregisterConstant(UnregisterConstantInput input) Upon receiving this, the member has to unregisterany llt:get-constant implementations it has registered.If no implementation has been registered, do nothing.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<UnregisterDefaultConstantOutput>>	unregisterDefaultConstant(UnregisterDefaultConstantInput input) Upon receiving this, the member has to unregisterany llt:get-contexted-constant default implementations it has registered.If no default implementation has been registered, do nothing.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<UnregisterFlappingSingletonOutput>>	unregisterFlappingSingleton(UnregisterFlappingSingletonInput input) Upon receiving this, the member checks whether it has createda flapping application, and fails if no.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<UnregisterSingletonConstantOutput>>	unregisterSingletonConstant(UnregisterSingletonConstantInput input) Upon receiving this, the member checks whether it has currently registereda singleton application, and fails if no.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<UnsubscribeDdtlOutput>>	unsubscribeDdtl(UnsubscribeDdtlInput input) Upon receiving this, the member checks whether it has currently subscribeda DOMDataTreeListener for llt:id-ints changes, and fails if no.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<UnsubscribeDtclOutput>>	unsubscribeDtcl(UnsubscribeDtclInput input) Upon receiving this, the member checks whether it has currently subscribeda Data Tree Change Listener for llt:id-ints changes, and fails if no.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<UnsubscribeYnlOutput>>	unsubscribeYnl(UnsubscribeYnlInput input) Upon receiving this, the member checks whether it has currently subscribeda yang listener for the given id, and fails if no.
com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<WriteTransactionsOutput>>	writeTransactions(WriteTransactionsInput input) Upon receiving this, the member shall make sure the outer list itemof llt:id-ints exists for the given id, and then start creating (one by one)and submitting transactions to randomly add or delete items on the inner list for that id.The randomness should avoid creating conflicting writes (at least for non-chainedtransactions).

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

MdsalLowLevelTestProvider

public MdsalLowLevelTestProvider(RpcProviderRegistry rpcRegistry,
                                 DOMRpcProviderService domRpcService,
                                 org.opendaylight.mdsal.singleton.common.api.ClusterSingletonServiceProvider singletonService,
                                 org.opendaylight.mdsal.dom.api.DOMSchemaService schemaService,
                                 org.opendaylight.mdsal.binding.dom.codec.api.BindingNormalizedNodeSerializer bindingNormalizedNodeSerializer,
                                 NotificationPublishService notificationPublishService,
                                 NotificationService notificationService,
                                 DOMDataBroker domDataBroker,
                                 org.opendaylight.mdsal.dom.api.DOMDataTreeService domDataTreeService,
                                 DistributedShardFactory distributedShardFactory,
                                 DistributedDataStoreInterface configDataStore,
                                 ActorSystemProvider actorSystemProvider)

Method Detail

unregisterSingletonConstant

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<UnregisterSingletonConstantOutput>> unregisterSingletonConstant(UnregisterSingletonConstantInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member checks whether it has currently registereda singleton application, and fails if no. If yes, the member shall unregisterthe application, presumably causing application instantiation on other member,and closing of the local application instance (unregistering llt:get-singleton-constant).If the unregistration fails for any reason, propagate the corresponding error.

Specified by:

unregisterSingletonConstant in interface OdlMdsalLowlevelControlService

startPublishNotifications

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<StartPublishNotificationsOutput>> startPublishNotifications(StartPublishNotificationsInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member checks whether it is already in the middle of publishing,for this id, and fails if yes. If no, the member shall clear any state tracking data possibly presentfrom the previous call wth this id, and start publishing llt:id-sequencenotifications with the given id and sequence numbers increasing from 1.The RPC shall return immediatelly before the first notification is published.The publishing task stops on first error of after the given time.

Specified by:

startPublishNotifications in interface OdlMdsalLowlevelControlService

subscribeDtcl

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<SubscribeDtclOutput>> subscribeDtcl(SubscribeDtclInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member checks whether it has already subscribedand fails if yes. If no, the member subscribes a Data Tree Change Listenerto listen for changes on whole llt:id-ints. The first notification received is stored immediately.Every notification received after the first one has the data(getDataBefore()) compared with thelast stored notification(called local copy), if they match the local copy is overwritten withthis notifications data(getDataAfter()). If they don't match the new notification is ignored.

Specified by:

subscribeDtcl in interface OdlMdsalLowlevelControlService

writeTransactions

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<WriteTransactionsOutput>> writeTransactions(WriteTransactionsInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member shall make sure the outer list itemof llt:id-ints exists for the given id, and then start creating (one by one)and submitting transactions to randomly add or delete items on the inner list for that id.The randomness should avoid creating conflicting writes (at least for non-chainedtransactions). The recommended way is to require the random numberhas low significant bits different than the past ~100k numbers.To ensure balanced number of deletes, the first write can createa random set of numbers. Other writes shall be one per number.The writes shall use the old API, transaction (chains) created directly on datastore(as opposed to DOMDataTreeProducer)..get with a timeout on currently earliest non-complete Future (from .submit)shall be used as the primary wait method to throttle the submission rate.This RPC shall not return until all transactions are confirmed successful,or an exception is raised (the exception should propagate to restconf response).OptimisticLockException is always considered an error.

Specified by:

writeTransactions in interface OdlMdsalLowlevelControlService

isClientAborted

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<IsClientAbortedOutput>> isClientAborted(IsClientAbortedInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Return state of cds-access-client.FIXME: Is an input needed?

Specified by:

isClientAborted in interface OdlMdsalLowlevelControlService

removeShardReplica

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<RemoveShardReplicaOutput>> removeShardReplica(RemoveShardReplicaInput input)

Description copied from interface: OdlMdsalLowlevelControlService

A specialised copy of cluster-admin:remove-shard-replica.FIXME: Is this really needed for prefix shards, or even module shards(or is the cluster-admin RPC sufficient)?

Specified by:

removeShardReplica in interface OdlMdsalLowlevelControlService

subscribeYnl

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<SubscribeYnlOutput>> subscribeYnl(SubscribeYnlInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member checks whether it has already subscribeda yang listener for the given id, and fails if yes.If no, the member subscribes a Yang notification listener to listen forllt:id-sequence notifications. The member also creates a local variable(called local-number) for the sequence number and initialize that to 0.Also three local counters are initialized to 0: all-not, id-not, err-not.Upon receiving any id-sequence notification, all-not is incremented.Each id-sequence notification of matching id shall increment id-not.If local-number was one less than the sequence number (from a notification matching id),increment local-number, else increment err-not.

Specified by:

subscribeYnl in interface OdlMdsalLowlevelControlService

removePrefixShard

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<RemovePrefixShardOutput>> removePrefixShard(RemovePrefixShardInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member removes the prefix based shard identifier by this prefix.This must be called from the same node that created the shard.

Specified by:

removePrefixShard in interface OdlMdsalLowlevelControlService

becomePrefixLeader

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<BecomePrefixLeaderOutput>> becomePrefixLeader(BecomePrefixLeaderInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member shall ask the appropriate APIto become Leader of the given shard (presumably the llt:list-ints one,created by produce-transactions) and return immediatelly.

Specified by:

becomePrefixLeader in interface OdlMdsalLowlevelControlService

unregisterBoundConstant

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<UnregisterBoundConstantOutput>> unregisterBoundConstant(UnregisterBoundConstantInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member has to unregisterany llt:get-contexted-constant implementations bound to the context.If no bound implementation for the context has been registered, do nothing.

Specified by:

unregisterBoundConstant in interface OdlMdsalLowlevelControlService

registerSingletonConstant

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<RegisterSingletonConstantOutput>> registerSingletonConstant(RegisterSingletonConstantInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member checks whether it has already registereda singleton application, and fails if yes. If no, the member createsan application implementation based on the given constantand registers the implementation as a singleton application.If the registration fails for any reason, propagate the corresponding error.If the application is instantiated, it creates and registersa llt:get-singleton-constant implementation, which returns the given costant.When the application instance is closed, it unregisters thatllt:get-singleton-constant implementation.

Specified by:

registerSingletonConstant in interface OdlMdsalLowlevelControlService

registerDefaultConstant

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<RegisterDefaultConstantOutput>> registerDefaultConstant(RegisterDefaultConstantInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member has to create and registera default llt:get-contexted-constant implementation (routed RPC).If the registration fails for any reason, propagate the corresponding error.

Specified by:

registerDefaultConstant in interface OdlMdsalLowlevelControlService

unregisterConstant

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<UnregisterConstantOutput>> unregisterConstant(UnregisterConstantInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member has to unregisterany llt:get-constant implementations it has registered.If no implementation has been registered, do nothing.

Specified by:

unregisterConstant in interface OdlMdsalLowlevelControlService

unregisterFlappingSingleton

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<UnregisterFlappingSingletonOutput>> unregisterFlappingSingleton(UnregisterFlappingSingletonInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member checks whether it has createda flapping application, and fails if no. If yes, the member shallset the active flag to false and return the current flap-count value.

Specified by:

unregisterFlappingSingleton in interface OdlMdsalLowlevelControlService

addShardReplica

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<AddShardReplicaOutput>> addShardReplica(AddShardReplicaInput input)

Description copied from interface: OdlMdsalLowlevelControlService

A specialised copy of cluster-admin:add-shard-replica.FIXME: Is this really needed for prefix shards, or even module shards(or is the cluster-admin RPC sufficient)?

Specified by:

addShardReplica in interface OdlMdsalLowlevelControlService

subscribeDdtl

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<SubscribeDdtlOutput>> subscribeDdtl(SubscribeDdtlInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member checks whether it has already subscribedand fails if yes. If no, the member subscribes a DOMDataTreeListenerto listen for changes on whole llt:id-ints, and storesthe state from the initial notification to a local variable (called the local copy).Each Data Tree Change from further notifications shall be appliedto the local copy if it is compatible(the old state from notification is equal to the local copy state).If a notification is not compatible, it shall be ignored.

Specified by:

subscribeDdtl in interface OdlMdsalLowlevelControlService

registerBoundConstant

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<RegisterBoundConstantOutput>> registerBoundConstant(RegisterBoundConstantInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member has to create and registera bound llt:get-contexted-constant implementation (routed RPC).If the registration fails for any reason, propagate the corresponding error.

Specified by:

registerBoundConstant in interface OdlMdsalLowlevelControlService

registerFlappingSingleton

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<RegisterFlappingSingletonOutput>> registerFlappingSingleton(RegisterFlappingSingletonInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member checks whether it has already createda 'flapping' application implementation and 'active' flag is set, and fails if yes.If no, the member (creates a flapping application implementation,)sets the active flag, initializes local variable flap-count to 0,and registers the implementation as a singleton application.If the registration fails for any reason, propagate the corresponding error.If the application is instantiated, it immediatelly un-registers itself.When the application instance is closed, it increments flap-countand if active flag is set, re-registers the application implementation as a singleton.If either un-registration or re-registration fails, 'active' flag is unset,flap-count is set to negative of its previous value (minus one in case of un-registration)to signal a failure has happened.

Specified by:

registerFlappingSingleton in interface OdlMdsalLowlevelControlService

unsubscribeDtcl

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<UnsubscribeDtclOutput>> unsubscribeDtcl(UnsubscribeDtclInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member checks whether it has currently subscribeda Data Tree Change Listener for llt:id-ints changes, and fails if no. If yes, the membershall unsubscribe the listener, read state of id-ints, compare thatto the local copy, and return whether the local copy is the same.

Specified by:

unsubscribeDtcl in interface OdlMdsalLowlevelControlService

createPrefixShard

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<CreatePrefixShardOutput>> createPrefixShard(CreatePrefixShardInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member creates a prefix shard at the instance-identifier, with replicason the required members.

Specified by:

createPrefixShard in interface OdlMdsalLowlevelControlService

deconfigureIdIntsShard

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<DeconfigureIdIntsShardOutput>> deconfigureIdIntsShard(DeconfigureIdIntsShardInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member shall ask the appropriate APIto remove the llt:id-ints shard (presumably created by produce-transactions)and return immediatelly.It is expected the data would move to the root prefix shard seamlessly.TODO: Make shard name configurable by input?

Specified by:

deconfigureIdIntsShard in interface OdlMdsalLowlevelControlService

unsubscribeYnl

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<UnsubscribeYnlOutput>> unsubscribeYnl(UnsubscribeYnlInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member checks whether it has currently subscribeda yang listener for the given id, and fails if no. If yes, the membershall unsubscribe the listener and return values of the local variables.

Specified by:

unsubscribeYnl in interface OdlMdsalLowlevelControlService

checkPublishNotifications

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<CheckPublishNotificationsOutput>> checkPublishNotifications(CheckPublishNotificationsInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member shall immediatelly returnthe current tracking data related to the current (or previous) taskstarted by start-publish-notifications with this id.

Specified by:

checkPublishNotifications in interface OdlMdsalLowlevelControlService

produceTransactions

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<ProduceTransactionsOutput>> produceTransactions(ProduceTransactionsInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member shall make sure the outer list itemof llt:in-ints exists for the given id, make sure a shard forthe whole (config) id-ints is created (by creating and closing producerfor the whole id-ints), and create a DOMDataTreeProducer for that item (using that shard).FIXME: Is the above the normal way of creating prefix-based chards?Then start creating (one by one) and submitting transactionsto randomly add or delete items on the inner list for that id.To ensure balanced number of deletes, the first write can createa random set of random numbers. Other writes shall be one per number.The writes shall use DOMDataTreeProducer API, as opposed to transaction (chains)created directly on datastore..get with a timeout on currently earliest non-complete Future (from .submit)shall be used as the primary wait method to throttle the submission rate.This RPC shall not return until all transactions are confirmed successful,or an exception is raised (the exception should propagate to restconf response).OptimisticLockException is always considered an error.In either case, the producer should be closed before returning,but the shard and the whole id item shall be kept as they are.

Specified by:

produceTransactions in interface OdlMdsalLowlevelControlService

shutdownShardReplica

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<ShutdownShardReplicaOutput>> shutdownShardReplica(ShutdownShardReplicaInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member will try to gracefully shutdown local configurationdata store module-based shard replica.

Specified by:

shutdownShardReplica in interface OdlMdsalLowlevelControlService

shutdownPrefixShardReplica

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<ShutdownPrefixShardReplicaOutput>> shutdownPrefixShardReplica(ShutdownPrefixShardReplicaInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member will try to gracefully shutdown local configurationdata store prefix-based shard replica.

Specified by:

shutdownPrefixShardReplica in interface OdlMdsalLowlevelControlService

registerConstant

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<RegisterConstantOutput>> registerConstant(RegisterConstantInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member has to create llt:get-constantimplementation (global RPC). If the registration fails for any reason,propagate the corresponding error.

Specified by:

registerConstant in interface OdlMdsalLowlevelControlService

unregisterDefaultConstant

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<UnregisterDefaultConstantOutput>> unregisterDefaultConstant(UnregisterDefaultConstantInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member has to unregisterany llt:get-contexted-constant default implementations it has registered.If no default implementation has been registered, do nothing.

Specified by:

unregisterDefaultConstant in interface OdlMdsalLowlevelControlService

unsubscribeDdtl

public com.google.common.util.concurrent.ListenableFuture<org.opendaylight.yangtools.yang.common.RpcResult<UnsubscribeDdtlOutput>> unsubscribeDdtl(UnsubscribeDdtlInput input)

Description copied from interface: OdlMdsalLowlevelControlService

Upon receiving this, the member checks whether it has currently subscribeda DOMDataTreeListener for llt:id-ints changes, and fails if no. If yes, the membershall unsubscribe the listener, read state of id-ints (by briefly subscribingand ubsubscribing again), compare that to the local copy,and return whether the local copy is the same.

Specified by:

unsubscribeDdtl in interface OdlMdsalLowlevelControlService