-
Type:
Story
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: 1.1.0
-
Component/s: None
-
Labels:None
-
Story Points:5
-
Epic Link:
-
Sprint:Blackbird Sprint 3 (jan19-30)
As a deployer or device vendor, I would like to dynamically supply device-specific code to tailor the behaviour of various providers with respect to specific device family, so that I can extend the device support matrix at run-time or deployment time, i.e. out-of-sync with ONOS releases.
Examples of use:
- OpenFlow drivers for support of custom TTPs through common abstraction.
- Element management (e.g. SNMP, NetConf) drivers to support device configuration & management through common abstraction.
Notes:
- framework for injecting facets of behaviour related to "talking about" and "talking to" devices
- framework for defining a hierarchy of drivers and for exploiting similarities between product families of devices
1.
|
Driver Framework API |
|
Closed | Thomas Vachuska |
2.
|
Implement driver management component(s) |
|
Closed | Thomas Vachuska |