Changes between Version 26 and Version 27 of components

Show
Ignore:
Timestamp:
06/14/11 11:59:01 (9 years ago)
Author:
bartek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • components

    v26 v27  
    2020  <area shape="rect" alt="Cross-cluster communication" href="http://www.qoscosgrid.org/trac/qcg/wiki/QCG_libraries_and_cross-cluster_communication" target="http://www.qoscosgrid.org/trac/qcg/wiki/QCG_libraries_and_cross-cluster_communication" title="Cross-cluster communication" coords="34,272,604,319"> 
    2121  <area shape="rect" alt="QCG Science Gateways" href="http://www.qoscosgrid.org/trac/qcg/wiki/user_information#QosCosGridScienceGateways" target="http://www.qoscosgrid.org/trac/qcg/wiki/user_information#QosCosGridScienceGateways" title="QCG Science Gateways" coords="236,64,404,149"> 
    22   <area shape="rect" alt="QCG Data Movement" href="components#QCG_DataMovement" target="components#QCG_DataMovement" title="QCG Data Movement" coords="457,224,523,264"> 
    23   <area shape="rect" alt="QCG Data Movement" href="components#QCG_DataMovement" target="components#QCG_DataMovement" title="QCG Data Movement" coords="111,224,178,264"> 
     22  <area shape="rect" alt="QCG Data Movement" href="components#DataMovement" target="components#DataMovement" title="QCG Data Movement" coords="457,224,523,264"> 
     23  <area shape="rect" alt="QCG Data Movement" href="components#DataMovement" target="components#DataMovement" title="QCG Data Movement" coords="111,224,178,264"> 
    2424  <area shape="rect" alt="QCG Broker" href="components#QCG-Broker" target="components#QCG-Broker" title="QCG-Broker" coords="255,182,383,221"> 
    2525  <area shape="rect" alt="QCG-Computing" href="components#QCG-Computing" target="components#QCG-Computing" title="QCG-Computing" coords="469,109,598,148"> 
     
    3333In 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.  
    3434 
    35 The key component of every administrative domain in !QosCosGrid is the [[components#QCG-Computing|QCG-Computing]], which gives the remote access to queuing systems resources. QCG-Computing 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 [[components#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 [[components#QCG-Notification|QCG-Notification]]. These services are tightly integrated and connected to the Grid-level services. The critical service on that level is [[components#QCG-Broker|QCG-Broker]], which is a meta-scheduling framework controlling executions of applicaitons on the top of queuing systems via QCG-Computing services. 
     35The key component of every administrative domain in !QosCosGrid is the [[components#QCG-Computing|QCG-Computing]], which gives the remote access to queuing systems resources. QCG-Computing 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 [[components#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 [[components#QCG-Notification|QCG-Notification]]. These services are tightly integrated and connected to the Grid-level services. The critical service on that level is [[components#QCG-Broker|QCG-Broker]], which is a meta-scheduling framework controlling executions of applicaitons on the top of queuing systems via QCG-Computing services. 
    3636 
    3737= QCG-Computing =