Title: INFN%20-%20Ferrara
1INFN - Ferrara
- BaBar Meeting
- SPGrid status in Ferrara
Enrica Antonioli - Paolo Veronesi Ferrara,
12/02/2003
2Topics
- The DataGrid project
- Ferrara Farm Configuration
- First SP submissions through the Grid
- Work in Progress
- Future Plans
3European DataGrid and INFN-GRID
EDG
- Computing Grids permit
- High Throughput Computing
- Analysis of large dimension data
- Sharing resources and data
- Applications involved
- Biomedical Sciences
- Earth Observation
- High Energy Physics
4EDG Architecture and Services
OS Net services
5Grid Elements in Ferrara
- The DataGrid Testbed consists of different types
of machines (Grid Elements). - In Ferrara the farm is composed by one Computing
Element (CE), three Worker Nodes (WN), one User
Interface (UI) and one Storage Element (SE). - All these machines are managed by a LCFGng (Local
ConFiGuration system new generation) server and
they are automatically configured.
6User Interface
- UI (User Interface) component for accessing to
the workload management system. - Users can submit a job and retrieve the output,
they sholud have an account and a personal
certificate installed in their home directory.
To access the GRID you have to request a
certificate to a certification authority.
INFN-GRID users can obtain a certificate from
the INFN CA (http//security.fi.infn.it/).
UI
To use the BaBar Grid, you must register that
certificate with the BaBar Virtual Organisation
(BaBar VO).
http//www.slac.stanford.edu/BFROOT/www/Computing/
Offline/BaBarGrid/registration.html
7Job Submission
Storage Element
8SPGrid Farm in Ferrara
CNAF - Bologna
CERN
Ferrara - EDG 1.4.3
9Configuration
- INFN Grid Testbed Status EDG 1.4.3 (RedHat 6.2).
- A BaBar software special release (12.3.2y) has
been built and installed to - Write Kanga files
- Run Moose on RH 6.2
- A special tag of ProdTools has been installed to
perform tests. - A pool of BaBar accounts (babar000, babar001,)
has been created in the EDG farm of Ferrara. - Each member of BaBar VO is able to submit jobs to
the farm of Ferrara through the RB located at
CNAF (grid009g.cnaf.infn.it).
10Current Status
- Created a JDL file to run Moose on Grid
resources. - Created scripts containing EDG commands to submit
jobs, to check their status and retrieve output
files. - An user can submit a range of runs.
- For each run a job is created and submitted to
the Resource Broker, then it is sent to the
Ferrara CE (grid0.fe.infn.it). - The output file is then transferred to the
closest SE (grid2.fe.infn.it).
11Moose.jdl
Similar to SP standard scripts (Job.Xsh)
grid1gt more Moose.jdl Executable
"Moose.csh" InputSandbox "Moose.csh",".cshr
c","config.csh" StdOutput
"Moose.txt" StdError "Moose.log" Output
Sandbox "Moose.txt","Moose.log"
Config file for BaBar. Similar to SP standard
scripts
General environment configurations
Globus command To copy output files from WN to SE
tar -czvf runRUNNUM.tar.gz
.root globus-url-copy -vb file//pwd/runRUNNU
M.tar.gz \ gsiftp//grid2.fe.infn.it/flatfiles/SE
00/paolo/runRUNNUM.tar.gz
12The launch script
grid1gt more launch !/bin/tcsh -v _at_ num_f
1 _at_ fin 2 while ( num_f lt fin
) build the run directories build a
config.csh with the appropriate environment
variables echo "\!/bin/tcsh -v" gt
config.csh now run the job dg-job-submit
-o runnum_f.jobid -r \ grid0.fe.infn.it2119/jobm
anager-pbs-long Moose.jdl cd .. _at_ num_f end
For each run a job is created runtime
Range of runs to submit
A config file is created for each run
EDG job submission command
13Job Submission
Range of runs to submit
grid1gt ./launch 1962016 1962017 dg-job-submit
-o runnum_f.jobid -r grid0.fe.infn.it2119/jobman
ager-pbs-long Moose.jdl Connecting to host
grid009g.cnaf.infn.it, port 7771 Logging to host
grid009g.cnaf.infn.it, port 15830
dg-job-submit Success The
job has been successfully submitted to the
Resource Broker. Use dg-job-status command to
check job current status. Your job identifier
(dg_jobId) is https//grid009g.cnaf.infn.it7846
/193.206.188.102/104224188091275?grid009g.cnaf.inf
n.it7771 The dg_jobId has been saved in the
following file /home/enrica/stress/1962016/run19
62016.jobid
CNAF RB
Job ID
grid1gt ls 1962016 1962017 Moose.csh Moose.jdl
config.csh launch monitor retrieve
14The monitor script
grid1gt more monitor !/bin/tcsh _at_ num_f 1 _at_
fin 2 while ( num_f lt fin ) echo Run
num_f is dg-job-status -i \ num_f/runnum_f.job
id grep Status _at_ num_f end
EDG command
grid1gt ./monitor 1962016 1962017 Run 1962016 is
Status Scheduled Status Reason initial Run
1962017 is Status Scheduled Status Reason
initial
grid1gt ./monitor 1962016 1962017 Run 1962016 is
Status Running Status Run 1962017 is Status
Running Status
grid1gt ./monitor 1962016 1962017 Run 1962016 is
Status Ready Status Reason job accepted Run
1962017 is Status Ready Status Reason job
accepted
grid1gt ./monitor 1962016 1962017 Run 1962016 is
Status OutputReady Status Reason terminated
Run 1962017 is Status OutputReady Status
Reason terminated
15The retrieve script
grid1gt more retrieve !/bin/tcsh -v _at_ num_f
1 _at_ fin 2 while ( num_f lt fin ) cd
num_f get logfiles dg-job-get-output -i
runnum_f.jobid --dir PWD get
rootfiles globus-url-copy \ gsiftp//grid2.fe.inf
n.it/flatfiles/SE00/paolo/runnum_f.tar.gz \
file//pwd/runnum_f.tar.gz tar -xzvf
runnum_f.tar.gz rm -f runnum_f.tar.gz
delete rootfiles form SE globus-job-run
grid2.fe.infn.it /bin/rm \ /flatfiles/SE00/paolo/r
unnum_f.tar.gz cd .. _at_ num_f end
EDG command
16Retrieving Output
grid1gt ls 1962016 1962017 Moose.csh Moose.jdl
config.csh launch monitor retrieve
17Future Plans
Ferrara
3) Install Objy DB on the SE
SPGrid Farm
2) MOOSE in RPM format
1) Use of IC RB and others
18Documentation
- The DataGrid Project
- http//eu-datagrid.web.cern.ch/eu-datagrid/default
.htm - EDG tutorials Archive Web Site
- http//hep-proj-grid-tutorials.web.cern.ch/hep-pro
j-grid-tutorials/loginex.html - INFN-Grid Testbed http//server11.infn.it/testbed
-grid/ - BaBar-Grid
- http//www.slac.stanford.edu/BFROOT/www/Computing/
Offline/BaBarGrid/ - Status of the Farm in Ferrara http//print.fe.inf
n.it/status/