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 ExperimentalTestingSetup ServiceDiscovery"
| Line 3: | Line 3: | ||
'''This work is experimental is is likely to change in the future'''. | '''This work is experimental is is likely to change in the future'''. | ||
The UMD GIP usr/libexec/glite-ce-glue2-applicationenvironment-dynamic is currently used generate GLUE2 ApplicationEnvironment entities. | |||
A small modification to this GIP | |||
[[GPGPU-WG:ExperimentalTestingSetup | Parent Page]] | [[GPGPU-WG:ExperimentalTestingSetup | Parent Page]] | ||
Revision as of 19:14, 17 July 2014
The objective is to allow GPGPU related resources and their state to be discovered by user commands such as glite-wms-job-list-match. In this experimental work, we would like to publish sufficient details about the GPGPU software and hardware within a GLUE2 based environment. The experimental work concentrates on using a basic GLUE2 ApplicationEnvironment to publish details about both the CUDA software environment and hardware details about the GPGPU resources and any node properties.
This work is experimental is is likely to change in the future.
The UMD GIP usr/libexec/glite-ce-glue2-applicationenvironment-dynamic is currently used generate GLUE2 ApplicationEnvironment entities. A small modification to this GIP