August 2006 - ogsa-wg - lists.ogf.org

Proposed agenda for Aug. 21st call
by Hiro Kishimoto 21 Aug '06

21 Aug '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Aug. 21st Monday from 5pm to 7pm (CDT). Sorry for the last minutes posting. The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0821 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Aug. 17th and 19th if available) - https://forge.gridforum.org/sf/go/doc13745?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) OGSA F2F meeting agenda discussion (20 min) Establish F2F agenda on Sep. 14 (Thur) and 15 (Fri) https://forge.gridforum.org/sf/go/wiki1555?nav=1 > Since many Data members > will be leaving on Thursday it would be good to arrange some time > early on Thursday (OGSA F2F). > - Confirmed that a number of people from EMS on the call (Donal, > Andreas) will be at the F2F. > > AI-0817c: Andreas will talk with Hiro about getting a 1-2 hour slot > on Thursday. It is important to know early next week---by > the Monday (8/21) call. 3) OGSA and EGA reference architecture (60 min) Preliminary discussion for GGF18 session. Bob Thome, EGA reference model WG co-chair, will join the call. EGA Reference Model and Use Cases v1.5 http://www.gridalliance.org/en/WorkGroups/ReferenceModel.asp 4) Wrap up (10 min) AOB <*NEXT CALL*> Aug. 24 (Thu): CDDLM joint (Jun, Dejan, and Hiro) Aug. 28 (Mon): Security (Takuya and Frank) Aug. 31 (Thu): EMS scenarios (Andreas and Steven) EMS & Data joint scenario (Allen, Dave Barry, Steven, and Andreas) Sep. 4 (Mon): No call (Labor Day) Sep. 7 (Thu): Roadmap (Chris), GGF18 prep (Tom and Hiro) Telecon schedule: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule/ <*ACTION ITEMS*> > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) AI-0817b: Stephen Davey will do a cut down parameter sweep scenario focusing on the JSDL+BES+Data Transfer/Staging service AI-0817c: Andreas will talk with Hiro about getting a 1-2 hour slot on Thursday. It is important to know early next week---by the Monday (8/21) call. > From Aug. 10 call AI-0810a: Donal to look into the relation of the EPS and CDL (retrieval, update, etc). (Eventually this should probably become a separate scenario.) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. <postponed> - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) (from July 18th F2F, By GGF18 as original discussed.) ---- Hiro Kishimoto

1 0

Teleconference minutes - 17 August 2006
by Andreas Savva 20 Aug '06

20 Aug '06

Attached. https://forge.gridforum.org/sf/go/doc13745?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 17 August 2006 ==================================== * Participants Jay Unger (IBM) Jem Treadwell (HP) Ellen Stokes (IBM) Andreas Savva (Fujitsu) Darren Pulsipher (EMC) Allen Luniewski (IBM) Chris Jordan (SDSC) Donal Fellows (Uom) Michel Drescher (Fujitsu) Stephen Davey (NESC) Dave Berry (NESC) Minutes: Andreas Savva * Summary of Actions AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) AI-0817b: Stephen Davey will do a cut down parameter sweep scenario focusing on the JSDL+BES+Data Transfer/Staging service AI-0817c: Andreas will talk with Hiro about getting a 1-2 hour slot on Thursday. It is important to know early next week---by the Monday (8/21) call. * Aug 10 minutes - not available * Aug 14 minutes - approved with no changes * July F2F minutes - Roadmap - approved with no changes * Review of Actions AI-0803a: Hiro to look into an option for a second EMS/Data call on Sep 7. Tentative; needs confirmation with likely participants. - Agreed to schedule this for Aug.31, preferably in the second part of the call. - Data will provide updates (if any) from their F2F at the end of August. AI-0803c: Ellen to book the IBM facility on Thursday afternoon - Done. - Andreas and Hiro to revise the EMS scenario document (i.e. examples) so that proposal 2 is fulfilled + Andreas will merge Hiro's updates into the next draft - Done - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) (from July 18th F2F, postpone until Aug. 17) - By GGF18 as original discussed. * OGSA Information Model and Data Ellen gave an overview of the Information Model work. - Slide 6 shows a middle abstract model. But it might be the case that different abstract model might be necessary for different purposes. One example in Data is where the information for discovery may be different than that for scheduling. - Implementation could be a (set of) XML document(s) or a database. And XQuery is supported by DBs as alternative to ODBC etc - Slide 11 shows a symmetric model. Expressing and matching between resource requirements and job capabilities may involve policy---there are many standards that may be applicable but the group has not worked through them yet. - For Data there are a number of open questions around the idea of different models for discovery vs scheduling. What are the interesting properties for Data scheduling? What information is needed for modeling and at what level of abstraction? - Agreed that there needs to be an effort to tackle the scheduling issue between EMS and Data - Data has so far mostly focused on access rather than scheduling. For example, issues with data availability on the network, or performance characteristics are not modeled - What are the necessary abstractions for these? (fast data, available, ...?) - There are a number of groups that should be consulted to get a better idea of current practice (GIN,Globus,etc). The impression is that the state of the art is - a metadata catalog---what is available - a replica catalog---abstract filename to physical location - choice of what to use is up to application AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) - The Data group is also thinking about a file metadata definition (something like the information retrievable from a POSIX stat()) - CIM has existing work on files and Ellen can help out * Common Data/EMS Scenarios Data has a set of scenarios describing services that interact with EMS. For example, the parameter sweep scenario. EMS also has some expectations, for example that a data staging description from a JSDL document will be correctly processed by some data transfer service---even though that service may not be described further. So it would be useful to have a set of common scenarions describing basic common activities, making sure that the overlap is checked and the interaction between Data and EMS services is done consistently. Agreed that a good first candidate scenario is simple job execution with data staging. In particular the combination of JSDL, BES, Data transfer service (DMI based?). AI-0817b: Stephen Davey will do a cut down parameter sweep scenario focusing on the JSDL+BES+Data Transfer/Staging service The aim is to discuss it at least within Data at the Data F2F (Aug 28-30 @Edinburgh) and with EMS at GGF18. Since many Data members will be leaving on Thursday it would be good to arrange some time early on Thursday (OGSA F2F). - Confirmed that a number of people from EMS on the call (Donal, Andreas) will be at the F2F. AI-0817c: Andreas will talk with Hiro about getting a 1-2 hour slot on Thursday. It is important to know early next week---by the Monday (8/21) call.

2 1

Re: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17))
by Subramaniam, Ravi 19 Aug '06

19 Aug '06

Hi Andreas, I think intent and means are clashing in our discussion. I feel that we need to capture decisions and consensus that we reached at meetings. The items are spread into minutes (though not always recorded as a resolution) and other discussions including email. I think these also have two levels like action items. One level is recording the essence in a few lines (whether the topic is on of the domains or procedural like formatting) like we do with AIs and the other is an elaboration where necessary or possible like a document or in case of an AI the work product of that item. It is very likely that a collection of resolution/decisions/observations would lead to a single document elaboration and a resolution may not have any other elaboration. Maybe the disconnect is that I think you are referring to the latter level and I am indicating the need for the former level. (I think both levels are important and have their value propositions) Having the 'summary resolutions' compiled in one location (organised by domain if necessary) allows us to see where we have conflicts and, if as new members join or in course of discussion, we are revisiting earlier resolutions (we may change resolutions but we know that we are changing a previous one and not reinventing). Where we need more clarity on the earlier resolution we may refer to the 'Architectural notes' or other such related document. My experiential perception is that we have revisted a topic many times and have reached the same conclusions. This is subjective (and I may be able to dig up a couple of recent examples). My one cent! Ravi Ravi Subramaniam -----Original Message----- From: Andreas Savva [mailto:andreas.savva@jp.fujitsu.com] Sent: Friday, August 18, 2006 01:39 AM Pacific Standard Time To: Subramaniam, Ravi Cc: Hiro Kishimoto; OGSA-WG ML Subject: Re: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17)) Ravi, I still feel that what you are asking is too fine-grain and would not work in the long run. What is really needed is to document what the approach is on important topics. Taking the 'font' example below it would not be very useful on a general list of resolutions if that list also included stuff on information modeling, execution management, data access, security, etc. Instead if someone thinks a topic is important and they want to maintain a short (or long) document explaining what the group consensus is, and *keep it up-to-date* I would be all for it. I'll just point out that I did set up an "Architecture Notes" forum some time back and we still only have one note there. But it's a very good note and I later used it to write up one subsection in OGSA 1.5. Andreas Subramaniam, Ravi wrote: > Thanks. I am ok with Andreas' rationale too. > > Just a quick clarification though: The "resolution" I was referring to > was not the resolution of the action item but noting any resolutions > that were made/taken in the meeting, for example, if we decided that > "All documents will be in 12 point font". It would be good to record > such resolutions taken (or maybe there is a better word than > 'resolution'). These will likely be around for a while and so the 'year' > may be required here :-). > > Ravi > -- Andreas Savva Fujitsu Laboratories Ltd

2 1

RE: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17))
by Subramaniam, Ravi 19 Aug '06

19 Aug '06

Thanks. I am ok with Andreas' rationale too. Just a quick clarification though: The "resolution" I was referring to was not the resolution of the action item but noting any resolutions that were made/taken in the meeting, for example, if we decided that "All documents will be in 12 point font". It would be good to record such resolutions taken (or maybe there is a better word than 'resolution'). These will likely be around for a while and so the 'year' may be required here :-). Ravi -----Original Message----- From: Hiro Kishimoto [mailto:hiro.kishimoto@jp.fujitsu.com] Sent: Thursday, August 17, 2006 11:42 PM To: Andreas Savva Cc: Subramaniam, Ravi; OGSA-WG ML Subject: Re: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17)) Hi Andreas and Ravi, Andreas's suggestions work for me. Thanks, ---- Hiro Kishimoto Andreas Savva wrote: > Hi Ravi, > > I used 'a-z' at the end instead of a number for contrast. Also I have > yet to see a meeting produce more than 26 actions but if we ever manage > to do it we could always append another letter at the end. :-) > > I thought about putting in the year but chose not to because an action > continuing for that long is either obsolete or it is a project. In > either case it shouldn't stay on this list! In other words, this list in > intended for short, one-off actions that don't need much tracking but > which we don't want to forget between meetings. > > If the result of an action is to start a document then the action is > closed and we track issues relating to that document more formally in > that document's tracker. It's not the intention here to re-invent trackers. > > Until now this list lived at the bottom of the minutes and stuff got > deleted once closed, with some explanation in the minutes. I think we > could have a heading (I like RS :-) but 'Done' would also be good) at > the end of the wiki page and move closed/resolved items under it with a > link to the relevant minutes; much like what Hiro does with the > teleconference schedule wiki page. > > Andreas > > Subramaniam, Ravi wrote: >> Hi Andreas, >> >> A small suggestion, if I may - would it make sense to augment the AI >> numbering from AI-mmdd'a-z' to AI-yymmdd-'number'. I think we need to >> think in terms of clarity since we can have AIs that span years >> especially near the end of the year. Also a - z means 26; could we not >> have more? :-). >> >> Since this trend has been started, could you also introduce RS (not Ravi >> Subramaniam :-) or RT for 'resolutions or resolution taken'. >> >> Ravi >> >> -----Original Message----- >> From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of >> Andreas Savva >> Sent: Tuesday, August 15, 2006 11:31 PM >> To: 'OGSA-WG ML' >> Subject: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference >> (August 17)) >> >> Donal's email motivated me to put the existing action list on the wiki. >> (This might make it easier to refer to and for other people--besides >> Hiro--to maintain.) >> >> https://forge.gridforum.org/sf/wiki/do/viewPage/projects.ogsa-wg/wiki/Ac >> tionItems >> or >> http://tinyurl.com/pzqs2 >> >> (This wiki page is not intended to replace trackers! Trackers record >> issues on documents.) >> >>> I seem to recall that there was an action item (on me) from the August >>> 10 telecon relating to review and updating of the EMS scenario >> document. >>> It's important that we don't lose track of these things... >>> >>> Donal. >>> >

3 2

RE: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17))
by Subramaniam, Ravi 18 Aug '06

18 Aug '06

Hi Andreas, A small suggestion, if I may - would it make sense to augment the AI numbering from AI-mmdd'a-z' to AI-yymmdd-'number'. I think we need to think in terms of clarity since we can have AIs that span years especially near the end of the year. Also a - z means 26; could we not have more? :-). Since this trend has been started, could you also introduce RS (not Ravi Subramaniam :-) or RT for 'resolutions or resolution taken'. Ravi -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Andreas Savva Sent: Tuesday, August 15, 2006 11:31 PM To: 'OGSA-WG ML' Subject: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17)) Donal's email motivated me to put the existing action list on the wiki. (This might make it easier to refer to and for other people--besides Hiro--to maintain.) https://forge.gridforum.org/sf/wiki/do/viewPage/projects.ogsa-wg/wiki/Ac tionItems or http://tinyurl.com/pzqs2 (This wiki page is not intended to replace trackers! Trackers record issues on documents.) > > I seem to recall that there was an action item (on me) from the August > 10 telecon relating to review and updating of the EMS scenario document. > It's important that we don't lose track of these things... > > Donal. > -- Andreas Savva Fujitsu Laboratories Ltd

3 2

Aug 16 Roadmap call minutes uploaded
by Christopher Jordan 17 Aug '06

17 Aug '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've uploaded the minutes of the August 16th OGSA Roadmap Editors call to GridForge, in the telecon minutes folder: https://forge.gridforum.org/sf/go/doc13744?nav=1 The next meeting will be August 30th. Enjoy. Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "Mother, I feel so far away from everything." - The Enigma of Kaspar Hauser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFE5La9PCVtcXn6kg8RAm7TAJ4mO5bX29ZeGzIxwluYJFjid3L3zgCfVPw2 VrJP7f27HBU9RZoqaA1y6n0= =f2xs -----END PGP SIGNATURE-----

1 0

OGSA Teleconference (August 17)
by Andreas Savva 17 Aug '06

17 Aug '06

Following is the proposed agenda for OGSA-WG teleconference on Aug. 17th Thursday from 8:30am - 10:30am (CDT). Dial-in numbers for Thursday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0817 More explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (15 min) Note taker assignment Roll call Telecon minutes approval (Aug. 10th) (If available) Telecon minutes approval (Aug. 14th) http://forge.gridforum.org/sf/go/doc13739?nav=1 OGSA-15 F2F minutes (Roadmap) http://forge.gridforum.org/sf/go/doc13734?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) OGSA Information Model & Data Model discussion (50 min) (Ellen and Fred) Overview of Information Model decisions from OGSA-15 F2F (July). Material to be used in the call: - OGSA Information Model & Data Model: https://forge.gridforum.org/sf/go/doc13738?nav=1 - Information Modeling in OGSA Architecture Paper https://forge.gridforum.org/sf/go/doc13726?nav=1 3) Common EMS and Data scenarios discussion (50 min) (Dave/Allen and Steven/Andreas) > There is a pretty clear need for EMS to be tied into Data. The key > to making this happen is to have one or more scenarios that both > EMS and Data agree to and are taking actions to ensure that their > respective work satisfies those scenarios. > > EMS and Data [should] discuss scenarios and come to agreement on a > plan to first create one or more joint scenarios and, two, to > coordinate activities to ensure that our mutual work satisfies > those scenarios in a compatible manner. 4) Wrap up (5 min) AOB <*NEXT CALL*> Aug. 21 (Mon): Joint EGA call Aug. 24 (Thu): CDDLM joint (Jun, Dejan, and Hiro) Aug. 28 (Mon): Security (Takuya and Frank) Aug. 31 (Thu): EMS scenarios (Andreas and Steven) Sep. 4 (Mon): No call (Labor Day) Sep. 7 (Thu): Roadmap (Chris), GGF18 prep (Tom and Hiro) Telecon schedule: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule/ <*ACTION ITEMS*> AI-0803a: Hiro to look into an option for a second EMS/Data call on Sep 7. Tentative; needs confirmation with likely participants. AI-0803c: Ellen to book the IBM facility on Thursday afternoon AI-0803d: Hiro to divide GGF18 B2B F2F survey into three periods: Thursday afternoon, Friday morning and afternoon. AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - Andreas and Hiro to revise the EMS scenario document (i.e. examples) so that proposal 2 is fulfilled + Andreas will merge Hiro's updates into the next draft - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. <postponed> - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) (from July 18th F2F, postpone until Aug. 17)

3 5

Roadmap Editors' call, 8/16
by Christopher Jordan 16 Aug '06

16 Aug '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Please join us for the next OGSA Roadmap document conference call, Wednesday, August 16th, 3PM PDT/6PM EDT/ 7AM, 8/17 Tokyo time. To Join Audio Conference Primary Dial-In: 1 (877) 213-2541 Alternate Dial-In: 1 (630) 424-7813 Passcode: 9737458# Meeting Agenda: 1. Preliminary business Agenda bashing Previous minutes approval 2. Review of changes to section 1 by Chris Jordan 3. Report from Dona on document status updates received 4. Discussion of use of Wiki page for textual document description drafts, discussion of maintenance of textual document description responsibilities 5. Revisitation of the question of how to deal with published documents 6. Review of schedule for Roadmap release, cut-off dates for status updates 7. AOB - I'm sure I had one or two other things to discuss, but it's late, so I reserve the right to remember them tomorrow. Thanks. Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "Mother, I feel so far away from everything." - The Enigma of Kaspar Hauser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFE4uLQPCVtcXn6kg8RArngAKDO3ngNXsEA43v04t/zZs1RPQ/QIQCg5CwT lWYFcidpfhFa9E6f6aZlz28= =+g/r -----END PGP SIGNATURE-----

1 0

Teleconference minutes - 14 August 2006
by Andreas Savva 16 Aug '06

16 Aug '06

Minutes attached. This was a Roadmap call. https://forge.gridforum.org/sf/go/doc13739?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 14 August 2006 ==================================== * Participants Mike Behrens (R2AD, LLC) Chris Jordan (SDSC) Andreas Savva (Fujitsu) Ellen Stokes (IBM) Jem Treadwell (HP) Minutes: Andreas Savva * No minutes approved - August 10 minutes not available * Next call - Information Modeling and Common EMS/Data scenarios are the main topics. - Ellen will review decisions and if there are questions will also give more details about other options considered. - Ellen will upload material to gridforge today. - Andreas will include links to Ellen's material in the agenda. - Chris will forward the agenda to the GFS list and also remind Dave Berry about the common scenarios discussion * OGSA Roadmap review - Chris has uploaded an edited version of the Roadmap document. Edits mainly to bring it up to date and to make it less dependent on developments relating to other specifications. - Also added information modeling documents; deleted obsolete entries, etc; - Consensus that these are good edits. - Is the Information Modeling document intended to be normative or not? - If it is intended to summarize what is described normatively in other documents then it should be non-normative. - Ellen's main concern is with making sure it can be implemented and can also be used by other bodies. In that sense a normative document may be better. - Agreed to revisit the issue of document type in a larger group; it is not critical at this point. - It is not necessary to capitalize "Service Oriented Architecture" - Is it important to change "Global Grid Forum" to "Open Grid Forum"? - Agreed to leave it for later; guidelines on what to do (e.g., copyright notices should say available soon). - Delete "Informational Profile" section? - Agreed to leave as is since this is a category defined in the Profile Definition. - Chapter 7 - Liaisons - needs updating - Review and confirm assignments; is all the work listed here still current? - Ellen will provide some updated material to Chris. - Update EGA connection; what happens to the EGA TCs and what is the relation of that work with OGSA? - There is call scheduled with some members of the EGA TC (reference model) next week and this question could be raised there. - SCRM description also needs update. The best person to talk is Hiro. - Chapter 8: Also need to contact the open source projects again and confirm that the paragraphs describing their activities are accurate. - Mike will contact Keisuke Fukui and update the ACS entry. - Why is the WSRF BP listed in the Appendix on the wiki? - It was one of Hiro's suggestions but it is not clear (nobody could recall) what the main motivation for this was. It was not just that the document was published already. - How should already published documents with ongoing revisions be treated? - One idea is to include the published version in the table of each document section together with the work-in-progress. - The official schedule for the Roadmap 1.1 was to submit it for public comment by GGF18. It will likely slip, but the plan is still to submit it to the Editor in September. - There is a bi-weekly call (Wednesdays). Interested people are welcome to join. - How are referenced specification updates handled? Should individual contributors use the spreadsheet? - The spreadsheet is still used. Andrew Wang is working on moving it to a relational db. - Individuals should send updates to Dona / Chris who will update the spreadsheet

2 2

Re: [ogsa-wg] OGSA Exec summary ...
by Hiro Kishimoto 16 Aug '06

16 Aug '06

Thanks Raj, Yes, "allocation" should be added to the list of functions/services including "reservation and deployment." Good catch! However, based on the recent architecture development, OGSA-WG has moved these services under "Execution Management Services" and made "Resource management" as general management framework. See my keynote slides: http://www.ggf.org/GGF17/materials/316/OGSA%20keynote%2020060510.ppt Now I am sure this exec summary needs major update. We will review Ravi's version in the very near future. Thanks, ---- Hiro Kishimoto Rajkumar Buyya wrote: > Hi Hiro: > > Regarding statements in your document: > --------- > • > Resource Management enables the monitoring, reservation, deployment, and > configuration of grid resources according to quality of service > requirements. Grids allow organizations to pool their departmental IT > resources and make them available for efficient and dynamic use across > the organization. > --------- > > "Resource allocation" need to be part of esource Management services. > > How about changing the above statements to following: > --------- > •Resource Management enables the monitoring, allocation, reservation, > deployment, and configuration of grid resources according to quality of > service requirements. Grids allow organizations to pool their > departmental IT resources and make them available for efficient and > dynamic use to meet demands from competing applications across the > organization. > --------- > > Thanks > raj > > Hiro Kishimoto wrote: >> Hi Ravi, >> >> The attached document is "OGSA introduction" we've used for SC04. >> I cannot find the final version but this is very close to the final. >> >> Since it is outdated, you need to update based on our recent >> major development. But I think it is good starting point. >> >> I would very much appreciate if you could bring yours back to >> OGSA-WG in the near future. >> >> Hope it helps, >> ---- >> Hiro Kishimoto >> >> Subramaniam, Ravi wrote: >>> Hi, >>> >>> >>> >>> Do we (or any kind soul willing to share) have an exec/mgmt summary of >>> the OGSA and OGSA architecture (yeah, seems redundant but am using OGSA >>> in the trademarked brand sense) - 2/3 pages? I am thinking of putting >>> one together for some conversations I need to have but in the essence of >>> "laziness" (efficiency/reuse in euphemistic terms) wanted to see if >>> there existed an exemplar that I could use. I am looking for an editable >>> version that I could tailor to my specific purpose (with the fond hope >>> that it is so well written that I could use it "right out of the box"). >>> >>> >>> >>> Thanks! >>> >>> >>> >>> Ravi >>> > >

1 0