Glossary service vs. resource (RE: [ogsa-wg] Proposed agenda for Nov. 17th call)
Hiro Kishimoto
hiro.kishimoto at jp.fujitsu.com
Wed Nov 17 16:27:46 CST 2004
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 at gridforum.org [mailto:owner-ogsa-wg at 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-comments/
>
> 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_outlin
> 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
>
>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Service-resource v2.doc
Type: application/msword
Size: 50688 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/ogsa-wg/attachments/20041118/54be3cfb/attachment.doc
More information about the ogsa-wg
mailing list