Presentation on theme: "WP 1 Members of Wp1: INFN Cesnet DATAMAT PPARC. WP 1 What does WP1 do? Broker Submission mechanism JDL/JCL and other UIs Logging computational economics."— Presentation transcript:
WP 1 What does WP1 do? Broker Submission mechanism JDL/JCL and other UIs Logging computational economics Checkpointing (Red = something by PM9, Green=after PM9 )
WP 1 What is PPARCs role? Testing and refinement. (provide a test site by mid June when the PM9 deliverables start be become available) Provide liaison between EU DataGRID and US grid projects.
WP 1 User interface:- All commands begin with dg- e.g. dg-job-submit dg-job-cancel dg-list-job-match UI will provide mechanism for certification UI will interpret ClassAds (providing defaults for mandatory Ads UI will be able use different RBs and LBs (depending on local config files) UI will be written in python, at least in PM9
WP 1 JCL/JDL :- Will be based on Condor style ClassAds. User specifies executable and data files. User specifies the resources they require … and preferences.
WP 1 Broker is central to the submission process. Matches ClassAds to available computational resources. Decides where best to submit job, and finally submits it to condor-g. All the way through broker tracks jobs. This information will be available to the user, either via a fast or slow mechanism. Broker is written in C++. C/C++ APIs will be available
WP 1 Logging and bookkeeping (provided by Cesnet) Logger is based on netlogger. All players in job submission mechanism will push information into the log files. This will be the case for PM9 … maybe passed over Fabric Management later.
WP 1 Lifecycle of a job Generic checkpointing as well as user checkpointing.
WP 1 Computational economics: More important than is generally recognised… if the cost is too high you cannot use the resource. Probably going to use e-Euros
WP 1 Conclusions: There will be a working DG job submission mechanism by PM9. With a large range of functionality.