|author||Carmelo Cascone <email@example.com>||Sun Nov 25 02:26:32 2018 -0800|
|committer||Carmelo Cascone <firstname.lastname@example.org>||Tue Dec 11 14:48:06 2018 -0800|
Improve fabric.p4 to reduce pipeline resources and refactor pipeconf impl This patch affects both the P4 pipeline implementation and the Java pipeconf. P4 PIPELINE - Less tables and smarter use of metadata to reduce inter-tables dependencies and favor parallel execution of tables. - Removed unused actions / renamed existing ones to make forwarding behavior clearer (e.g. ingress_port_vlan table) - Remove co-existence of simple and hansed table. Hashed should be the default one, but implementations that do not support action profiles might compile fabric.p4 to use the simple one. - Use @name annotations for match fields to make control plane independent of table implementation. - Use @hidden to avoid showing actions and table on the p4info that cannot be controlled at runtime. - First attempt to support double VLAN cross-connect (xconnect table). - New design has been tested with "fabric-refactoring" branch of fabric-p4test: github.com/opennetworkinglab/fabric-p4test/tree/fabric-refactoring JAVA PIPECONF This patch brings a major refactoring that reflects the experience gathered in the past months of working on fabric.p4 and reasoning on its pipeconf implementation. Indeed, the FlowObjective API is under-specified and sometimes ambiguous which makes the process of creating and maintaining a pipeliner implementation tedious. This refactoring brings a simplified implementation by removing unused/ unnecessary functionalities and by recognizing commonality when possible (e.g. by means of abstract and utility classes). It also makes design patterns more explicit and consistent. Overall, the goal is to reduce technical debt and to make it easier to support new features as we evolve fabric.p4 Changes include: - Changes in pipeliner/interpreter to reflect new pipeline design. - By default translate objective treatment to PiAction. This favors debuggability of flow rules in ONOS. - Support new NextObjective’s NextTreatment class. - Remove lots of unused/unnecessary code (e.g. async callback handling for pending objective install status in pipeliner as current implementation was always returning success) - Gather commonality in abstract classes and simplify implementation for objective translator (filtering, forwarding, next) - New implementation of ForwardingFunctionTypes (FFT) that looks at criterion instance values along with their types (to avoid relying on case-specific if-else conditions to recognize variants of an FFT) - Adaptive translation of NextObjective based on presence of simple or hashed table. - Support DENY FilteringObjective Also: - Fix onos-p4-gen-constants to avoid generating conflicting PiMatchFieldId variable names. - Install Graphviz tools in p4vm to generate p4c graphs - Generate p4c graphs by default when compiling fabric.p4 - Use more compact Hex string when printing PI values Change-Id: Ife79e44054dc5bc48833f95d0551a7370150eac5
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 reuqired:
To install Oracle JDK8, use following commands (Ubuntu):
$ sudo apt-get install software-properties-common -y && \ sudo add-apt-repository ppa:webupd8team/java -y && \ sudo apt-get update && \ echo "oracle-java8-installer shared/accepted-oracle-license-v1-1 select true" | sudo debconf-set-selections && \ sudo apt-get install oracle-java8-installer oracle-java8-set-default -y
ONOS is built with Bazel, an open-source build tool developed by Google. ONOS supports Bazel 0.17 You can download it from official website or package manager (e.g. apt, brew...)
$ 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:
$ ok [clean] [debug]
The above command will create a local installation from the onos.tar.gz file (re-building it 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 of ONOS and the
debug option means that the default debug port 5005 will be available for attaching a remote debugger.
To access ONOS UI, use browser to open http://localhost:8181/onos/ui or use
onos-gui localhost command
The default username and password is onos/rocks
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 includes 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