Cloud Computing & CloudSim

PRESENTED BY :-
SWATI KUMARI (18075060)
VIKRANT KUMAR (18075063)
 CONTENTS
●
Introduction to Cloud Computing
●
What is CloudSim?
●
Advantages of CloudSim
●
CloudSim Architecture
●
CloudSim Class Design
●
CloudSim Class
●
Installation of CloudSim
 CLOUD COMPUTING

●
Cloud computing can be defined as ‘a type of parallel and distributed
system .
●
It consists of collection of inter-connected and virtualized computers
that are dynamically provisioned , and presented as one or more
unified computing resources .
●
It is based on service-level agreements established through
negotiation between the service provider and consumers .
●
It implements services in a pay as-you-go model to consumers.
 CloudSim
●
Services based Model :-
- Infrastructure as Service (IaaS)
- Platform as Service (PaaS)
- Software as Service (SaaS)
●
Cloud Deployment Model :-
- public clouds

- private clouds
- hybrid clouds
- community clouds
 CloudSim

●
CloudSim is a framework for modeling and simulation of cloud
computing infrastructures and services .

●
By using CloudSim, developers can focus on specific systems
design issues that they want to investigate, without getting
concerned about details related to cloud-based infrastructures
and services.

●
CloudSim is completely written in java .
 Need of CloudSIm

●
The application services hosted under Cloud computing model
have complex provisioning, composition, configuration, and
deployment requirements.

●
Evaluating the performance of Cloud provisioning policies,
application workload models, and resources performance
models in a repeatable manner under varying system and user
configurations and requirements is difficult to achieve.
 Advantages of CloudSim :-
●
The CloudSim toolkit supports both system and behavior modeling of
Cloud system components such as data centers, virtual machines
(VMs) and resource provisioning policies.

●
It implements generic application provisioning techniques that can be
extended with ease and limited effort.

●
it supports modeling and simulation of Cloud computing environments
consisting of both single and inter-networked clouds (federation of
clouds).
 CLOUDSIM
ARCHITECTURE
 USER CODE LAYER

●
It exposes basic entities for hosts (number of
machines, their specification, and so on), applications
(number of tasks and their requirements), VMs,
number of users and their application types, and
broker scheduling policies.
 USER CODE LAYER

Developer can :-
●
Generate a mix of workload request distributions,
application configurations
●
model Cloud availability scenarios and perform robust
tests based on the custom configurations
●
implement custom application provisioning techniques
for clouds and their federation.
 User Interface Structure

●
Cloudlet: This class models the cloud based application services
(such as content delivery, social networking & business workflow).
●
VM : This class models a virtual machine, which is managed & hosted
by cloud host component.
 VM Services :-

●
Cloudlet Execution : Used to support modelling of
other performance and composition metrics for
application such as transactions in data-base oriented
applications.
●
VM Management: The VM management stands for the
operations control policied related to VM cycle such as
provisioning a host to VM,VM creation & VM Migration.
 Cloud Services : -

●
VM Provisioning: The process of creating VM
instances on hosts.
●
CPU allocation : CPU is allocated to each of the
services.
●
Memory allocation
●
Storage allocation
●
Bandwidth allocation
 Cloud Services : -

●
VM Provisioning: The process of creating VM instances on
hosts.
●
CPU allocation : CPU is allocated to each of the services.
●
Memory allocation
●
Storage allocation
●
Bandwidth allocation
 Cloud Resources:

●
Events Handling:This is an abstract class that represents the
provisioning policy for allocating primary memory (RAM) to the
Vms.
●
Cloud Coordinator: This abstract class extends a Cloud-based
data centre to the federation .
●
Sensor : This interface must be implemented to instantiate a
sensor component that can be used by a cloud coordinator for
monitoring specific performance parameters.
●
Data centre : This class models the core infrastructure-level
services (hardware) that are offered by Cloud
providers(Amazon,Azure,App Engine).
 Network

●
Network Topology: This class contains the information for
inducing network behaviour (latencies) in the simulation. It
sotres the topology information, which is generated using the
BRITE topology generator.
●
Message delay calculation: This class contains the algorithms
that claculate the delay in the delivery of the message.
CloudSim class Design
 CloudSim class
●
BwProvisioner: This is an abstract class that models the policy for
provisioning of bandwidth to VMs. The main role of this component is
to undertake the allocation of network bandwidths to a set of
competing VMs that are deployed across the data center.
●
CloudCoordinator: This abstract class extends a Cloud-based data
center to the federation. It is responsible for periodically monitoring
the internal state of data center resources and based on that it
undertakes dynamic load-shredding decisions.

●
Cloudlet: This class models the Cloud-based application services
(such as content delivery, social networking, and business workflow).
 CloudSim Class

●
CloudletScheduler: This abstract class is extended by the
implementation of different policies that determine the share of
processing power among Cloudlets in a VM.
- space-shared (CloudetSchedulerSpaceShared)
- time-shared (CloudletSchedulerTimeShared)
●
Datacenter: This class models the core infrastructure-level services
(hardware) that are offered by Cloud providers (Amazon, Azure, App
Engine).
●
DatacenterBroker or Cloud Broker: This class models a broker, which
is responsible for mediating negotiations between SaaS and Cloud
providers; and such negotiations are driven by QoS requirements.
 CloudSim Class

●
DatacenterCharacteristics: This class contains configuration
information of data center resources.
●
Host: This class models a physical resource such as a compute
or storage server.
●
NetworkTopology: This class contains the information for
inducing network behavior (latencies) in the simulation. It stores
the topology information, which is generated using the BRITE
topology generator.
●
RamProvisioner: This is an abstract class that represents the
provisioning policy for allocating primary memory (RAM) to the
VMs.
 CloudSim Class
●
Sensor: This interface must be implemented to instantiate a
sensor component that can be used by a CloudCoordinator for
monitoring specific performance parameters.
●
Vm: This class models a VM, which is managed and hosted by
a Cloud host component.
●
VmmAllocationPolicy: This abstract class represents a
provisioning policy that a VM Monitor utilizes for allocating VMs
to hosts.
●
VmScheduler: This is an abstract class implemented by a Host
component that models the policies (space-shared, time-
shared) required for allocating processor cores to VMs.