jsdl-wg

Download

jsdl-wg@lists.ogf.org

January 2014

3 participants
2 discussions

Hangout sessions on Friday
by Morris Riedel 17 Jan '14

17 Jan '14

Hi, My team is still in vacation and I'm on a full-day meeting tomorrow. Otherwise I would be in Oxford probably. Any plans for Hangout sessions for BES-II on Friday? Take care, Morris ------------------------------------ Dr. - Ing. Morris Riedel Head of Research Group High Productivity Data Processing Federated Systems and Data Division Jülich Supercomputing Centre Germany Adjunct Associate Professor School of Engineering and Natural Sciences University of Iceland ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------

2 5

Documents for discusion in Oxford next week
by Andrew Grimshaw 07 Jan '14

07 Jan '14

Colleagues, After a long gestation period the documents first discussed in Lyon several years ago are ready for discussion. To my GLUE colleagues you are receiving this email because the first document includes the incorporation of GLUE2 into JSDL and BES factory attributes. The documents can be found in the OGSA-BES document area: http://redmine.ogf.org/dmsf/ogsa-bes-wg Andrew Document 1: BES/JSDL 1.1 Extensions The Production Grid Interoperability Working Group identified a number of execution management use cases and requirements in GFD.180. A number of ways to meet these requirements have been extensively discussed. They fall into two categories: 1) define a new set of specifications from scratch to meet the requirements, and 2), profile and minimally extend existing specifications to meet the requirements. The second approach, combining and refining existing production use specifications, has been embraced by the existing OGSA BES and JSDL communities. The approach combines, extends, and profiles five existing specifications to meet the PGI requirements: WS Addressing EndPoint References, OGSA Basic Execution Services (OGSA_BES, or BES) [GFD.108], RNS 1.1 OGSA-WSRF Basic Profile 1.0 [GFD.172], WS-Iterator 1.0 [GFD.188], and OGSA-ByteIO WSRF Basic Profile 1.0 [GFD.98]. The BES/JSDL extensions described in this document are a part of the second approach. Along with the BES Basic Directory Profile (BDP) and the Activity Endpoint Profile (AEP) the BES/JSDL extensions meet the PGI requirements. Profiled JSDL extensions and their corresponding additions to BES factory attributes include: incorporation of GLUE2 [] compute resource properties, arbitrary name/value pair matching parameters, additional file system types, and richer file staging options. The profiled BES extensions include a substate model with a set of "Held" substates and pre-and-post-processing substates, a "ResumeActivities" porttype, and clarified JSDL mechanism to subscribe to notifications. The document is nearing completion. Areas in YELLOW need discussion and decision. Document 2: BES Directory Profile The BES Directory Profile (BDP) is a profile on OGSA Basic Execution Services 1.0 that provides a Unix directory like interface to OGSA BES endpoints that allow the client to examine and modify BES configuration information as well as list, create, and terminate activities. The profile defines no port-types; rather it simply describes what directory elements MUST exist in a compliant implementation and what the semantics are of interacting with those entries. The goal is to provide a simple uniform mechanism to support requirements identified by the Production Grid Interoperability Working Group of the Open Grid Forum [cite]. The mechanism described for the BDP is independent of the OGSA BES specification. Thus, changes in the OGSA BES specification in the future will not impact the usefulness of the BDP. Document 3: Activity Endpoint Profile The Activity Endpoint Profile is a profile on the EndPointReference returned by an OGSA Basic Execution Services CreateActivity call. It defines port-types that the endpoint must support, and values that MUST be returned from calls and values that MAY be returned. The goal is to provide a uniform mechanism to support requirements identified by the Production Grid Interoperability Working Group of the Open Grid Forum [cite].

2 1