Changes between Version 25 and Version 26 of main_old

Show
Ignore:
Timestamp:
05/12/11 08:37:15 (12 years ago)
Author:
bartek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • main_old

    v25 v26  
    66 
    77=== QCG Middleware === 
    8 In a nutshell, the QosCosGrid middleware consists of two logical levels: grid domain and administrative domain (AD) one. Grid-level services control, schedule and generally supervise the execution of end-users applications, which are spread between independent administrative domains. The Administrative domain (AD) represents a single resource provider (e.g. HPC or datacenter) participating in a certain Grid or Cloud environment by sharing its computational resources 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  
    9 benefit of the entire Grid or Cloud, while controlling its own administrative domain and own resource allocation/sharing policies 
     8In 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 
    109 
    1110The !QosCosGrid framework is highly flexible as it is composed of pluggable components that can be easily modified to support different scheduling and access policies to better maximize a diversity of utility functions. Furthermore, the framework exploits novel algorithms for topology-aware co-allocations that are required by parallel programming and execution set-ups in production-level high-performance computing environments, such as the Message Passing Interfaces (MPI), !ProActive, or their hybrid extensions linking programming models like OpenMP or CUDA.