vertical.md

Vertical Scaling Scenario

In this scenario a hadoop cluster with one worker node getting monitored is deployed. Thereafter, a MAPE-k loop is initialized that periodically checks whether the CPU utilization of the worker node reaches a critical level. If that is the case a request against the OCCI API is performed, increasing the number of cores and memory available to the machine.

Deploying the Cluster

First, the hadoop cluster has to be deployed. Therefore, first start the MartServer. If the getting started VM is used the following script can be executed:

./startMART.sh

Note: If this scenario is not performed in a running cloud environment consider executing the resetMart.sh script first.

Thereafter, start the InitialDeployment.java file as an Java Application. If the VM is used: Open a terminal and navigate to the VM's desktop and execute the initialDeployment.jar.

java -jar initialDeployment.jar

After the deployment has been performed you can investigate the deployed OCCI model by opening your browser and query for OCCI entitites:

http://localhost:8080/compute
http://localhost:8080/sensor
http://localhost:8080/monitorableproperty

Starting the Adaptation Script

To start the script execute the vertical.sh script. In the VM it is located on the desktop, otherwise you can find it here.

./vertical.sh

In this scenario, a simple bash script is used to check the gathered monitoring data and perform corresponding actions. This scenario serves as an example on how to directly work with the OCCI API, including the monitoring extension, by simply writing small bash scripts.

Note: This scenario mainly serves to get started with the OCCI API. Currently, there is no connector implementing the vertical adjustment as shown in this scenario.

Tuning the Scenario

As the adaptation only reacts on a Critical behavior, it may be interesting to tune the simulated monitoring results. Therefore, the following steps have to be performed:

1. Stop the MartServer (CTRL-C)
2. Navigate to ~/martserver-plugins
3. Open the de.ugoe.cs.rwm.mocci.connecter.dummy.jar with the archive manager.
4. Doubleclick on the resultprovider.properties file
5. Adjust the values to your liking

The file contains the following:

CPU = None,Low,Medium,High,Critical,5000

• CPU: Represents the monitorable.property to be adjusted.
• 5000: Represents the interval in which monitoring.results are written.
• None-Critical: Represents the simulated monitoring.results.

Note; If you want to execute the second scenario please bring the resultprovider.properties file to its original state.