CloudSimSDN

CloudSimSDN: SDN extension of CloudSim project. Version 2.0 is now availalbe.

New Features:

Introduction

CloudSimSDN is to simulate utilization of hosts and networks, and response time of requests in SDN-enabled cloud data centers. CloudSimSDN is an add-on package to CloudSim, thus it is highly recommended to learn how to use CloudSim before using CloudSimSDN. CloudSimSDN supports calculating power consumption by both hosts and switches. For instance, network-aware VM placement policies can be evaluated using CloudSimSDN. As an example, we will present energy savings in SDN-enabled cloud data center via VM consolidation. If VMs are consolidated to the minimum number of hosts, the unused hosts and switches can be powered off to save more power. We will show two different VM placement policies: Best Fit (MFF, Most Full First) and Worst Fit (LFF, Least Full First).

Program Dependenciesđź“„

  1. You can download cloudsim-4.0.jar here (https://github.com/Cloudslab/cloudsimsdn/releases/tag/v2.0.1-beta) or clone [CloudSim (cloudsim-4.0)] src code (https://github.com/Cloudslab/cloudsim), either include all src code or export the jar of the newest version (bugs fixed to support cloudsimsdn-nfv);
  2. Add (downloaded cloudsim-4.0.jar) local jar into the maven dependencies: add 2 lines of cloudsim dependency in pom.xml.
        <dependency>
            <groupId>org.cloudbus.cloudsim</groupId>
            <artifactId>cloudsim</artifactId>
            <version>4.0</version>
            <scope>system</scope>
            <systemPath>${project.basedir}/YOUR_PATH/cloudsim-4.0.jar</systemPath>
        </dependency>
  3. enter the project's root directory and execute mvn clean install to install the jar packages into your local maven repository.

Other dependencies are already included.

Quick Start⚡️

After the mvn build, you could simply run the project's example in IDE's Run Configurations by adding commands in the Arguments:

Package Components

  1. org.cloudbus.cloudsim.sdn

    Main components of CloudSimSDN. Core functions are implemented in this package source codes.

  2. org.cloudbus.cloudsim.example

    Example program. SimpleExample.java is the entry point of the example program. Please follow the code from SimpleExample.java This document is to describe the example program. Other Scenarios includes: Inter cloud data centers, Link Selection Policy, Overbooking Host Resources, QoS, Service Function Chaining, and Service Function Chaining in edge computing.

  3. org.cloudbus.cloudsim.sdn.exmaple.topogenerators

    Example topology generators. Physical / Virtual topology files (inter-clouds, Edge computing, SFC, multi-tier web application, etc.) can be generated by using these generators with customizable parameters. Some distributions can be used within topology generators.

  4. org.cloudbus.cloudsim.sdn.monitor

    Energy consumption and utilization monitor.

  5. org.cloudbus.cloudsim.sdn.nos

    Main components of Networking Operation System includes flow channel manager, and extended version of nos for different scenarios.

  6. org.cloudbus.cloudsim.sdn.parsers

    Parsers for physical topology, virtual topology, and workload.

  7. org.cloudbus.cloudsim.sdn.physicalcomponents

    SDN-enabled components includes node, link, physical topology, switches (Aggregation, core, edge, gateway, inter-cloud), routing table, extended datacenter, and host.

  8. org.cloudbus.cloudsim.sdn.policies

    Policies (algorithms) for Host selection, Link selection, Vm allocation, Host overbooking.

    1. org.cloudbus.cloudsim.sdn.provisioners

    Bandwidth(bw) and CPU(Pe) overbooking provisioners.

    1. org.cloudbus.cloudsim.sdn.sfc

    Main components of Service Function Chaining (SFC) festures, including SFC Forwarder, SFC policy, auto scaling algorihtms (scaling up and out), etc.

    1. org.cloudbus.cloudsim.sdn.virtualcomponents

    Flows created in VMs (SDNVM.java) through channel(Channel.java) based on corresponding Flow configuration(FlowConfig.java) are forwarded according to rules(ForwardingRule.java) in SDN-enabled switches. VirtualNetworkMapper includes the main APIs for network traffic forwarding.

    1. org.cloudbus.cloudsim.sdn.workload

    Core components for workload processing and networking transmission. Request.java represents the message submitted to VM that includes a list of activities(Activity.java) that should be performed at the VM (Processing and Transmission). Furthermore, in some senarios, one request could include another request for the subsequent requests which will be performed at the other VMs.

Input Data

We need to submit three input files to CloudSimSDN: data center configuration (physical topology), resource deployment request (virtual topology), and workloads for VMs.

Physical topology (Data center configuration)

Configurations of physical hosts, switches and links that consist of SDN-enabled cloud data center. This can input as JSON file. Please look at sdn-example-physical.json file. In this example, data center is configured to operate 100 hosts, 10 edge switches connecting 10 hosts each, and one core switch that connects all edge switches.

Virtual topology (Resource deployment request)

When customers send VM creation requests to the cloud data center, they provide virtual topology for their network QoS and SLA. Virtual topology consists of VM types and virtual links between VMs. This can input as JSON file. Please look at sdn-example-virtual.json file.

The resource deployment file includes 500 VM creation requests in which three to five VMs are grouped in a same virtual network to communicate with each other.

Workloads (workload.csv)

After VMs are created in the data center, computation and network transmission workloads from end-users are passed to VMs to be processed. A workload consists of compute processing and network transmission. This can input as CSV file. Please look at sdn-example-workload-*.csv files

Workload file has a long packet transmission between VMs in a same virtual network. Since we should measure power consumption of switches, data transmissions between VMs are necessary to let switches work for the experiment time. To make the experiment simple, we make VMs use network bandwidth in full during their lifetime, so that just one long packet transmission workload for each VM is given in the workload file.

A tutorial for 3-tier web application (wikipedia) workloads: https://github.com/Cloudslab/sfcwikiworkload

Simulation Execution

You have to build the project using your IDE or typing mvn clean install at the project's root directory. After that, to execute the example, enter the project's target directory and use the following command:

java -cp cloudsimsdn-1.0-with-dependencies.jar org.cloudbus.cloudsim.sdn.example.SDNExample <LFF|MFF> [physical.json] [virtual.json] [workload1.csv] [workload2.csv] [...]

EXAMPLE:

java -cp cloudsimsdn-1.0-with-dependencies.jar org.cloudbus.cloudsim.sdn.example.SDNExample MFF ../dataset-energy/energy-physical.json ../dataset-energy/energy-virtual.json ../dataset-energy/energy-workload.csv > results.out

This command will run the simulation using MFF algorithm, and the output is redirected to results.out file.

Simulation results

The results have five parts.

EXAMPLE:

To compare with the result of LFF policy, run the same program with 'LFF' parameter instead of 'MFF'. The result shows that 2,508,871Wh was consumed with LFF policy.

Generate different scenarios

  1. Use topology generators (org.cloudbus.cloudsim.sdn.example.topogenerators) to create more complex scenario in larger scale.
  2. Implement different VM allocation policy to test different VM placement algorithms
  3. Implement different NetworkOperatingSystem to test different network policies.

Publication

For the NFV and SFC version, please cite this paper:

Please cite this paper: