February 2008 - ogsa-hpcp-wg

Unresolved issues in BES from implementation experiences
by Steven Newhouse 13 Mar '08

13 Mar '08

There are some issues arising from recent implementation experiences that need some discussion... * Handling SOAP Faults Many BES operations take in a vector of activities and return a vectorised response based on these activities. How should faults be handled? The current document is ambiguous. Should: 1. Any fault generated by one of the activities in the vector can only be returned as part of the response vector from the operation. The WSDL is then incorrect as currently only a single specified fault can currently be generated from the operations. 2. Faults can be returned directly. Say if the vector length is 1. In which case text in 6.2.2, 6.2.3 & 6.2.4 needs to be clarified and the WSDL changed to allow faults of other types to be returned. See Glenn's original tracker for more details - https://forge.gridforum.org/sf/go/artf6066?nav=1 * Handling Authorization for the BES Port types The BESFactory port type contains operations that are to be applied to a vector of activities. An authenticated client may be authorized to access the operation - but may not be allowed to access one (or more) of the specified activities, for instance if the activity is owned by a different user. I've added NotAuthorizedFaults to the GetActivityStatuses, TerminateActivities & GetActivityDocument operations. The BESManagement port type does not throw any (authorization) faults. Authentication and authorization is provided by the container. A deployment therefore specifies who has access to the operations within BESManagement and any client that enters the operation is already authorized to start/stop the container from accepting activities and no fault is needed. Are these changes sufficient?

3 5

HPC File Staging extension in public comment
by Steven Newhouse 27 Feb '08

27 Feb '08

The HPC File Staging Profile is now in public comment http://www.ogf.org/Public_Comment_Docs/Documents/2008-02/HPC%20File%20Stagi… Abstract: This document profiles the File staging capabilities of the Job Submission Description Language (JSDL) for use by HPC Basic Profile-compliance services. It includes clarifications, refinements, interpretations and amplifications of JSDL which promote interoperability. Please review and make comments (positive or negative): https://forge.gridforum.org/sf/discussion/do/listTopics/projects.ggf-editor… Thanks, Steven

1 0

OGSA DMI Functional Specification
by Steven Newhouse 27 Feb '08

27 Feb '08

The OGSA DMI Functional Specification is now in public comment http://www.ogf.org/Public_Comment_Docs/Documents/2008-02/ogsa-dmi-spec-edit… Abstract The Open Grid Services Architecture Data Movement Interface (OGSA-DMI) specification defines a standardized mechanism for moving data from its source to its destination. By abstracting this movement, the client complexity for moving data within a grid will be greatly reduced. OGSA-DMI defines two port types for initiating, scheduling and managing data transfers from a given source to a specified destination. The source and destination are described through Data End Point References (DEPRs), a specialized form of a WS-Address. An OGSA-DMI service will use the properties of the data to be transferred and the properties of the infrastructure to decide what the best underlying transfer protocol to undertake the actual data transfer is for the given combination of data source and sink. By this means OGSA-DMI provides a common interface, though its abstraction layer, that can be used to span the preferred transfer mechanisms used across many different types of Grid infrastructures. This version of the specification aims to ensure that the OGSA-DMI port types are composable with other Web Service (WS) specifications whilst being agnostic about any specific WS rendering. OGSA-DMI is only concerned with the moving of data, i.e. bytes. Any associated semantics are the responsibility of higher level services that leverage off OGSA-DMI. The OGSADMI framework is general enough to cater for the movement of single elements of data or composites. Please review and make comments (positive or negative): https://forge.gridforum.org/sf/discussion/do/listTopics/projects.ggf-editor… Thanks, Steven

1 0

Updates to BES Specification GFD 108
by Steven Newhouse 23 Feb '08

23 Feb '08

Going through the trackers I've generated a new change tracked draft https://forge.gridforum.org/sf/docman/do/downloadDocument/projects.ogsa-bes… based on the current GFD 108. It has the following changes: 1. An activity is put in a Cancelled state through a TerminateActivity operation. The document was inconsistent. 2. The example response on page 40 had the activity state in the body of the element as opposed to in an attribute as specified in the schema on page 26. The example has been corrected to be consistent with the schema. 3. The paragraph immediately before the heading of section 6.2.4 should have been after the section heading. It is now. 4. NotAuthorizedFaults are now generated in the GetActivityStatuses, TerminateActivities & GetActivityDocument. An authenticated and authorized user to the operation may not have sufficient privileges to perform the operation on all of the activities they have specified, i.e. the activity may be owned by someone else. I hope these are all relatively uncontroversial changes. They can be backed out if we want to do so.

1 0

Telecon Notes
by Steven Newhouse 21 Feb '08

21 Feb '08

Attendees Chris Smith Marty Humphreys Glen Wasson Steven Newhouse Blair Dillaway Agenda 1. IPR Noted. 2. Agenda Bash OGF Session discussion. 3. Application Template Specification Review (Steven) No further comments. Review at OGF session. 4. Kerberos Use Cases Discussion (Chris) Typical use of Kerberos by a site around job submission. * Authentication: Use Kerberos credentials to identify myself to the container. Still use https to do the connection, but use the client token to provide authentication. Could establish a secure conversation using Kerberos that can then be used within WS-Security. Mutual authentication may not be widely enabled. Start with just the server side identification for https - same as current HPCBP model. Happy to use certificates for servers but not for users. * Token Forwarding What could the token be used for? 1. Placed in the running environment of the running application. Establish the environment in the job. 2. Used in file transfer mechanism. Place the token in the environment of the file transfer. 3. Forwarding the job to another BES. Will the original BES container impersonate the user to the second BES. Generally, don't use restricted delegation. Just send the main ticket granting ticket (TGT) - harder to bind the ticket to a specific service. Again make sure that the TGT gets put into the job environment. Make sure tickets are not bound to a specific IP address. In the meta-scheduling use case... the authentication takes place at the BES to BES level, but the user credential is still passed with the job object. Does this need to be profiled? The token does need to be forwarded to any subsidiary file staging or meta-scheduling activity. Running UNIX environment uses Kerberos, in some scenarios might uses certificates to use web services. Next Steps: * Chris to look at specification documents for next week. * Is this one or two profiles - Kerberos for authentication to the service & Ticket forwarding into subsidiary environments (i.e. file staging, local job or job submitted to remote cluster) 5. Experiences Document Comments Review (Marty/Glenn) Document revised and new version submitted to the OGF Editor. 6. AOB OGF Session Planning Experiences Document: Goes through GFSG review (7 day) and then published. Current HPCBP spec needs no changes. File Staging: Marty to do 10-15 min review as will hopefully be in public comment. Application Template: Steven to review current draft. Kerberos: Chris/Blair to do a 10-15 min review to gather interest and participants in profile writing. Steven to look at BES errata.

1 0

HPCP WG Telecon - February 21st 2008
by Steven Newhouse 15 Feb '08

15 Feb '08

When: Thursday, February 21, 2008 9:30 AM-10:30 AM (GMT-08:00) Pacific Time (US & Canada). Where: Telecon *~*~*~*~*~*~*~*~*~* All, We have a call scheduled for Thursday 21st Feb 2008. Time: 9.30AM (Pacific), 12.30PM (East Coast), 5.30PM (UK) Call details: PIN - 2719140 USA: 866 500 6738 UK +44 118 909 2000 Agenda 1. IPR 2. Agenda Bash 3. Application Template Specification Review (Steven) 4. Kerberos Use Cases Discussion (Chris) 5. Experiences Document Comments Review (Marty/Glenn) 6. AOB

1 0

Updated Application Template specification
by Steven Newhouse 15 Feb '08

15 Feb '08

All, A new version of the Application Template specification, following on from discussions on today's call and comments on the list, is now available. Please review and provide further comments. Steven https://forge.gridforum.org/sf/docman/do/downloadDocument/projects.ogsa-hpc…

1 0

HPCP WG Telecon notes
by Steven Newhouse 14 Feb '08

14 Feb '08

Present Blair Dillaway Glenn Wasson Marty Humphrey Steven Newhouse Chris Smith Apologies Andrew Grimshaw Donal Fellows Agenda 1. IPR Noted. 2. Agenda Bash Bashed. 3. Application Template Discussion * Application Identifier: A property of the application or a property of a site? Consensus to make the application a property of the site. * Should the JSDL application name and version elements be used? The definition of these element seems unclear. Proposals to add an ApplicationURI element to contain this... or overload this string into the application name and move away from the URI model. DRMAA has the notion of an application name - intended for the local site to provide details. Consensus to make the JSDL Application Name & Version elements with no particular unique naming model in the Application Name. * Discovery - Should the application list be kept somewhere else? As we are moving away from the URI this cannot be used. But a URI describing that fact that the Application Template is supported is still needed. Consensus: Use extensibility in Factory Resource Attributes document to place in the JSDL:Application (with child elements) in a ApplicationTemplates wrapper element. * Invocation - What must the user still provide & what are they expecting the service provider to mandate? Goal to allow the user to specify as little as possible. If there is a clash... then the service provider takes precedence. If the user specifies a value that the service provider does not like then a fault can be generated. A lot of these will be implementation specific - a site may have its own model as to how to deal with provided elements. Arguments & Environment variables need to be cumulative - but with the system provide able to override or push back through a fault. 4. OGF 22 Session Planning One session on 11.15 Tuesday morning - 'Next Extensions' 90 min session * Reponses to the HPCBP Experiences Document (15 min) * File Staging overview to encourage public comment (15 min) * Kerberos use cases (15 min) * Application Template discussion (15 min) * Advanced Filter profile (15 min) 5. OGF 22 Spec Adoption Demo & Presentation Monday evening for the Demo. UVa - Profile in Sharepoint work & handheld device MS - Beta software demo of HPCBP and extensions. Tuesday morning (9.30-11.00) - Marty & Steven presenting stuff, and possibly Chris 6. AOB * Experience document comments All to make comments if not formal authors. 7. DONM - Next week * Chris: Kerberos use cases * Steven: Application Templates * Marty/Glenn: Experiences document comment

1 0

today's the last day to make pub comments on the HPC Basic Profile Experiences doc
by Marty Humphrey 14 Feb '08

14 Feb '08

Folks, [[ re-sending to try to avoid the SPAM filter ]] Just a quick reminder: *today* is the last day to make comments on the HPC Basic Profile Experiences doc. https://forge.gridforum.org/sf/discussion/do/listTopics/projects.ggf-editor… Even just a "Ive read it and it looks good" comment could be useful Thanks, Marty ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

1 0

***SPAM*** today's the last day to make pub comments on the HPC Basic Profile Experiences doc
by Marty Humphrey 14 Feb '08

14 Feb '08

Folks, Just a quick reminder: *today* is the last day to make comments on the HPC Basic Profile Experiences doc. https://forge.gridforum.org/sf/discussion/do/listTopics/projects.ggf-editor/ discussion.exp_hpcp_basic_profile_experienc Even just a "I've read it and it looks good" comment could be useful Thanks, Marty

1 0