Welcome to the ONOS documentation pages!If you are new to ONOS, the Tutorials and the FAQs are great places to start.Guides!
Table of Contents | ||
---|---|---|
|
Contents
The ONOS guides Guides provide comprehensive information, and are divided into several categories. It It is highly recommended that you work through the tutorials before Tutorials before taking a look at the ONOS guides to get the most out of the information here.
- User's Administrator Guide - InstallingHow to install, configuringconfigure, and using use ONOS and its applications, and its current use cases
- Developer 's Guide - Development and contributionHow to develop on and/or contribute to ONOS, and the tools and procedure related to itprocedures involved
- Architecture and Internals Guide - Design The design and implementation of ONOS, its major subsystems, and sample use cases
We also provide Javadocs for the ONOS APIs.
Conventions used
There are a few conventions that we use throughout these docs.
Unix shell commands begin with '$' or for superuser, '#' :
Code Block language text $ sudo -s # id uid=0(root) gid=0(root) groups=0(root)
ONOS CLI commands begin with 'onos>' :
Code Block language text onos> summary
- Both shell and CLI commands are inlined in sentences in
monospace
font, e.g.ls
ortopology.
- File names, directory paths, and keywords are in italic.
- User inputs and navigation of web pages are bold e.g. Ctrl-D and Browse > Pages.
- Italic and monospace terms may also be bolded to emphasize them.
Further conventions, if any, are described where relevant.
Contributing
We try our best to keep this wiki and documentation set up-to-date. Please refer to Contributing to ONOS Documentation if you're interested in helping out.