Gitiles
Code Review Sign In
gerrit.onosproject.org / spring-open / e2238bcbe25e1dacccfde4b79ee87d724124fc27
commite2238bcbe25e1dacccfde4b79ee87d724124fc27[log] [tgz]
authorPavlin Radoslavov <pavlin@onlab.us>Mon Jun 09 18:05:23 2014 -0700
committerGerrit Code Review <gerrit2@gerrit.onos.onlab.us>Tue Jun 10 14:35:09 2014 -0700
treeac511ebd985450cf56d0ec6c530eeac20a1c6776
parent26d7789c6529edce469733c62015e66b7a32ce24 [diff]
Update the Intent Delete API and semantics:

 * Added new Java API for adding/removing Application Intents:
   IPathCalcRuntimeService.addApplicationIntents(...)
   IPathCalcRuntimeService.removeApplicationIntents(...)
   IPathCalcRuntimeService.removeAllApplicationIntents(...)

 * Updated the corresponding REST API to use the new Java API, and
   move all API implementation complexity within the Intent framework.

 * Added a new REST API to support deleting multiple Intents together:
   REST DELETE: /wm/onos/intent/high?intent_id=1,2,3

 * Updated the semantics for deleting an Intent:
   Using the new Intent API (REST or Java) to delete an intent will
   prune the intent as well.
   For now, the pruning is asynchronous.

 * Implemented the corresponding backend support to automatically
   prune intents that have been deleted.
   See class DeleteIntentsTracker inside file PathCalcRuntimeModule.java

 * Updated test PathCalcRuntimeModuleTest.testIntentReroute() to
   reflect the old path deletion.

 * Updated the EntryForIntentMatcher.matchesSafely() to remove
   assertThat() statement.
   With the new implementation, this matcher can be used with not()
   Hamcrest wrapper.

Change-Id: I88e7de119bab9d955d71cede14eb7847c7b6afbf
7 files changed
tree: ac511ebd985450cf56d0ec6c530eeac20a1c6776
  1. .checkstyle
  2. .gitignore
  3. .gitreview
  4. Authors
  5. LICENSE.txt
  6. NOTICE.txt
  7. PARTNERS.txt
  8. README.md
  9. build-ramcloud-java-bindings.sh
  10. cluster-mgmt/
  11. conf/
  12. install-oracle-java.sh
  13. lib/
  14. old-scripts/
  15. onos.sh
  16. onoscli
  17. pom.xml
  18. prep-for-offline.sh
  19. ramcloud-build-scripts/
  20. sample/
  21. scripts/
  22. setup-eclipse.sh
  23. setup-ramcloud.sh
  24. src/
  25. start-ons2014demo.sh
  26. start-rest.sh
  27. vm-utils/
  28. web/
README.md

ONOS (Open Networking Operating System)

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.

License

Apache 2.0

Steps to download and setup a development Virtual Machine

https://wiki.onlab.us:8443/display/onosdocs/Getting+Started+with+ONOS

Building ONOS

  1. Cleanly build ONOS

     $ cd ${ONOS_HOME}/
 $ mvn clean
 $ mvn compile

External Dependencies

  1. Required packages

     $ sudo apt-get install maven python-flask python-cmd2 python-pyparsing

  2. 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.

  3. 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

Configuration

./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

Running ONOS and required components

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.

Running ONOS and required components one by one

You can manually start/stop individual ONOS components as follows:

  1. Start Zookeeper

     $ cd ${ONOS_HOME}/
 $ ./onos.sh zk start

 ## Confirm Zookeeper is running:
 $ ./onos.sh zk status

  2. 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

  3. Start RAMCloud Server

     $ cd ${ONOS_HOME}/
 $ ./onos.sh rc-server start

 ## Confirm RAMCloud Server is running:
 $ ./onos.sh rc-server status

  4. Start ONOS

     $ cd ${ONOS_HOME}/
 $ ./onos.sh core start

 ## Confirm ONOS is running:
 $ ./onos.sh core status

  5. Start ONOS REST API server

     $ cd ${ONOS_HOME}/
 $ ./start-rest.sh start

 ## Confirm the REST API server is running:
 $ ./start-rest.sh status

Developing ONOS in offline environment (Optional)

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