2 * Copyright (c) 2015 Cisco Systems, Inc. and others. All rights reserved.
4 * This program and the accompanying materials are made available under the
5 * terms of the Eclipse Public License v1.0 which accompanies this distribution,
6 * and is available at http://www.eclipse.org/legal/epl-v10.html
9 package org.opendaylight.openflowplugin.api.openflow.device;
11 import com.google.common.util.concurrent.ListenableFuture;
12 import io.netty.util.Timeout;
13 import java.math.BigInteger;
14 import java.util.List;
15 import javax.annotation.CheckForNull;
16 import javax.annotation.Nullable;
17 import org.opendaylight.controller.md.sal.binding.api.NotificationPublishService;
18 import org.opendaylight.openflowplugin.api.openflow.connection.ConnectionContext;
19 import org.opendaylight.openflowplugin.api.openflow.device.handlers.DeviceReplyProcessor;
20 import org.opendaylight.openflowplugin.api.openflow.device.handlers.MultiMsgCollector;
21 import org.opendaylight.openflowplugin.api.openflow.registry.ItemLifeCycleRegistry;
22 import org.opendaylight.openflowplugin.api.openflow.registry.flow.DeviceFlowRegistry;
23 import org.opendaylight.openflowplugin.api.openflow.registry.group.DeviceGroupRegistry;
24 import org.opendaylight.openflowplugin.api.openflow.registry.meter.DeviceMeterRegistry;
25 import org.opendaylight.openflowplugin.api.openflow.rpc.RpcContext;
26 import org.opendaylight.openflowplugin.api.openflow.statistics.StatisticsContext;
27 import org.opendaylight.openflowplugin.api.openflow.statistics.ofpspecific.MessageSpy;
28 import org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.MultipartReply;
29 import org.opendaylight.yang.gen.v1.urn.opendaylight.role.service.rev150727.OfpRole;
33 * The central entity of OFP is the Device Context, which encapsulate the logical state of a switch
34 * as seen by the controller. Each OpenFlow session is tracked by a Connection Context.
35 * These attach to a particular Device Context in such a way, that there is at most one primary
36 * session associated with a Device Context. Whenever the controller needs to interact with a
37 * particular switch, it will do so in the context of the calling thread, obtaining a lock on
38 * the corresponding Device Context – thus the Device Context becomes the fine-grained point
39 * of synchronization. The only two entities allowed to send requests towards the switch are
40 * Statistics Manager and RPC Manager. Each of them allocates a Request Context for interacting
41 * with a particular Device Context. The Request Contexts are the basic units of fairness,
42 * which is enforced by keeping a cap on the number of outstanding requests a particular Request
43 * Context can have at any point in time. Should this quota be exceeded, any further attempt to make
44 * a request to the switch will fail immediately, with proper error indication.
47 public interface DeviceContext extends AutoCloseable,
53 void setStatisticsRpcEnabled(boolean isStatisticsRpcEnabled);
56 * distinguished device context states
58 enum DEVICE_CONTEXT_STATE {
60 * initial phase of talking to switch
64 * standard phase - interacting with switch
68 * termination phase of talking to switch
74 * Method returns current device context state.
76 * @return {@link DeviceContext.DEVICE_CONTEXT_STATE}
78 DEVICE_CONTEXT_STATE getDeviceContextState();
81 * Method close all auxiliary connections and primary connection.
83 void shutdownConnection();
86 * Method add auxiliary connection contexts to this context representing single device connection.
88 * @param connectionContext
90 void addAuxiliaryConnectionContext(ConnectionContext connectionContext);
93 * Method removes auxiliary connection context from this context representing single device connection.
95 * @param connectionContext
97 void removeAuxiliaryConnectionContext(ConnectionContext connectionContext);
100 * Method provides state of device represented by this device context.
102 * @return {@link DeviceState}
104 DeviceState getDeviceState();
107 * Method has to activate (MASTER) or deactivate (SLAVE) TransactionChainManager.
108 * TransactionChainManager represents possibility to write or delete Node subtree data
109 * for actual Controller Cluster Node. We are able to have an active TxManager only if
110 * newRole is {@link OfpRole#BECOMESLAVE}.
111 * Parameters are used as marker to be sure it is change to SLAVE from MASTER or from
112 * MASTER to SLAVE and the last parameter "cleanDataStore" is used for validation only.
113 * @param oldRole - old role for quick validation for needed processing
114 * @param role - NewRole expect to be {@link OfpRole#BECOMESLAVE} or {@link OfpRole#BECOMEMASTER}
115 * @return RoleChangeTxChainManager future for activation/deactivation
116 * @deprecated replaced by method onDeviceTakeClusterLeadership and onDevicLostClusterLeadership
119 ListenableFuture<Void> onClusterRoleChange(@Nullable OfpRole oldRole, @CheckForNull OfpRole role);
122 * Method has to activate TransactionChainManager and prepare all Contexts from Device Contects suite
123 * to Taking ClusterLeadership role {@link OfpRole#BECOMEMASTER} (e.g. Routed RPC registration, StatPolling ...)
124 * @return DeviceInitialization furure
126 ListenableFuture<Void> onDeviceTakeClusterLeadership();
129 * Method has to deactivate TransactionChainManager and prepare all Contexts from Device Contects suite
130 * to Lost ClusterLeadership role {@link OfpRole#BECOMESLAVE} (e.g. Stop RPC rounting, stop StatPolling ...)
131 * @return RoleChangeTxChainManager future for deactivation
133 ListenableFuture<Void> onDeviceLostClusterLeadership();
136 * Method has to close TxManager ASAP we are notified about Closed Connection
137 * @return sync. future for Slave and MD-SAL completition for Master
139 ListenableFuture<Void> shuttingDownDataStoreTransactions();
142 * Method provides current devices connection context.
146 ConnectionContext getPrimaryConnectionContext();
149 * Method provides current devices auxiliary connection contexts.
153 ConnectionContext getAuxiliaryConnectiobContexts(BigInteger cookie);
156 * Method exposes flow registry used for storing flow ids identified by calculated flow hash.
160 DeviceFlowRegistry getDeviceFlowRegistry();
163 * Method exposes device group registry used for storing group ids.
167 DeviceGroupRegistry getDeviceGroupRegistry();
170 * Method exposes device meter registry used for storing meter ids.
174 DeviceMeterRegistry getDeviceMeterRegistry();
178 * @return translator library
180 TranslatorLibrary oook();
183 * store cancellable timeout handler of currently running barrier task
185 void setCurrentBarrierTimeout(Timeout timeout);
188 * @return cancellable timeout handle of currently running barrier task
190 Timeout getBarrierTaskTimeout();
192 void setNotificationPublishService(NotificationPublishService notificationPublishService);
194 MessageSpy getMessageSpy();
196 MultiMsgCollector getMultiMsgCollector(final RequestContext<List<MultipartReply>> requestContext);
199 * indicates that device context is fully published (e.g.: packetIn messages should be passed)
204 * change packetIn rate limiter borders
206 * @param upperBound max amount of outstanding packetIns
208 void updatePacketInRateLimit(long upperBound);
211 * @return registry point for item life cycle sources of device
213 ItemLifeCycleRegistry getItemLifeCycleSourceRegistry();
215 void setRpcContext(RpcContext rpcContext);
217 RpcContext getRpcContext();
219 void setStatisticsContext(StatisticsContext statisticsContext);
221 StatisticsContext getStatisticsContext();