Home About Software Documentation Support Outreach Ecosystem Blog Dev Awards Team & Sponsors

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

about:functionality:deploy [ - 2015/03/09, 12:58 - ] (current)
Line 1: Line 1:
 +====== D. Installation & Configuration Issues ======
 +
 +
 +===== D.1. Modular Architecture =====
 +
 +
 +**Description:​**
 +
 +    * Adaptation to different grid infrastructures.
 +
 +**Support in Last Release:**
 +
 +    * GridWay modular architecture allows communication with the resource management, file management and information services available in a given infrastructure. In fact, it could be extended or used as a building block for more complex architectures that implements service-level agreements (SLAs) or advanced reservation.
 +
 +===== D.2. Requirements on Core Grid Services =====
 +
 +
 +**Description:​**
 +
 +    * Services required apart from Globus basic services.
 +
 +**Support in Last Release:**
 +
 +    * The GridWay framework is a light component for meta-scheduling in the Grid Ecosystem intended for end users and grid application developers. GridWay is an execution management tool for use with the Globus Toolkit. The GW framework is installed on the client system and does not require the installation or deployment of new services in the remote resource, apart from Globus services.
 +
 +===== D.3. Supported Remote Services =====
 +
 +
 +**Description:​**
 +
 +    * A grid meta-scheduler manages resource managers that coordinate and control local resources, mainly dedicated and non-dedicated clusters and servers; performs file transferring and requires access to information services.
 +
 +**Support in Last Release:**
 +
 +    * GW interfaces to remote resources through Globus GRAM. So it supports the remote platforms and resource managers (fork, PBS, SGE, LSF, LoadLeveler and Condor) compatible with Globus. GW is able to harness pre-WS GRAM (from GT 2.4), WS GRAM (GT4.0) and LCG resources, even simultaneously.
 +    * GW provides transfer management drivers for GridFTP and RFT.
 +    * GW includes information drivers for MDS 2.0 and MDS 4.0, both the default and the GLUE scheme.
 +    * GW modular approach allows the development of drivers for new grid managers and the easy development of interfaces to new grid infrastructure information services.
 +
 +===== D.4. Supported Client Platforms =====
 +
 +
 +**Description:​**
 +
 +    * Platforms where the meta-scheduler has been tested.
 +
 +**Support in Last Release:**
 +
 +    * Minimum installation requirements.
 +    * Installation based on auto-tools.
 +    * GW has been tested on Linux and Solaris platforms.
 +
 +===== D.5. Decentralized Architecture =====
 +
 +
 +**Description:​**
 +
 +    * Scalability and multiple administration domains prevent the deployment of centralized resource brokers, with total control over client requests and resource status.
 +
 +**Support in Last Release:**
 +
 +    * GW decentralized architecture gives the possibility of boosting scalability.
 +
 +===== D.6. Security =====
 +
 +
 +**Description:​**
 +
 +    * Security mechanisms that are supported.
 +
 +**Support in Last Release:**
 +
 +    * Multiple-user support.
 +    * Globus Toolkit GSI infrastructure.
 +    * Proxy renewal.
 +    * A global name space is not assumed.
 +
 +===== D.7. Meta-scheduling Infrastructure Scenarios =====
 +
 +
 +**Description:​**
 +
 +    * A single Grid scheduling strategy will not suit all infrastructure scenarios. See Grid Scheduling Infrastructures Based on GridWay Section.
 +
 +**Support in Last Release:**
 +
 +    * Single-user mode GridWay installation provides support for the deployment of user-level meta-scheduling infrastructures for partner grid computing.
 +    * Multiple-user mode GridWay installation provides support for the deployment of site-level meta-scheduling infrastructures for partner and enterprise grid computing.
  
Admin · Log In