Lawrencium Cluster

Cluster Description

LAWRENCIUM is the platform for the LBNL Condo Cluster Computing (LC3) program, which provides a sustainable way to meet the midrange computing requirement for Berkeley Lab. LAWRENCIUM is part of the LBNL Supercluster and shares the same Supercluster infrastructure. This includes the system management software, software module farm, scheduler, storage and backend network infrastructure.
Storage and Backup:

Login and Data Transfer:

The Lawrencium Supercluster uses One Time Password (OTP) for login authentication for all the services provided below. Please also refer to the Data Transfer page for additional information.

• Login server: lrc-login.lbl.gov
• DATA transfer server: lrc-xfer.lbl.gov
• Globus Online endpoint: lbnl#lrc

Hardware Configuration:

LAWRENCIUM is composed of multiple generations of hardware hence it is physically separated into several partitions to facilitate management and to meet the requirements to host Condo projects. The following table lists the hardware configuration for each individual partition.

Storage and Backup:

Recharge Model

Scheduler Configuration:

Lawrencium cluster uses SLURM to submit jobs as the scheduler to manage jobs on the cluster. To use the Lawrencium resource the partition “lr3, lr4, lr5, lr6, es1, cm1, cm2” must be used (“–partition=xxx”) along with user (“–account=xxx”). Currently the QoS is lr_normal and lr_debug and lr_lowprio. A standard fair-share policy with a decay half life value of 14 days (2 weeks) is enforced.

• For normal users to use the LAWRENCIUM resource the proper project account, e.g., “–account=ac_abc”, is needed. The QoS “lr_normal” is also required based on the partition that the job is submitted to,          e.g., “–qos=lr_normal”.
• If a debug job is desired the “lr_debug”  QoS should be specified, e.g., “–qos=lr_debug” so that the scheduler can adjust job priority accordingly.
• Condo users please use the proper condo QoS, e.g., “–qos=condo_xyz”, as well as the proper recharge account “–account=lr_xyz”.
• The partition name is always required in all cases, e.g., “–partition=lr6”.
• A standard fair-share policy with a decay half life value of 14 days (2 weeks) is enforced. All accounts are given equal shares value of 1.  All users under each account associated within a partition is subjected to decay’g in priority based on the resources used and the overall parent account usage.   Usage is a value between 0.0 and 1.0 that represents the the associates proportional usage of the system. A value of 0 indicates that the association is over-served.  In other words that account has used its share of the resources and will be given a lower value of shares compared to users who have not used as much resources.
• Job prioritization is based on Age, Fairshare, Partition and QOS – note: lr_lowprio qos jobs are not given any prioritization and some QOS have higher values than others.
• If a node feature is not provided, the job will be dispatched to nodes based on a predefined order, for “lr3” the order is: lr3_c16, lr3_c20; for “lr5” the order is: lr5_c28, lr5_c20.

Software Configuration:

The Lawrencium cluster uses Global Software Farm and Environment Modules to manage the cluster wide software installation.

Cluster Status: