commit | 284e70f6a4871ee567b2da692a1fdf6817dca172 | [log] [tgz] |
---|---|---|
author | Jonathan Hart <jono@onlab.us> | Sat Jul 05 12:32:51 2014 -0700 |
committer | Gerrit Code Review <gerrit2@gerrit.onos.onlab.us> | Wed Jul 09 14:14:57 2014 -0700 |
tree | 9a1b9204de44527cf8b6c832a7d32786847f159e | |
parent | e2a4e1728f002b01328657d0fd517c1641fecaf0 [diff] |
General link discovery module cleanup. * Removed all events we don't use from the event system (switch and port events, link updates) * Refactored event interface to two separate methods to match the other event interfaces * Removed the LDUpdate class and moved all the event enums and classes to be internal to the LinkDiscoveryManager * Removed all LinkTypes we no longer used and moved the one remaining type to the ILinkDiscoveryService. After this the ILinkDiscovery interface is no longer needed. * Made Link immutable * Removed the linkdiscovery.internal package as it only contained one class * Readability improvements to LinkDiscoveryManager Change-Id: Ifae97879aadc49b70a7b3d2294dcc540538c2cfc
ONOS (Open Networking Operating System) is an experimental distributed SDN OS. Currently, it is under active development. ONOS was announced and demonstrated at ONS'13, '14.
Apache 2.0
https://wiki.onlab.us:8443/display/onosdocs/Getting+Started+with+ONOS
Cleanly build ONOS
$ cd ${ONOS_HOME}/ $ mvn clean $ mvn compile
Required packages
$ sudo apt-get install maven python-flask python-cmd2 python-pyparsing
ZooKeeper
Download and install apache-zookeeper-3.4.6: http://zookeeper.apache.org/releases.html
By default ONOS expect ZooKeeper to be installed in ~/zookeeper-3.4.6
.
This can be changed by specifing the path using ZK_HOME
environment variable.
Data directory ZooKeeper uses by default is /var/lib/zookeeper
. You will need to give current user permission to write to this directory.
This directory can be changed using specifying ZK_LIB_DIR
environment variable and running ./onos.sh setup
to generate ${ONOS_HOME}/conf/zoo.cfg
.
See Configuration for details about ./onos.sh setup
.
RAMCloud
Run setup-ramcloud.sh to download and install RAMCloud to ~/ramcloud
.
Installation path can be changed by specifing RAMCLOUD_HOME
environment variable.
$ cd ${ONOS_HOME}/ $ ./setup-ramcloud.sh
./onos.sh setup
script is used to generate ONOS related configuration files. This script read configuration from "${ONOS_CONF_DIR}/onos_node.`hostname`.conf".
Copy the file "${ONOS_HOME}/conf/onos_node.conf" to match the hostname and configure the content appropriately.
e.g., To use RAMCloud as data store change host.backend
to ramcloud
Once you're done with required configuration run following to generate configuration files.
$ cd ${ONOS_HOME}/ $ ./onos.sh setup
To start ZooKeeper, RAMCloud (if enabled in configuration) and ONOS core.
$ cd ${ONOS_HOME}/ $ ./onos.sh start single-node
To stop all the above
$ cd ${ONOS_HOME}/ $ ./onos.sh stop
If you need to use the REST APIs, follow the instruction for "Start ONOS REST API server" in next section.
You can manually start/stop individual ONOS components as follows:
Start Zookeeper
$ cd ${ONOS_HOME}/ $ ./onos.sh zk start ## Confirm Zookeeper is running: $ ./onos.sh zk status
Start RAMCloud Coordinator (only on one of the node in cluster)
$ cd ${ONOS_HOME}/ $ ./onos.sh rc-coord start ## Confirm RAMCloud Coordinator is running: $ ./onos.sh rc-coord status
Start RAMCloud Server
$ cd ${ONOS_HOME}/ $ ./onos.sh rc-server start ## Confirm RAMCloud Server is running: $ ./onos.sh rc-server status
Start ONOS
$ cd ${ONOS_HOME}/ $ ./onos.sh core start ## Confirm ONOS is running: $ ./onos.sh core status
Start ONOS REST API server
$ cd ${ONOS_HOME}/ $ ./start-rest.sh start ## Confirm the REST API server is running: $ ./start-rest.sh status
Maven need the Internet connection to download required dependencies and plugins, when they're used for the first time.
If you need to develop ONOS in an Internet unreachable environment you may want to run the following helper script before you go offline, so that required dependencies and plugins for frequently used maven target will be downloaded to your local environment.
$ ./prep-for-offline.sh