Difference between revisions of "GPGPU-WG KnowledgeBase GLUE2 Profile Application"
m (moved GPGPU-WG:GPGPU Working Group KnowledgeBase:GLUE2:Profile:Application to GPGPU-WG KnowledgeBase GLUE2 Profile Application) |
|||
(17 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{Template:Op menubar}} {{TOC_right}} | |||
[[Category:Task_forces]] | |||
'''[[GPGPU_Working_Group| << GPGPU Working Group main page]]''' | |||
= Introduction = | |||
The Working Group shall define an EGI Community GLUE2 based standard that encapsulates and publishes data about the application software its environment required by Computational Accelerators. | |||
There are two GLUE2 classes to consider here: | |||
* The [[GPGPU-WG:GPGPU_Working_Group_KnowledgeBase:GLUE2:Profile:Application:ApplicationEnvironment |ApplicationEnvironment]], which is a significant extension to the GLUE1 GlueHostApplicationSoftwareRunTimeEnvironment. | |||
* The [[GPGPU-WG:GPGPU_Working_Group_KnowledgeBase:GLUE2:Profile:Application:ApplicationHandle| ApplicationHandle]], a new class that can indicate how an to describe an ApplicationEnvironment instance can setup the software environment. | |||
In addition, each application can have a reference to one or more application benchmarks. | |||
The GIP plugin ''glite-ce-glue2-applicationenvironment-dynamic'' produces ApplicationEnvironment data by converting the basic GLUE1 GlueHostApplicationSoftwareRunTimeEnvironment to a simple ApplicationEnvironment instance. | |||
Line 8: | Line 19: | ||
* Each Application is identified by a name. | * Each Application is identified by a name. | ||
* These names are not defined by the schema, but should be assigned in a way that allows applications to be uniquely identified. | * These names are not defined by the schema, but should be assigned in a way that allows applications to be uniquely identified. | ||
== Task 1 == | |||
The Working Group shall propose a convention to advertise application software that support GPGPUs and CAs. In particular, we should consider the following ApplicationEnvironments: | |||
* CUDA | |||
* OpenCL | |||
* Support Applications/Compilers for Intel Xeon Phi | |||
* Application Benchmarks? | |||
* Other User Application Software? | |||
== Task 2 == | |||
The working group shall discuss the merits of using ApplicationHandle instances to help bootstrap each | |||
[[GPGPU-WG:GPGPU_Working_Group_KnowledgeBase:GLUE2:Profile:Application:ApplicationEnvironment |ApplicationEnvironment]] | |||
---- | |||
| | |||
Latest revision as of 16:05, 22 January 2015
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
<< GPGPU Working Group main page
Introduction
The Working Group shall define an EGI Community GLUE2 based standard that encapsulates and publishes data about the application software its environment required by Computational Accelerators.
There are two GLUE2 classes to consider here:
- The ApplicationEnvironment, which is a significant extension to the GLUE1 GlueHostApplicationSoftwareRunTimeEnvironment.
- The ApplicationHandle, a new class that can indicate how an to describe an ApplicationEnvironment instance can setup the software environment.
In addition, each application can have a reference to one or more application benchmarks.
The GIP plugin glite-ce-glue2-applicationenvironment-dynamic produces ApplicationEnvironment data by converting the basic GLUE1 GlueHostApplicationSoftwareRunTimeEnvironment to a simple ApplicationEnvironment instance.
The ApplicationEnvironment is a GLUE2 class that describes the software environment in which a job will run.
- Each Application is identified by a name.
- These names are not defined by the schema, but should be assigned in a way that allows applications to be uniquely identified.
Task 1
The Working Group shall propose a convention to advertise application software that support GPGPUs and CAs. In particular, we should consider the following ApplicationEnvironments:
- CUDA
- OpenCL
- Support Applications/Compilers for Intel Xeon Phi
- Application Benchmarks?
- Other User Application Software?
Task 2
The working group shall discuss the merits of using ApplicationHandle instances to help bootstrap each ApplicationEnvironment