KK,
On the same note, is there a common documentation for using the
topology(usage and/or implementation)? Appreciate your help.
Thanks
Soundar
-Original Message-
From: nox-dev-boun...@noxrepo.org [mailto:nox-dev-boun...@noxrepo.org] On
Behalf Of kk yap
Sent: Tuesday, December 14, 2010
Hi,
You can try the doxygen, but it will not be that complete. If
topology the component people are looking at? I can go ahead and add
documentation if there is only a few components.
Regards
KK
On 14 December 2010 10:40, Soundararajan Ramaswamy
soundararaja...@huawei.com wrote:
KK,
On the
KK,
I will try doxygen. Documentation always helps, less effort for you folks
too in replying to all the mails.
Thanks
Soundar
-Original Message-
From: yap...@gmail.com [mailto:yap...@gmail.com] On Behalf Of kk yap
Sent: Tuesday, December 14, 2010 10:51 AM
To: Soundararajan Ramaswamy
Cc:
Python support for this has been added in destiny in commit
a2efd049da9f0d0d8dc4e56dc1aaa64930c1d257 .
You can now register_handler(Error_event, callback), and the handler is
called with an event object having type, code, and data members.
You should be able to apply the patch against zaku
The topology module seems to have all the necessary information. It's just
that it's not reflected in pytopology. So, pytopology, in it's current
state, does not seem to be very useful, at least not complete.
I'd like to go ahead and fix this. Are there any guidelines on how to write
a SWIG
[cross-posting to nox-dev, openflow-discuss, ovs-discuss]
I have prepared a patch based on NOX Zaku that improves its
performance by a factor of 10. This implies that a single controller
instance can run a large network with near a million flow initiations
per second. I am writing to open up a
This is awesome Amin, thanks for posting. It is also probably worth
mentioning that cbench was broken and over-reporting numbers. Do you
mind sending out a few details about that? I presume that will be
helpful to those using cbench
[cross-posting to nox-dev, openflow-discuss,
