180 likes | 393 Views
First evaluation of the Globus GRAM service. Massimo Sgaravatto INFN Padova. GRAM & fork system call. Simple job submission tests using globusrun, globus-job-run, globus-job-submit No serious problems found. GRAM & Condor. INFN WAN Condor pool configured as Globus resource
E N D
First evaluation of the Globus GRAM service Massimo Sgaravatto INFN Padova
GRAM & fork system call • Simple job submission tests using globusrun, globus-job-run, globus-job-submit • No serious problems found
GRAM & Condor • INFN WAN Condor pool configured as Globus resource • ~ 200 machines spread across different sites • Heterogeneous environment • No single file system and UID domain
GRAM & Condor • The RSL common set is often insufficient (i.e. the Condor “requirements” attribute is necessary) • The unrecognized attributes are not passed unchanged • Serious problem in particular for Condor vanilla jobs
Submittig Condor jobs to Globus resources • Two possible mechanisms: • Globus Universe • GlideIn mechanisms
Globus Universe Universe=globus Executable=/users/noi/sgaravat/CondorGlobus/ciao Output=/users/noi/sgaravat/CondorGlobus/out.$(Process) GlobusScheduler=lxde16.pd.infn.it/jobmanager-fork Queue 10 • Is it a simple translation: condor_submit globusrun ? • Why is it useful ? • It will be very very very useful when Condor will be so smart to choose the Globus resource where to submit the jobs
GlideIn lxde01% condor_glidein lxde15.pd.infn.it lxde01% condor_glidein lxde16.pd.infn.it
GlideIn • Standard and vanilla Condor jobs successfully submitted and executed • The current implementation is not too much useful: • It is not necessary to install Condor on the remote resources … • … but it is necessary to install Globus !
GRAM & LSF • Not all operations are possible (the RSL attributes are not enough) • Not a so serious problem because usually the policies are defined in the queue
RSL • We need a uniform language to specify resources, between different resource management systems !!! • The RSL syntax model seems suitable to define even complicated resource specification expressions • The common set of RSL attributes is often not sufficient
RSL • The attributes not belonging to the common set are ignored • Serious problem in particular when Globus relies upon a heterogeneous Condor pool • More flexibility is required • It should be possible to define new attributes and users should be allowed to use them in resource specification expressions (Condor ClassAds model) • Same language to describe the offered resources and the requested resources (ClassAds model) ?
Conclusions • RSL must be improved • Local GRAMs should provide the GIS with other important information about characteristics and status of local resources • Globus & Condor • Promising activities • Not too much useful at the moment
Future activities • GRAM and other resource management systems (e.g. PBS) • Use of GRAM API • Use of GRAM service in production environments for real applications (e.g. HLT activities) • Resource broker • Condor and Globus • Personal Condor as HTB for Globus Resources ?
Globus Gatekeeper Globus Gatekeeper Globus Gatekeeper Site X jobs Site Z Personal Condor Personal Condor as broker for Globus resources ? Site Y