Exactly - there's an example of using this in netapps/monitoring.py (line 188) in destiny, (and you can trace how it's handled etc)
If all you need is to print out/look at the flow stats (rather than act on them programatically), and you do switch to destiny, you could use the gui for that. On Mon, Feb 21, 2011 at 8:44 AM, Murphy McCauley <jam...@nau.edu> wrote: > I believe that the flow stats event is Pythonized in both the zaku and > destiny branches -- it's just that a helper method to make the callback easy > to register is missing from zaku. A simple register_for_flow_stats_in > method DOES exist in the destiny branch, though. So I'd suggest you either > switch to the destiny branch, or look at the relevant patch to destiny > (21e3bf59aca5d3df8e86bcd09cc9156a66866f7f) which should demonstrate how to > register a callback for flow stats events (it's not particularly hard -- > basically you call register_handler with > Flow_stats_in_event.static_get_name() as the first parameter). > > Hope that helps. > > -- Murphy > > On Feb 21, 2011, at 8:30 AM, Malveeka Tewari wrote: > > Hi > > I am writing a python app for the NOX controller and want to obtain flow > statistics for individual flows from an openflow switch. > I can see that nox supports python callback handlers for handling stats > reply for aggregate flows stats, table stats , port stats and desc stats > events, but the handler for individual flow stat seems to be missing. > > Any suggestions on how can I extend the functionality to handle flow stats > event in a python nox app. > > Thanks! > Malveeka > _______________________________________________ > nox-dev mailing list > nox-dev@noxrepo.org > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org > > > > _______________________________________________ > nox-dev mailing list > nox-dev@noxrepo.org > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org > >
_______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
