Deploying a software on the grid can be time consuming. We wrote a chain of scripts that should facilitate the deployment of a software across multiple sites. You can downlad an archive containing a collection of scripts at the bottom of the page (deploy.tgz)
This collection of script is aimed at facilitating grid software deployment.
FIrst you should go in 1.check-status and run the numbered script.
will generate a jdl file per computing element that are currently advertized (found with lcg-infosites
will submit a job per ce. The job is really small (see FILES/mdirectory) and give some general info about the software directory hierarchie etc...
Check the status of the jobs.
Get the output if the job is succesfull
get the output if the job has exit different than 0.
Once you run script 2. you should wait a while (24h?) to give the time for the jobs to finish. You can check with 3. You can use multipe time 4. and 5. as if the job is already cleared, it won't get the output anymore.
Only the ce with succesfull jobs will be used later on for grid deployment.
Then you should go into 2.deploy dir. For each software you want to deploy, you should
a.Add a soft link of all the files in DEPLOY-TEMPLATE/ dir in the SOFTWARE/target-software/ you want to deploy
[christophe@ui-enmr gmx4.5.3.rtc]$ for i in ../../DEPLOY-TEMPLATE/*.sh; do ln -s $i ./; done
b. Create correctly the file SOFTWARE/target-software/FILES/deploy.sh and SOFTWARE/target-software/FILES/test.sh
For example SOFTWARE/gmx4.5.3.rtc/FILES/deploy.sh
c. Create correctly the tag file SOFTWARE/target-software/FILES/tag
For example SOFTWARE/gmx4.5.3.rtc/FILES/tag
d. call in the correct order the scripts linked in 1. More details bellow.
It list all ce and show if the target tag is already presents
generate 2 jdls (test and deploy) per targets. The targets are the one for succesfull jobs during the check-status phase (in the 1.check-status/OUT/ dir)
This script will ask you on which ce you want to deploy. It will display the output of the 1.check-status/OUT/ directory for visual inspection. Be carfull, some ces actually mount multiple time the same SOFT directory, so if you deploy simultanesouly the same software to 2 ces that mount the same SOFT dir, you might run into trouble.
run this command to see the status of the deploy jobs
Run this job to get the output of the deploy job (can be run multiple time)
Same if the job has exit != 0
For succesfull deploy jobs, you can submit a test job. It will ask you for visual inspection of the output done at script 4.
you can chekc the status of the test jobs
You can get the output of the test jobs
you can get the output of jobs with exit code != 0
This script will display for every succesfull job the output, and ask you if you want to tag the corresponding ce.