Changes between Version 3 and Version 4 of net.sf.basedb.opengrid/install
- Timestamp:
- Jan 23, 2017, 2:04:28 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
net.sf.basedb.opengrid/install
v3 v4 52 52 || `<host-info-command>` || no || uname -srmo || A command to run on the Open Grid Cluster to get information about the operating system. It is used only for informational purposes. || 53 53 || `<opengrid-info-command>` || no || qstat -help | head -n1 || A command to run on the Open Grid Cluster to get information about the Open Grid software. This is currently only used for informational purposes, but in the future this information may be used for feature-detection. || 54 || `<job-agent-id>` || no || || The external ID of a job agent that is defined in BASE. When this value exists the job agent is used as a proxy for access permissions. BASE users need to have USE permission for the job agent in order to use this Open Grid Cluster. Note that the job agent is not used for anything else. The job agent software should not be installed on the Open Grid Cluster. Open Grid Clusters withouta job agent proxy can be used by all users. ||54 || `<job-agent-id>` || no || || Links the Open Grid Cluster to a job agent that is defined in BASE via the external ID. When this value exists the job agent is used as a proxy for access permissions. BASE users need to have USE permission for the job agent in order to use this Open Grid Cluster. Note that the job agent is not used for anything else. Do not set a server and/or port. The job agent software should not be installed on the Open Grid Cluster. Open Grid Clusters that are not linked to a job agent proxy can be used by all users. || 55 55 || `<nodes>` || no || || A list with one or more `<node name="..." />` elements identifying individual nodes in the Open Grid Cluster. Individual nodes are not used by this extension, but may be required by other extensions for doing Open Grid related tasks that can't be scheduled as jobs (for example, parsing out data from result files that should be stored in BASE). The list of nodes that can be used for this is configured here simply as a service for other extensions. Typically, one or two nodes can be set aside for this and it is recommended that actions are quick and not too resource consuming. Extensions that require access to nodes should document this requirement. ||