The mobile processing unit support as well as a sample application are added.

The mobile processing units are simulated via CloudSim.
It is assumed that the mobile devices operate Hosts and VMs like a server.
Therefore, the classes located in the mobile_processing_unit package have a similar naming convention to the other Cloud and Edge components.

scripts/sample_app3/config/default_config.properties

@@ -0,0 +1,43 @@
+#default config file
+simulation_time=33
+warm_up_period=3
+vm_load_check_interval=0.1
+vm_location_check_interval=0.1
+file_log_enabled=true
+deep_file_log_enabled=false
+
+min_number_of_mobile_devices=200
+max_number_of_mobile_devices=2000
+mobile_device_counter_size=200
+
+wan_propogation_delay=0.1
+lan_internal_delay=0.005
+wlan_bandwidth=0
+wan_bandwidth=0
+gsm_bandwidth=0
+
+#all the host on cloud runs on a single datacenter
+number_of_host_on_cloud_datacenter=1
+number_of_vm_on_cloud_host=4
+core_for_cloud_vm=4
+mips_for_cloud_vm=100000
+ram_for_cloud_vm=32000
+storage_for_cloud_vm=1000000
+
+#each mobile device has one host which serves one VM
+#all the host runs on a single datacenter due to the out of memory (oom) issue
+core_for_mobile_vm=1
+mips_for_mobile_vm=4000
+ram_for_mobile_vm=2000
+storage_for_mobile_vm=32000
+
+#use ',' for multiple values 
+orchestrator_policies=ONLY_EDGE,ONLY_MOBILE,HYBRID
+
+#use ',' for multiple values
+simulation_scenarios=MOBILE_PROCESSING_SCENARIO
+
+#mean waiting time in seconds
+attractiveness_L1_mean_waiting_time=480
+attractiveness_L2_mean_waiting_time=300
+attractiveness_L3_mean_waiting_time=120