Sa grid application inventory 36

SAGrid Ops

Application
Inventory
Status Report
and
21.9.2012
Developments
Bruce Becker | bbecker@csir.co.za
Coordinator – SAGrid | http://www.sagrid.ac.za

SAGrid VO applications -
organisation
● SAGrid is a catch-all VO - need
● to deploy a wide set of useful applications
● procedure for identifying new applications
● Procedure for porting/deploying new applications
● Applications are in many different domains, and some
underpin others
● Dependencies
● Tools
● Applications

21.9.2012 Bruce Becker | bbecker@csir.co.za

Application deployment (1)
● Applications need to be available on the site in
order for the user to run them. Either
● In system-level (local root priveliges required)
● In VO software directory (SAGrid SoftwareManager
priveliges required)
● Sites need to be tagged in order for users to find
the applications
● Site-info.def (local root priveliges)
● Lcg-tags (SAGrid SoftwareManager priveliges)


Application Deployment (2)
SAGrid Software Admin Site admin
Installation method Installation job sent to the Application is found
site
Software source SVN repo for script and SVN repo for script and
small ISB small ISB
Software packages from Software packages from
website and/or LFC website and/or LFC + yum
repo
Bottleneck/ Script not tested/produced Site administrator
showstopper Dependencies missing on themsevles
site No installation script
Required version doesn't
exist in repos


Installation by pros cons
SoftwareManager Can install on any site Same installation script
needs to be run on all sites

Can test on any site that Duplication of effort when
runs sgm jobs application exists in repo

Can install, test, validate
and tag sites synchronously

Site Admin


Ways to make our WN better
● With a few tweaks to the WN installation procedure, we can
make sites much better
● Site admin is by definition present when installing/configuring WN
● SGM can prepare a master script to run after yaim completes :
– Install SAGrid apps from any relevant repo
– Ensure perms are correct
– Tag site correctly
– Inform SGM if additional steps are necessary (email)
● Propose : add milestone to tracking system for post-yaim-config
checks, keep the master file in SVN, keep standard tags on
ROC and wiki.


Current status
● Keep a master ticket for common dependencies of
applications: https://ops.sagrid.ac.za/trac/ticket/474
● Many SAGrid apps and domain-specific apps
depend in principle on these libraries
● The depgraph is meant to track these dependencies
● Not all dependencies need to be provided by SAGrid
repo – where possible provided by external repo


Dependency tree
Start at the top, work down

SAGrid Tools SAGrid Apps
Master ticket Master ticket


Tools and dependencies
GCC

modules

ATLAS AUTOdock

Domain-specific applications

Wrong dependency !


Common dependencies status
Package name In repo ? Newer version Script in SVN repo ? Note :
on website ?
LAPACK Needed by many
applications, as wel
BLAS as numpy/scipy
ATLAS
SuiteSparse Needed by ATLAS
and one cosmo app
GCC (+ deps) Few apps need newer
GCC
modules Needed for user env.
GSL Can be linked in
statically at compile
BOOST C++ time for user
numpy applications.

scipy
fftw

SL REPO EPEL REPO Major version Script works
difference
SAGrid REPO Not in a REPO Development
Minor version started
difference
Nothing
Coordinator – SAGrid | http://www.sagrid.ac.za yet

Site tool status
ZA- ZA-UJ ZA-UFS ZA-NWU ZA- ZA- ZA- ZA-
WITS- Glexec UCT- TLABS SAAO CHPC
CORE problem ICTS Output
problem
LAPACK 3.0-37 3.0-37 Site not Site not
BLAS 3.0-37 3.0-37 3.0-37 running running
jobs jobs
ATLAS 3.8.3 3.8.3 3.8.3 3.8.3
SuiteSparse

GCC (+ deps) 4.12 4.12 4.1.2 4.12 4.4.6 4.1.2
modules 3.2.6 3.2.8a 3.2.9c 3.2.7b 3.2.7b 3.2.9c
GSL 1.13 1.13 1.13 1.13
BOOST C++ 1.33 1.33 no 1.33 1.33 no 1.41 1.33
headers headers
numpy 1.2.1 Only 1.2.1 Only
python- python-
numpy numpy
scipy

fftw 3-3.1 3.1.2


Where are we going ?
● Identifying and maintaining dependencies of applications doesn't require
grid expertise
● Maintaining installation and tagging scripts doesn't require site-admin rights
● Applications are either generic (cross-domain) or specific (to a domain)
● We can organise responsibility hierarchically:
● Ensure that SAGrid tools are installed on WN by site admins – checked by Ops
Coordinator
● Each domain gets a master ticket, milestone, etc on trac – new requests block the
master ticket
● Identify domain-specific champion to coordinate domain-level user requests –
can evolve into separate VO
● Open up app porting to wider community of developers


Domain-specific requests (astro)


Applications status
Package name In repo ? Newer version Script in SVN Note :
on website ? repo ?

SL REPO EPEL REPO Major version Script works
difference
SAGrid REPO Not in a REPO Development
Minor version started
difference
Nothing
Coordinator – SAGrid | http://www.sagrid.ac.za yet

Site-level Tags


Application tags


Sa grid application inventory 36

Recomendados

Recomendados

Mais conteúdo relacionado

Semelhante a Sa grid application inventory 36

Semelhante a Sa grid application inventory 36 (20)

Mais de Bruce Becker

Mais de Bruce Becker (9)

Último

Último (20)

Sa grid application inventory 36