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
user of the device driver framework does not require knowledge of the type of device with which it
is interacting.
Device Type Information
Information describing a type of device is stored in XML files. This information describes the
attributes (capabilities) of a type of device, not an actual device that exists on the network. As
physical devices are discovered, the Device Driver Framework will determine the best device type
for the discovered device.
Device type information is stored in XML files and organized in a hierarchical fashion with more
specific types extending from more general device types. The following figure illustrates this
concept.
At the top of the tree is the BaseSwitch.xml file. This XML file defines a “Default Switch”. The
default switch defines only a DeviceIdentity Facet that can be used to get basic information about
the device. This indicates that it has a DeviceIdentity Facet available to be accessed; the
implementation of the DeviceIdentity Facet will be a specific class name to get instantiated when
the Facet is accessed.
Extending from the BaseSwitch are XML files that contain more information about a type of device.
For example, at this level the XML files contain information about a “generic” HP device, or some
other generic device. The HP.xml file specifies the vendor as HP, and it defines several Facets that
can be used with all HP devices. One example is the DeviceIdentityHandler Facet that can be
used to interact with the device via SNMP to determine more granular information. For example,
for HP devices the model, serial number, specific flags such as type of chassis can be obtained to
better determine the specific type of HP device.
At the next level, the figure shows XML files for several HP devices. The 5400.xml file specifies the
5400 device type and it extends from the HP Switch type. This file also defines device types for
115