![]() |
|||
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
| ||
Viewing SettingsWhen you click the Settings menu item a table displays with all the configurable settings available in GEMM. Figure 1-26 Settings Page ![]() The parameters are grouped in four categories: Monitor Alert settings, N1GE settings, NFS mount settings and Proxy settings. Changing Monitor Alert SettingsThese settings affect the display of alerts in the GEMM Monitor. All these parameters must be set using decimal numbers. Any other type of input produces a formatting error. Load Warning -- You use this parameter to specify the load warning threshold. If this threshold is exceeded, a load warning alert appears in the Monitor. The value is in terms of system load, as reported by the OS, divided by the number of CPUs. Note - Certain microprocessors with special features such as hyperthreading may be registered as having more than one CPU per physical CPU socket, depending upon factors such as the BIOS or PROM configuration. Load Critical -- You use this parameter to specify the load critical threshold. If this threshold is exceeded, a load critical alert appears in the Monitor. Similar to the Load Warning parameter, you set this parameter in terms of the system load scaled by number of CPUs. Memory Warning -- You use this parameter to set the memory warning threshold. If the value drops below this threshold, a memory warning alert appears in the Monitor. You set the parameter value in terms of megabytes of free virtual memory. Memory Critical -- You use this parameter to set the memory critical threshold. If the value drops below this threshold, a memory critical alert appears in the Monitor. You set the value in terms of megabytes of free virtual memory. Maximum Job Pending Time -- You use this parameter to specify the amount of time that a job spends pending after which a Job Pending alert appears in the Monitor. You set the value in hours. Note - It is important that you set these five parameters to sensible values, according to the characteristics of your particular grid. Otherwise, an excessive number of alerts will appear on the Monitor main page, cluttering the display. Changing N1GE SettingsThe N1GE settings affect the way N1GE is installed onto the master, compute and access hosts. The N1GE administrator must determine the various parameter values suited to their local Grid environment. Factors you should determine include the local namespace for users, TCP services, file directory structure, operating system, and so forth. The values have default options which are suitable for a generic installation. You should be familiar with the N1GE 6 product before changing any of these values. If you wish to change more advanced configuration settings, please see Chapter 3, Using the Setup configuration file. Once you deploy the master host, you cannot edit these values which remain in effect for all further deployments of compute and access hosts. You can only edit the values again if you uninstall the master host. The following section describes each setting SGE Root -- This setting is the root directory under which the N1GE files will be installed. Note that the files will be installed on all hosts in this directory. SGE Cell -- This settings is the N1GE cell name used for the deployment. Qmaster TCP Port -- This setting is the TCP port to use for the N1GE qmaster daemon. Execd TCP Port -- This setting is the TCP port to use for the N1GE execd daemon. Admin Username -- This setting is the username of the N1GE admin user. Admin UID -- This setting is the UID of the N1GE admin user. Grid Engine Version -- This parameter indicates the version of N1 Grid Engine that will be deployed on the compute and access hosts. Changing NFS SettingsThese settings affect the way the N1GE "common" directory for the chosen cell name is mounted on all access and compute hosts. The settings are described as follows. NFS Server Name -- The name of the NFS server from which all compute and access hosts will mount the N1GE "common" directory. When you deploy the master host using GEMM, this parameter is set automatically to the master host. Once you deploy the master host you cannot edit this value and it remains in effect for all further deployments of compute and access hosts. You can only edit the setting again if you uninstall the master host. NFS Mount Point -- The directory which is mounted from the NFS server for the N1GE "common" directory. When deploying the master host using GEMM, this is set automatically to <SGE_Root>/<SGE_Cell>/common, where <SGE_Root> and <SGE_Cell> are the values specified above. Once you deploy the master host you cannot edit this value and it remains in effect for all further deployments of compute and access hosts. You can only edit the setting again if you uninstall the master host. Linux NFS Mount Options -- This setting is the options used when mounting the "common" directory onto a Linux compute or access host. The value in this field is inserted into the Linux /etc/fstab file on each host as:
where <Servername> and <Mountpoint> are the values specified above and <Mountoptions> are the specified Linux NFS mount options. Note - This parameter cannot contain any spaces Solaris NFS Mount Options -- This setting specifies the options used when mounting the "common" directory onto a Solaris compute or access host. The value in this field is inserted into the Solaris /etc/vfstab file on each host as:
where <Mountpoint> is the values specified above and <Mountoptions> is the specified Solaris NFS mount options. Note - This parameter cannot contain any spaces. Changing the Proxy HostFigure 1-27 Change Proxy Host Page ![]() Currently, there is only one proxy setting, which indicates the host on which monitoring commands are executed. If the master host has been previously deployed using GEMM, then the proxy host is set to this host and cannot be changed until the master is uninstalled. To choose the proxy host, click the Choose Proxy button at the bottom of the page. A table of all the hosts on which the GEMM framework has been installed. Select one host from this table. Note - The host you chose must be an N1GE admin host; otherwise, install and uninstall of other hosts, as well as monitoring, could fail Changing the N1GE VersionFigure 1-28 Change N1GE Version Page ![]() To set N1GE version parameter, click the Choose Version button at the bottom of the page. This action presents a table from which you select a version by clicking its Inspect icon. The available versions are those uploaded in the GEMM Version management page. If you deployed the master host previously using GEMM, the version chosen at that time is displayed. Manual changes to this parameter are not allowed until you uninstall the master host. Special Consideration: External Master HostYou can use GEMM for deployment and monitoring even with an N1GE master host not configured by GEMM. Possible scenarios include:
Collecting the N1GE and NFS settingsOnce you have configured the master host and ensured that it is up and running properly, take note of all the values for the N1GE settings as well as the NFS settings. These settings are essentially the parameters you would use if you were to install an execution host manually and associate with the master host, including the choice of NFS options for mounting the N1GE common directory. For example, you might mount the common directory from the master host or you may need to mount it from a separate file server system or appliance. Note that the correct choice of the NFS settings for the N1GE common directory is a critical step, since the common directory contains a file which tells the compute and access hosts where to find the master host. Part of this step is to ensure that the exact same version of N1 Grid Engine which is running on the master host has been uploaded to GEMM using the Version page. N1 Grid Engine will not function properly unless the same version, including update level is used on the master host and all compute and access hosts. Once you have determined and set the N1GE and NFS settings, it is important not to modify them again. Otherwise, further compute and access host deployments could be corrupted and will not work. | ||
| ||
![]() |