mopdf.com

cshrc.lsf and profile.lsfXLSF UIDDIR /usr/lsf/lsf 9/9.1/linux2.6-glibc2.3-x86/lib/uidValuesv In cshrc.lsf for csh and tcsh:setenv XLSF UIDDIR LSF TOP/ LSF VERSION/ BINARY TYPE/lib/uidv Set and exported in profile.lsf for sh, ksh, or bash:XLSF UIDDIR LSF TOP/ LSF VERSION/ BINARY TYPE/lib/uidEGO environment variables set by cshrc.lsf and profile.lsfEGO BINDIRSyntaxEGO BINDIR dirDescriptionDirectory where EGO user commands are installed.Examplesv Set in csh and tcsh by cshrc.lsf:setenv EGO BINDIR /usr/lsf/lsf 9/9.1/linux2.6-glibc2.3-x86/binv Set and exported in sh, ksh, or bash by profile.lsf:EGO BINDIR /usr/lsf/lsf 9/9.1/linux2.6-glibc2.3-x86/binValuesv In cshrc.lsf for csh and tcsh:setenv EGO BINDIR LSF BINDIRv Set and exported in profile.lsf for sh, ksh, or bash:EGO BINDIR LSF BINDIREGO CONFDIRSyntaxEGO CONFDIR dirDescriptionDirectory containing the ego.conf file.Examplesv Set in csh and tcsh by cshrc.lsf:setenv EGO CONFDIR /usr/lsf/lsf 9/conf/ego/lsf1.2.3/kernelv Set and exported in sh, ksh, or bash by profile.lsf:EGO CONFDIR /usr/lsf/lsf 9/conf/ego/lsf1.2.3/kernelValuesv In cshrc.lsf for csh and tcsh:setenv EGO CONFDIR /usr/lsf/lsf 9/conf/ego/lsf1.2.3/kernelv Set and exported in profile.lsf for sh, ksh, or bash:EGO CONFDIR /usr/lsf/lsf 9/conf/ego/lsf1.2.3/kernel6Platform LSF Configuration Reference

cshrc.lsf and profile.lsfEGO ESRVDIRSyntaxEGO ESRVDIR dirDescriptionDirectory where the EGO the service controller configuration files are stored.Examplesv Set in csh and tcsh by cshrc.lsf:setenv EGO ESRVDIR /usr/lsf/lsf 9/conf/ego/lsf702/eservicev Set and exported in sh, ksh, or bash by profile.lsf:EGO ESRVDIR /usr/lsf/lsf 9/conf/ego/lsf702/eserviceValuesv In cshrc.lsf for csh and tcsh:setenv EGO ESRVDIR /usr/lsf/lsf 9/conf/ego/lsf702/eservicev Set and exported in profile.lsf for sh, ksh, or bash:EGO ESRVDIR /usr/lsf/lsf 9/conf/ego/lsf702/eserviceEGO LIBDIRSyntaxEGO LIBDIR dirDescriptionDirectory where EGO libraries are installed. Library files are shared by all hosts ofthe same type.Examplesv Set in csh and tcsh by cshrc.lsf:setenv EGO LIBDIR /usr/lsf/lsf 9/9.1/linux2.6-glibc2.3-x86/libv Set and exported in sh, ksh, or bash by profile.lsf:EGO LIBDIR /usr/lsf/lsf 9/9.1/linux2.6-glibc2.3-x86/libValuesv In cshrc.lsf for csh and tcsh:setenv EGO LIBDIR LSF LIBDIRv Set and exported in profile.lsf for sh, ksh, or bash:EGO LIBDIR LSF LIBDIREGO LOCAL CONFDIRSyntaxEGO LOCAL CONFDIR dirDescriptionThe local EGO configuration directory containing the ego.conf file.Chapter 1. Configuration Files7

cshrc.lsf and profile.lsfExamplesv Set in csh and tcsh by cshrc.lsf:setenv EGO LOCAL CONFDIR /usr/lsf/lsf 9/conf/ego/lsf1.2.3/kernelv Set and exported in sh, ksh, or bash by profile.lsf:EGO LOCAL CONFDIR /usr/lsf/lsf 9/conf/ego/lsf1.2.3/kernelValuesv In cshrc.lsf for csh and tcsh:setenv EGO LOCAL CONFDIR /usr/lsf/lsf 9/conf/ego/lsf1.2.3/kernelv Set and exported in profile.lsf for sh, ksh, or bash:EGO LOCAL CONFDIR /usr/lsf/lsf 9/conf/ego/lsf1.2.3/kernelEGO SERVERDIRSyntaxEGO SERVERDIR dirDescriptionDirectory where EGO server binaries and shell scripts are installed. These includevemkd, pem, egosc, and shell scripts for EGO startup and shutdown.Examplesv Set in csh and tcsh by cshrc.lsf:setenv EGO SERVERDIR /usr/lsf/lsf 9/9.1/linux2.6-glibc2.3-x86/etcv Set and exported in sh, ksh, or bash by profile.lsf:EGO SERVERDIR /usr/lsf/lsf 9/9.1/linux2.6-glibc2.3-x86/etcValuesv In cshrc.lsf for csh and tcsh:setenv EGO SERVERDIR LSF SERVERDIRv Set and exported in profile.lsf for sh, ksh, or bash:EGO SERVERDIR LSF SERVERDIREGO TOPSyntaxEGO TOP dirDescriptionThe top-level installation directory. The path to EGO TOP must be shared andaccessible to all hosts in the cluster. Equivalent to LSF TOP.Examplesv Set in csh and tcsh by cshrc.lsf:setenv EGO TOP /usr/lsf/lsf 9v Set and exported in sh, ksh, or bash by profile.lsf:EGO TOP /usr/lsf/lsf 98Platform LSF Configuration Reference

cshrc.lsf and profile.lsfValuesv In cshrc.lsf for csh and tcsh:setenv EGO TOP /usr/lsf/lsf 9v Set and exported in profile.lsf for sh, ksh, or bash:EGO TOP /usr/lsf/lsf 9dc conf.cluster name.xml parametersThis is a new file for Dynamic Cluster configuration parameters.ResourceGroupConf sectionExample: ResourceGroupConf HypervisorResGrps ResourceGroup Name KVMRedHat Hosts /Name Template rhel55hv /Template MembersAreAlsoPhysicalHosts Yes /MembersAreAlsoPhysicalHosts /ResourceGroup /HypervisorResGrps /ResourceGroupConf The following parameters are configured in the ResourceGroupConf section of ptionDefines a host as a hypervisor which can also run physical machine workload onidle resources.DefaultNot defined.NameSyntaxKVMRedHat HostsDescriptionThe name of the resource group to which this hypervisors of the given templatebelong. The only valid value is KVMRedHat Hosts.DefaultNot defined.Chapter 1. Configuration Files9

dc conf.cluster name.xmlTemplateSyntaxtemplate nameDescriptionThe name of the template associated with the hypervisor resource group. Thismust match a template name defined in the Templates section.DefaultNot defined.Parameters sectionMost parameters are configured as shown: ParametersConf Parameter name "PARAMETER 1" Value value 1 /Value /Parameter Parameter name "PARAMETER 2" Value value 2 /Value /Parameter /ParametersConf The following parameters are configured in the ParametersConf section of thefile.DC CLEAN PERIODSyntaxsecondsDescriptionTime to keep provision requests in memory for query purposes after they arecompleted. Before this period is completed, the requests appear in the output ofthe bdc action command. After this period expires, they only appear in the outputof bdc hist. Specify the value in seconds.Default1800DC CONNECT STRINGSyntaxadmin user name::directory pathDescriptionA connection string to specify the Platform Cluster Manager Advanced Editionadministrator account name and installation directory10Platform LSF Configuration Reference

dc conf.cluster name.xmlDefaultAdmin::/opt/platformThe Platform Cluster Manager Advanced Edition administrator is Admin and theinstallation directory is /opt/platform.DC EVENT FILES MAX NUMSyntaxintegerDescriptionMaximum number of Dynamic Cluster event log files (dc.events) to keep.DependencyDC EVENT FILES MIN SWITCH PERIODDefault10DC EVENT FILES MIN SWITCH PERIODSyntaxsecondsDescriptionThe minimum elapsed time period before archiving the Dynamic Cluster event log.Define the value in seconds.Works together with DC PROVISION REQUESTS MAX FINISHED to controlhow frequently Dynamic Cluster archives the file dc.events. The number offinished requests in the file is evaluated regularly, at the interval defined by thisparameter. The file is archived if the number of requests has reached the thresholddefined by DC PROVISION REQUESTS MAX FINISHED.The event log file names are switched when a new file is archived. The new file isnamed dc.events, the archived file is named dc.events.1, and the previousdc.events.1 is renamed dc.events.2, and so on.DependencyDC PROVISION REQUESTS MAX FINISHEDDefault1800DC LIVEMIG MAX DOWN TIMESyntaxsecondsChapter 1. Configuration Files11

dc conf.cluster name.xmlDescriptionFor KVM hypervisors only. The maximum amount of time that a VM can be downduring a live migration. This is the amount of time from when the VM is stoppedon the source hypervisor and started on the target hypervisor. If the live migrationcannot guarantee this down time, the system will continue to retry the livemigration until it can guarantee this maximum down time (or theDC LIVEMIG MAX EXEC TIME parameter value is reached). Specify the value inseconds, or specify 0 to use the hypervisor default for the down time.Default0DC LIVEMIG MAX EXEC TIMESyntaxsecondsDescriptionFor KVM hypervisors only. The maximum amount of time that the system canattempt a live migration. If the live migration cannot guarantee the down time (asspecified by the DC LIVEMIG MAX DOWN TIME parameter) within this amount of time,the live migration fails. Specify the value in seconds from 1 to 2147483646.Default2147483646DC MACHINE MAX LIFETIMESyntaxminutesDescriptionLimits the lifetime of a dynamically created virtual machine. After the specifiedtime period has elapsed since a VM’s creation, if the VM becomes idle, the systemautomatically powers off and destroy the VM.This parameter is useful when propagating updates to a shared template. If ashared template is updated, all VM instances which were generated from thistemplate will still run with the old template even if they were powered off.Setting this parameter to a finite value will cause VMs to be uninstalled (deletedfrom disk) after the specified period and completing running workload. Anyfurther requests for the shared template must install a new VM, which will then bebased on the new version of the template. Therefore administrators can be surethat the template update has been propagated throughout the system after thespecified time period.DefaultNot defined. Infinite time.12Platform LSF Configuration Reference

dc conf.cluster name.xmlDC MACHINE MIN TTLSyntaxminutesDescriptionMinimum time to live of the Dynamic Cluster host or virtual machine before it canbe reprovisioned. This parameter is used to prevent system resources from beingreprovisioned too often and generating unnecessary load on the infrastructure. Forexample, if the value is set to 60, any freshly provisioned machine will not bereprovisioned in less than 60 minutes.Default0DC PROVISION REQUESTS MAX FINISHEDSyntaxintegerDescriptionNumber of finished provisioning requests in the Dynamic Cluster event log beforeit is archived. Works together with DC EVENT FILES MIN SWITCH PERIOD tocontrol how frequently Dynamic Cluster archives the file dc.events. The numberof jobs in the file is evaluated regularly, at the interval defined byDC EVENT FILES MIN SWITCH PERIOD. The file is archived if the number ofjobs has reached or exceeded the threshold defined byDC PROVISION REQUESTS MAX FINISHED.The event log file names are switched when a new file is archived. The new file isnamed dc.events, the archived file is named dc.events.1, the previousdc.events.1 is renamed dc.events.2, and so on.DependencyDC EVENT FILES MIN SWITCH PERIODDefault5000DC REPROVISION GRACE PERIODSyntaxsecondsDescriptionAfter each job finishes, allow a grace period before the machine can accept anotherprovision request. Specify the value in seconds.By default, when a job completes, the machine it was running on becomes eligiblefor reprovisioning. However, some jobs have post-execution processes that may beChapter 1. Configuration Files13

dc conf.cluster name.xmlinterrupted if the host is reprovisioned too quickly. This parameter configures agrace period after job termination during which the host cannot be reprovisioned,which gives these processes a chance to complete.To ensure that the machine is not reprovisioned until post-execution processing isdone, specify JOB INCLUDE POSTPROC Y in lsb.params.Default0DC VM UNINSTALL PERIODSyntaxminutesDescriptionTime period to uninstall (delete from storage) a dynamically created VM in the offstate. Specify the value in minutes.A virtual machine can be created to meet peak workload demands. However, afterpeak loads pass, those virtual machines will be powered off and stored in storage.Those dynamic virtual machines can be configured to be deleted if they remain offfor a long time.Note: VMs in the OFF status still hold an IP address reservation. To release this IPaddress, the VM must be uninstalled (deleted from disk). To have VMs releasetheir IP reservation immediately when powered down, specify 0 as the value ofthis parameter to uninstall them immediately."Default1440DC VM MEMSIZE DEFINEDSyntaxintegerMultiple values allowed.This parameter wraps each value in memsize instead of Value . For example: memsize integer /memsize DescriptionSpecify one or more choices for VM memory size. Specify the value in MB.Separate values in a list with space.The memory size of any new VM is the smallest of all the choices that satisfy thejob’s resource requirement.14Platform LSF Configuration Reference

dc conf.cluster name.xmlFor example, if a job requires 500 MB memory, and this parameter is set to "10241536", the VM is created with 1024 MB memory. If a job requires 1025 MB memory,a VM is created with 1536 MB memory.Using this feature helps prevent the hypervisor hosts from being fragmented withmultiple VMs of different size. When the VMs have standardized memory size,they can easily be reused for jobs with similar memory requirements.DependencyDynamic Cluster only.If this parameter is used, DC VM MEMSIZE STEP in lsb.params is ignored.Valid Values512 minimumDefaultNot definedDC VM PREFIXSyntaxstringDescriptionPrefix for naming a new VM that is created by Dynamic Cluster. Specify a textstring.You can specify more than one name using multiple Value/ entries, but only thefirst value is used for dynamically creating new VMs. However, all VMs namedwith any of these prefixes will be treated as dynamically created VMs even if theywere manually created. They will be subject to DC VM UNINSTALL PERIOD,DC MACHINE MAX LIFETIME.Defaultvm lsf dynDC VM RESOURCE GROUPSSyntaxresource group nameDescriptionSpecify names of Dynamic Cluster resource groups which are allowed to createnew VMs. For KVM hypervisors, the only valid value is KVMRedHat Host.DC WORKDIRSyntaxdirectory pathChapter 1. Configuration Files15

dc conf.cluster name.xmlDescriptionDynamic Cluster working directory. This is the location where the dc.events filewill be stored.Default/opt/lsf/work/cluster name/dcTemplates sectionFor more information, see the setup instructions.hostsFor hosts with multiple IP addresses and different official host names configured atthe system level, this file associates the host names and IP addresses in LSF.By default, LSF assumes each host in the cluster:v Has a unique official host namev Can resolve its IP address from its namev Can resolve its official name from its IP addressHosts with only one IP address, or hosts with multiple IP addresses that alreadyresolve to a unique official host name should not be configured in this file: they areresolved using the default method for your system (for example, localconfiguration files like /etc/hosts or through DNS.)The LSF hosts file is used in environments where:v Machines in cluster have multiple network interfaces and cannot be set up in thesystem with a unique official host namev DNS is slow or not configured properlyv Machines have special topology requirements; for example, in HPC systemswhere it is desirable to map multiple actual hosts to a single head end hostThe LSF hosts file is not installed by default. It is usually located in the directoryspecified by LSF CONFDIR. The format of LSF CONFDIR/hosts is similar to theformat of the /etc/hosts file on UNIX machines.hosts file structureOne line for each IP address, consisting of the IP address, followed by the officialhost name, optionally followed by host aliases, all separated by spaces or tabs.Each line has the form:ip address official name [alias [alias .]]IP addresses can have either a dotted quad notation (IPv4) or IP Next Generation(IPv6) format. You can use IPv6 addresses if you define the parameterLSF ENABLE SUPPORT IPV6 in lsf.conf; you do not have to map IPv4addresses to an IPv6 format.Use consecutive lines for IP addresses belonging to the same host. You can assigndifferent aliases to different addresses.16Platform LSF Configuration Reference

hostsUse a pound sign (#) to indicate a comment (the rest of the line is not read byLSF). Do not use #if as this is reserved syntax for time-based configuration.IP addressWritten using an IPv4 or IPv6 format. LSF supports both formats; you do not haveto map IPv4 addresses to an IPv6 format (if you define the parameterLSF ENABLE SUPPORT IPV6 in lsf.conf).v IPv4 format: nnn.nnn.nnn.nnnv IPv6 format: nnnn:nnnn:nnnn:nnnn:nnnn:nnnn:nnnn:nnnnOfficial host nameThe official host name. Single character names are not allowed.Specify -GATEWAY or -GW as part of the host name if the host serves as a GATEWAY.Specify -TAC as the last part of the host name if the host is a TAC and is a DoDhost.Specify the host name in the format defined in Internet RFC 952, which states:A name (Net, Host, Gateway, or Domain name) is a text string up to 24 charactersdrawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.). Periodsare only allowed when they serve to delimit components of domain style names.(See RFC 921, Domain Name System Implementation Schedule, for background).No blank or space characters are permitted as part of a name. No distinction ismade between upper and lower case. The first character must be an alphacharacter. The last character must not be a minus sign or a period.RFC 952 has been modified by RFC 1123 to relax the restriction on the firstcharacter being a digit.For maximum interoperability with the Internet, you should use host names nolonger than 24 characters for the host portion (exclusive of the domaincomponent).AliasesOptional. Aliases to the host name.The default host file syntaxip address official name [alias [alias .]]is powerful and flexible, but it is difficult to configure in systems where a singlehost name has many aliases, and in multihomed host environments.In these cases, the hosts file can become very large and unmanageable, andconfiguration is prone to error.The syntax of the LSF hosts file supports host name ranges as aliases for an IPaddress. This simplifies the host name alias specification.To use host name ranges as aliases, the host names must consist of a fixed nodegroup name prefix and node indices, specified in a form like:Chapter 1. Configuration Files17

hostshost name[index x-index y, index m, index a-index b]For example:atlasD0[0-3,4,5-6, .]is equivalent to:atlasD0[0-6, .]The node list does not need to be a continuous range (some nodes can beconfigured out). Node indices can be numbers or letters (both upper case andlower case).For example, some systems map internal compute nodes to single LSF host names.A host file might contains 64 lines, each specifying an LSF host name and 32 nodenames that correspond to each LSF host:.177.16.1.1 atlasD0 atlas0 atlas1 atlas2 atlas3 atlas4 . atlas31177.16.1.2 atlasD1 atlas32 atlas33 atlas34 atlas35 atlas36 . atlas63.In the new format, you still map the nodes to the LSF hosts, so the number of linesremains the same, but the format is simplified because you only have to specifyranges for the nodes, not each node individually as an alias:.177.16.1.1 atlasD0 atlas[0-31]177.16.1.2 atlasD1 atlas[32-63].You can use either an IPv4 or an IPv6 format for the IP address (if you define theparameter LSF ENABLE SUPPORT IPV6 in lsf.conf).IPv4 Example192.168.1.1 hostA hostB192.168.2.2 hostA hostC host-CIn this example, hostA has 2 IP addresses and 3 aliases. The alias hostB specifiesthe first address, and the aliases hostC and host-C specify the second address. LSFuses the official host name, hostA, to identify that both IP addresses belong to thesame host.IPv6 Example3ffe:b80:3:1a91::2 hostA hostB 3ffe:b80:3:1a91::3 hostA hostC host-CIn this ex

This edition applies to version 9, release 1 of IBM Platform LSF (product number 5725G82) and to all subsequent releases and modifications until otherwise indicated in new editions. Significant changes or additions to the text and illustrations are indicated by a vertical line ( ) to the left of the change.