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

Both sides previous revision Previous revision
Next revision
Previous revision
documentation:release_5.14:ia [ - 2013/02/15, 13:24 - ]
Eduardo Huedo
documentation:release_5.14:ia [ - 2015/03/09, 12:58 - ] (current)
Line 4: Line 4:
 **Figure 1.Components of the GridWay Meta-scheduler.** **Figure 1.Components of the GridWay Meta-scheduler.**
  
- +{{ :documentation:​administrator:​gw_arch.png?​350 ​|Components of the GridWay Meta-scheduler.}}\\
- +
-{{ documentation:​administrator:​gw_arch.jpg |Components of the GridWay Meta-scheduler.}}\\ +
  
 GridWay 5 architecture consists of the following components: GridWay 5 architecture consists of the following components:
  
-  * //User Interface// provides the end user with DRM-like commands to submit, kill, migrate, monitor and synchronize jobs and includes DRMAA (Distributed Resource Management Application API) GGF (Global ​Grid Forum) standard support to develop distributed applications (C and JAVA bindings). +  * //User Interface// provides the end user with DRM-like commands to submit, kill, migrate, monitor and synchronize jobs and includes DRMAA (Distributed Resource Management Application API) OGF (Open Grid Forum) standard support to develop distributed applications (C and Java bindings). 
-  * //GridWay core// is responsible for job execution management and resource brokering, providing advanced scheduling, and job failure & recovery capabilities. The Dispatch Manager performs all submission stages and watches over the efficient execution of the job. The Information Manager, through its MADs (Middleware Access Driver), is responsible for host discovery and monitoring. The Execution Manager, through its MADs, is responsible job execution and management. The Transfer Manager, through its MADs, is responsible for file staging, remote working directory set-up and remote host clean-up.+  * //GridWay core// is responsible for job execution management and resource brokering, providing advanced scheduling, and job failure & recovery capabilities. 
 +    * The Dispatch Manager performs all submission stages and watches over the efficient execution of jobs. 
 +    * The Information Manager, through its MADs (Middleware Access Driver), is responsible for host discovery and monitoring. 
 +    * The Execution Manager, through its MADs, is responsible job execution and management. 
 +    * The Transfer Manager, through its MADs, is responsible for file staging, remote working directory set-up and remote host clean-up
 +  * Several //​Middleware Access Drivers// interface with Discovery and Monitoring, Job Management and Data Management services available in the Grid infrastructure.
   * //​Scheduler//​ makes scheduling decisions for jobs on available resources.   * //​Scheduler//​ makes scheduling decisions for jobs on available resources.
-  * //​Information Manager MAD// interfaces with the monitoring and discovering services available in the Grid infrastructure. 
-  * //Execution Manager MAD// interfaces with the Job Management Services available in the Grid resources. 
-  * //Transfer Manager MAD// interfaces with the Data Management Services available in the Grid resources. 
- 
Admin · Log In