ONOS stands for "Open Network Operating System". We realize it's a bit confusing, considering ON.Lab stands for "Open Networking Laboratory"!
We currently actively support Ubuntu and OS X. ONOS works with Oracle Java 1.8, but OpenJDK should work as well.
Please check our Jira to see what's in progress. If what you are looking for isn't there, you can always help by contributing!
Thank you for your interest! The Contributor Guide should give you the details of what's involved.
You can find the latest documentation on the ONOS Documentation homepage. The tutorials and sample code can be found in Tutorials.
Confluence generates URLs based on a page's name, so renaming it changes its URL. Sadly, Confluence doesn't do automatic redirects from the old URL, but luckily it automatically updates the links within the wiki, so you don't have to worry about links within the wiki breaking.
For linking to a page from emails, blogs, etc., Confluence recommends using a page's shortened URL, which remains stable across name changes.
Go to the Tools dropdown and select Link to this Page.... A window should pop up with both a regular and a shortened URL. For example, for this page:
Of course, the result is more dramatic and useful for pages with longer names.
Currently, pages can only be deleted by ONOS wiki administrators. For the time being, you can move your page under the Trashbin and then drop a line in the #onos-docs channel or onos-discuss to have your page removed.
The default username/password is karaf/karaf.
This usually means ONOS did not start up properly, so the ONOS services are not available even though the CLI commands are loaded. Try looking in the ONOS log for exceptions or errors that may indicate why ONOS did not start up.
Please first read the Flow Rule Subsystem page to understand how flows are managed in ONOS. The reason flows are stuck in PENDING_ADD state is because ONOS is unable to confirm that the flow is present on the dataplane.
If you are using OpenFlow, the provider periodically sends FLOW_STATS_REQUEST messages to the device and expects FLOW_STATS_REPLY messages in return. One possible reason for flows being in PENDING_ADD state is the device doesn’t properly support sending FLOW_STATS_REPLY messages doesn’t send the right information in the FLOW_STATS_REPLY.
Another possible reason could be that ONOS simply can’t match the flows in the FLOW_STATS_REPLY with the state in the flow store. The OpenFlow provider uses the FlowModBuilder to map ONOS constructs to OpenFlow, and the FlowEntryBuilder to map OpenFlow constructs back to ONOS constructs. Often flows being stuck in PENDING_ADD means that these mappings are not properly symmetric, i.e. the FlowEntryBuilder doesn’t map the flow stats to the same FlowRule object that was installed. This could be because a new criterion/instruction was added, or a bug in the existing mappings.
This is generally a different symptom of the same problem as above (flows stuck in PENDING_ADD). If ONOS can’t match the returned flow stats with flow rules in the store, it will remove what it considers to be an extraneous flow and install the flow in the store again. The solution to this problem is to ensure that ONOS can match observed flows with its internal flow store.