Hi Amin,
The goal is certainly for Nox 0.6 to support all 1.0 features. However,
that will happen after wire protocol compatibility (shooting for this
Friday ... though that might slip).
Regarding tracing the event call stack. This would certainly be a
useful debugging tool. However, the nature of events is that the
infrastructure is decoupled from the senders and receivers so it isn't
clear to me how we'd mark the originator an a general way without
requiring the originators to add themselves. I'm certainly open to
ideas ...
.martin
Hi Martin,
Will the upcoming NOX release be OpenFlow 1.0 feature compatible and
not just OpenFlow 1.0 candidate wire protocol compatible?
One more question: It seems that it is currently impossible to trace
an event and a NOX generated OpenFlow message back to their originator
events (e.g., a Packet_in_event may cause other events to be
dispatched and some OpenFlow messages to be sent out). It would be
useful to have an entry in the Event and OpenFlow Message classes to
pinpoint their originators. It seems that this needs only a few
changes to the code base and enables NOX (& third-party applications)
to have a high level view of NOX operation. I am working on OpenFlow
control plane distribution and this feature would be quite useful for
that I believe.
Thanks,
Amin
_______________________________________________
nox-dev mailing list
[email protected]
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
_______________________________________________
nox-dev mailing list
[email protected]
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
