Device Identification and Driver Management
didm
The Device Identification and Driver Management (DIDM) project addresses the need to provide device specific functionality. Device specific functionality is code that performs a “feature”, and the code is knowledgeable of the capability and limitations of the device. For example, configuring VLANs and adjusting Flowmods are features, and there may be different implementations for different device types. Device specific functionality is implemented as Device Drivers. Device Drivers need to be associated with the devices they can be used with. To determine this association requires the ability to identify the device type.
The DIDM project creates the infrastructure to support the following functions:
The purpose of this proposal is to provide a framework that can used to inform the Controller of new devices to be controlled, identity the type of device, register Device Drivers as routed RPCs, collect data from the device, update the inventory model, and invoke Device Drivers.
The framework design is in progress and will be completed as the project progresses.
Where appropriate, this project will work with and consult existing device / protocol teams to help ensure the framework meets the needs of the community as opposed to any specific vendor's devices.
The DIDM Project will use the SNMP Soutbound plugin component which has been proposed by the SNMP project team.
Interacting with devices using protocols such as SNMP requires security credential. The DIDM project envisions a Credential Manager that will be used to manage security credentials. A REST API or GUI will allow the operator to populate the credential store. It is felt that the Credential Manager should be owned by the AAA project team. The DIDM team will work with the AAA project team regarding the Credential Manager.
Dean, Steve (sdean@hp.com) ODL Username: sdean
Chau, Uyen (uyen.chau@hp.com) ODL Username: uchau
Harmon, Nathan (nathan.harmon@hp.com) ODL Username: nathan.harmon
Julie Britt (julie.britt@hp.com) ODL Username: jbritt
Sean Humphress (sean.humphress@hp.com) ODL Username: sean.humphress
David Bainbridge (dbainbri@ciena.com) ODL Username: dbainbri
Gunjan Patel (gupatel@ciena.com) ODL Username: patelgunjan5@gmail.com
Rahul Sharma (rahushar@ciena.com) ODL Username: rahushar
Anandhi Manikantan(anandhi.manikantan@hpe.com) ODL Username: anandhi
Dean, Steve (sdean@hp.com) ODL Username: sdean
Chau, Uyen (uyen.chau@hp.com) ODL Username: uchau
Harmon, Nathan (nathan.harmon@hp.com) ODL Username: nathan.harmon
Julie Britt (julie.britt@hp.com) ODL Username: jbritt
Sean Humphress (sean.humphress@hp.com) ODL Username: sean.humphress
David Bainbridge (dbainbri@ciena.com) ODL Username: dbainbri
Gunjan Patel (gupatel@ciena.com) ODL Username: patelgunjan5@gmail.com
Rahul Sharma (rahushar@ciena.com) ODL Username: rahushar
Anandhi Manikantan(anandhi.manikantan@hpe.com) ODL Username: anandhi
This code base contains only the standard ODL copyright notice as it was started with the idea of eventually moving it to open source.
The DIDM project formally joins the OpenDaylight Lithium Simultaneous Release and agrees to the activities and timeline documented on the Lithium Release Plan Page