Hi, We are not part of the NOX development team, so we are definitely not planning a merge; but would be happy to contribute. Our branch is based on the Zaku branch (now called NOX-Classic), and given that I don't know what changed between zaku and new NOX, it is hard to tell how much effort this would take. Also, iirc, the NOX team was planning to create an OF version agnostic NOX, whereas we have separate repositories per version, so something should be done on this front as well...
Hopefully the NOX team is listening, and will share their plans with us. BR, Zoltan. ________________________________________ From: Simhon Doctori [[email protected]] Sent: Sunday, 03 February 2013 2:19 PM To: Zoltán Lajos Kis; [email protected] Subject: RE: [nox-dev] Features supported in nox13oflib Zoltan hi, Are you planning to merge these two branches so the classic repo will contain OpenFlow 1.3 support? If so, when is it planned to happen? Thanks for your answers, Simhon Doctori -----Original Message----- From: Zoltán Lajos Kis [mailto:[email protected]] Sent: Sunday, February 03, 2013 2:41 PM To: Simhon Doctori; [email protected] Subject: RE: [nox-dev] Features supported in nox13oflib Hi, Nox13oflib contains two essential changes compared to nox classic. The OpenFlow events are replaced with a single event wrapping oflib structures, and the Python support is dropped. The core code, i.e., event handling, app dependency management did not change. As such, it should be fairly easy to portclassic apps to nox13oflib, as long as they are implemented in c++; the ones you list are. The straightforward way is to convert the applications' OF 1.0 syntax to OF 1.3 syntax (e.g., replace the match structure with oxm fields, move actions to apply instructions), and use the new OpenFlow event API. Potentially you can also tweak the semantics (e.g., multicast in OF 1.0 was done by multiple output ports, this could be replaced by a group entry), but this is not so straightforward, as it requires some planning and a deep understanding of the OF specifications. The JSON messenger module is still there, so your existing Python apps should work with this code. Whether the NOX apps that listens to the Python app need to be changed depends on the application... Best Regards, Zoltan. ________________________________________ From: [email protected] [[email protected]] on behalf of Simhon Doctori [[email protected]] Sent: Sunday, 03 February 2013 1:16 PM To: [email protected] Subject: [nox-dev] Features supported in nox13oflib Hi, This NOX repo (nox13oflib) supporting OpenFlow 1.3 seams to miss some of the basic features supported on the classic repo - such as lavi, route, hoststate and others (located under ../src/nox/netapps/...). 1. Is it possible to add these features? I tried to add lavi but it appears that the core code is slightly different, so make failed... 2. How can I run a python application with json commands sent to the controller when the controller is based on the above NOX repo? even the basic nox-console.py requires that lavi will run on the controller 3. Are you planning to support OpenFlow 1.3 on the classic branch? If so, when is it planned to happen? Regards, Simhon Doctori
