Changes between Version 24 and Version 25 of main_old

05/12/11 08:32:25 (12 years ago)



  • main_old

    v24 v25  
    33= !QosCosGrid = 
     4== Introduction == 
    45!QosCosGrid could be viewed as a ''quasi-opportunistic supercomputer'' whose computational performance exceeds the power offered by a single supercomputing or data center. !QosCosGrid is designed as a multi-layered architecture that is capable of dealing with computationally intensive large-scale, complex and parallel simulations that are usually too complex to run within a single computer cluster or machine. The !QosCosGrid middleware enables computing resources (at the level of processor cores) from different administrative domains to be combined into a single powerful computing resource via Internet. Clearly, bandwidth and latency characteristics of the Internet may have an affect on overall application performance of !QosCosGrid-enabled applications. However, the ability to connect and efficiently control advanced applications executed in parallel over the Internet is a feature that is highly appreciated by !QosCosGrid users. 
     7=== QCG Middleware === 
     8In 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  
     9benefit of the entire Grid or Cloud, while controlling its own administrative domain and own resource allocation/sharing policies 
    611The !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. 
    2530Additional services were required in order to support the spawning of parallel application processes on co-allocated computational resources. The main reason for this was that standard deployment methodologies used in OpenMPI and !ProActive relied on either RSH/SSH or specific local queuing functionalities. Both are limited to single-cluster runs (e.g., the SSH-based deployment methods are problematic if at least one cluster has worker nodes that have private IP addresses). Those services are called the coordinators and are implemented as Web services.  
     32=== End-user Information === 
     33=== Developer & Admin Information === 
     34=== Community === 
     35== News == 
     36== Download & Install == 
     37== Interoperability & standards supported == 
     38== Publications & Talks