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 org.opendaylight.controller.md.sal.common.api.data.TransactionChain;
12 import org.opendaylight.openflowplugin.api.openflow.connection.ConnectionContext;
13 import org.opendaylight.openflowplugin.api.openflow.device.handlers.MessageHandler;
14 import org.opendaylight.yang.gen.v1.urn.opendaylight.table.types.rev131026.TableFeatures;
15 import java.math.BigInteger;
16 import org.opendaylight.yangtools.yang.binding.DataObject;
17 import org.opendaylight.yangtools.yang.common.RpcResult;
18 import java.util.Collection;
19 import java.util.concurrent.Future;
22 * The central entity of OFP is the Device Context, which encapsulate the logical state of a switch
23 * as seen by the controller. Each OpenFlow session is tracked by a Connection Context.
24 * These attach to a particular Device Context in such a way, that there is at most one primary
25 * session associated with a Device Context. Whenever the controller needs to interact with a
26 * particular switch, it will do so in the context of the calling thread, obtaining a lock on
27 * the corresponding Device Context – thus the Device Context becomes the fine-grained point
28 * of synchronization. The only two entities allowed to send requests towards the switch are
29 * Statistics Manager and RPC Manager. Each of them allocates a Request Context for interacting
30 * with a particular Device Context. The Request Contexts are the basic units of fairness,
31 * which is enforced by keeping a cap on the number of outstanding requests a particular Request
32 * Context can have at any point in time. Should this quota be exceeded, any further attempt to make
33 * a request to the switch will fail immediately, with proper error indication.
35 * Created by Martin Bobak <mbobak@cisco.com> on 25.2.2015.
37 public interface DeviceContext extends MessageHandler {
41 * Method add auxiliary connection contexts to this context representing single device connection.
43 * @param connectionContext
45 void addAuxiliaryConenctionContext(ConnectionContext connectionContext);
48 * Method removes auxiliary connection context from this context representing single device connection.
50 * @param connectionContext
52 void removeAuxiliaryConenctionContext(ConnectionContext connectionContext);
56 * Method provides state of device represented by this device context.
58 * @return {@link DeviceState}
60 DeviceState getDeviceState();
63 * Method sets transaction chain used for all data store operations on device
64 * represented by this context. This transaction chain is write only.
66 * @param transactionChain
68 void setTransactionChain(TransactionChain transactionChain);
71 * Method exposes transaction created for device
72 * represented by this context. This should be used as write only.
74 TransactionChain getTransactionChain();
77 * Method provides capabilities of connected device.
81 TableFeatures getCapabilities();
84 * Method provides current devices connection context.
88 ConnectionContext getPrimaryConnectionContext();
91 * Method provides current devices auxiliary connection contexts.
95 ConnectionContext getAuxiliaryConnectiobContexts(BigInteger cookie);
99 <T extends DataObject> Future<RpcResult<T>> sendRequest(DataObject dataObject);