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 org.opendaylight.controller.md.sal.binding.api.NotificationPublishService;
16 import org.opendaylight.openflowplugin.api.openflow.OFPContext;
17 import org.opendaylight.openflowplugin.api.openflow.connection.ConnectionContext;
18 import org.opendaylight.openflowplugin.api.openflow.device.handlers.DeviceReplyProcessor;
19 import org.opendaylight.openflowplugin.api.openflow.device.handlers.MultiMsgCollector;
20 import org.opendaylight.openflowplugin.api.openflow.lifecycle.LifecycleService;
21 import org.opendaylight.openflowplugin.api.openflow.registry.ItemLifeCycleRegistry;
22 import org.opendaylight.openflowplugin.api.openflow.statistics.ofpspecific.MessageSpy;
23 import org.opendaylight.yang.gen.v1.urn.opendaylight.openflow.protocol.rev130731.MultipartReply;
27 * The central entity of OFP is the Device Context, which encapsulate the logical state of a switch
28 * as seen by the controller. Each OpenFlow session is tracked by a Connection Context.
29 * These attach to a particular Device Context in such a way, that there is at most one primary
30 * session associated with a Device Context. Whenever the controller needs to interact with a
31 * particular switch, it will do so in the context of the calling thread, obtaining a lock on
32 * the corresponding Device Context – thus the Device Context becomes the fine-grained point
33 * of synchronization. The only two entities allowed to send requests towards the switch are
34 * Statistics Manager and RPC Manager. Each of them allocates a Request Context for interacting
35 * with a particular Device Context. The Request Contexts are the basic units of fairness,
36 * which is enforced by keeping a cap on the number of outstanding requests a particular Request
37 * Context can have at any point in time. Should this quota be exceeded, any further attempt to make
38 * a request to the switch will fail immediately, with proper error indication.
41 public interface DeviceContext extends
49 * Method close all auxiliary connections and primary connection.
51 void shutdownConnection();
54 * Initial submit transaction
56 void initialSubmitTransaction();
59 * Method add auxiliary connection contexts to this context representing single device connection.
60 * @param connectionContext new connection context
62 void addAuxiliaryConnectionContext(ConnectionContext connectionContext);
65 * Method removes auxiliary connection context from this context representing single device connection.
66 * @param connectionContext connection which need to be removed
68 void removeAuxiliaryConnectionContext(ConnectionContext connectionContext);
71 * Method provides state of device represented by this device context.
73 * @return {@link DeviceState}
75 DeviceState getDeviceState();
78 * Method has to close TxManager ASAP we are notified about Closed Connection
79 * @return sync. future for Slave and MD-SAL completition for Master
81 ListenableFuture<Void> shuttingDownDataStoreTransactions();
84 * @return current devices connection context
86 ConnectionContext getPrimaryConnectionContext();
89 * @return current devices auxiliary connection contexts
91 ConnectionContext getAuxiliaryConnectiobContexts(BigInteger cookie);
95 * @return translator library
97 TranslatorLibrary oook();
100 * store cancellable timeout handler of currently running barrier task
102 void setCurrentBarrierTimeout(Timeout timeout);
105 * @return cancellable timeout handle of currently running barrier task
107 Timeout getBarrierTaskTimeout();
109 void setNotificationPublishService(NotificationPublishService notificationPublishService);
111 MessageSpy getMessageSpy();
113 MultiMsgCollector getMultiMsgCollector(final RequestContext<List<MultipartReply>> requestContext);
116 * indicates that device context is fully published (e.g.: packetIn messages should be passed)
121 * change packetIn rate limiter borders
123 * @param upperBound max amount of outstanding packetIns
125 void updatePacketInRateLimit(long upperBound);
128 * @return registry point for item life cycle sources of device
130 ItemLifeCycleRegistry getItemLifeCycleSourceRegistry();
135 void setSwitchFeaturesMandatory(boolean switchFeaturesMandatory);
137 void putLifecycleServiceIntoTxChainManager(LifecycleService lifecycleService);
139 void replaceConnectionContext(ConnectionContext connectionContext);
141 boolean isSkipTableFeatures();