Changes between Version 50 and Version 51 of components
- Timestamp:
- 11/05/12 15:59:55 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
components
v50 v51 42 42 For more information see [[http://www.qoscosgrid.org/trac/qcg-computing|QCG-Computing Home Page]] 43 43 44 === QCG-Coordinator === 45 QCG-Coordinator supports the spawning of parallel application processes on co-allocated computational resources. Since the standard methodologies used in MPI or !ProActive are adjusted to run jobs only on a single machine, it was needed to provide additional entity to support multi-cluster runs. 46 47 For more information see [[http://www.qoscosgrid.org/trac/qcg-computing/QCG-Coordinator|QCG-Coordinator Home Page]] 48 44 49 === QCG-Notification === 45 50 QCG-Notification is an open-source implementation of the family of WS-Notification standards (version 1.3). In the context of !QosCosGrid, it is used to extend features provided by QCG-Computing by adding standards-based synchronous and asynchronous notification features. QCG-Notification supports the topic-based publish/subscribe pattern for asynchronous message exchange among Web services and other entities, in particular services or clients that want to be integrated with !QosCosGrid. The main part of QCG-Notification is based on a highly efficient, extended version of the !NotificationBroker, managing all items participating in notification events. Today, QCG-Notification offers sophisticated notification capabilities, e.g. topic and message content notification filtering, pull-and-push styles of transporting messages. QCG-Notification has been integrated with a number of communication protocols as well as various Web Service security mechanisms. The modular architecture of QCG-Notification makes it relatively straightforward to develop new extensions and plugins to meet new requirements. … … 52 57 For more information see [[http://www.qoscosgrid.org/trac/qcg-broker|QCG-Broker Home Page]] 53 58 54 === QCG-Coordinator ===55 QCG-Coordinator supports the spawning of parallel application processes on co-allocated computational resources. Since the standard methodologies used in MPI or !ProActive are adjusted to run jobs only on a single machine, it was needed to provide additional entity to support multi-cluster runs.56 57 For more information see [[http://www.qoscosgrid.org/trac/qcg-computing/QCG-Coordinator|QCG-Coordinator Home Page]]58 59 59 === Data Movement === 60 60 As many other e-infrastructures controlled by middleware services, !QosCosGrid takes advantage of the GridFTP protocol for large data transfer operations, in particular to stage in and stage out files for advanced simulations. GridFTP is a high-performance, secure, reliable data transfer protocol optimized for high-bandwidth wide area networks. It is a de facto standard for all data transfers in grid and cloud environments and extends the standard FTP protocol with functions such as third-party transfer, parallel and striped data transfer, self-tuning capabilities, X509 proxy certificate-based security, support for reliable and restartable data transfers. The development of GridFTP is coordinated by the GridFTP Working Group under the hood of the Open Grid Forum community.