This repository contains a prototype of CHIMA, a framework for the deployment of heterogeneous Service Function Chains whose performance can be guaranteed through the use of runtime redeployments and monitoring with In-band Network Telemetry.
This software and its dependencies have been tested on a fresh install of Ubuntu 20.04 LTS
- Clone this repository
cd
git clone https://github.com/ANTLab-polimi/CHIMA
cd CHIMA
- Install FOP4 dependencies
- Be aware that this process may take a very long time, probably one hour. If this is run in a VM you may want to assign an appropriate number of cores to it, since it involves compiling different packages
- As described in FOP4's readme, at least 2GB of RAM and 12GB of FREE disk space are required
./install/fop4/install-dependencies.sh
- Install FOP4
./install/fop4/install-fop4.sh
cd ~/CHIMA
- Install ONOS
./install/onos/install-onos.sh
- Install Framework
./install/framework/install-framework.sh
- Log out of your current session and log back in to ensure the correct loading of groups, environment variables and bash profile
After all the installation steps have been completed, tests can be executed.
- Start ONOS with the correct set of applications
cd $CHIMA_ROOT
./run-onos.sh
-
Wait for ONOS to complete its startup process
-
Build and install the CHIMAStub application from a different terminal
cd $CHIMA_ROOT/chima-stub
make
- Run the "pre" expect script for the system to be correctly setup. This step is only needed once.
cd $CHIMA_ROOT/measurements
sudo -E ./pre.exp
- Run desired tests using the provided expect script, with configurable parameters
sudo -E ./test.exp [topology] [polling interval] [ewma coefficent]
The available topologies are the following:
- minimal
- medium
- large
- concentrated
- datacenter
- mesh
- unbalanced
Here is an example command to run a test on the minimal topology:
sudo -E ./test.exp minimal 0.1 3
After a test is completed, its results can be found in the $CHIMA_ROOT/measurements/Times directory.
Text files containing the recorded measurements are named according to the timestamp at which they are generated, the name of the used topology, and the value of the two parameters.