7. LSF Database - Windows NT

This chapter is aimed at the LSF administrator running a Windows NT only cluster. If your cluster contains any UNIX hosts, see Chapter 6, `LSF Database - UNIX', on page 41.

All examples in this chapter assume the use of Microsoft SQL Server 6.5 as the LSF database, and use of an ODBC-compliant DBMS.

In This Chapter

Database Installation Procedures

• `Database Setup' on page 50
• `Host Setup' on page 51
• `LSF Setup' on page 53

Database Commands and Parameters

• `LSF Database Utility Command' on page 56
• `LSF Data Collection Parameters' on page 56
• `lsb.acct Data Conversion' on page 57

Database Setup

Log on as the Microsoft SQL Server Database Administrator (DBA) and complete the following procedures in order.

• `Create LSF Database Accounts' on page 50
• `Create A New Database' on page 51
• `Build LSF Database Schema' on page 51
• `Grant Permissions to LSF Database Accounts' on page 51

Create LSF Database Accounts

1. Create a new account that will be used by LSF Batch to write information to the LSF database. This is the LSF database user account.

By default, LSF Analyzer also uses this account to read information in the LSF database.

2. If you are very concerned about security, you may choose to create a second account that does not have permission to write to the database. This is the optional LSF database guest account.

LSF Analyzer does not require permission to write to the database, so if you create the guest account, LSF Analyzer will use it instead of the LSF database user account. The guest account could also be used by other users who only need to read the contents of the database.

Note

To simplify database setup, give the LSF database user account the same name as your LSF primary administrator user account, and do not create the LSF database guest account. You can specify any password you want, but do not confuse the database password with the password for the Windows NT user account.

Create A New Database

Create a database that will be the new LSF database.

Note

To simplify database setup, give the database the same name as your LSF cluster (e.g., cluster1).

Build LSF Database Schema

Create the tables in the new database according to the LSF database schema. The LSF database schema is specified in a Microsoft SQL Server 6.5 ISQL executable file named createschema.sql, located in the cluster\bin directory (e.g., cluster1\bin).

Grant Permissions to LSF Database Accounts

Grant the LSF database user account Select, Delete, and Update permissions for all tables in the new database.

If you created an LSF database guest account, grant it Read permission for the new database.

Host Setup

Before you can use LSF Analyzer, you must install the ODBC driver and set up a Data Source Name (DSN) on each batch host in the cluster and on the host used to run the LSF Analyzer (xanalyzer) graphical user interface.

Log onto each host and, if necessary, install the ODBC driver before you set up the DSN.

ODBC Driver Installation

LSF Analyzer requires the version 3.0 or later ODBC driver for Microsoft SQL Server 6.5. The driver is available from Microsoft.

1. Download the Microsoft ODBC 3.5 SDK (ODBC35IN.exe) which installs the supported ODBC driver for Microsoft SQL Server 6.5 from:

   http://www.microsoft.com/data/odbc

2. Run ODBC35IN.exe to install the Setup for Microsoft ODBC 3.5 SDK
3. Run Setup.exe from the ODBC 3.5 SDK install directory to begin the ODBC driver installation. Select the Minimum installation option.

DSN Setup

1. Run ODBC Administrator from the Windows Control Panel.
2. Select the System DSN tab.
3. Click the Add button. Displays the Create New Data Source dialog.
4. Select the MS SQL driver from the list. Displays the Create New Data Source for SQL Server dialog.
5. Enter the name of your MS-SQL database in the Name field and add the .ana extension (e.g., cluster1.ana).
6. Select the LSF database server from the Server list.
7. Enter a description for the DSN into the Description field. Click Next.
8. Select the With SQL Server authentication using a login ID & Password entered by the user option. Enables the Login ID and Password fields.
9. Enter the name of the LSF database account for Login ID (e.g., lsfadmin) and the password of the LSF database account for Password. Click Next.
10. Select the Change the default database to option and enter the name of the LSF database (e.g., cluster1). Click Next.
11. Follow the prompts and accept all default values to complete the configuration. Click Finish when displayed. Displays the Confirmation dialog.
12. Click Test.
13. After the test completes, click OK.

LSF Setup

Log on as an LSF cluster administrator (not the LSF primary administrator).

The following process describes the activities for the LSF cluster administrator to carry out for setting up LSF for use with Microsoft SQL Server 6.5 and LSF Analyzer:

• `Set Database Login Passwords' on page 53
• `Set LSF Database Parameters' on page 54
• `Update LSF' on page 54

Set Database Login Passwords

LSF needs to know the database password for the LSF database user account and the LSF database guest account, if it was created (see `Create LSF Database Accounts' on page 50).

Use the lsdbpasswd command to set the passwords in LSF, see `lsdbpasswd' on page 56. This command will ask for the password for the specified user ID, encrypt the password and save it into a file. For example, type:

C:> lsdbpasswd lsfadmin

If the LSF database user account has the same name as a Windows NT user account, use this command to input the database password, not the Windows NT password.

Set LSF Database Parameters

Edit the lsf.conf file and set the following parameters to define the LSF database environment.

Note

If you took all the recommended steps to simplify database setup, you do not need to set these parameters. The default values will match your database setup.

LSF_DB_ACTIVE
Specifies the name of the active LSF database, see `Step 5' on page 52.

Default: the name of the cluster is used (e.g., cluster1), but the variable remains undefined.

LSF_DB_ACCT
Specifies the Login ID for the LSF database account, see `Create LSF Database Accounts' on page 50.

Default: the name of the LSF primary administrator account is used (e.g., lsfadmin), but the variable remains undefined.

LSF_DB_GUEST_ACCT
Specifies the Login ID for the LSF database guest account, see `Create LSF Database Accounts' on page 50.

Default: the name of the LSF primary administrator account is used (e.g., lsfadmin), but the variable remains undefined.

Update LSF

The procedure to update LSF differs depending on whether LSF is running or yet to be started. Is LSF running?

• Yes - Go to Reconfigure LSF
• No - Go to Starting LSF

Reconfigure LSF

Reconfigure LSF by executing the following two commands:

C:> lsadmin reconfig
C:> badmin reconfig

Starting LSF

The LSF service and daemons on each LSF server host will start automatically when the machine is restarted.

If you cannot restart each host at this time, log on as an LSF cluster administrator (a member of the LSF Global Administrators group) and start the LSF service and daemons manually.

Note

You should not use the primary LSF administrator's account (normally lsfadmin) to start or stop LSF service and daemons.

To start the LSF service and daemons, use any one of the following methods:

• Use the Windows NT Server Manager to start "LSF Service" on all LSF server hosts.
• Click "Services" on the Windows NT Control Panel and start "LSF Service". You will have to repeat this step on each LSF server host.
• If LSF Batch has been installed, go to the "LSF Suite for Workload Management/LSF Batch" program folder, and use the LSF administrative tool "LSF Batch Administration". (You can use this tool to perform all your administrative tasks for LSF Base and LSF Batch products.)
• Start a new command console, and type:

C:> lssrvcntrl start -m all lssrvman

Usage information for lssrvcntrl is available by typing lssrvcntrl with no options.

LSF Database Utility Command

lsdbpasswd

lsdbpasswd [ -h ] userID
Sets and changes the user's password. The password is encrypted then written to the lsf.dbpasswd file.

-h
Print command usage to stderr and exit.

userID
Specifies user ID.

LSF Data Collection Parameters

Data collection can be tuned by modifying the parameters configured in the lsb.params file. For example, edit:

LSB_CONFDIR\cluster\configdir\lsb.params

The following parameters can be configured:

DB_DEFAULT_INTVAL
Specifies the time interval to log job data (except load information and resource usage of running and suspended jobs) to the database, in minutes. To stop logging job data, set DB_DEFAULT_INTVAL=-1.

Default: 5

DB_JOB_RES_USAGE_INTVAL
Optional. If defined, specifies the time interval to log job resource usage to the database, in minutes.

Default: undefined (job resource is not logged).

DB_LOAD_INTVAL
Specifies the time interval to log load information (internal and external load indices and shared resources), in minutes.

Minimum: 15

Default: 60 (1 hour)

DB_SELECT_LOAD
Optional. Specifies which load information to collect. Possible values internal load indices, external load indices, and shared resources. This parameter is case sensitive. If more than 4 load values are specified (separated by spaces) only the first 4 will be used. For example,

DB_SELECT_LOAD = ut mem ext_idx1 shared_lic1

will collect CPU utilization, available memory, the user-specified external load index ext_idx1, and the user-specified shared resource shared_lic1.

Default: ut

lsb.acct Data Conversion

The acct2db utility is used to convert job log files (e.g., lsb.acct) into LSF databases, allowing you to analyze LSF data collected before LSF Analyzer was installed. These databases cannot be used as online (active) databases. The license for the acct2db utility expires 30 days after your LSF 3.2 license is generated.

To convert data from an existing job log file, take the following steps (all Windows NT examples assume the use of Microsoft SQL Server 6.5 as the LSF database, and use of an ODBC-compliant DBMS). Log on as the Microsoft SQL Server Database Administrator to complete steps 1 through 4.

1. Create a new LSF database, see `Create A New Database' on page 51.
2. Build the schema, see `Build LSF Database Schema' on page 51.
3. Grant the LSF database user account permission to read and write to the new database. If you have created an LSF database guest account, grant it Read permission for the new database.
4. Set up a DSN for the new database on every batch host, and on the host where LSF Analyzer is installed. See`DSN Setup' on page 52.
5. Log onto the host where the job log file (i.e., lsb.acct) is stored.
6. Issue the acct2db command and specify the new database as the target database. Each finished job record in the job log file is converted into a database record.

Syntax

acct2db [ -h ] [ -V ] [ -f lsb.acct.file ] database_name

-h
Prints command usage to stderr and exits.

-V
Prints the LSF release version to stderr and exits.

-f lsb.acct.file
Specifies the job log file on the local host which is to be converted into a database.

Default: LSB_SHAREDIR\cluster\logdir\lsb.acct

database_name
Specifies the name of the target LSF database. The target database cannot be the online (active) database.