Skip to content
Marco Ieni edited this page Sep 25, 2017 · 4 revisions

In this page we provide detailed documentation for the D-SPACE4Cloud Optimisation plug-in for Storm technology. As discussed the Getting-Started page, the plug-in implements a five step wizard whose windows change according to the selected technology and target deployment.

The Getting-Started page provides an overview of the plug-in usage when the Spark technology and public cloud deployment are selected. In this section, we report the description of the windows specific for the private deployment and Storm technology.

The optimization wizard starts selecting the entry Optimization Wizard from the menu in Figure 1.

Figure 1: D-SPACE4Cloud three-tier architecture

In case of private deployment, the end user needs to specify the characteristics of the physical infrastructure available and of the VM types which are in use. In particular D-SPACE4Cloud assumes that the physical cluster is homogeneous and allows to specify the characteristics of the physical servers (in terms of number of CPUs, memory available, and cost). Pressing the button Add new configuration (see Figure 2) then the user can specify the configuration of the VM types in use. As for the public cloud deployment, multiple configurations can be specified (see Figure 3) and selected as candidate deployment in the following steps of the wizard. In particular, VMs are described in terms of virtual CPUs number, memory and expected hourly costs (which of course depends on the characteristics of the underlying hardware and can be estimated by relying on industry benchmarks).

Figure 2: Wizard step 2. Specifying private deployment (physical servers)

Figure 3: Wizard step 2. Specifying VM type characteristics

Finally, if Storm is selected as DIA reference technology, then the D-SPACE4Cloud allows to specify as constraint in step 3 the cluster utilization (a number between 1 and 100) through the window reported in Figure 4.

Figure 4: Wizard step 2. Specifying private deployment (physical servers)

All the Optimisation plug-in settings (e.g., simulator to be used, front-end and back-end end-points, path of the JMT pre-processor needed to transform PNML files for the JMT simulator) can be set through the window shown in Figure 5 which can be accessed through the the Window->Preferences menu selecting afterwards D-SPACE4Cloud plug-in.

Figure 5: D-SPACE4Cloud preferences window

Clone this wiki locally