1. I want to learn more about grids. Where can I get information about it?
   
2. What are the requirements?
   
3. Which are the GridWay features?
   
4. How do I get the GridWay releases?
   
5. How do I get help/provide feedback regarding this release?
   
6. Is GridWay's source code available?
   
7. What programming language have you used to code GridWay?
   
8. Is GridWay compatible with my operating system?
   
9. What are the plans for updates to GridWay?
   
10. Will be a Windows' version of GridWay in the near future?
    
11. Is GridWay compatible with EGEE?
    
12. What resource managers does the meta-scheduler integrate with?
    
13. What platforms are supported?
    
14. What security mechanisms are supported?
    
15. Does it support checkpoints and process migration?
    
16. Does it assume a global name space?
    
17. Can it coordinate data staging in addition to job scheduling?
    
18. What scheduling policies are provided?
    
19. What tools are provided to update existing policies or add custom policies?
    
20. Does it support dynamic policy updates?
    
21. Does it support parallel and serial job submission?
    
22. Does it support advanced reservation?
    
23. Does it support dynamic clients?
    
24. Does it support dynamic configuration changes?
    
25. Does it provide diagnostic tools?
    
26. Does it provide accounting of resource consumption?
    
27. What are the tested and supported configurations?
    
28. What documentation and training is available?
    
29. What is the license cost?
    
30. What type of service is available and at what cost?
    
31. What type of interface is provided for users, for administrators?
    

There are a lot of web pages about grids. Go to the Grid Cafe website.

Check the Installation and Configuration Guide.

Check the GridWay Functionality page or download the Flyer.

Go to the GridWay Download page.

Please go to the support page.

GridWay (from 4.7 release) is released as “open source” under the Apache license, version 2.0. Please go to the how-to-contribute page

GridWay is coded in ansi C, JAVA and shell scripts.

GridWay has been tested on Linux and Solaris.

Work continues on adding features and making improvements to GridWay.

GridWay uses Globus, the most similar to a Grid standard. Globus is not available for Windows at this time, so GridWay will only work on the same architectures as Globus does.

Yes. In EGEE, Globus behavior has been slightly modified, but it doesn't loose its main protocols and interfaces, so GridWay can be used in a standard way..

The following questions are the product-specific questions of the checklist for choosing a meta-scheduler proposed in IBM's article Grid in action: Managing the resource managers. Please visit the functionality page for more information.

GridWay 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.

The GridWay tool has been tested on Linux and Solaris platforms.

Globus Toolkit GSI infrastructure.

Yes, GridWay supports migration on-request and opportunistic migration User-level checkpointing or restarted architecture-independent files managed by the programmer must be implemented because system-level checkpointing is not possible among heterogeneous resources.

No, a global name space is not assumed.

Yes, GridWay allows unattended, reliable, and efficient file staging and execution of jobs, array jobs, or complex jobs consisting of task dependencies.

Last release provides state-of-the-art scheduling policies, comprising job prioritization policies (fixed priority, urgency, share, deadline and waiting-time) and resource prioritization policies (fixed priority, usage, failure and rank).

Last release includes a new scheduling module that allows the deployment of custom scheduling policies.

Yes, last release supports dynamic policy update.

Last version supports submission of both, serial jobs and MPI jobs.

Globus GRAM does not support advanced reservation.

Yes, GridWay performs all the job scheduling and submission steps transparently to the end user and adapts job execution to changing Grid conditions by providing fault recovery mechanisms, dynamic scheduling, migration on-request and opportunistic migration.

Yes, GridWay performs all the job scheduling and submission steps transparently to the end user and adapts job execution to changing Grid conditions by providing fault recovery mechanisms, dynamic scheduling, migration on-request and opportunistic migration.

Yes, GridWay provides commands to monitor the state and history of the submitted jobs. Last release includes a new command to show the static and dynamic attributes of the resources available in the infrastructure.

GridWay generates scheduling and job logging. Last release provides accounting of resource consumption (average execution and transfer times, failures…) and job type execution.

GridWay has been tested on infrastructures based on the Globus Toolkit, pre-WS (from GT2.4) to WS (from 4.0.x), and the LCG middleware. Please visit the success stories page in our web site to find out the grid infrastructure and projects where GW has been used as a production-level service.

Please visit the documentation section in our web site.

GridWay is free. The GridWay project is an open source development effort.

Please visit the contact us section in our web site.

GridWay provides a command line interface similar to that found on Unix and resource management systems such as PBS or SGE. It allows users to submit, kill, migrate, monitor and synchronize jobs, that could be described using the OGF standard JSDL. GridWay provides support for OGF standard DRMAA to develop distributed applications (C, JAVA, Perl, Ruby and Python bindings).