Gitiles
Code Review Sign In
gerrit.onosproject.org / spring-open / 39f0f2ec75390d53f8ede00e7b4be3ee4fad429f
commit39f0f2ec75390d53f8ede00e7b4be3ee4fad429f[log] [tgz]
authorPavlin Radoslavov <pavlin@onlab.us>Thu Mar 20 12:04:57 2014 -0700
committerGerrit Code Review <gerrit2@onos-services>Thu Mar 20 17:33:41 2014 -0700
treecf7d2c5678246a27d13d312039349fc6a39325d1
parent8040b71aca86119d8265d7d7011e1c693cd2b0e2 [diff]
Work toward fixing ONOS-1031: Remove or comment-out references to the FlowManager

Removed or commented-out references to the FlowManager, in preparation for
its removal:

 * BgpRoute.java
   Commented-out references to the FlowManager to add/delete flows.
   Those should be replaced by calls to the new Path Intent framework.
   Currently, we don't have the setup to test BgpRoute and the new Path Intent
   framework is not ready yet, hence those references are commented-out.

 * FlowProgrammer.java
   - Disabled the FlowSynchronizer, because it needs to be refactored,
     and probably now is not working as expected.
   - Removed a call to the FlowManager.flowEntryOnSwitchExpired(sw, id)
     and replaced it with a comment that the Forwarding module needs to be
     informed that a flow is expired.
     Currently, the Forwarding module is not functional and needs to be
     refactored, hence we cannot test any code refactoring around this.

 * FlowSynchronizer.java
   Commented-out a call and relevant code around
   FlowDatabaseOperation.extractFlowEntry()
   The FlowSyncronizer itself needs refactoring, and it is not clear what
   the next version is going to look like.

 * Forwarding.java
   Commented-out a call to flowService.addFlow(flowPath)
   This should be replaced by a call to the new Path Intent framework.
   Currently, the Forwarding module is not working, and the new Path Intent
   framework is not ready yet, hence the call is commented-out.

 * ControllerTest.java
   Removed reference to IFlowService.class because that class will be removed

 * FlowSyncronizerTest.java
   Commented out test code that refers to the FlowDatabaseOperation class.
   That class will be removed, and the test needs to be rewritten after
   the all the cleanup is completed.

Change-Id: I034636ba9c882220f71761a61ea9e6e10bc93357
6 files changed
tree: cf7d2c5678246a27d13d312039349fc6a39325d1
  1. .gitignore
  2. .gitreview
  3. Authors
  4. Documentation/
  5. LICENSE.txt
  6. NOTICE.txt
  7. PARTNERS.txt
  8. README.md
  9. build-ramcloud-java-bindings.sh
  10. cluster-mgmt/
  11. conf/
  12. demo-scripts/
  13. lib/
  14. onos-embedded.sh
  15. perf-scripts/
  16. pom.xml
  17. prep-for-offline.sh
  18. ramcloud-build-scripts/
  19. scripts/
  20. setup-eclipse.sh
  21. setup-ramcloud.sh
  22. src/
  23. start-onos-embedded.sh
  24. start-onos-jacoco.sh
  25. start-onos.sh
  26. start-ramcloud-coordinator.sh
  27. start-ramcloud-server.sh
  28. start-rest.sh
  29. start-zk.sh
  30. test-network/
  31. testbed-ctrl-add-ext.sh
  32. testbed-ctrl-none.sh
  33. vm-utils/
  34. 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.

License

Apache 2.0

Steps to download and setup a development Virtual Machine

http://wiki.onlab.us/display/Eng/ONOS+Development+VM

Building ONOS

  1. Cleanly build ONOS

     $ mvn clean
 $ mvn compile

    NOTE: installing maven for the first time may switch java version from 1.7 to 1.6. This might prevent Cassandra to run.

External Dependencies

  1. Zookeeper

    Download and install apache-zookeeper-3.4.5: http://zookeeper.apache.org/releases.html

  2. RAMCloud

    Run setup-ramcloud.sh to install RAMCloud git repository

Configuration

To configure the processes (ONOS, RAMCLoud and Zookeper) refers to the files in (ONOS-INSTALL-DIR)/conf. A detailed explanation is given in the ONOS WiKi: - "ONOS Documentation/Getting Started with ONOS/Running the RAMCloud branch of ONOS"

Running ONOS with RAMCloud as a separate process

  1. Start Zookeeper

     $ cd (ONOS-INSTALL-DIR)/
 $ ./start-zk.sh start

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

  2. Start RAMCloud Coordinator (only one for cluster)

     $ cd (ONOS-INSTALL-DIR)/
 $ ./start-ramcloud-coordinator.sh start

 ## Confirm RAMCloud Coordinator is running:
 $ ./start-ramcloud-coordinator.sh status

  3. Start RAMCloud Server

     $ cd (ONOS-INSTALL-DIR)/
 $ ./start-ramcloud-server.sh start

 ## Confirm RAMCloud Server is running:
 $ ./start-ramcloud-server.sh status

  4. Start ONOS

     $ cd (ONOS-INSTALL-DIR)/
 $ ./start-onos.sh start

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

  5. Start ONOS REST API server

     $ cd (ONOS-INSTALL-DIR)/
 $ ./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

Running in offline mode (Optional)

Maven is used to build and run ONOS. By default, maven tries to reach the repositories. The '-o' option can be given to the 'mvn' command to suppress this behavior. The MVN environmental variable can be used to set additional options to the 'mvn' command used in ONOS.

  • Example: Running in offline mode

      $ env MVN="mvn -o" ./start-onos.sh start