JRA1 Contribution to CHEP06

→ Europe/Zurich
Mumbai

Mumbai

  • Monday 13 February
    • 09:00 → 12:00
      Data Management
      • 09:00
        The gLite File Transfer Service 15m
        In this paper we describe the architecture and implementation of the gLite File Transfer Service (FTS) and list the most basic deployment scenarios. The FTS is addressing the need to manage massive wide-area data transfers on dedicated network channels while allowing the involved sites and users to manage their policies. The FTS manages the transfers in a robust way, allowing for an optimized high throughput between storage systems. The FTS can be used to perform the LHC Tier-0 to Tier-1 data transfer as well as the Tier-1 to Tier-2 data distribution and collection. The storage system peculiarities can be taken into account by fine-tuning the parameters of the FTS managing a particular channel. All the manageability related features as well as the interaction with other components that form part of the overall service are described as well. The FTS is also extensible so that particular user groups or experiment frameworks can customize its behavior both for pre- and post-transfer tasks.
        Speaker: Gavin McCance (CERN)
      • 09:15
        The gLite File Transfer Service: Middleware Lessons Learned from the Service Challenges 15m
        In this paper we report on the lessons learned from the Middleware point of view while running the gLite File Transfer Service (FTS) on the LCG Service Challenge 3 setup. The FTS has been designed based on the experience gathered from the Radiant service used in Service Challenge 2, as well as the CMS Phedex transfer service. The first implementation of the FTS was put to use in the beginning of the Summer 2005. We report in detail on the features that have been requested following this initial usage and the needs that the new features address. Most of these have already been implemented or are in the process of being finalized. There has been a need to improve the manageability aspect of the service in terms of supporting site and VO policies. Due to different implementations of specific Storage systems, the choice between 3rd party gsiftp transfers and SRM-copy transfers is nontrivial and was requested as a configurable option for selected transfer channels. The way the proxy certificates are being delegated to the service and are used to perform the transfer, as well as how proxy renewal is done has been completely reworked based on experience. A new interface has been added to enable administrators to perform Channel Management directly by contacting the FTS, without the need to restart the service. Another new interface has been added in order to deliver statistics and reports to the sites and VOs interested in useful monitoring information. This is also presented through a web interface using javascript. Stage pool handling for the FTS is being added in order to allow pre-staging of sources without blocking transfer slots on the source and also to allow the implementation of back-off strategies in case the remote staging areas start to fill up.
        Speaker: Paolo Badino (CERN)
    • 09:00 → 12:00
      JRA1-UK
      • 09:00
        Multiple Virtual Databases to support multiple VOs in R-GMA 15m
        R-GMA is a relational implementation of the GGF's Grid Monitoring Architecture (GMA). In some respects it can be seen as a virtual database (VDB), supporting the publishing and retrieval of time-stamped tuples. The scope of an R-GMA installation is defined by its schema and registry. The schema holds the table definitions and, in future, the authorization rules. The registry holds a list of the available producers and consumers. At present, while it is possible to have multiple installations, a user can only use one at a time and hence cannot access tables in another installation. We plan to introduce multiple VDBs, where each VDB is defined by its own registry and schema. In this paper we explain the basic idea of R-GMA, why we need multiple VDBs to support multiple VOs, and how we will implement them. We also discuss the possible need to create some VDBs not related to end-user VOs. We also explain why we do not plan to provide a catalogue of VDBs as a part of R-GMA.
        Speaker: Antony J Wilson (RAL)
    • 12:00 → 15:00
      IT-CZ cluster
      • 12:00
        CREAM: A Web Service-based Job Management System for Grids 15m
        Efficient and robust system for accessing computational resources and managing job operations is a key component of any Grid framework designed to support large distributed computing environment. CREAM (Computing Resource Execution And Management) is a simple, minimal system designed to provide efficient processing of a large number of requests for computation on managed resources. Requests are accepted from distributed clients via a web-service based interface. The CREAM architecture is designed to be a robust, scalable and fault tolerant service of a Grid middleware. In this paper we describe the CREAM architecture and the provided functionality. We also discuss how CREAM is integrated within the EGEE gLite middleware in general, and with the gLite Workload Management System in particular.
        Speaker: TBD
      • 12:15
        Flexible job submission using Web Services: the gLite WMProxy experience 15m
        Contemporary Grids are characterized by a middleware that provides the necessary virtualization of computation and data resources for the shared working environment of the Grid. In a large-scale view, different middleware technologies and implementations have to coexist. The SOA approach provides the needed architectural backbone for interoperable environments, where different providers can offer their solutions without restricting users to just one specific implementation. The WMProxy (Workload Manager Proxy) is a new service providing access to the gLite Workload Management System (WMS) functionality through a simple Web Services based interface. The WMProxy was designed to efficiently handle a large number of requests for job submission and control to the WMS and the service interface addresses the Web Services and SOA architecture standards, in particular adhering to the WS-Interoperability basic profile. In this paper we describe the WMProxy service: from its architecture, independent from the used Web Services container, up to the provided functionality, all together with the rationale behind the decisions made during both the design and implementation phases. In particular, we provide a description of how the WMProxy is integrated with the gLite Workload Management System; the used technologies, focusing on the Web Services features; the mechanisms adopted to improve performances still keeping high reliability and fault-tolerance; the changes in the job submission operation chain with respect to the previous generation of Workload Management System and the new operations provided in order to support bulk-submission and improve Client-Server interaction capabilities.
        Speaker: Giuseppe Avellino (Datamat SpA)