Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • UCC - Command line client
  • UNICORE Rich Client
    • Eclipse-based UNICORE Rich Client (URC) offers the full set of functionalities functionality to the users in a graphical representation. 
    • Uses GridBeans for interacting with Grid Services
    • Download: http://www.unicore.eu/download/unicore6/
  • HiLA - High Level API for Grid Applications
    • This is a layer of abstraction for use with web clients, but it might provide a way to either run jobs directly from the current Ergo architecture or for building DataWolf (Cyberintegrator) Java tools to run jobs
    • Download:  http://www.unicore.eu/download/unicore6/

...

  • Open Grid Forum (OGF)
  • World Wide Web Consortium (W3C)
  • Advancing Open Standards for the Information Society (OASIS)
  • IETF
  • Open Grid Services Architecture (OGSA) - a distributed interaction and computing architecture based around services, assuring interoperability on hetergenous systems so that different types of resources can communicate and share information. OGSA is based on several other web service technologies such as the Web Services Description Language (WSDL) and the Simple Object Access Protocol (SOAP), but it aims to be largely independent of transport-level handling of data.
  • Web Services Resource Framework (WS-RF 1.2)
  • Job Specification Description Language 1.0 - describes the requirements of computational jobs for submission to resources, particularly in Grid Environments, though not restricted to the Grid.
    • Reference
    • XML based language
    • Widely adopted Adopted by several software platforms - compatible with UNICORE 6, Genesis II, Windows HPC Server 2008, etc
    • Not intended for human consumption

...

  • Globus Toolkit - an open source software toolkit used for building grids that follows OGSA standards
  • Simple API for Grid Applications (SAGA) - an abstractions-based suite of well-defined capabilities that are architected for scalable, interoperable and sustainable approaches to support science on a range of high-performance and distributed computing systems

Questions

  1. What are the target resources to be considered? We should pick one or more current and/or upcoming HPC systems that ERGO must be able to submit to so we can determine if a common standard is used across the systems (e.g. do multiple target systems have client libraries supporting JSDL).