gridsim-developers — GridSim DevelopersFor contributing to GridSim or questions related to the existi

[GridSim-developers] contribution

[mansoor h. <muz...@ya...>]

dear sir,
   im interedted n designing of new scheduling
algorithm in gridsim so please suggest me to implement
various scheduling algorithm.


yours,
mansoor


      Why delete messages? Unlimited storage is just a click away. Go to http://help.yahoo.com/l/in/yahoo/mail/yahoomail/tools/tools-08.html

Re: [GridSim-developers] A couple of questions regarding GridSim

[Anthony S. <an...@cs...>]

> 1. The "ResourceCharacteristics" class defines only the 'static'
> information of a GridResource.

correct

> Except Resource Failure, there's currently no support for
> dynamic loading, e.g. current CPU usage, current available memory,
> current available disk space, current queue length at a GridResource

this one should be the responsible of the resource scheduler since
it has a better information about these stats.
Or the resource scheduler should pass relevant info to another
object for stats.


> 2. A "GridInformationService" is not a GridResource. This means the
> registration and maintenance of monitoring information is cost-free.

correct, but you can create your own GIS that charge for registration
free, etc


> 3. Upon the creation of a GridResource, the GridResource registers
> itself to a RegionalGIS or (the default) System GIS. This registration
> is "once for all" - no further maintenance is needed, for example the
> GIS ask the resource 'are you still there?'.

correct, all registrations are done in the beginning, except for
the resource failure case. However, this is all done internally
by the GridResource class so users do not need to worry
(in case of a failure).


> 4. A GridSim simulation starts by calling GridSim.startGridSimulation().
> But how is the termination of a GridSim simulation defined and managed?
> I guess by finishing all GridLet entities?

no, check the example code carefully:

 	// signal the end of a simulation for this user entity
 	super.finishSimulation();

The above method is from the GridSimCore class.
Once ALL users send this event, the GridSimShutdown class will
notify all entities. That's why when you initialize GridSim,
you need to provide the correct num of users.

 	GridSim#init(int numUser, Calendar cal, boolean traceFlag)


Once Gridlets are done, then of course you can set the user
to do other things, not just exiting.


> Can a simulation keep running for a user-defined period of time, say 10
> minutes, to observe what's going on even most of the entities are idle?

yes, just send an internal event to itself.
This is just a rough guide: 
See the res failure example in GridUserFailureEx01#body()

 	// sends a reminder to itself
 	super.send(super.get_id(), init_time, SUBMIT_GRIDLET);

You can set init_time = 10*60;  // in seconds
Then have a while loop to wait for this event with the same
tag name, i.e. "SUBMIT_GRIDLET":


while (Sim_system.running())
{
     Sim_event ev = new Sim_event();
     super.sim_get_next(ev); // get the next event in the queue

     switch (ev.get_tag())
     {
         // submit a gridlet
         case SUBMIT_GRIDLET:
             ... // your code
             break;

        ... // other event name
     }
}



> 5. How to calculate the current bandwidth of a network link, and the
> network throughput of a resource?

just send a ping message to the resource:
     GridSimCore#pingBlockingCall(String entityName, int size)
     or
     GridSimCore#ping(String entityName, int size)

The InfoPacket class stores the latest information about network 
condition.


anthony

[GridSim-developers] A couple of questions regarding GridSim

[Shuo Y. <ya...@cs...>]

Dear All,

I'm Shuo Yang, a.k.a Alex, a PhD student in University of Manchester.
I'm studying GridSim with the purpose to extend it to support dynamic
loading and topology adaptation for Grid Information Service. So far, I
find the GridSim source code and tutorials are really clearly documented
and straightforward. The overall architecture is also fantastic.

I have a couple of questions regarding the functions in GridSim. So I'm
sending this email to check my understanding and discuss with you.
Please correct me if I'm wrong. 

1. The "ResourceCharacteristics" class defines only the 'static'
information of a GridResource. For a given GridResource, the
ResourceCharacteristics will stay unchanged during the life time of the
GridResource. Except Resource Failure, there's currently no support for
dynamic loading, e.g. current CPU usage, current available memory,
current available disk space, current queue length at a GridResource
etc.

2. A "GridInformationService" is not a GridResource. This means the
registration and maintenance of monitoring information is cost-free. 

3. Upon the creation of a GridResource, the GridResource registers
itself to a RegionalGIS or (the default) System GIS. This registration
is "once for all" - no further maintenance is needed, for example the
GIS ask the resource 'are you still there?'.

4. A GridSim simulation starts by calling GridSim.startGridSimulation().
But how is the termination of a GridSim simulation defined and managed?
I guess by finishing all GridLet entities?

Can a simulation keep running for a user-defined period of time, say 10
minutes, to observe what's going on even most of the entities are idle?

5. How to calculate the current bandwidth of a network link, and the
network throughput of a resource?


Many thanks in advance,

Alex Yang
School of Computer Science,
University of Manchester

Re: [GridSim-developers] Problems with Gridlet cancellation and some questions

[Marcos D. de A. <ma...@cs...>]

Hi Anthony,

thanks for your email. I just want to understand to check if I am not
doing anything wrong by ignoring the conversions.

> For example, the resource is in UTC+10 and the user is in UTC+5
> and init time is 05:00:00 (UTC+0) for simplicity.
> At the start of simulation, resource time is 15:00:00 and
> user time is 00:00:00

> If the user submits at GridSim.clock() = 1 hour and
> NO time zone conversion, then the resource thinks
> the current time is 01:00:00, i.e. user init time + GridSim.clock(),
> which is already expired. This is because the ARObject only stores
> the user current time and the user has no idea about
> the resource time zone is.

I do agree that in a real distributed application the time zones have
to be handled. However, in the simulation, the user will make a
reservation request relative to the simulation clock (in seconds). The
provider will abide to the same clock to check whether it accepts or
rejects the request (in seconds). If a user requests 5 PEs at
simulation time 60 sec. for 1 hour, then the provider will check if
there are 5 PEs available at simulation time 60 sec. for one hour. The
ARObject may handle the times as doubles reflecting the simulation
clock. I do not see the need for time zone here.

However, let's suppose that the provider has a policy that states that
resources may not be reserved on Mondays. The provider has information
in which time zone it is. In this case I see the need for converting
the 60 sec. simulation time to the provider's time zone to check
whether it is a Monday or not. Apart from cases like this one, I do
not see a clear reason for using relative times. I may be wrong.

Regards,

Marcos


-- 
Marcos Dias de Assuncao
Grid Computing and Distributed Systems (GRIDS) Laboratory
Department of Computer Science and Software Engineering
The University of Melbourne, Australia
Email: ma...@cs...

Re: [GridSim-developers] Problems with Gridlet cancellation and some questions

[Anthony S. <an...@cs...>]

> For example, the resource is in UTC+10 and the user is in UTC+5


oops, the user time zone should be UTC -5.


anthony

Re: [GridSim-developers] Problems with Gridlet cancellation and some questions

[Anthony S. <an...@cs...>]

> However, I still do not understand why all those conversions are
> needed since in the end everything is related to the simulation clock.

true that everything is related to the simulation clock,
but the time zone does matter !

For example, the resource is in UTC+10 and the user is in UTC+5
and init time is 05:00:00 (UTC+0) for simplicity.
At the start of simulation, resource time is 15:00:00 and
user time is 00:00:00

If the user submits at GridSim.clock() = 1 hour and
NO time zone conversion, then the resource thinks
the current time is 01:00:00, i.e. user init time + GridSim.clock(),
which is already expired. This is because the ARObject only stores
the user current time and the user has no idea about
the resource time zone is.


regards,
anthony

Re: [GridSim-developers] Problems with Gridlet cancellation and some questions

[Marcos D. de A. <ma...@cs...>]

Thanks for the prompt reply. I hadn't looked carefully the SpaceShared policy.

Regarding the time zones, the providers having time zones is ok.
However, I still do not understand why all those conversions are
needed since in the end everything is related to the simulation clock.
But never mind that, I will just discard these conversions in my work.

Regards,

Marcos


On 24/09/2007, Anthony Sulistio <an...@cs...> wrote:
>
>
> > It seems that at no point the Gridlet status is changed to CANCELED.
>
> See SpaceShared.java  line 754 or TimeShared.java line 770:
>
> // if a Gridlet is finished upon cancelling, then set it to success
> // instead.
> if (rgl.getRemainingGridletLength() == 0.0) {
>      rgl.setGridletStatus(Gridlet.SUCCESS);
> }
> else {
>      rgl.setGridletStatus(Gridlet.CANCELED);
> }
>
>
> See the output from Example7 of Test Case 8.
> It shows Gridlet #2 has been cancelled.
>
>
> ============= OUTPUT for User_1 ==========
> Gridlet ID    STATUS    Resource ID    Cost
>      2        Canceled        11        435.12199999999984
>      0        Success        7        405.0544
>      1        Success        11        1008.9780000000001
>      3        Success        7        1200.0
>
>
> > why do we need time zones particularly in advance reservations?
> > Therefore, why do we need to convert times
> > between time zones?
>
> the time used by the AR scheduler is the absolute time not relative.
> See ARPolicy.java line 4995:
>
> protected long getCurrentTime() {
>      return initTime_ + (int) (GridSim.clock() * MILLI_SEC);
> }
>
> where initTime_ = Calendar.getInstance().getTimeInMillis()
> when you call GridSim.init() method +/- resource time zone.
>
> See AllocPolicy#init() method line 359:
>
>          // looking at the init simulation time
>          Calendar calendar = GridSim.getSimulationCalendar();
>          long simTime = calendar.getTimeInMillis();
>          int simTimeZone = calendar.getTimeZone().getRawOffset() /
>                            AdvanceReservation.HOUR;
>
>          // then convert into the local resource time
>          initTime_ = AdvanceReservation.convertTimeZone( simTime,
>                             simTimeZone,
>                             resource_.getResourceTimeZone() );
>
>
> When you have entities (resources or users) with different time zones,
> then the time will be different.
>
> regards,
>
> anthony
>


-- 
Marcos Dias de Assuncao
Grid Computing and Distributed Systems (GRIDS) Laboratory
Department of Computer Science and Software Engineering
The University of Melbourne, Australia
Email: ma...@cs...

Re: [GridSim-developers] Problems with Gridlet cancellation and some questions

[Anthony S. <an...@cs...>]

> It seems that at no point the Gridlet status is changed to CANCELED.

See SpaceShared.java  line 754 or TimeShared.java line 770:

// if a Gridlet is finished upon cancelling, then set it to success
// instead.
if (rgl.getRemainingGridletLength() == 0.0) {
     rgl.setGridletStatus(Gridlet.SUCCESS);
}
else {
     rgl.setGridletStatus(Gridlet.CANCELED);
}


See the output from Example7 of Test Case 8.
It shows Gridlet #2 has been cancelled.


============= OUTPUT for User_1 ==========
Gridlet ID    STATUS    Resource ID    Cost
     2        Canceled        11        435.12199999999984
     0        Success        7        405.0544
     1        Success        11        1008.9780000000001
     3        Success        7        1200.0


> why do we need time zones particularly in advance reservations?
> Therefore, why do we need to convert times
> between time zones?

the time used by the AR scheduler is the absolute time not relative.
See ARPolicy.java line 4995:

protected long getCurrentTime() {
     return initTime_ + (int) (GridSim.clock() * MILLI_SEC);
}

where initTime_ = Calendar.getInstance().getTimeInMillis()
when you call GridSim.init() method +/- resource time zone.

See AllocPolicy#init() method line 359:

         // looking at the init simulation time
         Calendar calendar = GridSim.getSimulationCalendar();
         long simTime = calendar.getTimeInMillis();
         int simTimeZone = calendar.getTimeZone().getRawOffset() /
                           AdvanceReservation.HOUR;

         // then convert into the local resource time
         initTime_ = AdvanceReservation.convertTimeZone( simTime,
                            simTimeZone,
                            resource_.getResourceTimeZone() );


When you have entities (resources or users) with different time zones,
then the time will be different.

regards,
anthony

[GridSim-developers] Problems with Gridlet cancellation and some questions

[Marcos D. de A. <ma...@cs...>]

Dear All,

Firstly, I would like to know if someone has used the gridlet
cancellation capabilities of GridSim? Secondly, I would like to
mention a few things about the gridletCancel() methods in the
allocation policy classes. It seems that at no point the Gridlet
status is changed to CANCELED. The method sendCancelGridlet() of the
AllocPolicy class contains:

[=85]
long gridletSize =3D 0;
        if (gl !=3D null) {
            gridletSize =3D gl.getGridletOutputSize();
        }
[=85]
super.sim_schedule( outputPort_, GridSimTags.SCHEDULE_NOW, tag,
                            new IO_data(gl, gridletSize, destId) );

Which means that the status of the Gridlet is not changed and that the
gridlet is sent back to the user when cancelled. The number of bytes
transmitted is in fact the size of the output files. That means that
even if the Gridlet is cancelled, it is actually not cancelled and the
number of bytes sent back to the sender is equals to the number of
bytes that would be sent if the Gridlet had been completed.

My questions are regarding the advance reservation features. I know
that GridSim uses a resource calendar and some estimates of local
load. It uses this to get information about days of the week and
respective local load. However, I am wondering and intrigued, why do
we need time zones particularly in advance reservations? If this is a
policy related issue, for example, a resource provider accepts advance
reservations on Mondays? Still, I am not sure whether we need the time
zone information in classes like ARObject. GridSim, as any event
driven simulator uses a simulation clock. All entities schedule events
based on this clock. Therefore, why do we need to convert times
between time zones? I would be grateful if anybody could explain to me
the design decisions that have led to the adoption of time zones in
the advance reservation framework.

Regards,

Marcos


--=20
Marcos Dias de Assuncao
Grid Computing and Distributed Systems (GRIDS) Laboratory
Department of Computer Science and Software Engineering
The University of Melbourne, Australia
Email: ma...@cs...

[GridSim-developers] GridSim Toolkit 4.1 is released

[Anthony S. <an...@cs...>]

Gridbus Project to Release GridSim Toolkit 4.1
September 2007


The Gridbus Project at The University of Melbourne, Australia has released 
the
next-version of Grid simulation software, the GridSim Toolkit 4.1.

The new version of GridSim adds a new functionality that supports
resource failures and failure detection of Grid resources. This work was 
done
in collaboration with Agustin Caminero, a Phd student from
Universidad de Castilla La Mancha (UCLM), Spain.

All components developed as part of the GridSim Toolkit are released as
"open source" under the GPL license to encourage innovation and pass full
freedom to our users. In addition, we have decided to use
SourceForge (http://sourceforge.net/projects/gridsim) for hosting
our future releases and developments. This allows us to share and
and to collaborate further on new functionalities.
Therefore, contributions to the GridSim Toolkit are greatly appreciated.

The early version of our GridSim toolkit has been used/dowloaded by 
several
academic and commercial organizations around the world including:
University of Southern California (USA), California Institute of 
Technology (USA),
Argonne National Labs (USA), University of Manchester (UK), CERN,
Universidad de Santiago de Compostela (Spain), Indian Institute of 
Technology,
Tsinghua University (China), Sun Microsystems, IBM Research, Unisys, HP,
Northrop Grumman Information Technology, British Telecom and EMC Corp.

The GridSim software has been used for modeling and simulating many
interesting systems and ideas. For example, IBM Research uses our DataGrid
package to simulate a grid meta-scheduler that tightly integrates
the compute and data transfer times of each job.
Another example is Universidad de Santiago de Compostela's extension of 
GridSim
to optimize execution of parallel applications on a Grid.
Our own uses include simulating economic Grid scheduler in a competitive
economy model, economic based cluster scheduler and cooperative Grid 
federation.

The contributors to the GridSim software (from early to new version) are:
* Rajkumar Buyya, GRIDS Lab @ The University of Melbourne.
* Manzur Murshed, GSCIT @ Monash University, Australia.
* Anthony Sulistio, GRIDS Lab @ The University of Melbourne.
* Gokul Poduval and Chen-Khong Tham,
Dept. of Electrical & Computer Engineering @ National University of 
Singapore.
* Marcos Dias de Assuncao, GRIDS Lab @ The University of Melbourne.
* Uros Cibej and Borut Robic, Faculty of Computer and Information Service,
The University of Ljubljana, Slovenia.
* Agustin Caminero, Department of Computing Systems,
Universidad de Castilla La Mancha (UCLM), Spain.


To download the GridSim software, please visit the Gridbus Project web 
site at
http://www.gridbus.org/gridsim/

Join the GridSim mailing lists at
http://sourceforge.net/projects/gridsim