1. bd7f742 Adding Device Listiner to BgpRouter so that filtering rules are sent to the by Saurav Das · 9 years ago
  2. 3d03826 Fixes bug where driver gets initialized only when device is available. by Saurav Das · 9 years ago
  3. 17d0045 Upgrade packet requests to use flow objectives API. by Jonathan Hart · 9 years ago
  4. 3ea4662 Removing dependency on lower level drivers for the BGPRouter application. by Saurav Das · 9 years ago
  5. d17abc2 Refactored driver to use new FlowRule api. by alshabib · 9 years ago
  6. 586afd8 Removing need for boilerplate app.xml; Instead defining onos.app.name and onos.app.origin (optional) is sufficient to trigger generation of boilerplate app.xml and features.xml files. by Thomas Vachuska · 10 years ago
  7. 2a441c6 Flow Objective implementation by alshabib · 10 years ago
  8. db7467a Separating onos-drivers to be delivered as a separate app from onos-openflow. Apps activated by default (via onos-setup-karaf or onos-install/onos-config) are now onos-drivers and onos-openflow. by Thomas Vachuska · 10 years ago
  9. cfd63d2 Adding more filtering objectives from the router application and handling them by Saurav Das · 10 years ago
  10. facc3f5 Enhancing the driver subsystem to allow retrieving originating data/handler contexts from the behaviours. by Thomas Vachuska · 10 years ago
  11. 910aff1 WIP: Initial implementation of filterObjectives using driver subsystem. by alshabib · 10 years ago
  12. 5c2f813 Device driver framework enhancements and CLI. by Thomas Vachuska · 10 years ago
  13. ca88bb7 Cleaning up and enhancing driver subsystem and the flow objective subsystem. by Thomas Vachuska · 10 years ago
  14. aebe775 WIP: default driver ignition by alshabib · 10 years ago
  15. 77b8848 added FlowObjectiveService to act as an objective manager between applications and drivers by alshabib · 10 years ago
  16. faa1e36 Initial sketch and implementaion of Objectives. by alshabib · 10 years ago