- ogsa-wg - lists.ogf.org

[ogsa-wg | Basic Profile - 1581] WS-I BSP 1.0 and SAML 1.0 are "Evolving Institutional" status
by Sourceforge Tracker Monitor 27 Jul '05

27 Jul '05

A new artifact has been added: 1581 Submitted by: Hiro Kishimoto Submitted date: 2005-07-27 16:18:21 Respond by visiting: https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1581&group_id… (https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1581&group_id…) Summary: WS-I BSP 1.0 and SAML 1.0 are "Evolving Institutional" status Project: Open Grid Services Architecture Tracker: Basic Profile Artifact ID: 1581 Category: <None> Group: <None> Status: Open Priority: 3 Last Modified By: Hiro Kishimoto Last Modified: 2005-07-27 16:18:21 Submitted By: Hiro Kishimoto Submit Date: 2005-07-27 16:18:21 Assigned To: &lt;None&gt; File(s): <None> Description: Given both WS-I Basic Security Profile and SAML Token Profile are WS-I Working Group Documents instead of WS-I final materials, their status shuold be "Evolving Institutional." View the Basic Profile : https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=… (https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=…)

1 0

[ogsa-wg | Roadmap - 1580] Comments from Olegario Hernandez
by Sourceforge Tracker Monitor 26 Jul '05

26 Jul '05

A new artifact has been added: 1580 Submitted by: Jem Treadwell Submitted date: 2005-07-26 16:02:27 Respond by visiting: https://forge.gridforum.org/tracker/?func=detail&atid=789&aid=1580&group_id… (https://forge.gridforum.org/tracker/?func=detail&atid=789&aid=1580&group_id…) File(s) Added: 'Roadmap_Comments_from_Oleg.doc' Summary: Comments from Olegario Hernandez Project: Open Grid Services Architecture Tracker: Roadmap Artifact ID: 1580 Category: <None> Group: <None> Status: Open Priority: 1 Last Modified By: Jem Treadwell Last Modified: 2005-07-26 16:02:27 Submitted By: Jem Treadwell Submit Date: 2005-07-26 16:02:27 Assigned To: Jem Treadwell File(s): Roadmap_Comments_from_Oleg.doc Description: The attached comments were received from Olegario during the public comment period (7/26/2005). - Jem Treadwell Hi, attached are my comments regarding the Roadmap document. I liked it. Regards, Olegario Hernandez IBM Certified ODB Solution Designer Civil Chemical Engineer - Universidad de Chile (56) 2 220 5168 Santiago - Chile View the Roadmap : https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=… (https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=…)

1 0

[ogsa-wg | Basic Profile - 1579] Need BaseFault Extension constraint
by Sourceforge Tracker Monitor 26 Jul '05

26 Jul '05

A new artifact has been added: 1579 Submitted by: Tom Maguire Submitted date: 2005-07-26 12:21:37 Respond by visiting: https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1579&group_id… (https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1579&group_id…) Summary: Need BaseFault Extension constraint Project: Open Grid Services Architecture Tracker: Basic Profile Artifact ID: 1579 Category: <None> Group: <None> Status: Open Priority: 2 Last Modified By: Tom Maguire Last Modified: 2005-07-26 12:21:37 Submitted By: Tom Maguire Submit Date: 2005-07-26 12:21:37 Assigned To: Tom Maguire File(s): <None> Description: The PR BaseFaults spec added extensibility which causes UPA validation errors for extensions. Need a constraint that precludes child elements in extensions. View the Basic Profile : https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=… (https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=…)

1 0

Small update to BP 1.0 v032
by Tom Maguire 26 Jul '05

26 Jul '05

Needed better description of BaseFaults Extension requirement and in doing so required a normative reference to XML Schema Part 1. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsrf-b… Tom Frey’s Law: “Every 5 years the number of architecture components double and the ability to comprehend them halves” Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away. – Antoine de Saint-Exupery T o m M a g u i r e STSM, On Demand Architecture Poughkeepsie, NY 12601

1 0

call to discuss security comments
by Tom Maguire 26 Jul '05

26 Jul '05

Folks I would like to have a telecon tomorrow to dicsuss some of the comments that the cc: list has raised on section 8 of the OGSA WSRF BP 1.0 document. If possible I would like all those on the cc list to attend. I am thinking that either 11AM EDT or 12PM EDT for a 1 hour duration. Please let me know your availability. Call-in Details Toll/International: +1(314)655-1412 Toll-free: +1(877)422-0036 Passcode: 496684# Tom Frey’s Law: “Every 5 years the number of architecture components double and the ability to comprehend them halves” Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away. – Antoine de Saint-Exupery T o m M a g u i r e STSM, On Demand Architecture Poughkeepsie, NY 12601

2 2

OGSA WSRF BP 1.0 v031 uploaded
by Tom Maguire 26 Jul '05

26 Jul '05

Changes based on the telecon of 7/25 have been made and uploaded to the gridforge. Please take some time and verify (before 7/27) that trackers in the fixed state have been faithfully addressed in this version. https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsrf-b… Tom Frey’s Law: “Every 5 years the number of architecture components double and the ability to comprehend them halves” Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away. – Antoine de Saint-Exupery T o m M a g u i r e STSM, On Demand Architecture Poughkeepsie, NY 12601

1 0

Teleconference minutes - 25 July 2005
by Andreas Savva 26 Jul '05

26 Jul '05

Minutes attached - F2F update - Teleconference schedule review - WSRF Basic Profile 1.0 review https://forge.gridforum.org/projects/ogsa-wg/document/minutes-20050725/en/1 -- Andreas Savva OGSA Teleconference - 25 July 2005 ================================== * Participants Mike Behrens (R2AD, LLC) Hiro Kishimoto (Fujitsu) Takuya Mori (NEC) Andreas Savva (Fujitsu) Dave Snelling (Fujitsu) Jem Treadwell (HP) Jay Unger (IBM) Pete Ziu (Northrop Grumman) Apologies: Fred Maciel, Steven Newhouse Minutes: Andreas Savva * Minutes of July 20 approved with no changes * August F2F update First version of agenda sent out by Hiro: https://forge.gridforum.org/projects/ogsa-wg/document/OGSA-2005-Aug-F2F-age… Venue: Fujitsu Laboratories America, Sunnyvale, CA - The meeting will be held in the same building as last year, but in a different, larger, room. - An additional room is reserved for Tuesday morning for the OGSA-EGA meeting (parallel session). - Internet access will be available. - There are more participants expected overall but many people will probably attend some sessions only. - The agenda is still in an early draft stage. Session leaders are expected to provide an agenda for their sessions. - OGSA-AuthZ WG participants have not been contacted yet. - Jem does not know if he can attend yet. * Teleconference schedule review Hiro put together a proposal for the teleconference schedule based on next items discussion (previous call) https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule/en/26 - Provisioning: There is some ongoing work within other bodies (e.g., DMTF Utility Computing WG, EGA). OGSA-WG should work to make clear how this work fits with other efforts. (Any overlapping effort at this moment is probably 'people overlap'. That is, the same people may be involved in more than one group.) - Aug 10: The plan is to invite OGSA-AuthZ to join the teleconference. This is in part to make sure the F2F is productive. - Agreed to move the OGSA 1.5 discussion from Wed (7/27) to Monday (8/3) to give Andreas and Jem some more time to prepare. - Agreed to move the Roadmap from 8/27 to 8/10. It is not expected that a revision of the Roadmap document will take a long time. - There is time allocated to resource modelling starting next week. * WSRF Basic Profile 1.0 review Based on version 30 uploaded by Tom before the call: https://forge.gridforum.org/projects/ogsa-wg/document/draft-ggf-ogsa-wsrf-b… Tom deleted existing comments from the document and put them in trackers. [Issue numbers are tracker artifact numbers on the gridforge BP tracker: https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=…] - Issue 1571: TLS extensions not in WS-I BSP 1.0 Hiro has confirmed that they are present in the BSP 1.0. Closed. - Issue 1559: l.483 remaining issue is the combination of 'only...permitted'. Agreed that for consistency with the rest of the text it should be changed to 'only....recommended.' Fixed. - Sec.6.1.1 Updated R0611 and R0612 to use the terms defined in the referenced WS-N documents: UseNotify changed to UseRaw; Filter, etc. R0617, R0618: deleted by accident. Rejected deletion and made similar terminology changes to bring up to date with current WS-N specification. The R06XX statements need re-numbering for consistency. - l.630: URI reference was deleted since it was not cited in the text. - Some URIs in the document were hyperlinks. Removed the hyperlinks. - SchemaCentricCanonicalization issues - Issues raised on serialization by Takuya in the last call. Some were retracted after a re-read of the canonicalization specification. (In particular the inefficient serialization issue.) - The remaining issue is with defining an envelope for the query response to hold the type of the XPath return value. - The issuer of the query should know what the return value is going to be. Anyway this information is best described in the data not the message. - Agreed that serialization is essential for interoperability and has to be defined in the BP. But that this extra definition is nice-to-have and probably best left to higher levels (JAX-RPC etc.) - GGF IPR in the schema - Consensus that it is ok to leave the full version in. It is somewhat verbose but it is on the safe side. It can be changed later if GGF comes up with a guideline. - R0423: the namespace should be wsrf-rpw - Issue 1242: verified and closed - Issue 1250: verified and closed - Issue 1251: verified and closed - Issue 1255: verified and closed - Issue 1256: verified and closed - Issue 1258: R0431: minor inconsistency: Change MUST to SHOULD - Verify and close in the next version - Issue 1294: Verified and closed. - But note that this spec refers to WS-I BSP 1.0 dated 20-Jan-2005. WS-I had updated the date of this spec but has not changed the version number (new date is 11-May-2005). Agreed to leave the citation as is. Action: Takuya will check for differences between the two versions and will report back to the group. - Issue 1320: verified and closed - Issue 1355: verified and closed - Issue 1360: Closed (as obsolete; insufficient description.) Note that the Base Faults PR spec has an extensibility element in the schema that causes indeterminism. A later draft has fixed it but it cannot be referenced yet. The extensibility point should be addded to Sec.7.1. Also to add a restriction that only type extension is allowed. And that no extensibility elements are allowed. Action: Tom has the pen and will update the document with the above changes. Action: ALL should check FIXED trackers before the next call to expedite the verification process. * Next call - WSRF BP final call - Review changes - Tracker review and verification.

1 0

Proposed agenda for July 27th call
by Hiro Kishimoto 26 Jul '05

26 Jul '05

Hi all, Public comment period for "OGSA roadmap" will end this Friday (July 29). Please read (or encourage your colleagues to read) and make your/their comments on the web site. https://forge.gridforum.org/forum/forum.php?forum_id=540 The following is a proposed agenda for OGSA-WG telecon on July 27th Wednesday from 5pm to 7pm (CDT). Dial-in numbers for Wednesday: 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: 0727 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 (Andreas will send out) Agenda bashing 2) OGSA F2F meeting update (if any) 3) OGSA WSRF Basic Profile 1.0 final call (60 min) Tom will upload revised version to the GridForge. Tom will host separate BP security call Tue 11am or noon Make all issues on the tracker to "closed" Final call on GGF Editor submission on this Friday 4) Wrap up (10 min) AOB Aug. 1 (Mon) OGSA roadmap public comments review, OGSA Arch 1.5 Aug. 3 (Wed) Resource Modeling discussion Aug. 8 (Mon) Provisioning, F2F preparation https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule/ (also attached to this email) ---- Hiro Kishimoto

1 0

RNS critique
by Andrew Grimshaw 26 Jul '05

26 Jul '05

All, Here are some of my comments on the RNS document. I jammed my finger yesterday in basketball, so typing is painful. Therefore, I'm limiting my comments to the most significant. Thank you to the RNS team for all of their work. Andrew High level comments: 1) The basic directory function is to provide a mapping handle f("string"), i.e., to map strings to some form of handle. Thus, in section 1.1. Why do we need four different types of junctions? Should we not have one type of junction: mainly to an EPR. Thus a directory would map a string to an EPR. EPR f("string"); Instead there are four "types" of junctions: EPR's Virtualized reference - either contains an EPR or a URL that points to some other service Referrals - point to another RNS service. Q: could this not be modeled as an EPR? Alias - points to another "entry" within the "same" RNS service. This seems to imply a container like model - more on this later. I suggest that we need only ONE type of junction - an EPR. That will simplify client coding - and the model significantly. 2) Implied model - Repositories There is a notion in the spec of "same service instance" that in conversations has also been called a "repository". The basic idea is that an RNS service may "contain" a set of directories - and that the service has a root. Thus junction types distinguish, for example, between internal and external things that they point to. Thus an RNS service is a rooted tree - that may point at the leaves to other rooted trees. So, first of all - it is implied. If we're going to have that model it should be right up front and discussed. What is a repository? What are it's special port types if any, etc. Second, I think that it is not the right way to think about the problem. Directories should be the resources - not collections of directories. If a particular implementation chooses to multiplex a large number of logically independent directories in a single container - great - we will certainly do that too. The issue is what is the model. I feel fairly strongly about this. Links "into" other RNS servers:1.1.2.4 "Alias Junction" is restricted to pointing to entries in the same repository. I think they should be able to point to anything - including directories in "other" repositories. It has been claimed that using the EPR of the "repository" and a path you can get that effect. However, what if the path changes in the other container? My link would break - even if the directory itself still exists. 3) Full path names In ANY directory system lookup really takes two parameters - a "root" at which to start, and a path. Often the "root" is implied, or is at some well-known location. RNS - as written, implies that all lookups are based on full paths with an implied, unspecified root. Assuming that full paths are to be used on all lookups, the potential for both hot spots AND single point of failure are clear. In conversation with Manual he mentioned that his clients cache intermediate parts of the tree in the sense that "/foo/bar/d1" as a prefix leads to a particular RNS service, and then use that info to not always traverse the tree. Besides the obvious implementation challenges of cache consistency when the tree is changing (a problem we certainly had/have in Legion) there is the modeling issue. If we expect clients to do that - then perhaps the architecture/specification should accommodate that and say that all lookups are relative path lookups with respect to some "root". The root could be a true "root", or interior node in a tree, which is itself a "root" of the subtree it defines. 4) Resolve and file system profile. We discussed these on the last ogsa call, my understanding is that they are going out. 5) Iterators. OGSA-Data-WG has discussed iterators in a more general way, e.g., on data base query results etc., I think that whatever is done in RNS should be consistent with whatever is done in OGSA-Data (note - consistency can happen either way). Medium level comments: S 1.1 "In all cases, junctions are capable of maintaining a list of references (EPRs/URLs) per entry, that is a single junction my render several available EPRs, each of which represent replicas, copies of the same resource, or operationally identical services. " Why? Are you saying that replication issues and semantics should be dealt with in the directory structure? Or are you saying that directories are not "sets" in the sense of only one entry - but rather "multi-sets" in the sense that one string can map to multiple things. If the later - what are the implied semantics. I think it may be safer to keep them as sets.

3 3

[ogsa-wg | Basic Profile - 1578] R0611 should be updated based on PR Base Notification
by Sourceforge Tracker Monitor 25 Jul '05

25 Jul '05

A new artifact has been added: 1578 Submitted by: Tom Maguire Submitted date: 2005-07-25 16:54:55 Respond by visiting: https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1578&group_id… (https://forge.gridforum.org/tracker/?func=detail&atid=780&aid=1578&group_id…) Summary: R0611 should be updated based on PR Base Notification Project: Open Grid Services Architecture Tracker: Basic Profile Artifact ID: 1578 Category: <None> Group: <None> Status: Open Priority: 2 Last Modified By: Tom Maguire Last Modified: 2005-07-25 16:54:55 Submitted By: Tom Maguire Submit Date: 2005-07-25 16:54:55 Assigned To: Tom Maguire File(s): <None> Description: see summary View the Basic Profile : https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=… (https://forge.gridforum.org/tracker/index.php?func=browse&group_id=42&atid=…)

1 0