- ogsa-wg - lists.ogf.org

Data: start of metadata summary
by Simon Laws 23 Nov '04

23 Nov '04

I've started looking at the metadata stories..... Simon Laws IBM Hursley - Emerging Technology Services

1 0

Data: Proposed agenda for Tuesday Nov 23rd
by Dave Berry 22 Nov '04

22 Nov '04

Dear all, Our next telcon will be November 23rd at the new usual time: 7.00am (PST) / 10.00am EST / 3.00pm (GMT) / 4.00 pm (CET) / Midnight (Japan) UK Dial In: 0845 245 0224 USA Freephone: 1866 838 0046 International Dial In: +44 1452 542309 PIN: 632 065 (Reference 225 4517) 1) Early discussion (5 min) Note taker assignment Roll call Minutes approval - https://forge.gridforum.org/projects/ogsa-wg/document/Minutes_16th_Novem ber_2004/en/1 Agenda bashing 2) Update on outstanding actions (5 min) - Mark to look at next version of GFS document. - Mark to start revising draft document for UVa implementation. - Manuel to see if Mark can get ahold of draft implementations of GFS - People review scenarios for metadata to find errors and mistakes - Simon to describe general pattern and look at metadata people have suggested. - Dave to push on Architecture work if he can. 3) Update on Metadata scenarios (15 min) - Commonalities and issues 4) BasicFiles and Contexts (15 min) - Discussion 5) Plans for strawman architecture (15 min) 6) Wrap up (5 min) AOB DONM Dave Berry Research Manager, National e-Science Centre 15 South College St., Edinburgh Tel: +44 131 6514039

3 2

Agenda: OGSA-EMS (Nov. 22nd, 2004)
by Subramaniam, Ravi 22 Nov '04

22 Nov '04

Hi, Here is the agenda for tommorrow's meeting: Logistics: Date: November 22, 2004 Time: 5 - 7 PM (CST) The dial-in number Free: +1-866-639-4741 Toll: +1-574-935-6703 PIN: 8980700 Screen share service will be provided. URL: http://hiro.glance.net Session key: 1122 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html You can find a minutes of the Oct 11th and 25th call; http://tinyurl.com/5fxfd/minutes-ems-20041011/en/1 http://tinyurl.com/5fxfd/minutes-ems-20041025/en/1 Nov. 8th minutes to be published Agenda: Standing agenda: - Roll call (5 mins) - Agenda Bashing (10 mins) - Ratification of previous minutes (5 minutes) - Topical agenda (90 mins) - Opens and Wrap up (10 mins) Topical agenda: 1. Discuss the Dec OGSA F2F. EMS topics to add on the agenda (20 mins) 2. Focus on - Jobs (definition, semantics, behavior and first stab at interfaces) (30 mins) * Review glossary definitions for accuracy too - Job manager (definition, semantics, behavior and first stab at interfaces) (30 mins) 3. Update EMS standards landscape (from the presentation that Hiro sent out for OGSA) (10 mins) Agenda Bin List (possible agenda topics for future meetings): 1. Additional usecases for consideration 2. Document structure. 3. Structure around how to drive contributions. (pick a few controversial topics like a job). 4. GSA is doing some work with the overlap (Give GSA comments based on how it fits with EMS). 5. What are the standards that apply to EMS (what are the specific pieces of that standard that apply)? Are we to relegate this to the implementer or make decisions in this document? 6. Review Olegario's comments 7. Process for effective progress in this design team. (Earlier we were only 3 active participants and so it was possible to do real time audits on the document. We may need to work more offline especially since there are persons who would like to participate but don't find this time slot convenient) 8. Need to identify the relevant sources for concepts in this area (we may be too restrictive in our prescriptions if we are very narrowly focused). 9. What are the important properties that entities in the EMS space need to adhere too? Are there a standard set of interfaces that all EMS services have to provide? Thanks! Ravi

1 0

May be of interest...
by Savas Parastatidis 18 Nov '04

18 Nov '04

...to the Europeans amongst you. Apologies to the rest. http://research.microsoft.com/ero/CSP/CfProposals.aspx Best regards, -- Savas Parastatidis http://savas.parastatidis.name

1 0

glossary: "manage*" terms
by Hiro Kishimoto 18 Nov '04

18 Nov '04

Hi all, This is a revised version of Bill's definition proposal. OGSA-WG agreed the following definitions at the Today's call. > Here are some words that may (or may not) help with the glossary > discussion on the "manage*" terms .... Manage - The administrative process of deploying, configuring, monitoring, metering, tuning, and / or troubleshooting resources. Manageability - The ability to be managed. Manageability interface - The interface through which a manageable resource is managed. Manageable entity (drop) Manager - Software that manages manageable resources. A manager may or may not require a human operator to perform its tasks. ---- Hiro Kishimoto

1 0

Glossary service vs. resource (RE: [ogsa-wg] Proposed agenda for Nov. 17th call)
by Hiro Kishimoto 18 Nov '04

18 Nov '04

Hi all, > From the telecon minutes of 20 Oct. 2004 > Action: Hiro to do a first try on 'service' & 'resource' wrt the above discussion > and discuss with a small group before bringing back to the call. The attached is my draft proposal for definition of service, resource, entity, manageable resource, and manageable entity with feedbacks form Dave Snelling and Fred Maciel. My proposal is (a) Service = Web service Dave: This is OK, although some may argue that there are services of interest that are not Web Services. Fred: Agreed. We could mention that OGSA concerns only Web services, and any service that's not a Web service is not part of the OGSA framework. Hiro: Agreed that OGSA v1.0 chooses Web service as its infrastructure. But OGSA does not prohibit the other plumbing. (b) Resource = entity (= stateful resource defined by WSRF) Dave: WSRF-Resource(*) defines a resource is an entity that has the following characteristics: - It MUST be identifiable; a resource has at least one resource identifier (see Section2.2). - It MUST have a set of zero or more properties which are expressible in XML infoset. - It MAY have lifecycle. Fred: I disagree. I think that in the real world not everything in a Grid will be manageable. Suppose that you have a host that's not manageable (say, you lost the root password -- you can only run jobs on it, press the reset button if things go wrong, and nothing else). It is still an entity, but I don't think that it is a resource. I think that the word resource implies that you may not only use it but also manipulate it (monitor it, provision it or provision stuff on it, change its IP address or reboot it remotely, etc.). Hiro: Everything is "resource" but not "manageable resource." (c) Manageable resource = manageable entity (will be represented by WS-resource) Dave: WSRF-Resource(*) defines a WS-Resource is a Web service Hiro: It is tricky but OGSA does not define WS-Resource. * the URL for WSRF-Resource: http://www.oasis-open.org/committees/download.php/9547/wsrf-WS- Resource-1.2-draft-01.doc Thanks, ---- Hiro Kishimoto > -----Original Message----- > From: owner-ogsa-wg(a)gridforum.org [mailto:owner-ogsa-wg@gridforum.org] On > Behalf Of Hiro Kishimoto > Sent: Tuesday, November 16, 2004 10:54 PM > To: 'ogsa-wg' > Subject: [ogsa-wg] Proposed agenda for Nov. 17th call > > Hi all, > > The following is a proposed agenda for OGSA-WG telecon on November 17th > Wednesday from 5pm to 7pm (CST). > > The dial-in number for Wednesday. > Free: +1-888-452-0308 > Intl/Toll: +1-484-644-0505 > PIN: 71815 > > Screen share service will be provided. > URL: http://hiro.glance.net > Session key: 1117 > See more explanation: > http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html > > 1) Early discussion (10 min) > Note taker assignment > Roll call (orally and send your name to note taker) > Telecon minutes approval (Nov. 10th, if available) > Agenda bashing > > 2) December F2F meeting update (20 min) > Meeting logistics and accommodation information; > https://forge.gridforum.org/projects/ogsa-wg/document/2004Dec_F2F_logistics/ > https://forge.gridforum.org/projects/ogsa- > wg/document/2004Dec_F2F_accomodations/ > > 3) Interested party list discussion (30 min) > For both our roadmap and v1 document, we should list up key > stakeholders including WG/RG/TCs, grid projects, venders. > Identify their interest (high level arch - actual spec - implementation) > and > involvement to OGSA activity. > Hiro will send out draft survey template before the call. > > 4) OGSA glossary update (30 min) > Continue with review of glossary public comments. > Last summary: > http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/10/msg00008.html > > 5) OGSA arch v1 document update (if time permit) > Continue with review of v1 public comments. > Last spreadsheet: > https://forge.gridforum.org/projects/ogsa-wg/documen/ogsa-v1-public-comment… > > 6) Wrap up (10 min) > AOB > > Nov. 22nd is EMS design team call > Nov. 24th is regular call > Nov. 29th is naming service design team call > > <pending issues> > ?) Process discussion until December F2F (?) > Agenda items > Design teams' deliverable and schedule > Solicit attendees from related WG/RG/TCs > > https://forge.gridforum.org/projects/ogsa-wg/document/200412_draft_agenda_o… > e/en/1 > > ?) Roadmap document review (?) > > > - Ian had some comments on the revised version and it was decided > > that it would be better to have him on the call. > > The version of the roadmap that came out of the Sept 1st call is on > gridforge: > http://tinyurl.com/5fxfd/draft-ggf-ogsa-roadmap/en/2 > > ?) GGF12 Action Items () > - Andreas will send out shortly > > > ?) Aug F2F meeting Action Item review (?) > > Action: Heather to send details on the work WSDM is doing on > Events. > - Ravi and Andrew would like to be involved in this > discussion. > > Fred will keep an eye on work progress and inform the group > > Andreas to send reminder to Heather again > Done > > Action: Andrew to check with Data team if producing a set of notes > each detailing a decision and its rationale (Architecture (AR) > notes) would be appropriate to solve the 'communication' > problem (what OGSA-WG has discussed and decided) > > - Andrew did not receive a positive or negative response so far > > - Andrew to talk with people who brought it up; this will likely > > not be before GGF12. > > Action: Frank to ask Ian for an MDS representative to join the > Information Services design team > > - Frank asked Ian; waiting for reply; will followup. > > Action: Jay to talk with Ian and Hiro and form a core design team to > work on dependencies at architecture level (roadmap). > > - Hiro will contact Jay > > Thanks, > ---- > Hiro Kishimoto > > > >

1 1