bconf

Submits live reconfiguration requests, updating configuration settings in active memory without restarting daemons.

Synopsis

bconf action object_type=object_name "value_pair[;value_pair...]"] [-c "comment"] [-f]

bconf hist [-l|-w] [-o object_type] [-u user_name] [-T time_period] [-a action] [-f config_file] [history_file]

bconf disable

bconf -h [action [object_type]]

bconf -pack pack_file_name

bconf -V

Action synopsis

create usergroup | limit | serviceclass=object_name "value_pair[;value_pair ...]" [-c "comment"]

delete usergroup | limit | serviceclass=object_name "value_pair[;value_pair ...]" [-c "comment"] [-f]

set user |usergroup | limit=object_name "value_pair[;value_pair ...]" [-c "comment"]

add host=object_name "value_pair[;value_pair ...]" [-c "comment"]

Description

The bconf command is enabled when the LSF_LIVE_CONFDIR parameter is defined in the lsf.conf file.

The bconf command allows configuration changes without restarting LSF or any daemons. Changes are made in active LSF memory, and updated configuration files are written to the directory defined by parameter LSF_LIVE_CONFDIR. Original configuration files are not changed. However, LSF reloads files found in the LSF_LIVE_CONFDIR directory during restart or reconfiguration in place of permanent configuration files.

Important: Before you enable live reconfiguration, run the badmin reconfig command to make sure that all configuration files have no error or warning messages. Merge multiple sections in configuration files where possible. Keep the order of sections and the syntax used in the configuration file templates in all configuration files used with live reconfiguration.

Configuration changes made by using the bconf command cannot be rolled back. Use the bconf command to reverse the configuration requests and undo unwanted configuration changes. You can also manually remove or replace the configuration files in the LSF_LIVE_CONFDIR directory before restart or reconfiguration.

The first bconf command that is executed after restart or reconfiguration backs up the files that were loaded into memory. All files that the bconf command can change are backed up in the LSF_LIVE_CONFDIR directory as *.bak files. The backup files always represent the configuration before bconf commands were run.

Cluster administrators can run all bconf commands. All users can run bconf hist queries. All bconf command requests must be made from static servers.

The gpool administrators can manage the corresponding guaranteed resource pool.

User group administrators with usershares rights can adjust user shares.

User group administrators with full rights can change the following configurations:

Adjust user shares and group members
Delete the user group
Create new user groups

User group administrators with full rights can add a user group member to the user group only if they also have full rights for the member user group. User group administrators who add a user group through the bconf create command are automatically added to the GROUP_ADMIN list with full rights for the new user group.

Important: Remove the configuration files in the LSF_LIVE_CONFDIR directory, or merge files into the LSF_CONFDIR directory before you disable live configuration, upgrade LSF, apply patches to LSF, or add server hosts.

The bconf command supports common configuration changes. The bconf command cannot change all configurations. For time-based configuration, global configurations are changed globally, and configuration for the active time window are changed only for the time window.

The bconf command changes the following configuration files:

lsb.resources
lsb.queues
lsb.users
lsb.hosts
lsf.cluster.clustername
lsb.serviceclasses

Important: Changing these configuration files manually while live reconfiguration is enabled automatically disables the bconf command. Further live reconfiguration requests are rejected.

The bconf command changes objects, or configuration blocks enclosed in Begin and End statements, in the configuration files. One bconf request can affect several configured objects. For example, deleting a user group that appears in the configuration for a limit and a queue also changes the limit and queue configuration, and returns the following confirmation messages:

bconf delete usergroup=ug1
bconf: Request to delete usergroup <ug1> impacts the following:
    <USERS> in limit <limit1>
    <USERS FAIRSHARE > in queue <big_mem_queue>
Are you sure you want to delete usergroup <ug1> (y/n)?

The API corresponding to the bconf command is lsb_liveconfig. For more information, see the IBM Spectrum LSF API reference.

Subcommands and options

action object_type=object_name "value_pair[;value_pair...]"] [-c "comment"] [-f]

action

action is the requested action that is supported by live reconfiguration. The following keywords can be an action value: addmember, rmmember, update, create, add, delete, set.

addmember

Adds a member to the group or list of an existing field in an object, or updates the value of an existing member.

Cannot be used with reserved words such as all, excluded elements such as ~user1 or !host1, or members defined by regular expressions such as hostA[01-10] or hostA*.

When used with an existing member, the value of the member is updated within the object.

rmmember

Removes a member from the group or list of an existing key (field) in an object.

Restriction: You cannot remove all members from groups and lists cannot have all (except USER_SHARES). The group or list cannot contain only reserved words such as others, all, or allremote, or contain only excluded members.

You cannot use the rmmember option with reserved words such as all, excluded elements such as ~user1 or !host1, or members defined by regular expressions such as hostA[01-10] or hostA*. Hosts added with the badmin hghostadd command cannot be removed with the bconf rmmember command.

update

Updates by replacing the old value with the new value, or adding the field if it is not already configured.

Use the update usergroup=group_name or update hostgroup=group_name command to reload an external user group.

create

Creates a new object.

add

Adds a new host.

delete

Deletes an existing object.

You cannot delete a user group under the following conditions:

The user group contains running or pending jobs (run the busers command to check)
The user group appears in a LSF multicluster capability UserMap section in the lsb.users file
The user group is the default user group defined by the DEFAULT_USER_GROUP parameter in the lsb.params file.

Deleted user groups are counted towards the maximum allowed number of user groups until the next restart or reconfig command is run. Deleted user groups might still show in the busers command output.

set

Forces an update or a create action.

object_type

Any block that is enclosed by BeginSection ... EndSection in a configuration file that is changed by a bconf command request. An object includes a type and name and contains attributes that are called keys, which are fields that are defined in the object section of the file. The following keywords can be an object_type value: user, usergroup, host, hostgroup, queue, limit, gpool. Not all actions apply to all object types.

user