1 / 5

MW clients in CVMFS (ATLAS perspective)

CERN IT-ES. MW clients in CVMFS (ATLAS perspective). Simone Campana (on behalf of many). Desired Scenario. MW clients are installed in CVMFS Each release on a dedicated path With a setup.sh script on that path Sites can install clients locally or use CVMFS ones

joelle
Télécharger la présentation

MW clients in CVMFS (ATLAS perspective)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CERN IT-ES MW clients in CVMFS(ATLAS perspective) Simone Campana (on behalf of many)

  2. Desired Scenario • MW clients are installed in CVMFS • Each release on a dedicated path • With a setup.sh script on that path • Sites can install clients locally or use CVMFS ones • The setup.shscript should overrule the existing configuration • Panda will instruct the pilot about which setup to source • Global configuration, with the possibility to overwrite per queue and per job • This would allow flexibility in commissioning new clients and deploy rapidly bug fixes Simone Campana – Nov 2012 GDB

  3. Some More Details • “MW Clients” on the WN means • The Data Management stuff • VOMS clients • 32 vs 64 bits • The default should be using 64 bits • We need also 32 bits libraries (for Athena) • Having both in LD_LIBRARY_PATH should be enough • Python version • Multiple python versions of clients should be in CVMFS (2.6,2.7 .. will be reduced) • setup.sh should allow an argument to specify the python version to use Simone Campana – Nov 2012 GDB

  4. What has been done • ATLAS installed MW clients in CVMFS (ATLAS RootBase) • Stop-gap solution to simplify the EMI-2 testing • Build a tarball from RPMs • http://walkerr.web.cern.ch/walkerr/emi_maketar.sh • Unpack in CVMFS • Add the setup scripts for the environment • Tried in UK, several iterations needed. Finally got to work • A thread of 53 emails, with 10 people • Rod Waker (tarball builder) • Asoka Da Silva (installation and configuration in CVMFS) • A. DeSalvo (ATLAS Grid SW installation) • UK site managers (particularly Cambridge), Alessandra and Wahid • And this to configure ATLAS only… Simone Campana – Nov 2012 GDB

  5. Conclusions • This is not just about making a tarballwith rpm2cpio • The configuration is the hard part • And whichever solution needs to be maintained • We should discuss • If we need this • Who can participate to the effort and how • ATLAS can offer some effort and an infrastructure for commissioning/testing • through Panda+HammerCloud • ATLAS does not have the right expertise nor manpower for client release management and configuration • So can not commit to WLCG for maintaining MW clients in CVMFS Simone Campana – Nov 2012 GDB

More Related