- ogsa-bes-wg - lists.ogf.org

Typos in doc15062 (latest BES-Spec draft)
by Piotr Domagalski 25 Aug '08

25 Aug '08

Hi! Just noticed 2 small problems: - in some places some Unicode version of a quotation mark is used, just look carefully in bes-management.wsdl at the value of "name" attribute in the lately added NotAuthorizedFaults (e.g. wsdl:operation/[name="StartAcceptingNewActivities"]/wsdl:fault/[@name]) - additional space is used in 3 places (as far as I remember) in namespaces, just search for "bes:factory: " and you'll now what I mean. -- Piotr Domagalski

2 1

Parameter Sweep and BES Factory
by Piotr Domagalski 24 Jul '08

24 Jul '08

Hi! I'm just wondering -- is there any agreed view on how Parameter Sweep Extension should interact with BES Factory job submission? My main concern is whether the submission should return an activity that hides all those individual tasks that the parameter sweep produced (say, 1000 jobs from one JSDL...) or should it be possible to somehow treat them individually? The problem with the former is that it would only be possible to get a some kind of heuristic view of the state of the activity (say, the activity is in running state if at least one of the individual tasks has moved to this state). The problem with the later is, in my understanding, the fact that the CreateActivity yields one and only one ActivityIdentifier. -- Piotr Domagalski

5 7

Fwd: File staging faults
by Piotr Domagalski 22 Jul '08

22 Jul '08

I'm forwarding my question here in case I sent it to a dead mailing list ;-) ---------- Forwarded message ---------- From: Piotr Domagalski <piotr.domagalski(a)fedstage.com> Date: Fri, Jul 11, 2008 at 12:29 AM Subject: File staging faults To: "ogsa-hpcp-wg(a)ogf.org" <ogsa-hpcp-wg(a)ogf.org> Hi! Hopefully, this is the last thing that bothers me: 1. As far as I can see, there no such thing as an XML Schema for HPC File Staging Profile. Is that right? 2. Assuming that #1 is true, I'm preparing a schema for me to ease handling of the specified elements. The faults seem a bit unclear to me, though. What are their types? Are they all xsd:string? What about UnsupportedProtocolFault and DeleteOnTerminationFault from which description you can read that they could have a <File> subelement? Do they solely have this subelement or are they mixed-type so that they can contain both string and <File> subelement, e.g.: <DeleteOnTerminationFault> something bad happend <File>ftp://foo.com/bar.txt</File> </DeleteOnTerminationFault> Thanks for any clarifications! -- Piotr Domagalski -- Piotr Domagalski

3 2

Activity Delegation Interfaces and Protocols
by Alexander Papaspyrou 04 Jun '08

04 Jun '08

----- Apologies for duplicates from the cross-post ----- Folks, for quite a while now, the topic of "Activity Instance Schema" has been floating around in JSDL. Basically, it boils down to what is used to describe the concretization of a something that has been initially defined by a JobDefinition template and submitted to a handling entity (such as a BES container or a scheduler). One of the use cases that has been extensively discussed in the past JSDL telecons was the delegation of a job (or, to be more general) of an activity after its initial submission. That is, how to ensure a submitted, but not running activity can be delegated in a simple, coherent and safe way from one scheduler to another. We would like to kick off discussion during today's session on this topic by starting with a very simple delegation protocol. Herefor, I'd like to invite everyone to join us today at 3:45pm in Sarria. Although we'll also discuss other issues (such as the applicability of SPARQL to CSG), there will be plenty of time to chew on this new thing. Looking forward to a vivid discussion, albeit a very last-minute notice. Cheers, Alexander -- Dipl.-Inform. Alexander Papaspyrou http://ds.e-technik.uni-dortmund.de/~alexp Robotics Research Institute phone : +49(231)755-5058 Information Technology Section fax : +49(231)755-3251 Dortmund University of Technology, Germany

2 1

Feedback about HPCBP and BES
by Steven Newhouse 04 Jun '08

04 Jun '08

All, These are my combined notes from the HPCP-WG (which discussed current and future extensions) and the GIN session that was providing feedback on BES/HPCBP/JSDL specifications. Hopefully, we can use this to drive future BES and HPCP WG activities. Steven In no particular order: * File Staging Extension: Should support EPRs in the Source & Target elements in addition to just URIs. This will enable data transfers from end points (such as ByteIO, DMI, etc) * File Staging Extension: Current model assumes that the HPCBP service pulls data into the container. A use case is to get something back to the client so that they can upload/download files into the job workspace. * GLUE Profiling: Now that GLUE is entering public comment we should look at how we can use this within BES to either replace the current BES information model or define a port type to provide GLUE information. * Attribute Support: How information relating to a user's attributes can be provided with the job request... for instance SAML attributes document for UNICORE job submission through BES. * State Change Request: If the BES state model is extended to support (say) suspend and resume how does the user initiate this state change? It was observed that the BES-Activity port exists in BES but is not used. This could provide an opportunity to use this port type to provide: * Operations to upload/download files into an activity specific file space * Provide a state change request to the activity (i.e. suspend) as part of an extension to the BES state model * Renew/provide a credential for access to external resources from the BES container

1 0

Final Call: Revised Specification
by Steven Newhouse 13 Mar '08

13 Mar '08

All, I think we are nearly there... below is a link to a change tracked version of GFD 108 that addresses (I hope) all of the issues that have come up during our recent implementation experiences. The WSDL and schemas have been updated and clarifications and corrections made to the text. *** Please review and make comments by the Friday 21st March 2008 *** https://forge.gridforum.org/sf/docman/do/downloadDocument/projects.ogsa-bes… Thanks, Steven

1 0

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