You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Introduction

This page will provide a high level overview of different grid standards for the service layer of each system identified as a site that Ergo will nee to communicate with to run jobs. For the service layer of each system, some brief introduction will be provided and for more detailed information, follow the links to the different standards mentioned.

Unicore

Service Layer

More information about the Unicore service layer can be found here:  http://www.unicore.eu/unicore/architecture/service-layer.php

UNICORE/X

  • UNICORE/X server is a WSRF compliant web service, it provides access to storage resources, file transfer services and job submission and management services.
    • UNICORE has a proprietary set of web service interfaces called UNICORE Atomic Services (UAS). It offers a complete, integrated set of basic services to higher level services, clients and users
    • Standardised set of interfaces based on open, common standards (OGSA-*) is available in UNICORE 6 in addition to UAS. Currently implemented standards are OGSA-BES and HPC-P, used for the creation, monitoring, and control of jobs
  • UNICORE Job definition is compliant with the JSDL (+ JSDL HPC extensions) standard. For file transfers (site to site and client to site), a variety of protocols are available (HTTPS, OGSA Byte-IO, UFTP, GridFTP and UDT)
  • For user authorization, UNICORE/X can use a variety of attribute resources such as XUUDB, UVOS or flat files. The actual authorization engine uses XACML 2.0 policies. Full X.509 certificates are used as a base line. Proxy certificates are optionally supported in UNICORE 6 (e.g. to use GridFTP)
  • UNICORE's internal execution management engine and link to the system layer is called XNJS



IDB

XUUDB

UVOS

Registry

CIS

Workflow Engine

Service Orchestrator

 

  • No labels