1) When creating a new protocol session, it fails with a Configuration Error.
It's likely the context for the given protocol doesn't contain enough information for a session to be created, or it's just wrong. Use the protocols:context command to register a context with corrected information. Check that the URI contains the user/password, host, schema, etc... Concrete context information, however, depends on the underlying protocol implementation.
2) When trying to start a new router resource, it fails with the following error: "The subsystem request failed".
The netconf subsystem for ssh connections is not enabled in the router. Thus, OpenNaaS netconf client cannot connect to the router device. Netconf should be enabled in the router before trying to start the resource in OpenNaaS. You can find the problem description and it solution at http://jira.i2cat.net:8080/browse/OPENNAAS-238
3) When building OpenNaaS, the build randomly fails with a: java.lang.OutOfMemoryError: PermGen space
This is due to the space that the JVM devotes to loaded classes running out. The reason for this is probably some uncleaned reference on a ClassLoader that prevents the GC to do its job.The temporary workaround is to prepend this to the maven calls:
MAVEN_OPTS="-Xmx512m -XX:MaxPermSize=128m" mvn install
Related to known bug: jira.i2cat.net/browse/OPENNAAS-417
4) When executing OpenNaaS platform, I only see 175 available commands.
None of the bundles are being loaded. There are several reasons why this might happen. In this case, we recommend you to report your situation using our bug reporting system, by creating a ticket in the following link: http://jira.i2cat.net:8080/secure/CreateIssue!default.jspa
It will be very helpful for the developer team if you attach the log in the ticket. You can find them at platform/target/opennaas-{version}/opennaa-{version}/data/log/
5) What are the system requirements for running OpenNaaS?
We have successfully tested OpenNaaS in Windows 7, Ubuntu and MAC OSX systems. There's a limitation by using Windows XP. The reason is that OpenNaaS uses Fuse 4.4 version, which requires at least either a Windows 2003 Server, a Windows 2008 Server or Windows 7, in case you're using a Microsoft OS.
6) Error cloning OpenNaaS git repository in Windows. error: unable to create file ... (No such file or directory).
There is a path length limitation in mingw32, which is 260 characters:
http://stackoverflow.com/questions/7866387/git-mingw32-and-long-path-file-names-under-windows
http://stackoverflow.com/questions/4992577/msys-git-and-long-paths
mingw32 is used to emulate the git CLI on windows.
Currently, none of OpenNaaS files have paths longer that 260 characters, current maximum is 216. However, depending on the directory you are cloning the git repo to, some files will end up with a path longer than 260.
Let's say you have 40 characters for the directory path. If you can keep the cloning directory shorter than that it should work. However, this is only a temporary solution.
In links above, it is suggested so use msys library or install cygwin to overcome this limitation.