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
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
The gCube Platform is a Software Platform for the implementation and servicing of Virtual Research Environments based on the Service Oriented Paradigm.
dCache provides a system for storing and retrieving huge amounts of data, distributed among a large number of heterogenous server nodes, under a single virtual filesystem tree with a variety of standard access methods. Depending on the Persistency Model, dCache provides methods for exchanging data with backend (tertiary) Storage Systems as well as space management, pool attraction, dataset replication, hot spot determination and recovery from disk or node failures. Connected to a tertiary storage system, the cache simulates unlimited direct access storage space. Data exchanges to and from the
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
GriF is a SOA Grid Framework aimed at running on the EGI Grid multi-purpose scientific applications. The SOA-based organization of GriF consists of two JAVA servers (YR and YP) and a JAVA client (YC). The first server YR (Yet a Registry) is based on the standard UDDI (Universal Description, Definition, and Integration) protocol. Users inspect YR to the end of finding the appropriate YPs. The second server YP (Yet a Provider) makes use of the Simple Object Access Protocol (SOAP) which is the XML-based messaging format established as transmission framework for inter-service communication via HTT
The Advanced Resource Connector (ARC) middleware integrates computing resources (usually, computing clusters managed by a batch system or standalone workstations) and storage facilities, making them available via a secure common Grid layer. In the past this middleware was called NorduGrid middleware, since it is being developed by the NorduGrid Collaboration. This software solution uses Grid technologies to enable sharing and federation of computing and storage resources distributed across different administrative and applica