...
The following variables are replaced on the basis of the target resource information contained in the Host Information Service:
| Code Block |
|---|
HOST_KEY: e.g., "ABE"
NODE_NAME: e.g., "grid-abe.ncsa.teragrid.org"
ARCHITECTURE: e.g., "x86_64"
OS_NAME: e.g., "Linux"
OS_VERSION: e.g., "2.6.9-42.0.10.EL_lustre-1.4.10.1smp"
|
2. Configurations for this profile, based on the various possible resolutions of the variable, are then written to the TupleSpace service. For example,
| Code Block | ||||
|---|---|---|---|---|
| ||||
<tspace-entry-builder id="1" owner="/C=US/O=National Center for Supercomputing Applications/OU=People/CN=Albert L. Rossi" typeName0="platform.configuration" typeValue0="paths-ABE" name="tspace-entry-paths-ABE"> <ranOn/> <payload payloadType="ncsa.tools.common.types.Configuration"> <configuration> <property xmlns:ncsa.updateable.id="ELF_HOME" <property name="ELF_HOME" category="environment"> <value xmlns:ncsa.updateable.id="value"> <value>/u/ncsa/arossi/elf-3.0.0</value> </property> </configuration> </payload> </tspace-entry-builder> |
Presumably there would be one tuple of this sort for each resource the workflow is able to run on.
...