1. ATLAS auto-setup Alessandro De Salvo 3-9-2013 A. De Salvo – 3 Sep 2013 Status Plans

2. Auto setup in details  The auto setup is installed in cvmfs  /cvmfs/atlas.cern.ch/repo/sw/local/bin/auto-setup  How it works  Set either ATLAS_SITE_NAME or SITE_NAME to a site name available in AGIS  ATLAS_SITE_NAME has precedence over SITE_NAME  Source the auto-setup  Example:  export SITE_NAME=INFN-ROMA1 &&. /cvmfs/atlas.cern.ch/repo/sw/local/bin/auto-setup  What it sets  FRONTIER_SERVER  DQ2_LOCAL_SITE_ID  What is the source of the data  Cached AGIS data  /cvmfs/atlas.cern.ch/repo/sw/local/etc/agis_site_info.json  Dump from AGIS to CVMFS every 12 hours  Fallback to direct AGIS access  Possible static overrides in CVMFS of values from AGIS 2

3. Status & Plans  Status  auto-setup working currently in transparent mode (no settings, just checking values) since more than 1 month  No significant negative impact of the new tool in the overall jobs lifecycle  Crosscheck the settings  Need to check that everything is set by the auto-setup make sense  Check AGIS data and local node settings (SITE_NAME and/or ATLAS_SITE_NAME)  The tentative plan is to go in production mode with auto-setup by the end of September 2013  Dismiss the requirement of the ATLAS_LOCAL_AREA shared filesystem  Dismiss the old Installation System  AGIS and unique source of configuration 3