Changes between Version 76 and Version 77 of main_old

Timestamp:

06/07/11 16:19:30 (14 years ago)

Author:

bartek

Comment:

--

main_old

@@ -71 +71 @@
 In 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. 
 
-The key component of every administrative domain in !QosCosGrid is the [[QCG_BES_AR|QCG BES/AR service]], which gives the 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.
+The key component of every administrative domain in !QosCosGrid is the [[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 [[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-Computing services.
 
 == End-user Information ==