SciencePAD is currently in its early design and prototyping phase. Most of the functionality of this site is under development and it is not as automated or user friendly as we plan it to be for the final production version. Your contributions to the site with new registrations of users, organizations, collaborations and software, comments and new ideas are warmly welcome. For more information make sure to check the current SciencePAD Roadmap
SAM is a grid monitoring and reporting system for large-scale production grids.
It builds on top of open-source components such as
The EMI X.509 Common Authentication Library provides support for:
• off-line certificate validation,
• creation of SSL sockets (both server and client side),
• handling certificate DNs, also in text format,
• usage of proxy certificates: from proxy generation to validation.
The library provides implementation of an easy to use and flexible validation logic, which can take advantage of different trust material sources. Proxy certificates, which are commonly
GridSite was originally a web application developed for managing and formatting the content of the GridPP website. It has further grown into a set of extensions to the Apache web server and a toolkit for Grid credentials, GACL access control lists and HTTP(S) protocol operations. In its simplest application, GridSite uses X.509 certificates loaded into unmodified versions of web browsers like Internet Explorer, Netscape or Mozilla to authenticate users, and then grant
StoRM (STOrage Resource Manager) is a:
Logging and Bookkeeping (LB for short) is a Grid service that keeps a short-term trace of Grid jobs and other grid-related processes as they are processed by individual Grid components. The LB was initially developed in the EU DataGrid project as a part of the Workload Management System (WMS). The development continued in the EGEE project (EGEE-II, EGEE-III respectively), where LB became an independent part of the gLite middleware. Currently we are participating in the EMI project ( see LB status in EMI, gLite Logging and Bookkeeping Product Team).
GFAL2 is a framework for Grid and Cloud file access, file transfer and file management.
The GFAL 2.0 library :
The GFAL 2.0 library (gfal2-core) provides a unified and protocol-generic API for file access, file transfer and file management operations in Grid and Cloud environments. GFAL 2.0 allows to build applications using the Grid technologies ( file, GridFTP, RFIO, Dcap, SRM, LFC, Http/Dav, xrootd ) in a transparent manner.
The GFAL 2.0 transfer library:
The GFAL 2.0 transfer library (gfal2-transfer) is an addit
FTS is the service responsible for distributing the majority of LHC data across the WLCG infrastructure. It is a low level data movement service, responsible for moving sets of files from one site to another while allowing participating sites to control the network resource usage. This control includes the enforcement of site and usage policies like fair-share mechanisms on dedicated network links.
Computing Resource Execution and Management (CREAM) is a simple and lightweight system designed for efficiently manage a Computing Element (CE) in a Grid environment. It provides a well defined set of job management functionalities exposed as WebService interfaces which, together with the adoption of the open standards, guarantee a high degree of interoperability. Moreover its architecture has been designed to make CREAM a robust, scalable and fault tolerant Grid service for serving the requests coming from either a single users or a high level Grid Services. CREAM is part of the gLite midd
YAIM (YAIM Ain't an Installation Manager) is, as the name suggests, a way of configuring Grid Services. The aim of YAIM is to provide a simple installation and configuration method that can be used to set up a simple Grid Site but can be easily adapted and extended to meet the need of larger sites. To ensure that local administrators can adapt YAIM, it has been implemented as a set of bash scripts. To support th
A Federated Service Endpoint Registry conceived during the EMI project. Its main goal is to discover all the Service Endpoints that exist. It consists of a collection of services that enables storing service records in a federated manner. Each of the record contains Service Endpoint Record (SER) according to the GLUE 2.0 standard. The deployment of EMIR (which implies building an EMIR network over WAN) is bipartite: 1) Building a rooted hierarchy with a single EMIR server aggregating all the information within a federation 2) Sharing the information at the root level among peered EMIR servers