|author||Carmelo Cascone <firstname.lastname@example.org>||Wed May 26 19:30:30 2021 +0200|
|committer||Carmelo Cascone <email@example.com>||Thu Jun 03 00:35:17 2021 +0000|
SDFAB-193 Add packet-out routing feature to fabric-v1model This is a port from fabric-tna: https://github.com/stratum/fabric-tna/pull/262 By default, all packet-outs are sent straight to the egress port passed as a controller packet-out metadata, bypassing the forwarding tables in the ingress pipe. With this change, the control plane can set a new packet-out metadata named `do_forwarding` to instruct the parser to forward packet-outs as regular packets. When handling `OutboundPacket` in ONOS, the pipeconf (interpreter) uses the `OUTPUT` instruction with logical port `TABLE` to enable forwarding. This is consistent with the OpenFlow behavior, from the spec: Required: TABLE: Represents the start of the OpenFlow pipeline (see 5.1). This port is only valid in an output action in the action list of a packet-out message (see 7.3.7), and submits the packet to the first flow table so that the packet can be processed through the regular OpenFlow pipeline. We also rename some test classes for consistency with main classes. Before we had a FabricPipelinerTest class that was used for a different purpose than testing FabricPipeliner. Change-Id: I1b47c4b4f233df5b67d1a6dc743dea27c54772b2 (cherry picked from commit db347377bec8bf6f71fb9828f4dc552731e562f7)
ONOS is the only SDN controller platform that supports the transition from legacy “brown field” networks to SDN “green field” networks. This enables exciting new capabilities, and disruptive deployment and operational cost points for network operators.
The following packages are required:
The minimum required Bazel version is 1.0.0
$ git clone https://gerrit.onosproject.org/onos
$ cd onos $ cat << EOF >> ~/.bash_profile export ONOS_ROOT="`pwd`" source $ONOS_ROOT/tools/dev/bash_profile EOF $ . ~/.bash_profile
$ cd $ONOS_ROOT $ bazel build onos
To run ONOS locally on the development machine, simply run the following command:
$ bazel run onos-local [-- [clean] [debug]]
Or simpler one, if you have added the ONOS developer environment to your bash profile:
$ ok [clean] [debug]
The above command will create a local installation from the ONOS tarbal (re-building if necessary) and will start the ONOS server in the background. In the foreground, it will display a continuous view of the ONOS (Apache Karaf) log file. Options following the double-dash (–) are passed through to the ONOS Apache Karaf and can be omitted. Here, the
clean option forces a clean installation, removing any state from previous executions. The
debug option means that the default debug port 5005 will be available for attaching a remote debugger.
To access ONOS UI, use a browser to open:
Or simpler, use the
onos-gui localhost command.
The default username and password is
To attach to the ONOS CLI console, run:
$ onos localhost
To run ONOS unit tests, including code Checkstyle validation, run the following command:
$ bazel query 'tests(//...)' | xargs bazel test
Or better yet, to run code Checkstyle and all unit tests use the following convenience alias:
ONOS code is hosted and maintained using Gerrit.
Code on GitHub is only a mirror. The ONOS project does NOT accept code through pull requests on GitHub.
To contribute to ONOS, please refer to Sample Gerrit Workflow. It should include most of the things you'll need to get your contribution started!
For more information, please check out our wiki page or mailing lists:
ONOS (Open Network Operating System) is published under Apache License 2.0
YourKit supports open source projects with innovative and intelligent tools for monitoring and profiling Java and .NET applications. YourKit is the creator of YourKit Java Profiler, YourKit .NET Profiler and YourKit YouMonitor.