Presentation on theme: "NorduGrid Grid Manager developed at NorduGrid project."— Presentation transcript:
NorduGrid Grid Manager developed at NorduGrid project
NorduGrid Grid Manager (essentials) The Target Provide job control and data handling functionality required by HEP applications. Limitation: Data is handled only at that beginning and end of the job. User must provide information about input and output data. Comparisons Globus gatekeeper Provides more functionality for controling job parameters and data handling EDG WP1 Moves part of Logging and Bookkeeping functionality from the centralized server. Hence gives better fault tolerance. Job is run in more restrictive environment (maybe not already??) No special requirements for working nodes of the cluster
NorduGrid Grid Manager (Globus is cornerstone) The Grid Manager is based on Globus Toolkit TM libraries and services. The following parts of Globus are used: GridFTP - fast and reliable data access for Grid GASS Copy interface - support for different data access protocols Replica Catalog - metadata storage GRAM - resource request (obsolete) RSL - expandable Resource Specification Language The advantages of using Globus: Widely accepted de-facto standard for Grid computing No need to develop low level services Security built in Continiously evolving (??)
NorduGrid Grid Manager (Functionality) Stage in input data and executables. Possible sources: Job submission machine GridFTP (preffered), FTP, HTTP or HTTPS servers Files registered in Globus Replica Catalog. Secure authentication. Destination is chosen automatically or can be forced. Stage out output data. Possible destinations: Keep on Grid cluster till user downloads GridFTP, FTP, HTTP or HTTPS servers Files can be registered in Globus Replica Catalog. Destination and protocol are obtained from Location information Email notification of job status changes Support for software runtime environment configuration Interface to the information about job (used by NorduGrid Information System)
NorduGrid Grid Manager (Things To Do) Better support for data handling: On-site data caching (preferably partial caching) On-site data sharing Better handling of failures More firewall friendly Better support for Local Resource Management System More flexible configuration suitable for demanding site managers Better support for running under non-root account Improve security More strict permissions Possible chroot environment
Your consent to our cookies if you continue to use this website.