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.
- 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