Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "GPGPU-WG KnowledgeBase GLUE2 Profile Application"

From EGIWiki
Jump to navigation Jump to search
 
(36 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The Working Group shall define an EGI Community standard that encapsulates the application software required on Worker Nodes in order to support Computational Accelerators.
{{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 5: 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.
* The ApplicationEnvironment is defined as follows:


{| class="wikitable"
 
!colspan="5"| '''ApplicationEnvironment'''
== 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:
|'''Entity'''
* CUDA
|colspan=3 | '''Inherits from'''
* OpenCL
|'''Description'''
* Support Applications/Compilers for Intel Xeon Phi
|-
* Application Benchmarks?
| ApplicationEnvironment
* Other User Application Software?
| colspan="3" | Entity
 
| A description of the installed application software available or software environment characteristics available within one or more Execution Environments.
== Task 2 ==
|-
The working group shall discuss the merits of using ApplicationHandle instances to help bootstrap each
| '''Inherited Attribute '''
[[GPGPU-WG:GPGPU_Working_Group_KnowledgeBase:GLUE2:Profile:Application:ApplicationEnvironment |ApplicationEnvironment]]
| '''Type'''
 
| '''Mult'''
 
| '''Unit'''
----
| '''Description'''
|-
| ''Creation Time''
| ''DateTime_t''
| ''0..1''
|
| ''Timestamp describing when the entity instance was created''
|-
| ''Validity''
| ''Unit64''
| ''0..1''
| ''s''
| ''The duration after CreationTime that the
information presented in the Entity SHOULD be
considered relevant. After that period has elapsed,
the information SHOULD NOT be considered
relevant''
|}

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


Retrieved from "https://wiki.egi.eu/w/index.php?title=GPGPU-WG_KnowledgeBase_GLUE2_Profile_Application&oldid=75846"