Reference Guide
Table Of Contents
- 1 Introduction
- 2 Establishing Your Test and Development Environments
- 3 Developing Applications
- Introduction
- Authentication
- REST API
- Audit Logging
- Alert Logging
- Configuration
- High Availability
- OpenFlow
- Metrics Framework
- GUI
- SKI Framework - Overview
- SKI Framework - Navigation Tree
- SKI Framework - Hash Navigation
- SKI Framework - View Life-Cycle
- SKI Framework - Live Reference Application
- UI Extension
- Introduction
- Controller Teaming
- Distributed Coordination Service
- Persistence
- Backup and Restore
- Device Driver Framework
- 4 Application Security
- 5 Including Debian Packages with Applications
- 6 Sample Application
- Application Description
- Creating Application Development Workspace
- Application Generator (Automatic Workspace Creation)
- Creating Eclipse Projects
- Updating Project Dependencies
- Building the Application
- Installing the Application
- Application Code
- 7 Testing Applications
- 8 Built-In Applications
- Appendix A
- Appendix B
- Bibliography
Chassis Devices
A “Chassis Device” is a modular chassis product that accommodates switching and management
modules. Modules with different capabilities can be inserted into the chassis. The HP Device
Identity Handler Facet will examine the flags in the Device Type data (i.e., XML data) to determine
if the device is a chassis product. For HP chassis switches, module identification is important.
However, the ability to tell whether the switch is in v1 or v2 mode can only be determined if
SNMP is enabled and the Device Identify Facet has the proper key. The module identification
affects only the FlowMod Facet. If the chassis is in v2 mode, there is a different implementation of
this Facet than the default v1 implementation. v2 modules support Openflow operations in the
hardware table that v1 modules do not. Therefore, if the Device Identity Facet cannot recognize
the module configuration (because SNMP is not enabled) then it assumes v1 and the Openflow
tables are simply less efficient. However, because the module information is not tied to a device
type, but rather to a configuration option on a switch of the given type, the FlowMod Facet
implementation cannot be specified in the device type’s XML file. The way to circumvent that is to
specify a Factory class for the FlowMod Facet implementation and have the Factory query the
configuration retrieved from the Device Identity Facet.
Device Objects
Several java objects are used to store information about devices. The following figure illustrates
the java objects used to store device information and how the objects are organized.
DeviceType: This object contains information about a device type. It contains all Facets and
Handler Facets that are supported by this type of device.
DeviceInfo: This object contains a DeviceType object and other information about an actual
device and its configuration.
KeyDeviceInfo: This object extends a DeviceInfo object and contains the security key that is
needed to communicate with the device. This object is created when the correct security key is
discovered.
120