July 2005 - ogsa-rss-bof

Strawmen...
by Donal K. Fellows 01 Aug '05

01 Aug '05

Hi all... Thinking about the upcoming F2F meeting, we're going to need some strawmen for people to poke fun at. Here's my first go (everything will need XML serialization, of course): CSG has one official operation: GetCandidates(JobDefinition[] atomicJobs) -> Candidate[] Each Candidate is a structure containing: EndpointReference eprOfBESToSubmitThisJobTo JobDefinition configuredAtomicJob ValuationTerm[] descriptionsOfQoSPriceEtc We permit multiple jobs in the request because this is useful in a setting where a CSG is defined hierarchically in terms of other CSGs (a good way of building a wider Grid in my experience). Any scheduling or reservation terms are done by writing extra things into the JobDefinition elements. JSDL is flexible enough for this. EPS needs at least this operation: PlanExecution(JobDefinition atomicJob, SelectionPolicy selector) -> ExecutionPlan I don't know what the SelectionPolicy will look like, but basing it off of Condor ClassAd selection rules might be a good start. The ExecutionPlan is a structure containing at least: EndpointReference eprOfBESToSubmitThisJobTo JobDefinition actualAtomicJobToSubmit ValuationTerm[] descriptionOfQoSPriceEtc (i.e. the contents of the Candidate) but I know more things will be needed to make this really work. The EPS will ask relevant CSG(s) for the candidates for the job submitted, and will then evaluate the policy to pick the best place to submit the job to. The EPS will not submit the job. The EPS *will* secure any reservations/holds required to carry out the selected candidate. However, an EPS really only becomes interesting when we move away from looking at single jobs; it's within the context of a workflow that having a service instead of doing it all by hand makes real sense. At least in my opinion. And I don't think we want to develop a workflow in this group! OK, that's my thoughts for now. Any opinions? Donal.

2 1

Regrets -- week of July 25-29
by Fred Maciel 23 Jul '05

23 Jul '05

Hi, On the week of July 25-29 I'll be in the SNIA/DMTF Technical Symposium. Regards, Fred Maciel Hitachi America R&D

1 0

Charter submitted
by Mathias Dalheimer 21 Jul '05

21 Jul '05

Hi! I just send our charter draft to Bill and Stephen, asking for GFSG approval. Thank you for all your input. Cheers, Mathias

2 1

Charter BoF report
by Mathias Dalheimer 20 Jul '05

20 Jul '05

Hi all, I just created the charter BoF report and would like to ask you to have a look at it. In addition, I edited the charter according to the comments we received. You find both files attached. Thanks, Mathias

4 14

OGSA RM teleconference -- where does resource modeling fits in?
by Fred Maciel 18 Jul '05

18 Jul '05

Hi, First of all, sorry for the cross-posting -- this subject involves all three WGs. Since GGF14 there have been a lot of discussions on where resource modeling fits -- BES considered it out of scope but Andrew thinks it's not totally out; RSS is discussing whether it's in scope; and this was discussed in the OGSA-WG also. So, let's discuss this in the Resource Modeling design team teleconference (which is, in fact, the place to discuss this). Oh, yes, part of this was supposed to be discussed in the RM teleconference this week, but only I and Ellen could come... Here are the details: Date: Tuesday, July 19th, at the following times: - 11:00-12:00 US Pacific (GMT - 7) - 12:00-13:00 US Mountain (GMT - 6) - 13:00-14:00 US Central (GMT - 5) - 14:00-15:00 US Eastern (GMT - 4) - 18:00-19:00 GMT - 19:00-20:00 UK (GMT + 1) - 20:00-21:00 Central Europe (GMT + 2) - 03:00-04:00 Japan (GMT + 9, following day) -- sorry. Dial-in: Toll Free: (888) 422-7120 Int'l Access: (608) 250-0194 Participant code: 693305 If screen sharing is needed, let's use Glance: URL: http://ogsa.glance.net Session key: 0719 Explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html See you there, Fred Maciel Hitachi America R&D

3 2

Resource Model Discussion during OGSA telecon
by Mathias Dalheimer 13 Jul '05

13 Jul '05

Hi! I just read the protocol of last nights OGSA-telecon: " * Resource model and BES discussion - It is unclear how or where the resource modelling work should continue now that BES has put it out of scope. - One option is to do this work in the context of RSS or perhaps even spawn a new group dedicated to resource modelling. The coordination problem is not insignificant, however. It is not yet clear how to proceed with this work. - BES put this work out of scope on the assumption that selection is over by the time a request reaches the BES container. (Also due to the fear that if the resource modelling work was taken on then it would cause the overall BES work to stall.) - Since RSS deals with resource selection it is probably a better (right?) place to do this modelling effort. - There is a concern that leaving this modelling work for later may cause rework of specs. This is not intended to stop ongoing work until the resource modelling is finished but to make sure people are aware of the risk. - BES is not doing modelling so the problem may not be that big - RSS would have to tackle this work---so it is probably going to be tackled relatively soon The consensus is that this topic needs more discussion. - Agreed that interested parties should discuss this offline, followed by discussing it on the BES call this week, followed by discussing it again in the OGSA call next Monday. - This activity is part of the coordination between OGSA & OGSA-BES WG " I think this is an very important discussion. In Chicago, we decided that the defintion of an information system is out of scope, but what about the underlying resource model? Basically, we need to identify which resource is capable of executing a job described in JSDL (Candidate Set Generator) and which resource to choose from this set (Execution Planning Service). While the first part is rather easy to answer (we need all the attributes used in the JSDL), the second part seems to be a kind of Pandora's box: The attributes vary greatly with the implementation of the scheduler. While something like load or queue length of the resource seems to be common, we can also have "network utilization", "existing reservations", "availability between 2 and 3 p.m. tomorrow"... In addition, the OGSA Information System session in Chicago revealed some other aspects: What about information necessary to manage resource (e.g. uptime, status, admin contact, ...) There are existing models like CIM which has been investigated by Fred Maciel. The design of an information system has been investigated by Abdeslem Djaoui. This seems to be a lot of work. So before making a statement on the OGSA mailing list, I would like to collect some opinions. What do you think about the resource model? Should we deal with it? Is it out of scope? Do we have the knowledge to deal with it? Can we - if it is out of scope - provide input to another team? Cheers, Mathias

3 2

OGSA-WG and fellow WG August '05 F2F Survey
by Hiro Kishimoto 12 Jul '05

12 Jul '05

Hi all, OGSA-WG and fellow WGs are planning to have August '05 F2F meeting. A schedule in week of August 29 at San Diego was proposed at GGF14. However, I got several requests for another date (week of August 15) and/or city (SF bay area). Thus I took action item to ask all expected attendees for their availability for F2F meeting. Please take the time to fill in the following online survey by this Friday (July 8) or at latest next Monday (July 11). We will decide date and city early next week. Post the survey on a Web site - use this URL: http://www.zoomerang.com/survey.zgi?p=WEB224GECBLCHX Thanks, -- Hiro Kishimoto

1 2