VeryQuickGuideCMSSWDeployment

CMSSW Deployment Home

A Very Quick Guide To CMSSW Deployment

Before Each Deployment

• login on m1.iihe.ac.be as cmssw

ssh cmssw@m1.iihe.ac.be

• create a proxy:

source CreateProxy.sh yourname

  This command changes the current directory to the release-installer area

/user/cmssw/Deployment/tag-handler

What To Do If ...

• a new version of CMSSW is released or an old version is deprecated:
  • • submit installation/removal jobs

ri -s

• • • Check the job status.

ri -l

• • • Retrieve (Fetch) the output of the installation jobs:

ri -f

     The output is stored in 

/user/cmssw/cms/release-installer/<JOBSTATUS>/<CE>/<TIMESTAMP>

     <JOBSTATUS> is the status of the job

     <CE> is de site ce name

     <TIMESTAMP is the time of submission in the format yyyy-mm-dd_T_hh_mm_ss

• you want to know where and which releases have to be installed/removed

ri -d

• a site needs manual intervention

ri -d

  This command will also show which sites need manual intervention. If this is the case, there exists a directory

/user/cmssw/cms/release-installer/stopped/<CE>/

  where CE is de site's CE name.

  Go through the output, solve the problem. Open, if useful, a Savannah Ticket. Once the problem is solved, remove the direcory

• a site makes a special request to remove, add or keep a specific release.
  

  Edit the file manual_install_requests.xml and submit to the site(s)

emacs -nw manual_install_requests.xml
ri -c CE1,CE2 -s

• you're not sure what to do:

ri

  a help page will be displayed