GridSim Toolkit 3.1: Modelling and Simulation of Global Grids

1
GridSim Toolkit 3.1 Modelling and Simulation of
Global Grids

• Dr. Rajkumar Buyya

Fellow of Grid
Computing Grid Computing and Distributed Systems
(GRIDS) Lab. Dept. of Computer Science and
Software EngineeringThe University of Melbourne,
Australiawww.gridbus.org/gridsim/
2
Presentation Outline

• Motivation
• System Architecture
• GridSim Entities
• Visual Modeller
• Advanced Reservation
• Summary

3
Performance Evaluation With Large Scenarios

• Varying the number of
• Resources (1 to 100s..1000s..).
• Resource capability.
• Cost (Access Price).
• Users.
• Deadline and Budget.
• Workload.
• Different Time (Peak and Off-Peak).
• We need a repeatable and controllable
  environment.
• Can this be achieved on Real Grid testbed ?

4
Grid Environment

• Dynamic
• Resource and User Properties vary with time.
• Experiment cannot be repeated.
• Resources are distributed and owned by different
  organisations. Heterogeneous users.
• It is hard to create a controllable environment.
• Grid testbed size is limited.
• Also, creating testbed infrastructure is time
  consuming and expensive.
• Hence, grid computing researchers turn to
  modelling and simulation.

5
GridSim Toolkit

• GridSim 1.0 released in Dec. 2001
• GridSim and GridBroker.
• GridSim 2.0 released in Nov. 2002 _at_ SC 2002.
• Improvements in GridSim and GridBroker.
• Add Visual Modeler.
• Few functionalities of GridSim
• Allows modelling of heterogeneous of resources
  users.
• Supports simulation of both static dynamic
  schedulers.
• Simulates applications with different parallel
  models.

6
System Architecture
Application, User, Grid Scenarios Input and
Results
. . .
Application Configuration
Resource Configuration
Visual Modeler
Grid Scenario
Output
Grid Resource Brokers or Schedulers
GridSim Toolkit
Application Modeling
Information Services
Resource Allocation
Statistics
Job Management
Resource Entities
Resource Modeling and Simulation (with Time and
Space shared schedulers)
Clusters
Single CPU
Reservation
SMPs
Load Pattern
Network
Basic Discrete Event Simulation Infrastructure
SimJava
Distributed SimJava
Virtual Machine (Java, cJVM, RMI)
Distributed Resources
PCs
Workstations
Clusters
SMPs
7
GridSim Entities
ShutdownSignal Manager i
Broker i
Internet
User i
Output
Output
Resource j
Scheduler
Application
Job Out Queue
Jobs
Process Queue
Job In Queue
Input
Input
Input
Output
Statistics Recorder i
Report Writer i
Resource List
InformationService
8
GridSim Entities Relationship
GridInformationService
communication
GridSim
GridResource
registration
Broker
ResourceCharacteristics
message passing
9
GridSim Resource Extensibility
GridResource
GridSim
AllocPolicy
AdvanceReservation
. . .
TimeShared
SpaceShared
ARPolicy
. . .
ARSpaceShared
New architecture allows flexibility to add new
scheduling policies for AR and non-AR resources.
10
GridSim Entities Communication Model
11
Time Shared Multitasking and Multiprocessing
Tasks onPEs/CPUs
P1-G2
P1-G1
P3-G2
P1-G3
P2-G3
P2-G2
G3
G2
G3
PE2
G2
PE1
G1
G2
2
6
9
12
16
19
26
22
Time
G1
G1F
G3
G2
G2F
G3F
G1
G1 Gridlet1 Arrives
Gridlet1 (10 MIs)
G1F Gridlet1 Finishes
G2
Gridlet2 (8.5 MIs)
P1-G2 Gridlet2 didnt finish at the 1st
prediction time.
G3
P2-G2 Gridlet2 finishes at the 2nd prediction
time.
Gridlet3 (9.5 MIs)
12
Space Shared Multicomputing
Tasks onPEs/CPUs
P1-G1
P1-G2
P1-G3
G2
G3
PE2
G1
G3
PE1
2
6
9
12
16
19
26
22
Time
G1
G1F
G3
G2
G2F
G3F
G1
G1 Gridlet1 Arrives
Gridlet1 (10 MIs)
G1F Gridlet1 Finishes
G2
Gridlet2 (8.5 MIs)
P1-G2 Gridlet2 finishes as per the 1st
Predication
G3
Gridlet3 (9.5 MIs)
13
Visual Modeler

• Available in GridSim 2.0
• Functionalities
• Create and delete many users and resources.
• Able to save and load the model file (XML
  format).
• Generate Java source code.

14
Main Window of Visual Modeler
15
View User Property Dialog
16
View Resource Property Dialog
17
GridSim with AR capability

• GridSim 3.0 has the framework to handle
• Creation of a new reservation
• Commitment of a new resevation
• Activation of a reservation once it is started
• Modification of an existing reservation
• Cancellation of an existing reservation
• Query of an existing reservation

18
State Transition Diagram for AR
Request
Request Accepted
Request Rejected
Commit Expired
Accepted
Rejected
Commit Accepted
Change Request
Change Specification
Committed
Change Accepted / Rejected
Start Time
Cancellation Request
Cancelled
Active
Finish Time
Termination Request
Completed
Terminated
19
1. Create a New Reservation

• Required information
• Start time
• Duration time or Finish time
• Number of Processing Elements (PEs)
• Designated resource id
• If successful returns booking id
  (resID_reservID) e.g. 8_1 expiry time
• If not successful returns approx. busy time
  interval (1, 5, 15, 30, 45 seconds or minutes)

20
Steps of making a reservation
Receive Request
Create a Request
Send to Resource
Check for conflicts
YES
NO
Generate Reservation Booking ID
Request Result
Add to List
User or Broker
AllocPolicy
21
Finding Empty Slots

• If (reservation list is empty) then accept
  reservation put into the list
• Else
• Find the begin and end interval in the list
• Find the exact slot for a new reservation
• Find empty slot
• Remove redundant reservations
• Calculate total PE used during the interval

22
2. Commit a Reservation

• If a request for reservation has been successful,
  then need to commit or to confirm it before an
  expiry time
• When committing a reservation, need to submit
• Booking ID
• Job or a list of jobs

23
3. Activation of a Reservation

• Once a reservation has committed
• Put the job(s) into a queue list
• Set the timer
• Send event to itself
• Once the time is up
• If PEs are full, then
• Remove unreserved jobs
• Remove reserved jobs that run longer than
  duration
• Look through the queue list and move into
  execution list

24
4. Modification of a Reservation

• Required information
• Start time
• Duration time or Finish time
• Number of Processing Elements (PEs)
• Booking ID
• At the moment, only able to reduce reservation
• Important If modification fails, the original
  reservation must not be lost.

25
5. Cancellation of a Reservation

• Required information
• Booking ID
• Resource ID
• Cancellation issues
• Before a reservation has been committed
• Before a reservation has been activated
• During an active
• After a reservation has been finished

26
6. Query of a Reservation

• Required information
• Booking ID
• Resource ID
• Status
• NOT_STARTED
• ACTIVE
• FINISHED
• CANCELED
• EXPIRED

27
GridSim 3.1 Advanced Networking
28
GrangeNet and Grid Modelling
29
Selected GridSim Users
30
Contributors

• Rajkumar Buyya (Melbourne)
• Manzur Murshed (Monash)
• Anthony Sulistio (Melbourne) - maintainer
• Chee Shin Yeo (Melbourne)
• Chen-Khong Tham (Singapore)
• Gokul Poduval (Singapore)
• A student Slovenia Data Grid

31
Conclusion

• GridSim toolkit is suitable for application
  scheduling simulations in Grid computing
  environment.
• GridSim is available to download
• www.gridbus.org