Re: [nox-dev] NOX cannot be compiled in Ubuntu 11.10?

2011-10-22 Thread Murphy McCauley
At this point, destiny is really the branch of choice for new installations, 
and is more than ripe to become the new stable branch.

We'll be becoming more transparent about our (rather loose) policies on this 
type of thing, but basically part of it for a while now has been that the 
stable branch runs on OSes/libraries that were current when it was released, 
while the unstable branch more or less tracks current systems/libraries.

-- Murphy

On Oct 21, 2011, at 11:49 PM, Heryandi wrote:

> I see... I will just ignore the test cases then.
> The python error was already fixed almost one year ago in destiny...
> 
> Well, there is no other reason for me to use zaku other than because it is 
> the stable branch...
> Thanks for the help so far, Murphy.
> 
> Regards,
> Heryandi
> 
> From: Murphy McCauley [jam...@nau.edu]
> Sent: Saturday, October 22, 2011 2:28 PM
> To: Heryandi
> Cc: nox-dev@noxrepo.org
> Subject: Re: [nox-dev] NOX cannot be compiled in Ubuntu 11.10?
> 
> So yeah, it doesn't surprise me that make check doesn't work.  I don't think 
> I have ever touched the tests, and I think a lot of them have been broken for 
> quite a while now.  If people are interested, maybe someone should take up 
> maintaining them.  But I personally have no knowledge of anyone ever actually 
> finding them useful.  I'm actually inclined to just remove them...
> 
> I think your Python error was also addressed quite a while ago in destiny.  
> This is going to be a recurring theme -- are you using zaku for any 
> particular reason?
> 
> -- Murphy
> 
> On Oct 21, 2011, at 11:19 PM, Heryandi wrote:
> 
>> Thanks again Murphy.
>> After applying 'aee2a3fb696a497a87a30cfc3285d142a464cbc0' and 
>> '473be844299ee7b213e9f7dc67ebea212af7d02f' to zaku, I am now able to 'make' 
>> successfully, with both boost 1.42 and boost 1.46.
>> However, 'make check' didn't run successfully. The error message is the same 
>> for both boost 1.42 and 1.46. Below is the error message:
>> make  test-classifier test-coop-preblock-hook test-coop-sema 
>> test-coop-signals test-ethernetaddr test-event-dispatcher-blocking 
>> test-event-dispatcher-starvation test-poll-loop-removal 
>> test-timer-dispatcher-delay test-timer-dispatcher-duplicates 
>> test-timer-dispatcher-starvation test-timeval test-type-props
>> make[4]: Entering directory 
>> `/home/heryandi/Downloads/nox-patched/build/src/tests'
>> g++ -DHAVE_CONFIG_H -I. -I../../../src/tests -I../..  
>> -DPKGDATADIR=\"/usr/local/share/nox\" -DPKGLIBDIR=\"/usr/local/bin/tests\" 
>> -DPKGLOCALSTATEDIR=\"/usr/local/var/nox\" 
>> -DPKGSYSCONFDIR=\"/usr/local/etc/nox\" -include ../../config.h -I 
>> ../../../src/include -I../../../src/include/openflow -I/usr/include 
>> -D_GNU_SOURCE=1   -D_REENTRANT -D__STDC_LIMIT_MACROS=1 
>> -D__STDC_FORMAT_MACROS=1 -D__STDC_CONSTANT_MACROS=1 
>> -D_GLIBCXX_CONCEPT_CHECKS=1 -D_GLIBCXX_DEBUG=1 -D_GLIBCXX_DEBUG_PEDANTIC=1 
>> -I   -fno-omit-frame-pointer -fno-strict-aliasing -Wall -Wno-sign-compare 
>> -Winit-self -Wformat-nonliteral -Wformat-security -g -O2 -MT 
>> test-classifier.o -MD -MP -MF .deps/test-classifier.Tpo -c -o 
>> test-classifier.o ../../../src/tests/test-classifier.cc
>> ../../../src/tests/test-classifier.cc: In function ‘void 
>> timed_test(Classifier_t&, Rule_list&)’:
>> ../../../src/tests/test-classifier.cc:133:38: warning: variable ‘match’ set 
>> but not used [-Wunused-but-set-variable]
>> mv -f .deps/test-classifier.Tpo .deps/test-classifier.Po
>> /bin/bash ../../libtool --tag=CXX   --mode=link g++ -fno-omit-frame-pointer 
>> -fno-strict-aliasing -Wall -Wno-sign-compare -Winit-self -Wformat-nonliteral 
>> -Wformat-security -g -O2 -R/usr/local/bin/tests -export-dynamic  -o 
>> test-classifier test-classifier.o ../lib/libnoxcore.la 
>> ../builtin/.libs/libbuiltin.la -L/usr/lib -lboost_unit_test_framework-mt 
>> -lboost_filesystem-mt -lssl -lcrypto ../components.xsd.o ../nox.xsd.o
>> libtool: link: g++ -fno-omit-frame-pointer -fno-strict-aliasing -Wall 
>> -Wno-sign-compare -Winit-self -Wformat-nonliteral -Wformat-security -g -O2 
>> -o .libs/test-classifier test-classifier.o ../components.xsd.o ../nox.xsd.o 
>> -Wl,--export-dynamic  ../lib/.libs/libnoxcore.so 
>> ../builtin/.libs/libbuiltin.so -L/usr/lib -lboost_unit_test_framework-mt 
>> -lboost_filesystem-mt -lssl -lcrypto -Wl,-rpath -Wl,/usr/local/bin/builtin 
>> -Wl,-rpath -Wl,/usr/local/bin/tests
>> /usr/bin/ld: ../components.xsd.o: undefined reference to symbol 
>> 'boost::system::system_category()'
>> /usr/bin/ld: note: 'boost::system::system_category()' is defined in DSO 
>> /usr/lib/libboost_system.so.1.46.1 so try adding it to the linker command 
>> line
>> /usr/lib/libboost_system.so.1.46.1: could not read symbols: Invalid operation
>> collect2: ld returned 1 exit status
>> 
>> My guess is that the script to run test cases updated with previous changes 
>> yet.
>> 
>> There is another problem, not with boost. When I run './nox_core', the 
>> res

[nox-dev] The status of NOX

2011-10-22 Thread Brandon Heller
I'll take responsibility for the confusion from the tutorial.  I
received erroneous direct information about the status of NOX, which
was corroborated by seeing the last update to the unstable branch done
3 months ago, leading to the mistaken belief that NOX was no longer
actively _developed_ (albeit clearly community-supported).  A
clarification is on its way to tutorial attendees - 60+ of which were
just introduced to NOX - and I've updated the tutorial docs.

As a NOX user and Python fan, I'm glad to hear about these new
developments, and look forward to future releases of NOX and POX.

Thanks,

Brandon Heller

-

Responding to:

Murphy McCauley jam382 at nau.edu
Fri Oct 21 14:46:01 PDT 2011

This is a quick update about the status of NOX.

While, over the past few years, NOX has gone from the only controller
available to one among many controller options, we want to emphasize
that NOX is still here and is being actively maintained and improved.

The NOX community is largely centered around the nox-dev mailing list
(which is relatively active -- something like 100 posts per month),
and consists of a mix of users -- those just playing around with the
technology (asking questions), those actively using NOX for research
or other projects (reporting bugs), those using NOX for a commercial
product, and a handful of developers (who, we hope, are effectively
meeting the needs of the previous three groups).

There has also been some progress on NOX that hasn't been widely
discussed yet.  Specifically, there's a new branch which we're pretty
excited about. It is the biggest update to NOX we've seen so far, and
it responds to requests from the community: in particular, this
release involves a streamlining of the codebase and API, along with a
sizable performance jump. We are close to making this branch public.

We also know that quite a few NOX users appreciate the Python
interface.  We want to support these users even better. To that end,
we've been developing POX -- a new controller framework written in
pure Python.  We think it's pretty quick and easy to hack on, and it
is remarkably easy to deploy.  It's still under active initial
development, but there are a handful of projects using it now or that
are planning to use it soon.  We aren't sure exactly when to expect a
1.0 release of POX, but it's coming along.

In short: NOX has a thriving community of users, both commercial and
academic, and an active set of developers committed to maintaining and
improving the codebase, with bugs fixed rapidly and a fairly
substantial NOX upgrade on the way.  There's even an entirely new
Python-only controller in the works to provide an even easier-to-use
controller for those who want a Python interface. The comments at ONS
about lack of NOX support were ill-informed and may have caused a bit
of undue concern, and we hope this note clarifies the situation.

We remain interested in your feedback, stand ready to fix any problems
you find, and are excited to keep the project moving forward.


Murphy McCauley
Martin Casado
Kyriakos Zarifis
Amin Tootoonchian
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev