Skip to content
This repository has been archived by the owner on Apr 27, 2023. It is now read-only.

Latest commit

 

History

History
103 lines (71 loc) · 3.7 KB

README_STANDALONE.md

File metadata and controls

103 lines (71 loc) · 3.7 KB
Raw

IOVisor-OVN Standalone

The Standalone Mode, allows to test a single or a chain of IOModules, without the OVN integration. The entire chain can be setup with a simple YAML configuration file.

Installation

This guide includes the instructions to install bcc, go, hover and iovisor-ovn. A Linux kernel with a version 4.9 or newer is required, we recommend to use Ubuntu as all the examples have been tested on that platform.

The simplest set of instructions for the upgrade to kernel version 4.9 is listed below.

mkdir /tmp/kernel-4.9/
cd /tmp/kernel-4.9/
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/linux-headers-4.9.0-040900_4.9.0-040900.201612111631_all.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/linux-headers-4.9.0-040900-generic_4.9.0-040900.201612111631_amd64.deb
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9/linux-image-4.9.0-040900-generic_4.9.0-040900.201612111631_amd64.deb
sudo dpkg -i *.deb
#Now reboot your system
sudo reboot

Automatic Installation

In order to automatically install all the required components please execute the following commands, please consider that they only work on Debian based distros.

git clone https://github.com/iovisor/iovisor-ovn.git
cd iovisor-ovn/
./install_alone.sh

Manual Installation

Please follow these steps to install the required components manually.

bcc

Follow the steps indicated in BCC Installation Guide in order to install bcc, please consider that the version 0.2.0 is required.

go

Please follow the Go Installation Guide, Go 1.4 or higher is required

hover

In order to install hover please follow the steps in Installing Hover

Please be sure that this patch is applied before the installation.

iovisor-ovn

Installing iovisor-ovn is very easy, just use the go get command:

go get github.com/iovisor/iovisor-ovn/iovisorovnd

How to use?

In this case the configuration and topology of the service topology to be deployed is passed through a .yaml file.

Launching IOVisor-OVN in Standalone Mode

In order to deploy a service topology from a file, the -file parameter should be passed to the IOVisor-OVN daemon.

export GOPATH=$HOME/go
cd $GOPATH/src/github.com/iovisor/iovisor-ovn/examples/switch
$GOPATH/bin/iovisorovnd -file <file.yaml> -hover <hover_url>

Configuration File

# list of modules to be deployed
modules:
  - name: modulename
    type: moduletype
    config:
      # module configuration

# links between modules
links:
  - from: moduleName
    to: moduleName

# connection to network interfaces
external_interfaces:
  - module: moduleName
    iface: interface name

The file is composed of three sections: modules, links and external_interfaces.

  1. modules: This section contains the modules to be deployed. The name and type are mandatory, while the configuration is optional and different for each kind of IOModules. Please see the documentation of each single IOModule to get information about the configuration parameters.

  2. links: These are the links between the different IOModules, "from" and "to" must correspond to the name of modules in the "modules" section.

  3. external_interfaces: The connection to the network interfaces are defined in this section. Module should be a module defined in the "modules" section and iface should be the name of the interface on the system.

Examples

Some examples with a complete explanation are provided in examples