Welcome to the Distributed ONOS Tutorial.
Slides for the tutorial are available on Google docs:
In this tutorial, you will learn to write a distributed ONOS application. The application you will be writing is called BYON (Build Your Own Network). This tutorial will teach you how to implement an ONOS service, an ONOS store, and how to use parts of the CLI and Northbound API.
(Here are some slides that can be used to accompany the tutorial: Slides)
You will need a computer with at least 2GB of RAM and at least 5GB of free hard disk space. A faster processor or solid-state drive will speed up the virtual machine boot time, and a larger screen will help to manage multiple terminal windows.
The computer can run Windows, Mac OS X, or Linux – all work fine with VirtualBox, the only software requirement.
To install VirtualBox, you will need administrative access to the machine.
The tutorial instructions require prior knowledge of SDN in general, and OpenFlow and Mininet in particular. So please first complete the OpenFlow tutorial and the Mininet walkthrough. Also being familiar with Apache Karaf would be helpful although not entirely required.
Stuck? Found a bug? Questions?
Setup your environment
Install required software
You will need to acquire two files: a VirtualBox installer and the Tutorial VM.
After you have downloaded VirtualBox, install it, then go to the next section to verify that the VM is working on your system.
Amazon Instance for Deployment
We have hosted the AMI used in the tutorial in the Northern California and Oregon zones. It available as a "Community AMI" when you launch an instance in EC2 called: onos-tutorial-v2
Create Virtual Machine
Double-click on the downloaded tutorial zipfile. This will give you an OVF file. Open the OVF file, this will open virtual box with an import dialog. Make sure you provision your VM with 4GB of RAM and if possible 4 CPUs, if not 2 CPUs should be ok.
Click on import. When the import is finished start the VM and login using:
Important Command Prompt Notes
In this tutorial, commands are shown along with a command prompt to indicate the subsystem for which they are intended.
indicates that you are in the ONOS command line, whereas
indicates that you are in mininet.
Verifying that ONOS is deployed
Now ONOS is installed let's quickly run some tests to make sure everything is ok. Let's start by connecting to the ONOS cli:
You should drop into the cli. Now in another cli window let's start mininet.
Now let's see if we have switches that are connected to ONOS:
Let's install reactive forwarding and see if we can forward traffic:
In the mininet console:
Finally let's see if we have switches connected to each instance of ONOS:
The number of switches per ONOS instance may be different for you because mastership is simply obtained by the first controller which handshakes with the switch. If you would like to rebalance the switch-onos ratio simply run:
And now the output of the masters command should give you something similar to this:
Now we should uninstall reactive forwarding so it doesn't get in the way for the next part of the tutorial.
At this point, you multi-instance ONOS deployment is functional. Let's move on to writing some code.
Writing 'Build Your Own Network'
We are now going to start building BYON. BYON is a service which allows you to spawn virtual networks in which each host is connected to every other host of that virtual network. Basically, each virtual network contains a full mesh of the hosts that make it up.
Lab 1: Importing and building an application
We have downloaded some starter code in the ~/onos-byon directory. It contains a root pom.xml file for the project, as well as a initial implementation of the CLI bundle. We can start by importing the entire project into IntelliJ.
Before we fetch stuff from git, run the following to make git happy.
Before we start, make sure you have the latest version of the template code by running:
First start IntelliJ by double clicking on the IntelliJ icon on your desktop. When you get prompted with the following window.
Select "Import Project" and import the onos-byon project.
Import the project from external model, and select "Maven".
And now make sure you check "Sources" and "Documentation" in the Automatically download section:
And click 'Next' and click next as well on the following window. Now, make sure you pick Java 8 in the next window by first clicking on the green '+' sign and selecting 'java-8-openjdk-amd64' and click 'ok' followed by 'Next'.
Finally click on 'Finish'. You should see the byon source tree on the left sidebar.
Next, we can return to a tutorial to build the project.
mci is an alias for mvn clean install. Now, that your project has successfully built your project let's push it up to the ONOS cluster..
The onos-app command will take the oar file that is generated during the build and push it into the specified ONOS instance. The command can also activate the application if you replace install with install! as well as separately activate, deactivate, and uninstall the application. Every time you update your code you simply need to run onos-app $OC1 reinstall! target/byon-1.0-SNAPSHOT.org and the new application will be loaded and started in the remote ONOS instances.
Let's check that everything works by heading into ONOS and running a couple commands:
The application has been successfully installed, but it has not yet been activated. Next, we will activate it:
The star next to the application indicates that it has been activated. We can try running the list-networks command to display the one fake network that is hard coded in the starter code.
Congratulations! You have successfully built, installed and activated the byon application.
Lab 2: Connect the Manager to the Store
In this part, we are going to implement some of the NetworkManager's methods using the provided store. The store will be used to store the service's network state; however, the implementation that is provided is not distributed. We will build a better store in a later part.
The NetworkManager is going to have to use the store (that we are going to build) to store information therefore we are going to need a reference on a NetworkStore:
There are six methods in the NetworkManager that should make calls to the network store. They are marked with "TODO Lab 2" in the starter code.
For example in the getNetworks() method, we will want to replace:
with a call to the store:
Next, let's verify that everything works.
First, you will need to compile byon again with mci and run onos-app $OC1 reinstall! target/byon-1.0-SNAPSHOT.oar again to get your latest bundle loaded into the ONOS docker instances.
Now at an ONOS shell, let's try some of the commands.
Lab 3: Add intents to allow traffic to flow in the virtual networks
In order to be able to use many of ONOS' services, the caller must supply an Application ID. An application ID allow ONOS to identify who is consuming which resources as well as track applications. To achieve this, we ask the CoreService for an application ID in the activate method. You should use the appId when constructing the intents for this part.
We will also need to get a reference to the IntentService. The reference will automatically be injected when the application is loaded after you uncomment the two lines near the top of the NetworkManager.
When addHost() is called, we will need to create an intent between the host and all other hosts that already exist in the network.
You should only to add the intents if this is the first time that the host is added, so be sure to check the store's return value. true indicates that the add was successful i.e. this is the first time.
For this exercise, we will be using HostToHostIntents and you can build one like this:
Make sure to submit a HostToHostIntent between the newly added host, and all other hosts that are already in the virtual network.
It's time to make sure that everything works; build with mci and run onos-app $OC1 reinstall! target/byon-1.0-SNAPSHOT.oar
Now check in mininet that you can actually communicated between the two hosts that you added to your virtual network.
Lab 4: Implementing removal of hosts from a virtual network
When a host is removed from a network or a network is removed entirely, we need to remove the intent related to that host or network from the IntentService. There are Lab 4 TODOs in the removeHost() and removeNetwork() methods. The starter code also contains a removeIntents() method that you will need to complete. In this method, you will need to get the intents from the IntentService, filter the relevant ones to remove, and then instruct the IntentService to withdrawn them. Note: For your convenience, we have provided a helper method, matches(), that can be used to filter the relevant intents.
Next, we will need to construct some CLI commands so that you can test your work, specifically, one command to remove hosts and another to remove networks.
Start by creating two files in the byon-cli package "RemoveHostCommand.java" and "RemoveNetworkCommand.java". These CLI commands are simple and very similar to the add CLI commands, so do this now as an exercise. When you have written these commands, you will need to add the following XML to the 'shell-config.xml' under resources.
Lab 5: Upgrading the store to make it distributed
The starter implementation of the DistributedNetworkStore uses a ConcurrentMap to store information about the virtual networks. This map only stores the data locally, and it knows nothing about other instances in the cluster. We will be replacing the map with a ConsistentMap which is cluster-aware, and one of the distributed primitives provided by ONOS.
Before we can instantiate a ConsistentMap, we need to get a reference to the StorageService; you can do this by uncommented in the StorageService reference near the top of the DistributedNetworkStore class.
Once you change the ConcurrentMap to a ConsistentMap, we will need to update the way the map is created in the activate() method. Here is how we can ask the storage service for a ConcurrentMap:
You will notice a few compilation errors after making this change. This is because the ConcurrentMap returns a Versioned<Value>, rather than just a Value. You should fix the compilation errors marked by Lab 5 TODOs.
Next, let's recompile your application and push it to the ONOS cluster. You should now be able to create, update, and delete networks from any node, and your distributed store will the application running on all instances in sync. Open a few terminals and test this on the different instances.
Lab 6: Network Events
Components in ONOS can use events to asynchronously notify other components when their state has changed. We will demonstrate how this can be done by creating a new event type, NetworkEvent, to notify listeners when a virtual network has been updated. These events will be fired by the distributed store and forwarded by the manager to listeners in the peer ONOS instance.
Let's start by adding a NetworkEvent class:
We are also going to need a couple interfaces that will be needed by the listeners and the and the delegates. The listeners are components which have registered to obtain events from this service, these are usually local. A delegate is a manager which is receiving events from a neighbouring store for the purpose of either taking action on the store event or notifying listeners. So we are going to add NetworkListener.
and a NetworkStoreDelegate interfaces
Of course now if we want the store to be delegate-capable we need to make it extend the Store as shown below.
And since we changed the interface of the Store we will have to add something to the implementation, namely DistributedNetworkStore. This abstract class is used to define the methods for posting event to its delegates.
We need to add the following methods to the NetworkService in order to allow components to add and remove listeners.
The ConsistentMap will already generate notifications when updates are made locally and remotely, so we can mostly leverage that feature to regenerate our events.
To do this, we will need to create a MapEventListener<String, Set<HostId>> class in the DistributedNetworkStore.
We will need to construct an instance of the InternalListener.
This listener will need to be added and removed to the networks map during activation and deactivation respectively.
Alright, so now that the stores emit events the managers should be made to receive them. For this we are going to have to add a reference on the EventDeliveryService an ListenerRegistry to keep track of listeners and NetworkStoreDelegate as shown in the code snippet below.
Then we need to add a couple lines in the activate in order to register our Event type for our listeners and set our delegate.
and vice versa deactivate
Finally add the methods to add listeners and dispatch events coming from the store:
To test this, you will need to create a new component that registers to the NetworkEvents with the NetworkService. We will leave this as an extra credit exercise.
Make sure to use the @Component annotation to start an instance of the class automatically. You will also want to register and deregister with the NetworkService in the activate and deactivate methods of your component.
Finally, build and push the app to the ONOS cluster. You should try to test your implementation. When you add and remove networks and/or hosts you should see this being reflected on the other ONOS instances.
Furthermore, you add, remove, or update a network you should see the following line in the ONOS log. You can get the ONOS log by running:
And you should see a line that look like:
Congratulations! You have learned how to develop an ONOS distributed application on ONOS.