August 2005 - ogsa-bes-wg

[ogsa-wg] OGSA-WG and fellow WG Winter F2F Survey
by Hiro Kishimoto 31 Aug '05

31 Aug '05

Hi all, and sorry for the cross-posting. OGSA-WG and fellow WGs are planning to have Winter F2F meeting in December or January. At the OGSA-WG F2F meeting in week before last, I took action item to ask all expected attendees for their availability for Winter F2F meeting. Please take the time to fill in the following online survey by next Monday (September 5th). We hope to decide date and city next week. Post the survey on a Web site - use this URL: http://www.zoomerang.com/survey.zgi?p=WEB224LBPWYVUT Thanks in advance, -- Hiro Kishimoto

1 0

OGSA F2Fminutes
by Steven Newhouse 24 Aug '05

24 Aug '05

The BES discussion at the recent OGSA F2F meeting are minuted (draft) here: https://forge.gridforum.org/projects/ogsa-wg/document/f2f-minutes-20050815-… Our thanks to Fred Maciel for the BES minutes. -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK

1 0

Next Telecon - 25/8/05
by Steven Newhouse 21 Aug '05

21 Aug '05

Toll-free dial-in: 1-877-422-0036 Toll/International dial-in: 1-314-655-1412 Tie-line dial-in: 422-0036 Participant passcode: 496684 Time: 10 AM eastern 7 AM Pacific 3 PM UK 4 PM Europe Duration: 1 hour Glance will provided at ogsa.glance.net Agenda: 0. Agenda Bashing 1. Review of OGSA F2F Changes (revised version attached) * If a WS-Name entry within a vector is 'bad' provide a response * Record previous state history * Reorder state model section * Other change tracked changes 3. Unresolved Issues from OGSA F2F * EPRs vs. WS-Names * Cleanup from/to Exceptions * Section 4 : Subscribing to Generated Events 4. AOB -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK

1 0

draft-ggf-ogsa-bes-spec-v9
by Steven Newhouse 12 Aug '05

12 Aug '05

All, A cleanup version of the document for the BES discussion next week at the F2F. The main unresolved issue is how we define what we want to sibscribe to and report on the events that are subscribed to. Steven -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK

1 0

draft-ggf-ogsa-bes-spec-v5
by Steven Newhouse 09 Aug '05

09 Aug '05

Further change tracked revsion to the changes Andrew made in the call. Ignoring white space alterations: * Extra arrow on the action state change diagram for Not Started to Active change. * Revision to the execution action with the 'Execution State' being reflected in the top-level state diagram. * Moving the authorisation issue to the security section. Discussion will continue from section 3.3 on this Thursday's call. Steven -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK

3 7

BES Agenda at OGSA F2F
by Steven Newhouse 08 Aug '05

08 Aug '05

As discussed at the last call the provisional agenda for the BES part of the F2F (Monday 10.30-15.00) 0. Agenda bashing [10 mins] 1. Review of current draft & discussion [50 mins] 2. Discussion about renderings [60 + 60 mins] 3. Discussion about implementations [30 mins] Consider this a stake in the ground! Steven -- ---------------------------------------------------------------- Dr Steven Newhouse Tel:+44 (0)2380 598789 Deputy Director, Open Middleware Infrastructure Institute (OMII) Suite 6005, Faraday Building (B21), Highfield Campus, Southampton University, Highfield, Southampton, SO17 1BJ, UK

1 0

WS-GRAM protocol sketch, as promised on telecon
by Karl Czajkowski 05 Aug '05

05 Aug '05

This is excerpted from a larger summary I sent to the BES BoF list back at the beginning of the year... it shows the "boxcar" submission+subscription mechanism as well as the hold/release mechanism. I've left out extra content that was in the previous email to focus on these parts. Note, WS-GRAM currently has only one "hold" state that is used for synchronizing _cleanup_ of jobs. It would be meaningful to have a _startup_ hold state such as we had in previous GRAM protocols, but it is not strictly necessary for reliable invocation because we use the idempotent message-id idiom instead. Also, keep in mind that the subscription patterns works because we are using WSRF style rendering w/ properties and topics defined for the job resource. So, the semantics are quite clear: create the job resource and then invoke the subscription operation on it w/ the arguments embedded in the creation message. Please see the Globus website documentation, for example, http://www-unix.globus.org/toolkit/docs/4.0/execution/wsgram/developer/WS_G… for examples of client-side programming to build up and send such protocol messages. karl --------------------------------------------------------- PORTTYPE ManagedJobFactoryPortType ---------- OPERATION job:createManagedJob Request creation of a Managed Executable Job Resource whose EPR will be returned in the response. INPUT message: createManagedJobInputMessage has one part: <createManagedJob> <InitialTerminationTime>xsd:dateTime</InitialTerminationTime>? <JobID>wsa:AttributedURI</JobID>? <wsnt:Subscribe></wsnt:Subscribe>? <desc:job> ... </desc:job> </createManagedJob> The optional JobID element is used to request idempotent invocation semantics in a binding-independent manner. The optional wsnt:Subscribe element is used to request automatic subscription to the newly created Managed Job. This call can also create a Managed Multi-Job Resource, i.e. a co-allocated job spread across multiple WS-GRAM hosts, because the job element is actually in an XSD choice with a multijob element. OUTPUT message: createManagedJobOutputMessage has one part: <createManagedJobResponse> <NewTerminationTime>xsd:dateTime</NewTerminationTime> <CurrentTime>xsd:dateTime</CurrentTime> <managedJobEndpoint>wsa:EndpointReferenceType</managedJobEndpoint> <subscriptionEndpoint>wsa:EndpointReferenceType</subscriptionEndpoint>? </createManagedJobResponse> The optional subscriptionEndpoint is returned if a corresponding subscription request was included in the input. --------------------------------------------------------- PORTTYPE ManagedExecutableJobPortType A Managed Executable Job Resource (MEJR) represents one job that has already been submitted by a client. It is a WSRF style resource with a resource properties document to represent status of the job: <managedExecutableJobResourceProperties> <stdoutURL>xsd:anyURI</stdoutURL>? <stderrURL>xsd:anyURI</stderrURL>? <credentialPath>xsd:string</credentialPath>? <exitCode>xsd:int<exitCode/>? <serviceLevelAgreement> <desc:job> ... </desc:job> </serviceLevelAgreement> <Capacity>xsd:int</Capacity> <userSubject>xsd:string</userSubject> <fault/> <TopicExpressionDialects>xsd:anyURI</TopicExpressionDialects> <Topic Dialect=xsd:anyURI> xsd:any? </Topic>+ <TerminationTime>xsd:dateTime</TerminationTime> <localUserId>xsd:string</localUserId> <CurrentTime>xsd:dateTime</CurrentTime> <holding>xsd:boolean</holding> <RegistrantData>xsd:base64Binary</RegistrantData> <RendezvousCompleted>xsd:boolean</RendezvousCompleted> <FixedTopicSet>xsd:boolean</FixedTopicSet> <state>Unsubmitted|StageIn|Pending|Active|Suspended|StageOut|Cleanup|Done|Failed</state> </managedExecutableJobResourceProperties> These properties relate to job output file management: stdoutURL, stderrURL delegated credential management: credentialPath parallel task rendezvous (for MPICH-G2): Capacity, RegistrantData, RendezvousCompleted job status: exitCode, fault, holding, state job introspection: credentialPath, serviceLevelAgreement, localUserId for WSRF introspection: TopicExpressionDialects, Topic, FixedTopicSet, TerminationTime, CurrentTime. ---------- OPERATION exec:release Releases job from hold state. The hold state is an optional behavior selected in the job description to prevent post-execution file deletions (clean-up) from occuring while a remote client is still attempting to access the files. The release operation permits the normal clean-up to occur. INPUT message: releaseInputMessage has one (empty) part: <release/> OUTPUT message: releaseOutputMessage has one (empty) part: <releaseResponse/> -- Karl Czajkowski karlcz(a)univa.com

1 0