[wg-all] New documents published

Below are details for GFD #176-181. Thanks to all the groups involved in their production, and thanks to the OGF for public comments. All OGF documents (including a few that are open for public comment!) may be found here: http://www.ogf.org/gf/docs/ * GFD.181 "OGF-Production Grid Infrastructure: Glossary of Acronyms and Terms, Version 1.0." E. Urbah, via PGI-WG Abstract: The Production Grid Infrastructure Working Group (PGI-WG) is elaborating documents permitting to improve interoperability of Production Grids. The purpose of this ‘Glossary of Acronyms and Terms’ is to provide an expansion of acronyms and an unambiguous definition of terms used in the context of a Production Grid. It is based on the ‘OGSA® Glossary of terms’ GFD.120, the ‘GLUE Specification v. 2.0’ GFD.147 and the PGI ‘Vocabulary’ Wiki page. The root terms are ‘Data processing’, ‘Administrative domain’, ‘Trust’ and ‘Federation’. It provides a minimum background information about Grids, but does NOT attempt to justify the definitions or the context in which they may be used. The reader is referred to external documents for further explanation where necessary. * GFD.180 "OGF-Production Grid Infrastructure: Use Case Collection, Version 1.0." M. Riedel, J. Watzl, via PGI-WG Abstract: The Production Grid Infrastructure (PGI) working group works on a well-defined set of standard profiles, and additional standard specifications if needed, for job and data management that are aligned with a Grid security and information model that addresses the needs of production Grid infrastructures. These needs have been identified in various international endeavors and are in many cases based on lessons learned obtained from the numerous activities in the Grid Interoperation Now (GIN) community group. Therefore, PGI can be considered as a spin-off activity of the GIN group in order to feed back any experience of using early versions of open standards (e.g. BES, JSDL, SRM, GLUE2, UR, etc.) in Grid production setups to improve the standards wherever possible. This particular document is a survey of common use cases provided by different stakeholders of PGI profiles or standard specifications. Such stakeholders include production Grid and e-science infrastructures as well as technology providers. The goal of this document is to have a foundation for a set of important requirements to be addressed by the PGI set of profiles and/or specifications. * GFD.179 "Smoa Computing HPC Basic Profile Adoption – Experience Report." M. Mamonski, via HPCP-WG, OGSA-BES-WG Abstract: This document describe experience gained while implementing the Smoa Computing Service, a component which development was steered by the following OGF specifications: * GFD 108 - OGSA® Basic Execution Service Version 1.0 * GFD.114 - HPC Basic Profile, Version 1.0 * GFD.135 - HPC File Staging Profile, Version 1.0 In addition to comments on those specifications, this document presents possible extension to the Basic Execution Service: a separate interface for managing Advance Reservations based on the BES-Factory port. * GFD.178 "SAGA API Extension: Message API." A. Merzky, via SAGA-WG Abstract: This document specifies a Message API extension to the Simple API for Grid Applications (SAGA), a high level, application-oriented API for grid application development. This Message API is motivated by a number of use cases collected by the OGF SAGA Research Group in GFD.70, and by requirements derived from these use cases, as specified in GFD.71). The API provides a wide set of communication pattern, and targets widely distributed, loosely coupled, heterogeneous applications. * GFD.177 "SAGA API Extension: Advert API." A. Merzky, via SAGA-WG Abstract: This document specifies an Advert API extension to the Simple API for Grid Applications (SAGA), a high level, application-oriented API for grid application development. This Advert API is motivated by a number of use cases collected by the OGF SAGA Research Group in GFD.70, and by requirements derived from these use cases, as specified in GFD.71). It allows to persistently store application specific meta data in a name space hierarchy, along with serialized saga::object instances. * GFD.176 "Experiences with Implementing the SAGA Core API." M. den Burger, M. Franceschini, M. Illingworth, C. Jacobs, S. Jha, H. Kaiser, T. Kielmann, A. Merzky, R. van Nieuwpoort, S. Reynaud, O. Weidner, via SAGA-WG Abstract: This document specifies a Message API extension to the Simple API for Grid Applications (SAGA), a high level, application-oriented API for grid application development. This Message API is motivated by a number of use cases collected by the OGF SAGA Research Group in GFD.70, and by requirements derived from these use cases, as specified in GFD.71). The API provides a of communication pattern, and targets widely distributed, loosely coupled, heterogeneous applications. With best wishes for a productive OGF31 in Taipai, Greg Newby, OGF Editor Dr. Gregory Newby, Chief Scientist of the Arctic Region Supercomputing Center Univ of Alaska Fairbanks-909 Koyukuk Dr-PO Box 756020-Fairbanks-AK 99775-6020 e: newby AT arsc.edu v: 907-450-8663 f: 907-450-8603 w: www.arsc.edu/~newby