INFOMRMONI

TORING OF
TECHNOLOG
Y
TRANSFER
PROJECTS
IN
INDUSTRIAL
CLUSTERS
EFFECTIVE INFORMATION SECURITY
MONITORING OVER IoT CLOUD
CONNECTED TECHNOLOGY AND
NETWORKS
Abstract: Over the years, the rise in connectivity between devices connected with sensors and
applications to transmit and collect information over network channels has been supported with
the advancement of technology infrastructure. IoT connected devices support real time exchange
of data over networked connections. Information security threats are present with new
technology advancements and need to be countered to ensure information security is maintained
over edge or fog cloud network. A PPDIOO system design and development approach is
outlined in this study to ensure real time information security monitoring or anomalous traffic
and incident detection over network communication supporting data transmission in an IoT
cloud connected network.
Contents
List of Figures............................................................................................................................................3
Project Information...................................................................................................................................4
Chapter 1: Introduction & Background..................................................................................................5
Chapter 2: Scope and Objective...............................................................................................................7
Aims and Objectives..............................................................................................................................8
Chapter 3: Literature Review.................................................................................................................10
Chapter 4: Project Plan..........................................................................................................................12
Chapter 5: Methodology.........................................................................................................................13
5.1: Prepare..........................................................................................................................................13
5.2: Plan................................................................................................................................................13
5.3: Design............................................................................................................................................14
5.4: Implement.....................................................................................................................................15
5.5: Operate..........................................................................................................................................16
5.6: Optimize........................................................................................................................................18
Chapter 6: Iterations...............................................................................................................................21
Iteration 1:Receiving events into the cloud network.........................................................................21
Iteration 2: Virtualization of the cloud data center to trigger authorized workload......................22
Reviewing Functional requirements...................................................................................................23
Chapter 7: Project Budget......................................................................................................................24
Skilled labor and human resource......................................................................................................24
 Hardware Equipment & Resources...................................................................................................24
Software Resources..............................................................................................................................24
Chapter 8: Project Risk Analysis...........................................................................................................26
Limitation of the Project.....................................................................................................................27
Chapter 9: Communication Plan............................................................................................................28
Chapter 10: Stakeholder Identification.................................................................................................29
Conclusion................................................................................................................................................30
References................................................................................................................................................31
Appendix..................................................................................................................................................32
Virtualization cloud simulation IoT task scheduling algorithm.......................................................32
Cloudsim simulation Output from the Algorithm.............................................................................37

List of Figures
Figure 1 :Information security issues affecting IoT Cloud networks..............................................8
Figure 2:Logical framework design of the proposed IoT network function ability......................14
Figure 3: A simulated design of an edge cloud network device nodes and data center................15
Figure 4: created Virtualization machines in data centers............................................................16
Figure 5: Successfully sent cloudlets to Virtualized data center logs...........................................16
Figure 6: Cloudsim simulation for cloudlet transmission..............................................................18
Figure 7: failed allocation instance to host data center logs..........................................................19
Figure 8.Successful simulation output...........................................................................................20
Figure 9: iteration 1.......................................................................................................................21
Figure 10:iteration 2......................................................................................................................22
Project Information
Project Details
Project Title
Project Type
Project Code
Project Location
Project Starting Date

Project Coordinator
Name
Phone number
Email

Project Team Members

Name
Student ID
 Phone Number
Email

Name
Student ID
Phone Number
Email

Project Supervisor
Project Title
Project Type
Project Code
Project Location
Project Starting Date

Chapter 1: Introduction & Background

The current world exists in the globalization era which increases the need to develop information
technology support to tools and techniques to answer the increasing business needs in
organizations across the globe [ CITATION Oni16 \l 1033 ]. IoT technology serves the need to
support real time information exchange and transfer between end sensor nodes and the cloud data
centers that host the IoT network to increase efficient business sustainability.

The advancement in the technology to support IoT transmission over cloud networks brings
about the rise in new way to establish cyberattacks to allow unauthorized modification and
exploitation of data and devices supported by IoT cloud networks [ CITATION Ste18 \l 1033 ].
Organizations need to allocate extra funds in their annual budgets to facilitate costs to meet the
ever growing cyber security concerns in their business information systems.

Achieving information security is an important component of the data management function for
every organization [ CITATION Coo18 \l 1033 ]. Organizational stakeholders rely on 3rd party
organizations to carry out the information security function over their cloud network for a
subscription fee or implement information security incident detection and mitigation on their
own through hired cyber security expert staff.
The use of 3rd party organizations to secure information transmitted by client organization comes
with major setbacks to the client information especially if non - disclosure agreements are not
met by the service provider. Most organizations prefer to build their own cloud networks to
facilitate secure transmission of IoT data from the connected end device nodes and their data
centers.

Information safety and compliance regulatory bodies around the globe emphasize the need for
information security for connected cloud networks. The Telecommunication Industry
Association defines a data center as a building or part of a building designed to centralize
information resources for organizations and allow businesses to provide uninterrupted network
transmission services for information processing operations [ CITATION Tho18 \l 1033 ]. The
procedures for designing a data center should include aspects such as network access control and
security, the network architecture, file storage, retrieval, and backup, electrical power
consumption and management system redundancy, cloud hosting for web, application, and
databases.

General Data Protection Regulation and compliance provides a guideline to control how
companies handle consumer and user private data within their networks .This regulation applies
to organizations operating anywhere in the world and serves consumer individuals in the
European union. ISO/IEC 27001:2013 specifies the requirements for establishing,
implementation, maintenance, and improvement of information security management and
enhance system for IOT network deployment in organizations.

Organizations whose operations and system activities are deployed over cloud connected
networks are expected to meet some requirements in order to get ISO 27001 certification. These
include establishment of a risk management framework, conduct a risk assessment on the IoT
supporting cloud network, implementing system controls against risk, Staff training to help
counter detected risks, and establishing monitoring and review to help improve and update the
information security system.
Chapter 2: Scope and Objective
The scope of the project addressed existing needs from previous technologies such as traditional
and centralized computing. Present challenges affecting existing cloud data centers to effectively
support information security between end device nodes and data centers in an IoT network are
addressed in the study.

The project was initiated to optimize cybersecurity for transmitted real time events, data, and
devices connected to IoT networks at cost friendly prices. The project manager and developer
team concentrated on dynamic task allocation of received and transmitted information workload
from IoT connected device nodes and data center.

Workloads transmitted over IoT cloud supported environments and networks come with different
processing needs, functional requirements and complexities [ CITATION Che21 \l 1033 ]. Hardware
equipment to optimize their transmission over cloud computing environments is expected to
maintain high speed transmissions and is expensive to acquire and implement in small sized and
medium sized organization.
The objective of this research is to bring knowledge to light on task scheduling mechanisms
applied to cloud computing. From distributed processing, IoT cloud equipment vendors to
organizations see the need to improve server and other hardware resources performance through
task scheduling to achieve real time and effective communication of the connected devices and
workload transmission.

Latency time of transmission is switches configured in a cloud networks is calculated to derive

the total time taken to transmit a genuine workload in a cloud network [ CITATION Xue18 \l 1033 ].
This allows for efficient allocation of processing time for received workload from devices
connected within the network and also allow the switch to detect anomalous traffic present in the
network as intercepted workload have a varying latency time of transmission in the network
despite similarity in characteristics.

This research shows the evolution of task scheduling technology and models over time to support
cloud computing systems for most institutions and users to allocate processing time for
transmitted workloads. Task scheduling models are designed differently according to the way
they function in approach to information and workload to be processed over cloud connected
systems. Complex data sets require sophisticated task scheduling models to transmit efficiently
and may be hard to detect in the event they are intercepted with malicious traffic in a cloud
network.

Dynamic task scheduling algorithm that will be used to allocate tasks to different enterprises on a
Cloud manufacturing setup. The proposed scheduling algorithm would be intended to deal with
the time uncertainty of tasks arrival in a Cloud Manufacturing environment [ CITATION JHC20 \l
1033 ]. The research would compare the model’s performance against previous work
transmission approaches.

This study highlights advanced applications derived from task scheduling designed algorithms
and how they can be used to detect and mitigate cyber security incidents e.g. cloud computing
topology attacks like DDoS deployed over cloud computing connected devices and systems for
businesses and other organizations.
Figure 1 :Information security issues affecting IoT Cloud networks

Aims and Objectives

The proposed project aims at achieving count of workload transmitted over an IoT cloud
network at a particular instance.

The proposed project aims to achieve cloud network accountability for network topology
security. This is through facilitation of workload transmission for only system authenticated
devices and end sensor nodes with authorized connections over IoT cloud networks.

The proposed IoT cloud network design project aims at achieving network transmission
productivity for client organizations with existing or outdated network support technology. This
is achieved by dynamically processing and transmission of authorized cloudlets and tasks to
connected data center over minimal transmission time.
Chapter 3: Literature Review
Topology networks supporting information transmission and device communication on cloud
computing network infrastructure are need internet access to facilitate real time information
exchange [ CITATION Moh20 \l 1033 ]. Cyber threats exist over internet connections, and with new
technology advancement over time, the number of cyber threat inventions to affect information
security in cloud connected network rises.

Topology attacks on connected servers to cloud supported infrastructure systems, back end
infrastructure, and the overall network infrastructure are facilitated through code injections, cross
site scripting attacks by hackers to input many recurring requests and instructions to the target
systems database and server till it is overwhelmed to perform instructions as authorized
[ CITATION Tho18 \l 1033 ]. This is leads to distributed denial of service attacks on the target cloud
system to validate the authorization and the authenticity of requests and commands leading to
system transactions in the network.
Network and topology infrastructure is presented as a vulnerability that affects the integrity of
information systems. Network servers represent the core function and support of web application
for all organizations. A vulnerable server leads to a vulnerable user application system since the
database is stored on it and information transmitted through the network are passed through the
server. Servers are affected by topology attacks such as DDOS attacks that overwhelm it with
more instructions and commands than it can handle.

Overwhelmed switches and servers allow the attacker to perform unauthorized modifications on
a target cloud network system transmitted data as the queries supported by servers can’t function
to ensure the set system parameters are met before allowing a transaction to occur.

Information security for topology infrastructure supporting cloud computing connections is

achieved by dynamic allocation of received events and system transactions in a cloud connected
network. Each received event by the cloud network requiring to be processed to the data center is
allocated a virtualization ID in respect to its characteristics [ CITATION Coo18 \l 1033 ]. The task
scheduling algorithm is requires the received events to meet the set system parameters e.g. ram
size or latency time needed for transmission before the switch processes the workload to the
server data center.

Received workload that does not the set parameters is not transmitted over the connected switch
and is logged as malicious or intercepted traffic for further analysis by cyber security experts or
system auditors [ CITATION Ste18 \l 1033 ]. This effects topology security in a connected cloud
network as distributed denial of service attack that overwhelm the function ability of cloud
topologies and infrastructure to ensure cloud network security are detected , mitigated and
reported before they occur.

Workload transmission over previous technologies such as traditional computing supported

centralized processing of received tasks to the data center. Real time workload processing could
not be facilitated over centralized networks, and the virtualization of connected devices requiring
communication over the network would not be supported in real time or online processing.

Cloud computing has revolutionized real time information processing over centralized network
servers to facilitate distributed processing for cloud connected devices and systems [ CITATION
JHC20 \l 1033 ]. With distributed processing, dynamic task scheduling can be supported over
different virtualized data centers and servers in a connected cloud network.

Latency time information for workload received in a cloud network requesting processing time
and cloud virtualization resources is determined over the bridged switch connected to the data
center. The bridged switch relays received and authorized workload through hop counts to
neighboring switch nodes [ CITATION Tho18 \l 1033 ]. The switch is configured to only process and
allocated processing time to authorized received workload that meet the set cloud system
parameters to effect information security in the supported cloud network.

Chapter 4: Project Plan

The project development team worked on a plan to approach the project system planning design,
development, and implementation. Time for each stage was allocated in regards to the technical
work required to approach the project and complete it to meet the set system objective. A
PPDIOO approach is used by the project developers to complete the project.
The project will take 20 weeks to complete. Time allocated for each phase of the project as noted
below.

Iteration No Name Estimated Duration Deliverable Date

(Weeks)
1 Proposal 2 05/04/2021
2 Prepare 3 19/04/2021
3 Plan 2 06/05/2021
4 Design 4 20/05/2021
5 Implement 5 19/06/2021
6 Operate 2 03/06/2021
7 Optimize 2 17/06/2021
 8 Project Completion 20 17/06/2021
Duration

Chapter 5: Methodology
5.1: Prepare
Technological and standardization gaps exist in previous technologies and networks to
efficiently enhance information security for devices connected to centralize and traditional
implemented networks.

Organizations which deploy their data and workload over IoT supported cloud networks are
expected to abide by set technology privacy guidelines such as TIA, GDPR, and ISO 27001:13
for them to be approved to operate in most jurisdictions such as Europe, US, and other part of the
world [ CITATION Moh20 \l 1033 ]. Organizations need to comply by these politically set
regulations in order to get business permits to operate over their networks and also achieve
business agility from efficient business transactions e.g. online sales to clients.

For this project, stakeholders in an organization need an IoT supported network that supports real
time information transfer from connected devices to established data center to meet se guidelines
and also achieve real time online sustainable business operations.
To establish an IoT cloud network as per Telecommunication Infrastructure Standard for data
centers (TIA-942), the following need to be considered in the project.

1. A data center room that meets TIA-942 standards needs to be designed to incorporate a
raised floor.
2. An operation command center should be included in the data center to enable
organizational employees to monitor connected servers
3. Staging area for data configuration of devices connected to the data center
4. Electrical power supply to power the IoT network

The project developers are required to include systems that meet ISO 27001:2013 for
information security in order to ensure information integrity on the connected cloud network. A
Meraki switch is proposed to be included in the network to meet user cloud demands to connect
devices wireless and also through wired transmission.

5.2: Plan
Network audits on passive traffic analysis from previously transmitted workload from existing
networks and active traffic analysis generated by an application generating synthetic traffic from
voice, application and web traffic from workload transmitted in cloud network technology is
used by project developers to audit the plan and methodology of the proposed network. Existing
documentation from previous network transmission technologies is used to check if the designed
model can meet transmission requirement for the proposed network to meet IoT user support and
transmission requirements.

Once the proposed model is accepted, the developers plan how to approach the development of
the proposed design and actualize. Feasibility studies are conducted to ensure that the proposed
IoT cloud design will benefit the client organization to meet their computing and information
traffic needs.
Figure 2:Logical framework design of the proposed IoT network function ability

5.3: Design
Once the plan is approved, a logical illustration of the proposed IoT network model is developed.
Hardware equipment to support the cloud network technology, Software to support the
transmission is included, CPU memory utilization for the network, Virtual private cloud to split
tunnel sensitive information to transmitted in the network.

Figure 3: A simulated design of an edge cloud network device nodes and data center

The existing data center room is improved to meet regulation policies by TIA-942. From figure
3, once the data center room has been completed, two data centers are connected to cloud
connection to facilitate scalable support for information transmission between the connected.
Workload transmission from the data center to device end nodes is depicted by the green and red
colors in figure 3.

A firewall system is implemented between routers and end device sensor nodes to ensure only
authorized traffic reach to the data center. The network topology is supported by the switch
devices that transmit workloads across it. Applications from system connected device sensors
e.g. IoT smart door, humidity monitor, fire monitor, connected laptop are controlled remotely
from the data center.

5.4: Implement
Once the IoT cloud network has been established, from one of the connected PC, Cloud simulation for
java projects is implemented in the network to monitor how the network accepts and transmits received
workloads.

The project development team wishes to achieve real time dynamic task scheduling for all events
transmitted in the developed cloud network. Received tasks into the cloud network are assigned a unique
ID in regards to its characteristics. The switch in the cloud network is configured to only transmit events
that have a cloudlet ID to the network’s data center.

The broker accepts virtue machines that meet the set parameters to connect to the host data
centers. E.g. does not exceed the set ram limit. Figure 4 below shows created virtualization
machines initializing in the data center for cloud simulation.
0.1: Broker: VM #0 has been created in Datacenter #2, Host #0
0.1: Broker: VM #1 has been created in Datacenter #2, Host #0
0.1: Broker: VM #2 has been created in Datacenter #2, Host #0
0.1: Broker: VM #3 has been created in Datacenter #2, Host #1
0.1: Broker: VM #4 has been created in Datacenter #2, Host #0
0.1: Broker: VM #5 has been created in Datacenter #2, Host #1
Figure 4: created Virtualization machines in data centers

Successfully connected virtualization machine instances to the data centers allows the algorithm to
trigger the transmission of received cloudlets representing applications and system transactions over
the data centers for simulation. The same simulation facilitates virtualization for IoT supported networks
to dynamically effect data transmission and connected device sensors real-time communication
0.2: Broker: Sending cloudlet 0 to VM #0
0.2: Broker: Sending cloudlet 1 to VM #1
0.2: Broker: Sending cloudlet 2 to VM #2
0.2: Broker: Sending cloudlet 3 to VM #3
0.2: Broker: Sending cloudlet 4 to VM #4
0.2: Broker: Sending cloudlet 5 to VM #5
Figure 5: Successfully sent cloudlets to Virtualized data center logs
5.5: Operate
A pseudocode algorithm design is developed by researchers to depict how the cloud simulation will run
to allocate received tasks, allocate a cloudlet ID over received task, and set the allowed cloudlets over
the virtue machines created to process the tasks over data centers.

The model designed by researcher is set to effect quality of transmission of the set tasks.

Start
Receive Ttasks in to cloud network 0;
Ttasks ={0,1,2,3,5,8,10,23,34,16,12,40,….n}
Set Ttasks over Br to filter off tasks that don’t meet set LV;
LV (Ttasks) = {ram size, mipr, system parameters set}
If (Ttasks) is not null
LV (ts)} +1
Else exit LV
Endif
For Vm = {0, 1, 2, 3,…n }
Assign Ttasks to broker and virtue machines
Select C from assigned Ttasks
Process C over DH and DC
Select beginning of transmission time
Select transmission end time
Calculate transmission time
End for
While Ttasks remain unassigned
Print transmission not successful
end while
print c
print transmission time

end
For the above pseudocode;
Ttasks For cloud network labeled as 0
Brokers as Br
 Received tasks as Ttasks
Virtue machines as VM
Data Center as DC
Data host as DH
Required parameters for transmission as LV
From the cloud simulation in figure 6 below, received cloudlets that meet the cloudsim
virtualization set requirements are attached with a cloudlet ID and allocated processing time for
transmission .The project development team can ensure that the cloud system only accepts
workload traffic that meets the set criteria into the IoT network. The received tasks whose
characteristics don’t meet the system set parameters are not transmitted and are logged as
unsuccessful workload transmission for further investigation by system administrators.

Figure 6: Cloudsim simulation for cloudlet transmission

5.6: Optimize
The received data packets and information traffic is transmitted through link layer discovery protocol
within the switches. From figure 3, Switches are programmed to forward receive data packets to the
designated destination device through neighboring nodes. These neighboring switch nodes receive and
forward transmitted packets to their neighboring nodes till a packet is successfully sent. Communication
of these nodes is cut off if a packet is not successfully transmitted across
Hop counts are run within each node to establish the latency time to require transmit a successful
packet through a switch to the data cloud centers. A constant latency time is derived per workload sent
from the edge sensors to the supported devices in the network cloud.

A function is declared to derive latency transmission time per neighboring node in a switch, switch
transmission time, frequency of transmission per switch in the edge cloud network.

Let;

Switch Hop count Ht ; counts per neighboring switch nodes required to forward a
transmitted packet to a cloud

Latency time be Lt; time required to forward a forwarded packet to a neighboring node.
Lh represents the highest latency time recorded and Ll represents the lowest

Latency time of switch transmission St ; ( Ht x Lt )

Frequency be F derived by; Lt/Ht

Number of nodes in a switch be Ns

The precision of transmission per workload in an edge network Pt

Mt= Mean switch transmission time = Lh - Ll

Ht

−Mt ± √ Mt 2−4 H t f
P t=
2 Ht

From the declared latency time of transmission per node, the frequency of data transmission can
be derived by calculating the time required to forward a data packet to a neighboring node per
the time an edge connected data switch requires to forward and receive a deployed data packet.

This frequency can be monitored to ensure that the information transmitted within the edge
network is authenticated and that its source and recipient is authorized to have access to the data.

Virtualization allows system users to create virtue layers over connected hardware which
allowed system users to run multiple instances on connected hardware. The broker rejects some
virtue machines trying to connect to the host data center as they don’t meet some parameters e.g.
Virtue machine RAM memory need to trigger the received event is greater than the system
allocated RAM.

[VmScheduler.vmCreate] Allocation of VM #7 to Host #0 failed by RAM

[VmScheduler.vmCreate] Allocation of VM #7 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #8 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #8 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #9 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #9 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #10 to Host #0 failed by RAM
Figure 7: failed allocation instance to host data center logs

Simulation output results from successful transmission over the cloud data center are tabulated into
cloudsim output log.

========== OUTPUT ==========

Cloudlet ID STATUS Data center ID VM ID Time Start Time Finish Time
4 SUCCESS 2 4 3 0.2 3.2
16 SUCCESS 2 4 3 0.2 3.2
28 SUCCESS 2 4 3 0.2 3.2
5 SUCCESS 2 5 3 0.2 3.2
17 SUCCESS 2 5 3 0.2 3.2
29 SUCCESS 2 5 3 0.2 3.2
6 SUCCESS 3 6 3 0.2 3.2
18 SUCCESS 3 6 3 0.2 3.2
25 SUCCESS 2 1 4 0.2 4.2
37 SUCCESS 2 1 4 0.2 4.2
2 SUCCESS 2 2 4 0.2 4.2
14 SUCCESS 2 2 4 0.2 4.2
26 SUCCESS 2 2 4 0.2 4.2
38 SUCCESS 2 2 4 0.2 4.2
3 SUCCESS 2 3 4 0.2 4.2
15 SUCCESS 2 3 4 0.2 4.2
27 SUCCESS 2 3 4 0.2 4.2
39 SUCCESS 2 3 4 0.2 4.2
Dynamic task scheduling simulation is complete!
Figure 8.Successful simulation output
Chapter 6: Iterations
Upon completion of the data center room, in stage iteration are designed to visualize the plan that
requires to be implemented in order to achieve the secure cloud network.

Information security is only achieved once some steps are achieved through device configuration and
cloud data center virtualization.

Iteration 1:Receiving events into the cloud network

Figure 9: iteration 1

The proposed cloud network is set to meet information safety requirements by ensuring
workload that need to transmitted to the data center falls within the set system parameters. The
system logs received workload whose properties exceed the set parameters e.g. ram size and
triggers the report to the authorized system and cloud network administrators . The cloud
network system only allocates transmission resources to received workload that meet the set
parameters
Iteration 2: Virtualization of the cloud data center to trigger authorized workload

Figure 10:iteration 2

Once authorized received workload is allocated virtualization resources, the cloud set broker
allocates the workload transmission time from the set latency transmission time. Transmission
time is counted for each workload transmitted over the switch and other connected devices
supporting the network. Transmitted workload whose latency transmission time exceeds the set
transmission time are logged as malicious or intercepted and system administrators follow up the
log report for malicious interception. The network shuts down the virtualization engine once
transmission ends.

Reviewing Functional requirements

For the cloud system to be completely functional, it must run to meet the following requirements;

Set parameters to filter out workloads that have more system requirements than the cloud
network can meet. This is through the set parameters initiated in the resource container .From the
code in the appendix, set parameter include;

//VM set Parameters

long size = 10000; //image size

int ram = 512; //vm memory
int mips = 1000;
long bw = 1000;
int pesNumber = 1; //number of cpus
String vmm = "Xen"; //Vm name

The system should also calculate the transmission time for all cloudlets transmitted from the
connected devices and sensors to the cloud data center. This derived latency time is used to
ensure that the transmitted workload are not intercepted by any unauthorized malicious script as
this increases the cloud network transmission time.

Nonfunctional system requirements are attributes discovered from running the system by the
cloud users. Dynamic task allocation of cloudlets and authorized workload ensures high
performance of the network to randomly allocate virtualization resources in a cloud connected
network securely. This reduces cloud system downtime and transmission lags due to deadlock
situations in the cloud network.
Chapter 7: Project Budget
The development of this project could only be successful if the hardware equipment acquired to
support the technology network transmission matched the skilled workforce to implement the
network cloud system. The project development team proposed a budget to be incurred for the
project expenses in order to make it a success.

Skilled labor and human resource

Workforce Hours worked Number of Rate Cost Discount
Workers hired Rate (%)
Project Manager 20 1 25 $/ 490 $ 3
hr.
Project development 20 4 18 $ / 1440 $ 0
team hr.
Information security 40 hrs. a week 1 12 480 $ 0
analyst $/hr.
Cisco IoT administrator 40 hrs. a week 1 10 400 $ 0
$/hr.
Cisco Certified Design 40 hrs. a week 1 11 440 $ 0
Professional $/hr.
Cisco Certified Network 40 hrs. a week 4 10 400 $ 0
Associate $/hr.
System administrator 40 hrs. a week 4 8 $/hr. 320 $ 0
TOTAL 3970 $

Hardware Equipment & Resources

Equipment Type Quantity Cost
Server Meraki MX60W-HW 2 1690 $
Firewall Cisco ASA 5500-X Series 2 880 $
IoT IAM sensors Global sign 3 120 $
Computers HP 6 1200$
Switch Cisco WS-C2960C-12PC- 2 2880 $
L
Data Center room Well aerated with a raised 1 600 $
floor cabinet
Data center smart locks IBM 2 40 $
TOTAL $7450

Software Resources
Software Type Quantity Cost
Chrome Browser Free to use software 6 0$
 Windows 10 100 $ 6 600 $
Kali Linux system Free to use software 3 0$
administration
Windows server Free to use software 3 0$
VM Ware 300$ 2 600 $
Cloudsim virtualization Free to use software 1 0$
TOTAL 1200 $

The total amount of money to be incurred to develop the project is $ 12620

Chapter 8: Project Risk Analysis
The project development team made an analysis of the constraints that would limit the
development of the project to completion. Some risks were highlighted and ways to mitigate
them were proposed.

Risk Risk Impact Probability Risk Mitigation Risk

ID Contingency
R1 Project High Low Client should follow up on Project may be
Termination the IoT development transferred to
progress to ensure that all another project
phases are met as per their development
requirements team
R2 Insufficient High Medium Client organization should Project
funds to ensure that funds are initialization
complete available before the project should be
entire development begins suspended
project until funds to
facilitate
development
of the network
are available
R3 Unmet High Medium Project manager should The client
requirement ensure that he has the right should only
s by project skill workforce to ensure the pay the project
development project is developed as per development
team the clients requirements team once the
requirements
are met
R4 Information High High Back up storage media The project
loss during should be implemented on development
system the existing systems before team should
migration the system is migrated to ensure that the
support cloud and IoT backup systems
information transmission ae completely
and network functional
before
upgrading the
previous
systems for
clients to
support IoT
networks
Limitation of the Project
The implemented cloud network support system comes with some limitations that may need to
be improved through future updates. These include;

The software can only counter topology attacks such as distributed denial of service attacks. The
system cannot independently detect malware from received workload and requires other 3rd party
software to fully protect the implemented network system from real-time information threats.
Chapter 9: Communication Plan
Communication between the project development team, client organization, and other
stakeholders who need the implementation of an IoT cloud network was necessary to track the
progress of the project development.
Stakeholders Communication Location Frequency
means
Client –Project Face To face meetings Project site After Completion of
manager each project
development phase.

Emails/phone Over mobile In the event an

calls/message connections emergency related to
the project
development arises.

Project manager & Face To face meetings Project site To address project
Project Team phase requirements
members before a new phase
begins

Emails/phone Over mobile While addressing

calls/message connections project development
issues
Project Team Face to face meetings Project device site Address the
members development of the
project

Skype/emails/online Over online Addressing project

meetings telecommunication progress when not
connections working in the
project site
Chapter 10: Stakeholder Identification
The stakeholders of the developed project include core users and developers from an external
and internal point of view. Their roles and responsibility towards the developed cloud network
system are outlined as below.

Position Internal/External Responsibility Contact

Project coordinator Internal Ensure Project Email:
Development team [email protected]
meet organization
cloud system needs
Project Manager External Ensure the Email:
development of the [email protected]
client system is
done as per the
agreed
requirements and
on a timely basis
Project External Develop clients Email:
Development Team project to meet the [email protected]
agreed client
requirements
System Internal Ensure the Email:
Administrator developed system [email protected]
is fully running and
the scope of the
implemented cloud
system serves the
organization
operational needs
Information Internal Ensure information Email:
Security manager integrity is [email protected]
maintained in the
developed IoT
supported network
and that only
authorized traffic is
transmitted in the
network
IoT Cloud system Internal Work with the Email:
users developed system [email protected]
to meet
organizations
operational needs
Conclusion
Dynamic allocation of processing time for cloudlets and received tasks over the Cloud platform
allows the network to support real time workload and event processing .The IoT network
developed functions to randomly accept tasks from network authorized devices and process them
over to the IoT cloud data center

Targeted distributed attacks over IoT cloud networks overwhelm authentication security control
bounds if the magnitude of the attack is high. Distributed denial of service attacks affect
topologies that support IoT cloud transmission .This is system has been developed to support the
countermeasures of such topology attacks. Its implementation on an organization’s network
secures organization devices and information transmitted from topology attacks.
References
Aburukba, R. A. &. L., 2020. Scheduling Internet of Things requests to minimize latency in
hybrid Fog–Cloud computing.. Future Generation Computer Systems.
Almogren, M. &., 2020. Security Challenges and Strategies for the IoT in Cloud Computing. s.l.,
11th International Conference on Information and Communication Systems (ICICS).
Chen, F. L. D. P. F. &. T., 2021. IoT Cloud Security Review: A Case Study Approach Using
Emerging Consumer-oriented Applications. s.l., ACM Computing Surveys (CSUR).
Cook, A. R. M. F. M. &. M. L., 2018. Internet of cloud: Security and privacy issues. In Cloud
Computing for Optimization: Foundations, Applications, and Challenges.
J.H. & Chowdhury, 2020. An improved genetic algorithm using greedy strategy toward task
scheduling optimization in cloud environments. Neural Computing and Applications.
Onizawa, R. &. T., 2016. Next-generation IoT-based production system for high-mix low-
volume products in an era of globalization. Hitachi Review.
Stergiou, B. &. K., 2018. Secure integration of IoT and cloud computing. Future Generation
Computer Systems.
Thota, C. S. R. M. G. V. &. P., 2018. Centralized fog computing security platform for IoT and
cloud in healthcare system. In Fog computing: Breakthroughs in research and practice .
Xue, W. &. S., 2018. Knowledge based differential evolution for cloud computing service
composition. Journal of Ambient Intelligence and Humanized Computing.
Appendix

Virtualization cloud simulation IoT task scheduling algorithm

package Dynamic task scheduling;

import java.text.DecimalFormat;
import java.util.ArrayList;
import java.util.Calendar;
import java.util.LinkedList;
import java.util.List;

import org.cloudbus.cloudsim.Cloudlet;
import org.cloudbus.cloudsim.CloudletSchedulerTimeShared;
import org.cloudbus.cloudsim.Datacenter;
import org.cloudbus.cloudsim.DatacenterBroker;
import org.cloudbus.cloudsim.DatacenterCharacteristics;
import org.cloudbus.cloudsim.Host;
import org.cloudbus.cloudsim.Log;
import org.cloudbus.cloudsim.Pe;
import org.cloudbus.cloudsim.Storage;
import org.cloudbus.cloudsim.UtilizationModel;
import org.cloudbus.cloudsim.UtilizationModelFull;
import org.cloudbus.cloudsim.Vm;
import org.cloudbus.cloudsim.VmAllocationPolicySimple;
import org.cloudbus.cloudsim.VmSchedulerTimeShared;
import org.cloudbus.cloudsim.core.CloudSim;
import org.cloudbus.cloudsim.provisioners.BwProvisionerSimple;
import org.cloudbus.cloudsim.provisioners.PeProvisionerSimple;
import org.cloudbus.cloudsim.provisioners.RamProvisionerSimple;

public class CloudSimExample6 {

//cloudlet list; triggered events and application services

private static List<Cloudlet> cloudletList;

private static List<Vm> vmlist;

private static List<Vm> createVM(int userId, int vms) {

//Resource container to store VMs

LinkedList<Vm> list = new LinkedList<Vm>();

//VM set Parameters

long size = 10000; //image size
int ram = 512; //vm memory
int mips = 1000;
long bw = 1000;
int pesNumber = 1; //number of cpus
String vmm = "Xen"; //Vm name
 //create VMs
Vm[] vm = new Vm[vms];

for(int i=0;i<vms;i++){
vm[i] = new Vm(i, userId, mips, pesNumber, ram, bw, size, vmm,
new CloudletSchedulerTimeShared());

list.add(vm[i]);
}

return list;
}

private static List<Cloudlet> createCloudlet(int userId, int cloudlets){

// Creates a container to store Cloudlets
LinkedList<Cloudlet> list = new LinkedList<Cloudlet>();

//cloudlet parameters
long length = 1000;
long fileSize = 300;
long outputSize = 300;
int pesNumber = 1;
UtilizationModel utilizationModel = new UtilizationModelFull();

Cloudlet[] cloudlet = new Cloudlet[cloudlets];

for(int i=0;i<cloudlets;i++){
cloudlet[i] = new Cloudlet(i, length, pesNumber, fileSize,
outputSize, utilizationModel, utilizationModel, utilizationModel);
// setting owner of the set Cloudlets
cloudlet[i].setUserId(userId);
list.add(cloudlet[i]);
}

return list;
}

public static void main(String[] args) {

Log.printLine("Starting CloudSimsimulation...");

try {
// Initialize the CloudSim package for simulation.
int num_user = 1; // number of grid users
Calendar calendar = Calendar.getInstance();
boolean trace_flag = false; // mean trace events

// Initialize the CloudSim library

CloudSim.init(num_user, calendar, trace_flag);

// Create Datacenters
//Datacenters are the resource providers in CloudSim. We need at
list one of them to run a CloudSim simulation
@SuppressWarnings("unused")
Datacenter datacenter0 = createDatacenter("Datacenter_0");
@SuppressWarnings("unused")
 Datacenter datacenter1 = createDatacenter("Datacenter_1");

//Third step: Create Broker

DatacenterBroker broker = createBroker();
int brokerId = broker.getId();

//Fourth step: Create VMs and Cloudlets and send them to broker
vmlist = createVM(brokerId,20); //creating 20 vms
cloudletList = createCloudlet(brokerId,40); // creating 40
cloudlets

broker.submitVmList(vmlist);
broker.submitCloudletList(cloudletList);

// Fifth step: Starts the simulation

CloudSim.startSimulation();

// Final step: Print results when simulation is over

List<Cloudlet> newList = broker.getCloudletReceivedList();

CloudSim.stopSimulation();

printCloudletList(newList);

Log.printLine("CloudSim simulation has finished!");

}
catch (Exception e)
{
e.printStackTrace();
Log.printLine("The simulation has been terminated due to an
unexpected error");
}
}

private static Datacenter createDatacenter(String name){

List<Host> hostList = new ArrayList<Host>();

List<Pe> peList1 = new ArrayList<Pe>();

int mips = 1000;

//The 4 parameters added to create a quad core supported VM

peList1.add(new Pe(0, new PeProvisionerSimple(mips)));
peList1.add(new Pe(1, new PeProvisionerSimple(mips)));
peList1.add(new Pe(2, new PeProvisionerSimple(mips)));
peList1.add(new Pe(3, new PeProvisionerSimple(mips)));

List<Pe> peList2 = new ArrayList<Pe>();

peList2.add(new Pe(0, new PeProvisionerSimple(mips)));
peList2.add(new Pe(1, new PeProvisionerSimple(mips)));

// Hosts with its id and other set parameters to the VM

int hostId=0;
 int ram = 2048;
long storage = 1000000;
int bw = 10000;

hostList.add(
new Host(
hostId,
new RamProvisionerSimple(ram),
new BwProvisionerSimple(bw),
storage,
peList1,
new VmSchedulerTimeShared(peList1)
)
);

hostId++;

hostList.add(
new Host(
hostId,
new RamProvisionerSimple(ram),
new BwProvisionerSimple(bw),
storage,
peList2,
new VmSchedulerTimeShared(peList2)
)
);

//Data center created Characteristics and properties for the set data center

String arch = "x86"; // this is system architecture

String os = "Linux"; // the cloud system runs under Linux OS
String vmm = "Xen";
double time_zone = 10.0;
double cost = 3.0;
double costPerMem = 0.05;
double costPerStorage = 0.1;
double costPerBw = 0.1;
LinkedList<Storage> storageList = new LinkedList<Storage>();

DatacenterCharacteristics characteristics = new

DatacenterCharacteristics(
arch, os, vmm, hostList, time_zone, cost, costPerMem,
costPerStorage, costPerBw);

// create a Power data center

Datacenter datacenter = null;
try {
datacenter = new Datacenter(name, characteristics, new
VmAllocationPolicySimple(hostList), storageList, 0);
} catch (Exception e) {
e.printStackTrace();
}
 return datacenter;
}

//broker policies to submit virtue machines and cloudlets

private static DatacenterBroker createBroker(){

DatacenterBroker broker = null;

try {
broker = new DatacenterBroker("Broker");
} catch (Exception e) {
e.printStackTrace();
return null;
}
return broker;
}

private static void printCloudletList(List<Cloudlet> list) {

int size = list.size();
Cloudlet cloudlet;

String indent = " ";

Log.printLine();
Log.printLine("========== OUTPUT ==========");
Log.printLine("Cloudlet ID" + indent + "STATUS" + indent +
"Data center ID" + indent + "VM ID" + indent + indent +
"Time" + indent + "Start Time" + indent + "Finish Time");

DecimalFormat dft = new DecimalFormat("###.##");

for (int i = 0; i < size; i++) {
cloudlet = list.get(i);
Log.print(indent + cloudlet.getCloudletId() + indent + indent);

if (cloudlet.getCloudletStatus() == Cloudlet.SUCCESS){
Log.print("SUCCESS");

Log.printLine( indent + indent + cloudlet.getResourceId()

+ indent + indent + indent + cloudlet.getVmId() +
indent + indent + indent +
dft.format(cloudlet.getActualCPUTime()) +
indent + indent +
dft.format(cloudlet.getExecStartTime())+ indent + indent + indent +
dft.format(cloudlet.getFinishTime()));
}
}

}
}
Cloudsim simulation Output from the Algorithm
Starting Cloud simulation for triggered events...
Initialising...
Starting CloudSim version 3.0
Datacenter_0 is starting...
Datacenter_1 is starting...
Broker is starting...
Entities started.
0.0: Broker: Cloud Resource List received with 2 resource(s)
0.0: Broker: Trying to Create VM #0 in Datacenter_0
0.0: Broker: Trying to Create VM #1 in Datacenter_0
0.0: Broker: Trying to Create VM #2 in Datacenter_0
0.0: Broker: Trying to Create VM #3 in Datacenter_0
0.0: Broker: Trying to Create VM #4 in Datacenter_0
0.0: Broker: Trying to Create VM #5 in Datacenter_0
0.0: Broker: Trying to Create VM #6 in Datacenter_0
0.0: Broker: Trying to Create VM #7 in Datacenter_0
0.0: Broker: Trying to Create VM #8 in Datacenter_0
0.0: Broker: Trying to Create VM #9 in Datacenter_0
0.0: Broker: Trying to Create VM #10 in Datacenter_0
0.0: Broker: Trying to Create VM #11 in Datacenter_0
0.0: Broker: Trying to Create VM #12 in Datacenter_0
0.0: Broker: Trying to Create VM #13 in Datacenter_0
0.0: Broker: Trying to Create VM #14 in Datacenter_0
0.0: Broker: Trying to Create VM #15 in Datacenter_0
0.0: Broker: Trying to Create VM #16 in Datacenter_0
0.0: Broker: Trying to Create VM #17 in Datacenter_0
0.0: Broker: Trying to Create VM #18 in Datacenter_0
0.0: Broker: Trying to Create VM #19 in Datacenter_0
[VmScheduler.vmCreate] Allocation of VM #6 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #6 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #7 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #7 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #8 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #8 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #9 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #9 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #10 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #10 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #11 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #11 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #12 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #12 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #13 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #13 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #14 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #14 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #15 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #15 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #16 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #16 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #17 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #17 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #18 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #18 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #19 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #19 to Host #1 failed by MIPS
0.1: Broker: VM #0 has been created in Datacenter #2, Host #0
0.1: Broker: VM #1 has been created in Datacenter #2, Host #0
0.1: Broker: VM #2 has been created in Datacenter #2, Host #0
0.1: Broker: VM #3 has been created in Datacenter #2, Host #1
0.1: Broker: VM #4 has been created in Datacenter #2, Host #0
0.1: Broker: VM #5 has been created in Datacenter #2, Host #1
0.1: Broker: Creation of VM #6 failed in Datacenter #2
0.1: Broker: Creation of VM #7 failed in Datacenter #2
0.1: Broker: Creation of VM #8 failed in Datacenter #2
0.1: Broker: Creation of VM #9 failed in Datacenter #2
0.1: Broker: Creation of VM #10 failed in Datacenter #2
0.1: Broker: Creation of VM #11 failed in Datacenter #2
0.1: Broker: Creation of VM #12 failed in Datacenter #2
0.1: Broker: Creation of VM #13 failed in Datacenter #2
0.1: Broker: Creation of VM #14 failed in Datacenter #2
0.1: Broker: Creation of VM #15 failed in Datacenter #2
0.1: Broker: Creation of VM #16 failed in Datacenter #2
0.1: Broker: Creation of VM #17 failed in Datacenter #2
0.1: Broker: Creation of VM #18 failed in Datacenter #2
0.1: Broker: Creation of VM #19 failed in Datacenter #2
0.1: Broker: Trying to Create VM #6 in Datacenter_1
0.1: Broker: Trying to Create VM #7 in Datacenter_1
0.1: Broker: Trying to Create VM #8 in Datacenter_1
0.1: Broker: Trying to Create VM #9 in Datacenter_1
0.1: Broker: Trying to Create VM #10 in Datacenter_1
0.1: Broker: Trying to Create VM #11 in Datacenter_1
0.1: Broker: Trying to Create VM #12 in Datacenter_1
0.1: Broker: Trying to Create VM #13 in Datacenter_1
0.1: Broker: Trying to Create VM #14 in Datacenter_1
0.1: Broker: Trying to Create VM #15 in Datacenter_1
0.1: Broker: Trying to Create VM #16 in Datacenter_1
0.1: Broker: Trying to Create VM #17 in Datacenter_1
0.1: Broker: Trying to Create VM #18 in Datacenter_1
0.1: Broker: Trying to Create VM #19 in Datacenter_1
[VmScheduler.vmCreate] Allocation of VM #12 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #12 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #13 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #13 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #14 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #14 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #15 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #15 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #16 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #16 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #17 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #17 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #18 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #18 to Host #1 failed by MIPS
[VmScheduler.vmCreate] Allocation of VM #19 to Host #0 failed by RAM
[VmScheduler.vmCreate] Allocation of VM #19 to Host #1 failed by MIPS
0.2: Broker: VM #6 has been created in Datacenter #3, Host #0
0.2: Broker: VM #7 has been created in Datacenter #3, Host #0
0.2: Broker: VM #8 has been created in Datacenter #3, Host #0
0.2: Broker: VM #9 has been created in Datacenter #3, Host #1
0.2: Broker: VM #10 has been created in Datacenter #3, Host #0
0.2: Broker: VM #11 has been created in Datacenter #3, Host #1
0.2: Broker: Creation of VM #12 failed in Datacenter #3
0.2: Broker: Creation of VM #13 failed in Datacenter #3
0.2: Broker: Creation of VM #14 failed in Datacenter #3
0.2: Broker: Creation of VM #15 failed in Datacenter #3
0.2: Broker: Creation of VM #16 failed in Datacenter #3
0.2: Broker: Creation of VM #17 failed in Datacenter #3
0.2: Broker: Creation of VM #18 failed in Datacenter #3
0.2: Broker: Creation of VM #19 failed in Datacenter #3
0.2: Broker: Sending cloudlet 0 to VM #0
0.2: Broker: Sending cloudlet 1 to VM #1
0.2: Broker: Sending cloudlet 2 to VM #2
0.2: Broker: Sending cloudlet 3 to VM #3
0.2: Broker: Sending cloudlet 4 to VM #4
0.2: Broker: Sending cloudlet 5 to VM #5
0.2: Broker: Sending cloudlet 6 to VM #6
0.2: Broker: Sending cloudlet 7 to VM #7
0.2: Broker: Sending cloudlet 8 to VM #8
0.2: Broker: Sending cloudlet 9 to VM #9
0.2: Broker: Sending cloudlet 10 to VM #10
0.2: Broker: Sending cloudlet 11 to VM #11
0.2: Broker: Sending cloudlet 12 to VM #0
0.2: Broker: Sending cloudlet 13 to VM #1
0.2: Broker: Sending cloudlet 14 to VM #2
0.2: Broker: Sending cloudlet 15 to VM #3
0.2: Broker: Sending cloudlet 16 to VM #4
0.2: Broker: Sending cloudlet 17 to VM #5
0.2: Broker: Sending cloudlet 18 to VM #6
0.2: Broker: Sending cloudlet 19 to VM #7
0.2: Broker: Sending cloudlet 20 to VM #8
0.2: Broker: Sending cloudlet 21 to VM #9
0.2: Broker: Sending cloudlet 22 to VM #10
0.2: Broker: Sending cloudlet 23 to VM #11
0.2: Broker: Sending cloudlet 24 to VM #0
0.2: Broker: Sending cloudlet 25 to VM #1
0.2: Broker: Sending cloudlet 26 to VM #2
0.2: Broker: Sending cloudlet 27 to VM #3
0.2: Broker: Sending cloudlet 28 to VM #4
0.2: Broker: Sending cloudlet 29 to VM #5
0.2: Broker: Sending cloudlet 30 to VM #6
0.2: Broker: Sending cloudlet 31 to VM #7
0.2: Broker: Sending cloudlet 32 to VM #8
0.2: Broker: Sending cloudlet 33 to VM #9
0.2: Broker: Sending cloudlet 34 to VM #10
0.2: Broker: Sending cloudlet 35 to VM #11
0.2: Broker: Sending cloudlet 36 to VM #0
0.2: Broker: Sending cloudlet 37 to VM #1
0.2: Broker: Sending cloudlet 38 to VM #2
0.2: Broker: Sending cloudlet 39 to VM #3
3.1980000000000004: Broker: Cloudlet 4 received
3.1980000000000004: Broker: Cloudlet 16 received
3.1980000000000004: Broker: Cloudlet 28 received
3.1980000000000004: Broker: Cloudlet 5 received
3.1980000000000004: Broker: Cloudlet 17 received
3.1980000000000004: Broker: Cloudlet 29 received
3.1980000000000004: Broker: Cloudlet 6 received
3.1980000000000004: Broker: Cloudlet 18 received
3.1980000000000004: Broker: Cloudlet 30 received
3.1980000000000004: Broker: Cloudlet 7 received
3.1980000000000004: Broker: Cloudlet 19 received
3.1980000000000004: Broker: Cloudlet 31 received
3.1980000000000004: Broker: Cloudlet 8 received
3.1980000000000004: Broker: Cloudlet 20 received
3.1980000000000004: Broker: Cloudlet 32 received
3.1980000000000004: Broker: Cloudlet 10 received
3.1980000000000004: Broker: Cloudlet 22 received
3.1980000000000004: Broker: Cloudlet 34 received
3.1980000000000004: Broker: Cloudlet 9 received
3.1980000000000004: Broker: Cloudlet 21 received
3.1980000000000004: Broker: Cloudlet 33 received
3.1980000000000004: Broker: Cloudlet 11 received
3.1980000000000004: Broker: Cloudlet 23 received
3.1980000000000004: Broker: Cloudlet 35 received
4.198: Broker: Cloudlet 0 received
4.198: Broker: Cloudlet 12 received
4.198: Broker: Cloudlet 24 received
4.198: Broker: Cloudlet 36 received
4.198: Broker: Cloudlet 1 received
4.198: Broker: Cloudlet 13 received
4.198: Broker: Cloudlet 25 received
4.198: Broker: Cloudlet 37 received
4.198: Broker: Cloudlet 2 received
4.198: Broker: Cloudlet 14 received
4.198: Broker: Cloudlet 26 received
4.198: Broker: Cloudlet 38 received
4.198: Broker: Cloudlet 3 received
4.198: Broker: Cloudlet 15 received
4.198: Broker: Cloudlet 27 received
4.198: Broker: Cloudlet 39 received
4.198: Broker: All Cloudlets executed. Finishing...
4.198: Broker: Destroying VM #0
4.198: Broker: Destroying VM #1
4.198: Broker: Destroying VM #2
4.198: Broker: Destroying VM #3
4.198: Broker: Destroying VM #4
4.198: Broker: Destroying VM #5
4.198: Broker: Destroying VM #6
4.198: Broker: Destroying VM #7
4.198: Broker: Destroying VM #8
4.198: Broker: Destroying VM #9
4.198: Broker: Destroying VM #10
4.198: Broker: Destroying VM #11
Broker is shutting down...
Simulation: No more future events
CloudInformationService: Notify all CloudSim entities for shutting down.
Datacenter_0 is shutting down...
Datacenter_1 is shutting down...
Broker is shutting down...
Simulation completed.
Simulation completed.

========== OUTPUT ==========

Cloudlet ID STATUS Data center ID VM ID Time Start Time Finish
Time
4 SUCCESS 2 4 3 0.2 3.2
16 SUCCESS 2 4 3 0.2 3.2
28 SUCCESS 2 4 3 0.2 3.2
5 SUCCESS 2 5 3 0.2 3.2
17 SUCCESS 2 5 3 0.2 3.2
29 SUCCESS 2 5 3 0.2 3.2
6 SUCCESS 3 6 3 0.2 3.2
18 SUCCESS 3 6 3 0.2 3.2
30 SUCCESS 3 6 3 0.2 3.2
7 SUCCESS 3 7 3 0.2 3.2
19 SUCCESS 3 7 3 0.2 3.2
31 SUCCESS 3 7 3 0.2 3.2
8 SUCCESS 3 8 3 0.2 3.2
20 SUCCESS 3 8 3 0.2 3.2
32 SUCCESS 3 8 3 0.2 3.2
10 SUCCESS 3 10 3 0.2 3.2
22 SUCCESS 3 10 3 0.2 3.2
34 SUCCESS 3 10 3 0.2 3.2
9 SUCCESS 3 9 3 0.2 3.2
21 SUCCESS 3 9 3 0.2 3.2
33 SUCCESS 3 9 3 0.2 3.2
11 SUCCESS 3 11 3 0.2 3.2
23 SUCCESS 3 11 3 0.2 3.2
35 SUCCESS 3 11 3 0.2 3.2
0 SUCCESS 2 0 4 0.2 4.2
12 SUCCESS 2 0 4 0.2 4.2
24 SUCCESS 2 0 4 0.2 4.2
36 SUCCESS 2 0 4 0.2 4.2
1 SUCCESS 2 1 4 0.2 4.2
13 SUCCESS 2 1 4 0.2 4.2
25 SUCCESS 2 1 4 0.2 4.2
37 SUCCESS 2 1 4 0.2 4.2
2 SUCCESS 2 2 4 0.2 4.2
14 SUCCESS 2 2 4 0.2 4.2
26 SUCCESS 2 2 4 0.2 4.2
38 SUCCESS 2 2 4 0.2 4.2
3 SUCCESS 2 3 4 0.2 4.2
15 SUCCESS 2 3 4 0.2 4.2
27 SUCCESS 2 3 4 0.2 4.2
39 SUCCESS 2 3 4 0.2 4.2
Dynamic task scheduling simulation is complete!