Changes between Version 35 and Version 36 of main_old

Timestamp:

05/12/11 13:40:27 (13 years ago)

Author:

bartek

Comment:

--

main_old

@@ -2 +2 @@
 
 = !QosCosGrid =
-== Introduction ==
-!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.
+The !QosCosGrid (QCG) middleware is an integrated e-infrastructure offering advanced job and resource management
+capabilities to deliver to end-users supercomputer-like performance and structure. By connecting many computing
+clusters together, QosCosGrid offers easy-to-use mapping, execution and monitoring capabilities for variety of
+applications, such as parameter sweep, workflows, MPI or hybrid MPI-OpenMP. Thanks to QosCosGrid, large-scale and
+complex computing models written in Fortran, C, C++ or Java can be automatically distributed over a network of
+computing resources with guaranteed Quality of Service. Consequently, applications can be run at given periods of time,
+their execution time and waiting times can be reduced, and thus bigger problem instances can be considered.
 
-=== QCG Middleware ===
+== QCG Middleware ==
 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. 
 
@@ -13 +18 @@
 [[Image(QCG-Architecture-v4.png, center, width=700px)]]
 
-=== End-user Information ===
+== End-user Information ==
 The demanding nature of scientific simulations requires a new e-Infrastructure that is able to simultaneously manage heterogeneous resources, such as computing resources, storage and network to guarantee the level of Quality of Service 
 (QoS) required by end-users for their applications, especially a large number of legacy applications designed to run in parallel. Addressing the need of end-users to run large scale complex simulations we have built a system capable to bring supercomputer-like performance for advanced applications, including sophisticated parameter sweep experiments, 
 workflows, and more importantly cross-cluster parallel computations. For high-level end-users we provide a QCG Science Gateways, the components offering an easy access to concrete applications. If you are interested in using QCG as a user see this [[user_information|section]].
 
-=== Developer & Admin Information ===
+== Developer & Admin Information ==
 !QosCosGrid provides a consistent environment for creating and deploying Grid applications. It is also relatively easy to install, configure and maintain. Developers of new applications and administrators should look at this [[developer_and_admin_information|section]] for more details.
 
-=== Community ===
+== Community ==
+
 == News ==
-==== !QosCosGrid in Mapper ====
-It was decided to use !QosCosGrid middleware to multi-scale computations in a Mapper project. Installation at production sites in Europe, including EGI and PRACE machines, are currently beeing discussed.
+'''!QosCosGrid in Mapper'''
 
-==== !QosCosGrid middleware deployed in PL-Grid ====
-!QosCosGrid was successfully deployed on the PL-Grid infrastructure in Poland. Currently the QCG middleware is available in Poznan Supercomputing and Networking Center as well as in Cyfronet in Krakow. Further deployment are planned.
+''April 2011''
 
-==== !QosCosGrid project page moved ====
-After the end of !QosCosGrid project, the old www.qoscosgrid.org page was moved to the archive. It is still possible to access the old site at the following address /Link/. The new page is strictly related to QosCosGrid middleware and further QosCosGrid sollutions. 
+It was decided to use !QosCosGrid middleware to multi-scale computations in a Mapper project. Installations of QosCosGrid middleware at production sites in Europe, including EGI and PRACE machines, are currently beeing discussed.
+
+'''!QosCosGrid middleware deployed in PL-Grid'''
+
+''March - April 2011''
+
+!QosCosGrid was successfully deployed on the PL-Grid infrastructure in Poland. Currently the QCG middleware is available in Poznan Supercomputing and Networking Center as well as in AGH Cyfronet in Krakow. Further deployment are planned.
+
+'''!QosCosGrid project page moved'''
+
+''2010''
+
+After the end of !QosCosGrid project, the old www.qoscosgrid.org page was moved to the archive. It is still possible to access the old site at the following address /Link/. The new page is strictly related to !QosCosGrid middleware and further !QosCosGrid sollutions. 
 
 == Download & Install ==
+For !QosCosGrid packages and installation istructions go to the [[download|Download]] section. 
+
 == Interoperability & standards supported ==
+The !QosCosGrid implementation is based only on the open standards. In general, QosCosGrid supports OGF DRMAA, JSDL, BES, HPC Profile and OASIS WS-Notification.
+
 == Publications & Talks
-
-
-
-
-
-
-