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;
26 * The central entity of OFP is the Device Context, which encapsulate the logical state of a switch
27 * as seen by the controller. Each OpenFlow session is tracked by a Connection Context.
28 * These attach to a particular Device Context in such a way, that there is at most one primary
29 * session associated with a Device Context. Whenever the controller needs to interact with a
30 * particular switch, it will do so in the context of the calling thread, obtaining a lock on
31 * the corresponding Device Context – thus the Device Context becomes the fine-grained point
32 * of synchronization. The only two entities allowed to send requests towards the switch are
33 * Statistics Manager and RPC Manager. Each of them allocates a Request Context for interacting
34 * with a particular Device Context. The Request Contexts are the basic units of fairness,
35 * which is enforced by keeping a cap on the number of outstanding requests a particular Request
36 * Context can have at any point in time. Should this quota be exceeded, any further attempt to make
37 * a request to the switch will fail immediately, with proper error indication.
39 public interface DeviceContext extends
47 * Method close all auxiliary connections and primary connection.
49 void shutdownConnection();
52 * Method add auxiliary connection contexts to this context representing single device connection.
53 * @param connectionContext new connection context
55 void addAuxiliaryConnectionContext(ConnectionContext connectionContext);
58 * Method removes auxiliary connection context from this context representing single device connection.
59 * @param connectionContext connection which need to be removed
61 void removeAuxiliaryConnectionContext(ConnectionContext connectionContext);
64 * Method provides state of device represented by this device context.
66 * @return {@link DeviceState}
68 DeviceState getDeviceState();
71 * Method has to close TxManager ASAP we are notified about Closed Connection
72 * @return sync. future for Slave and MD-SAL completition for Master
74 ListenableFuture<Void> shuttingDownDataStoreTransactions();
77 * @return current devices connection context
79 ConnectionContext getPrimaryConnectionContext();
82 * @return current devices auxiliary connection contexts
84 ConnectionContext getAuxiliaryConnectionContexts(BigInteger cookie);
88 * @return translator library
90 TranslatorLibrary oook();
93 * store cancellable timeout handler of currently running barrier task
95 void setCurrentBarrierTimeout(Timeout timeout);
98 * @return cancellable timeout handle of currently running barrier task
100 Timeout getBarrierTaskTimeout();
102 void setNotificationPublishService(NotificationPublishService notificationPublishService);
104 MessageSpy getMessageSpy();
106 MultiMsgCollector getMultiMsgCollector(final RequestContext<List<MultipartReply>> requestContext);
109 * indicates that device context is fully published (e.g.: packetIn messages should be passed)
114 * change packetIn rate limiter borders
116 * @param upperBound max amount of outstanding packetIns
118 void updatePacketInRateLimit(long upperBound);
121 * @return registry point for item life cycle sources of device
123 ItemLifeCycleRegistry getItemLifeCycleSourceRegistry();
128 void setSwitchFeaturesMandatory(boolean switchFeaturesMandatory);
130 void putLifecycleServiceIntoTxChainManager(LifecycleService lifecycleService);
132 void replaceConnectionContext(ConnectionContext connectionContext);
134 boolean isSkipTableFeatures();