Match Architecture

Policies concerning matching jobs to specific hardware architecture at execution sites

  1. These are valid for the glideinWms world
  2. We do not tag CE's with a list of SCRAM_ARCH's anymore
  3. pilots advertise the WN hardware using HTCondor standard class ads
  4. CMS job submission tools (CRAB2, CRAB3, WMA) will request HTCondor the list of architecture which can run our executable, taking into account compatibility issues
    • to make a specific example, for SCRAM_ARCH=slc5_amd64_gcc462 we will put in condor JDL file:
      +DESIRED_OpSyses ="LINUX"
      +DESIRED_OpSysMajorVers ="5,6"
      +DESIRED_Archs ="X86_64"
      
  5. glideinWms FE will make sure factories only ask pilots for the proper architectures
  6. Computing Operations will make sure that we only add to the pool CE's whose WN's have the needed compatibility libraries to allow e.g. SL5 and SL6 executable to run on a WN with OpSysMajorVers=6 etc.

-- StefanoBelforte - 26 Mar 2014

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2014-03-26 - StefanoBelforte
 
    • 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-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback