GlideinWMS Feature Usage

Multicore

Multicore entries require (examples from test multicore entry for PIC):

-To be declared as HTPC, see below (attr name="GLIDEIN_Is_HTPC" const="True" glidein_publish="True" job_publish="False" parameter="True" publish="True" type="expr" value="True"/>)

-The type of slots to create, in general multicore pilots should create and manage partitionable slots. (submit cluster_size="10" max_per_cycle="10" sleep="2" slots_layout="partitionable"/>)

-To point to remote multicore resources or ask for such resources to the local WMS. This is achieved by means of a rsl expression which should pass the appropriate request to the remote batch systems via the CEs. Syntax therefore needs to be understood by the CE (CREAM and ARC/Nordugrid) and correctly translated to the batch system. (rsl="WholeNodes = False; HostNumber = 1; CPUNumber = 4")

-To specify what resources will be managed by the pilots, as they will partition the total resources into slots according to the jobs requests, until one of the resources is exhausted. So far we have used:
* number of cores (attr name="GLIDEIN_CPUS" const="True" glidein_publish="False" job_publish="True" parameter="True" publish="True" type="string" value="4"/>)
* total memory (attr name="GLIDEIN_MaxMemMBs" const="True" glidein_publish="False" job_publish="True" parameter="True" publish="True" type="int" value="8192"/>)

High-Memory

To check the amount of memory for an entry/CE, see http://vocms32.cern.ch/gfactory/factoryEntryStatusNow.html, choose the entry, and scroll down GLIDEIN_MaxMemMBs variable in the "Attributes" section.

To submit to this resource, set DESIRED_Sites="GLIDEIN_CMSSite" and RequestMemory set to a number LESS THAN GLIDEIN_MaxMemMBs.

Opportunistic

Resource name # cores available notes
ASGC    

Cloud Resources

How to access - only need to set DESIRED_Site in jdl. Currently these entries are able to be reached by the production submitters.

Resource name # cores available notes
T2_CH_CERN_HLT x cores notes
T2_CH_CERN_T0/CERN/AI x cores notes

Hammercloud Testing

To check the SE of an entry, see http://vocms32.cern.ch/gfactory/factoryEntryStatusNow.html, choose the entry, and scroll down GLIDEIN_SEs variable in the "Attributes" section.

Current Matching Constraints for CMS Production

This match constraint is an HTML logic string set in the CERN production frontend (vocms157)

To check any Glidein Factory Variable for any site CE/entry, see this monitoring page: http://vocms32.cern.ch/gfactory/factoryEntryStatusNow.html, choose the entry and scroll down to "Attributes".

Match Constraint Required Variables in jdl Glidein Factory Variable Notes
DESIRED_Sites or DESIRED_SEs MUST BE SET
Site name DESIRED_Sites="TX_XX_XXXX,..." GLIDEIN_CMSSite Will match any GLIDEIN_CMSSite within DESIRED_Site variable, separated by commas (spaces are ok).
SE name DESIRED_SEs=",..." GLIDEIN_SEs DESIRED can use comma separted lists. Used mainly for Hammercloud testing
HTPC DESIRES_HTPC=1 GLIDEIN_Is_HTPC Match multicore resources
OS REQUIRED_OS GLIDEIN_REQUIRED_OS Can set to rhel5 (rhel5 only), rhel6, or any.
RequestMemory RequestMemory GLIDEIN_MaxMemMBs

Edit | Attach | Watch | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions

Topic revision: r5 - 2014-03-17 - AntonioPerezCalero
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CMSPublic All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback