Next: Constructing and Destroying ResourceBroker
Up: The Resource Management Package
Previous: Constructing and Destroying HardwareDescription
  Contents
Constructing and destroying a GATSoftwareResourceDescription is similar to creating and
destroying a GATHardwareResourceDescription instance. One uses the following function
GATSoftwareResourceDescription GATSoftwareResourceDescription_Create(GATTable_const attributes)
This function takes a GATTable instance and returns a GATSoftwareResourceDescription
upon success, upon failure it returns NULL. The passed GATTable contains a
description, i.e. various name/value paris, of the returned GATSoftwareResourceDescription.
The supported name/value pairs which can occur in this GATTable instance are given
in table
Table:
Software Resource Description: the minimum set of supported name/values.
| Name |
Type |
Description |
os.name |
String |
The os name as returned from uname -s. |
os.type |
String |
The os type as returned from uname -p. |
os.version |
String |
The os version as returned from uname -v. |
os.release |
String |
The os release as returned from uname -r. |
os.name |
String |
The os name as returned from uname -s. |
|
Again, if a particular name/value pair is not specified in a particular GATTable instance,
then GAT assumes that this name/value pair can take on any value. So, for example, if
the there is no key os.release in a GATTable instance, then GAT assumes that
this property can take on any value.
To destroy the so created GATSoftwareResourceDescription one uses the following function
void GATSoftwareResourceDescription_Destroy(GATSoftwareResourceDescription *resource)
This function takes as its first argument a pointer to a GATSoftwareResourceDescription. This
points to the GATSoftwareResourceDescription to be destroyed. Upon successful completion
this any resources this GATSoftwareResourceDescription maintained will be released.
Next: Constructing and Destroying ResourceBroker
Up: The Resource Management Package
Previous: Constructing and Destroying HardwareDescription
  Contents
Andre Merzky
2004-05-13
|