本文整理汇总了Java中org.opendaylight.controller.sal.packet.IPluginOutDataPacketService类的典型用法代码示例。如果您正苦于以下问题:Java IPluginOutDataPacketService类的具体用法?Java IPluginOutDataPacketService怎么用?Java IPluginOutDataPacketService使用的例子?那么, 这里精选的类代码示例或许可以为您提供帮助。
IPluginOutDataPacketService类属于org.opendaylight.controller.sal.packet包,在下文中一共展示了IPluginOutDataPacketService类的3个代码示例,这些例子默认根据受欢迎程度排序。您可以为喜欢或者感觉有用的代码点赞,您的评价将有助于系统推荐出更棒的Java代码示例。
示例1: setPluginOutDataPacketService
import org.opendaylight.controller.sal.packet.IPluginOutDataPacketService; //导入依赖的package包/类
void setPluginOutDataPacketService(Map<String, Object> props,
IPluginOutDataPacketService s) {
if (props == null) {
logger.error("Didn't receive the service properties");
return;
}
String containerName = (String) props.get("containerName");
if (containerName == null) {
logger.error("containerName not supplied");
return;
}
if (this.pluginOutDataPacketServices != null) {
// It's expected only one SAL per container as long as the
// replication is done in the SAL implementation toward
// the different APPS
this.pluginOutDataPacketServices.put(containerName, s);
logger.debug("New outService for container: {}", containerName);
}
}
示例2: unsetPluginOutDataPacketService
import org.opendaylight.controller.sal.packet.IPluginOutDataPacketService; //导入依赖的package包/类
void unsetPluginOutDataPacketService(Map<String, Object> props,
IPluginOutDataPacketService s) {
if (props == null) {
logger.error("Didn't receive the service properties");
return;
}
String containerName = (String) props.get("containerName");
if (containerName == null) {
logger.error("containerName not supplied");
return;
}
if (this.pluginOutDataPacketServices != null) {
this.pluginOutDataPacketServices.remove(containerName);
logger.debug("Removed outService for container: {}", containerName);
}
}
示例3: configureInstance
import org.opendaylight.controller.sal.packet.IPluginOutDataPacketService; //导入依赖的package包/类
/**
* Function that is called when configuration of the dependencies
* is required.
*
* @param c dependency manager Component object, used for
* configuring the dependencies exported and imported
* @param imp Implementation class that is being configured,
* needed as long as the same routine can configure multiple
* implementations
* @param containerName The containerName being configured, this allow
* also optional per-container different behavior if needed, usually
* should not be the case though.
*/
public void configureInstance(Component c, Object imp, String containerName) {
if (imp.equals(QoSHandler.class)) {
// export the service
Dictionary<String, String> props = new Hashtable<String, String>();
props.put("salListenerName", "qoshandler");
c.setInterface(new String[] { IPluginOutDataPacketService.class.getName(),
IListenDataPacket.class.getName() }, props);
c.add(createContainerServiceDependency(containerName).setService(
ISwitchManager.class).setCallbacks("setSwitchManager",
"unsetSwitchManager").setRequired(true));
c.add(createContainerServiceDependency(containerName).setService(
ITopologyManager.class).setCallbacks("setTopologyManager",
"unsetTopologyMananger").setRequired(true));
c.add(createContainerServiceDependency(containerName).setService(
IDataPacketService.class).setCallbacks(
"setDataPacketService", "unsetDataPacketService")
.setRequired(true));
// the Host Listener is optional
c.add(createContainerServiceDependency(containerName).setService(
IfHostListener.class).setCallbacks("setHostListener",
"unsetHostListener").setRequired(false));
// the IfIptoHost is a required dependency
c.add(createContainerServiceDependency(containerName).setService(
IfIptoHost.class).setCallbacks("setHostTracker",
"unsetHostTracker").setRequired(true));
}
}