Three SGAS components are interesting from the point of view of logging:
- the BANK service
- the LUTS (which is a
logging service)
- the JARM component which is interacting with the grid middleware, ARC in our
case.
What is happening when a job is submitted to an ARC server (which is setup to use SGAS)? First
the BANK is contacted by JARM and a reservation is made (based on the requested wallclock) on the
corresponding account. Then, JARM spools usage records (locally on disk, on the ARC server) for
executed jobs. These jobs are not charged immediately, but can be charged (against the account) and
logged (to the LUTS) periodically in batches with the $SGAS_LOCATION/bin/sgas-batch-job-release
script. In fact, this script is suggested to be executed as a cron job in the installation guide.
Installationwise, I followed the steps describing the binary installation in
http://www.sgas.se/downloads/2.0/SGASInstallConfig.pdf, starting on page 4.
Basically one needs to install JRE 1.5 (1.6 works as well), then download and unpack the installer
from http://www.sgas.se/downloads/2.0/sgas-2.0-installer.tar.gz. At UiB I am currently running the SGAS
BANK and LUTS services on a separate machine from the ARC server, so I needed to install SGAS on
both machines.
Next folow the steps 8-11 in the guide.
My SGAS environment is:
SGAS_BANK_PORT=4455
SGAS_LOCATION=/local/sgas
SGAS_CONTAINER_CERT=/etc/grid-security/hostcert.pem
SGAS_CONTAINER_KEY=/etc/grid-security/hostkey.pem
SGAS_LUTS_PORT=4477
Check the main configuration file which is located at:
$SGAS_LOCATION/etc/sgas-common/sgas.conf, it should look similar to what is attached.
Another important location is
$SGAS_LOCATION/etc/sgas-security, particularly the files:
bank-mapfile, super-users.conf (bank sus), trusted-banks, luts-authz.conf (DNs of entities allowed
to communicate with the LUTS service). I also attached copies of these, so that you have them as
examples.
Now we are ready to start the BANK and LUTS:
sgas-start-bank -p 4455
sgas-start-luts -p 4477
After this one should be able to create an account in the bank and grant some quota to it, this is
well described in the guide on page 24. Regarding the size of the quota, by default, jobs are
charged with one credit per CPU second. Furthermore, unless JARM can approximate the job execution
time (e.g. from a wallclock limit in the job specification), JARM will default to making a
reservation on the account quota for a 24 hour job (i.e. 86400 seconds)*. So make sure you have a
large enough quota, otherwise JARM will signal an account overdraft violation.
Finally one needs to setup SGAS to work with ARC, this resumes to adding a couple of lines to
nordugrid.conf (see page 25 in the guide). We will need a proper SGAS installation on the ARC
server as well.
It is also wise to subscribe to the accounting mailing list: swegrid-accounting@pdc.kth.se
Installation, operation notes
