Changes between Version 49 and Version 50 of main_old

Show
Ignore:
Timestamp:
05/12/11 17:32:58 (12 years ago)
Author:
bartek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • main_old

    v49 v50  
    3636 
    3737== QCG Middleware == 
     38=== Main features === 
     39* the most efficient remote access to computational resources in a single cluster or many clusters in Poland and Europe, 
     40* automatic steering of various types of complex computing experiments ranging from multi-parameter sweep studies to cross-cluster executions of parallel applications, 
     41* fully transparent integration with parallel programming and execution environments like OpenMPI and ProActive located on many computing clusters, 
     42* support for Quality of Service (e.g. start time) based on advance reservation mechanisms, 
     43* shorter waiting times and improved resource utilization by hierarchical grid- and local-level job scheduling, 
     44* management of input and output files in distributed computing clusters, 
     45* efficient integration between services and queuing systems ensuring high performance and reliability of the overall system, 
     46* extensible, open and standard based architecture supporting OGF DRMAA, JSDL, BES and HPC Profile with pluggable modules, 
     47* secure communication channels using transport level (SSL/TLS, X.509) and message level (SAML2.0) mechanisms, 
     48* delivered together with command-line, graphical, web-based or even mobile phone tools for end users and administrators, 
     49* fast and reliable installation procedures. 
     50 
     51[[Image(QCG-Architecture-v4.png, center, width=700px)]] 
     52 
    3853In a nutshell, the !QosCosGrid middleware consists of two logical levels: grid domain and administrative domain. Grid-level services control, schedule and generally supervise the execution of end-users applications, which are spread between independent administrative domains. The administrative domain represents a single resource provider (e.g. HPC or datacenter) participating in a certain Grid or Cloud environment by sharing its computational resources, e.g. computing clusters, with both local and external end-users. The logical separation of administrative domains corresponds with the fact that they are possessed by different institutions or resource owners. Each institution contributes its resources for the benefit of the entire Grid or Cloud, while controlling its own administrative domain and own resource allocation/sharing policies.  
    3954 
    4055The key component of every administrative domain in !QosCosGrid is the [[QCG_BES|QCG BES/AR service]], which gives the  
    41 remote access to queuing systems resources. QCG BES/AR supports advance reservations, parallel execution environments - OpenMPI, !ProActive and MUSCLE with coordinators responsible for synchronization of cross-cluster executions (see [[QCG_libraries_and_cross-cluster_communication|Cross-cluster communication]]) and [[QCG_DataMovement|QCG Data Movement services]] for managing input and output data. The another relevant service at the administrative domain is in charge of notification mechanism and it is called [[QCG_Notification|QCG Notification]]. These services are tightly integrated and connected to the Grid-level services. The critical service on that level is [[QCG_Broker|QCG Broker]], which is a meta-scheduling framework controlling executions of applicaitons on the top of queuing systems via QCG BES/AR services. !QosCosGrid architecture is depicted in the figure presented below. 
    42  
    43 [[Image(QCG-Architecture-v4.png, center, width=700px)]] 
     56remote access to queuing systems resources. QCG BES/AR supports advance reservations, parallel execution environments - OpenMPI, !ProActive and MUSCLE with coordinators responsible for synchronization of cross-cluster executions (see [[QCG_libraries_and_cross-cluster_communication|Cross-cluster communication]]) and [[QCG_DataMovement|QCG Data Movement services]] for managing input and output data. The another relevant service at the administrative domain is in charge of notification mechanism and it is called [[QCG_Notification|QCG Notification]]. These services are tightly integrated and connected to the Grid-level services. The critical service on that level is [[QCG_Broker|QCG Broker]], which is a meta-scheduling framework controlling executions of applicaitons on the top of queuing systems via QCG BES/AR services. 
    4457 
    4558== End-user Information ==