![]() |
|||
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
| |||||
Hosts and Host FunctionalityClicking the Host Configuration button in the QMON Main Control window displays an overview of the functionality that is associated with the hosts in your cluster. However, without manager privileges, you cannot apply any changes to the configuration. The host configuration dialog boxes are described in Chapter 1, "Configuring Hosts and Clusters," in N1 Grid Engine 6 Administration Guide. The following sections describe the commands used to retrieve this kind of information from the command line. Finding the Name of the Master HostThe location of the master host can migrate between the current master host and one of the shadow master hosts at any time. Therefore the location of the master host should be transparent to the user. With a text editor, open the sge-root/cell/common/act_qmaster file. The name of the current master host is in the file. Displaying a List of Execution HostsTo display a list of hosts that are configured as execution hosts in your cluster, use the following commands:
The qconf -sel command displays a list of the names of all hosts that are currently configured as execution hosts. The qconf -se command displays detailed information about the specified execution host. The qhost command displays status and load information about the execution hosts. See the host_conf(5) man page for details on the information displayed using qconf. See the qhost(1) man page for details on its output and other options. Displaying a List of Administration HostsUse the following command to display a list of hosts with administrative permission:
Displaying a List of Submit HostsUse the following command to display a list of submit hosts:
Requestable AttributesWhen users submit a job, a requirement profile can be specified for the job. Users can specify attributes or characteristics of a host or queue that the job requires in order to run successfully. The grid engine software maps these job requirements onto the host and queue configurations of the cluster and therefore finds suitable hosts for a job. The attributes that can be used to specify the job requirements are related to one of the following:
The attributes can also be derived from site policies such as the availability of installed software only on certain hosts. The available attributes include the following:
For convenience, however, the administrator commonly chooses to define only a subset of all available attributes to be requestable. The currently requestable attributes are displayed in the Requested Resources dialog box, which is shown in the following figure. ![]() Use the QMON Submit Job dialog box to access the Requested Resources dialog box. Requestable attributes are listed under Available Resources. Displaying a List of Requestable AttributesTo display the list of configured resource attributes, from the command line type the following command:
The grid engine system complex contains the definitions for all resource attributes. For more information about resource attributes, see Chapter 3, "Configuring Complex Resource Attributes," in N1 Grid Engine 6 Administration Guide. See also the complex format description on the complex(5) man page. The output from the qconf -sc command looks like Example 2-2. Example 2-2 Complex Attributes Displayed
The column name is identical to the first column displayed by the qconf -sq command. The shortcut column contains administrator-definable abbreviations for the full names in the first column. The user can supply either the full name or the shortcut in the request option of a qsub command. The column requestable tells whether the resource attribute can be used in a qsub command. Thus the administrator can, for example, disallow the cluster's users to request certain machines or queues for their jobs directly. The administrator can disallow direct requests by setting the entries qname, hostname, or both, to be unrequestable. Making queues or hosts unrequestable implies that feasible user requests can be met in general by multiple queues, which enforces the load balancing capabilities of the grid engine system. | |||||
| |||||
![]() |