[ogsa-rss-wg] First hack at slides for F2F

[Soonwook Hwang]

Hi,

I think my confusion with the RS in Donal's picture might comes 
from the terminology which we may want to make clear. In the Mathias's 
previous mail, Mathias explained Calana using the local RS and  central 
RS. I think we shouldn't interchange the local RS and central one because
they plays different roles. The local RS is the one usually sitting
on the local resource like the Calana use-case, directly interacting
with the local resource management system (e.g., maui, PBSPro) to
commit the reservation. Apparently, the local RS should provide an
interface with operations like "make reservation" for committing 
reservation to local resource management system and "cancel reservation" 
for aborting the reservation are already made. It could be that maybe the
some advanced service container could act as the local RS by providing 
such a reservation interface as well as the BES interface.

If the RS in Donal's picture means the local RS, then I think
I am okay with that even if I am still a little bit problem 
with mapping the Calana architecture onto the Donal's picture
because I think I understand what Donal means with the 
interaction between CSG and RS and between EPS and RS. :-)  

How about the Central RS? What is the Central RS about? Does the 
RS described in OGSA-EMS architecture (page 25 in the OGSA v1.o spec)
means the local RS or some kind of central RS? Does somebody give
an explanation about the Central RS? What is the major difference 
between the local RS and central one in service description and 
interface?
 
Soonwook
-----Original Message-----
From: Mathias Dalheimer [mailto:dalheimer at itwm.fhg.de] 
Sent: Friday, August 12, 2005 12:10 AM
To: Donal K. Fellows
Cc: Soonwook Hwang; ogsa-rss-wg at ggf.org
Subject: Re: [ogsa-rss-wg] First hack at slides for F2F

Donal K. Fellows wrote:
> Soonwook Hwang wrote:
> 
>> The architecture picture looks very nice. I like it very much. 
>> However, the interaction between
>> the CSG and the reservation service makes me a little bit confused. I 
>> guess what you mean by the "CSG gets potential atomic
>> reservation..," is that CSG makes a reservation request to the 
>> Reservation
>> service (RS). The RS will probably interact with service containers (or
>> other reservation service providers closely residing on resources) to
>> make a reservation on the local resources. Would you give an
>> a bit more explanation on the interaction (1)between CSG and RS and 
>> (2) between EPS and RS.  
> 
> 
> The connection between CSG and RS is so that situations like the Calana
> use-case can be incorportated, where candidates have a reservation
> attached. On the other hand, the EPS should do something to deal with
> reservations that aren't associated with a chosen candidate. Probably
> also ought to confirm that a particular reservation *has* been selected.

Well, in Calana you can't really separate the CSG and the EPS: 
Candidates are represented by bids (which have a reservation attached). 
The reservation is then commited for the winning resource, and canceled 
for all other resources. So for Calana, both CSG and EPS would have to 
interact with the RS. I am thinking about dropping reservations 
automatically if they're not commited during a certain period - this 
would minimize the task for the EPS.

-Mathias