Baremetal experiments

In this new version of Kollaps we introduced baremetal deployments, in these new types of deployments there are some differences in some components.

Everything else will function the same way.

Topology Description

To specify a baremetal topology we must first specify in the dashboard service the name and the ip of the machine that will serve as a controller to the experiment.

Example:

<service name="dashboard" supervisor="true" port="8088" controllername = "remote1.us" controller_ip = "172.1.2.3"/>

In this example machine remote1.us with ip 172.1.2.3 will serve as the controller for the experiment, the machine must have access to the other machines.

The way we specify services also changed now we must specify the machine name and the ip address, the location of the Kollaps folder containing the binaries, topology file, etc., and the name of the topology file.

Example:

<service name="client1" machinename = "remote2.us" ip = "172.1.2.4" kollaps_folder = "/home/ubuntu/baremetal" topology_file = "kollaps.xml"/>

In this example, the service with the name client1 will be on machine "remote2.us" with ip "172.1.2.4" the location of the kollaps-folder is "/home/ubuntu/baremetal" and the name of the topology file is kollaps.xml

We also added the script attribute which specifies the script that can be run we the user starts the experiment.

Example:

<service name="client1" machinename = "remote2.us" ip = "172.1.2.4" kollaps_folder = "/home/ubuntu/baremetal" topology_file = "kollaps.xml" script = "client1.sh" />

In this example when the user presses start on the Dashboard the script with the name "client1.sh" inside the kollaps_folder will be run.

Dashboard

In the dashboard there will be now 3 commands:

command	action
INITIALIZE BAREMETAL	which will start the emulation of the network state.
START	which will start the script if the user provides one.
STOP	which will stop the emulation.