Setup of a Local (LHCb-) Dirac Developer Environment

For future reference and in case I need to do it again, the necessary steps for the setup are documented here. Some just concern my machine, i.e. the dual-boot setup, and are declared as such.

Debian (Ubuntu 12.04)

First of all run the update-manager and install some python-packages and useful tools.

sudo apt-get update; sudo apt-get upgrade
sudo apt-get install ipython python-dev python-lfc python-mysqldb 
sudo apt-get install vim subversion git

The next step serve only to get my dual-boot setup working:

sudo apt get lvm2
#reboot
#mount partition with other linux distro
sudo update-grub

The pyGSI package is needed and available on Github:

cd ~/Downloads
 git clone https://github.com/acasajus/pyGSI
 cd pyGSI
 sudo python setup.py install
 cd ..

This should have gotten you all packages needed. DIRAC itself can be setup with:

(I skipped forging the DIRAC-repo, because most likely I am not going to change it. )

mkdir ~/devDirac; cd ~/devDirac
 export DEVDIRAC=/home/vali/devDirac/ 
 git clone /DIRAC.git
 git clone https://github.com/DIRACGrid/DIRAC.git
 cd DIRAC/
 git remote add upstream https://github.com/DIRACGrid/DIRAC.git
 git fetch upstream
 cd ..
The next part can be skipped if you use your session username with cerns svn. In order to check out the lhcb with another username than you are currently logged in, edit/create ~/.ssh/config and add the lines (as described in https://twiki.cern.ch/twiki/bin/view/LHCb/SVNUsageGuidelines#Connecting_with_a_different_user )

Host svn.cern.ch svn
   User myusername
   Protocol 2
   ForwardX11 no
   IdentityFile ~/.ssh/id_rsa
Host isscvs.cern.ch
   User myusername    
   Protocol 2
   ForwardX11 no
   IdentityFile ~/.ssh/id_rsa

This enables you to run

svn co svn+ssh://svn.cern.ch/reps/lbdirac/LHCbDIRAC/trunk/LHCbDIRAC LHCbDIRAC

Now is the time to run

DIRAC/Core/scripts/dirac-deploy-scripts.py

The last missing parts are the certificates (https://twiki.cern.ch/twiki/bin/view/LHCb/FAQ/Certificate). Following the steps in the link export the certificate from your browser as a .p12 file

mkdir $HOME/.globus; cd $HOME
openssl pkcs12 -in myCert.p12 -clcerts -nokeys -out $HOME/.globus/usercert.pem
openssl pkcs12 -in myCert.p12 -nocerts -out $HOME/.globus/userkey.pem
 chmod 404 .globus/userkey.pem 
I then copied the key and certificate to a newly created etc/grid-security directory in our dirac development path.
cd $DEVDIRAC
mkdir etc; mkdir etc/grid-security
cp ~/.globus/user* etc/grid-security/

We have to set another few variables:

export PYTHONPATH=/home/vali/devDirac
 export PATH=$PATH:/home/vali/devDirac/script

Now what remains to do is to deploy the configuration file dirac.cfg in etc. For me it was simply needed to update the user entry in the registry

Users
  {
    [your username]
     {
      DN = [your DN]
      CA = [your CA]
      Email = [your email]
    }

Now dirac-proxy-init and the DIRAC imports in python should work.

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2013-07-23 - ValentinVolkl
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox 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.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback