February 2008 - ogsa-bes-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

BES and SOAP 1.2?
by Piotr Domagalski 25 Feb '08

25 Feb '08

Hi! Is using BES with SOAP 1.2 breaking the specification? There are few places were SOAP 1.1 is mentioned but it is not said, whether this version is really mandatory... I know that the answer will most probably be `yes' but I was just wondering what was your general opinion on that. -- Piotr Domagalski

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

The up-to-date specification?
by Piotr Domagalski 20 Feb '08

20 Feb '08

Hi all, I'm implementing an OGSA-BES service and I've encountered some requirements that are unfortunately not clear to me: 1. The BES-Management port doesn't allow any faults to be throwed - so how should I notify the client that he is not authorized to perform this call? 2. Generally, the fault semantics are unclear to me, i.e. when should I use the fault directly in SOAP response and when should I put it into the response message. My questions are almost exactly the same as in https://forge.gridforum.org/sf/go/artf6066?nav=1 Any chance on getting answers to that? 3. I'm willing to extend the state model. Where should I add appropriate operations then (e.g. to suspend an activity)? BES-Factory? Is there any guidelines on that? 4. Finally, where should I look for the most up-to-date specification? Is the GFD.108.pdf at ogf.org the only source of the latest specification? As far as I can see in the tracker, there were some changes scheduled, but it seems to me they haven't gone into the pdf doc. -- Piotr Domagalski

5 13