Ali En the works Ali En Site Server

Ali. En: the works Ali. En Site Server Job submission Ali. En CE Ali. En SE Status report Data Catalogue WN’s = The CE “pulls” a job from the server and sends it to a WN = The job, once on the WN, reports to the server, identifying and authenticating itself via a Proc. ID/Job. Token pair = Any data produced is stored on the local SE, and files are registered in the Data Catalogue File registration Data. TAG WP 4 Meeting CNAF Jan 14, 2003 Interfacing Ali. En and EDG 2/13 Stefano Bagnasco, INFN Torino

Exploiting Data. GRID The philosophy: Server Interface Site Ali. En CE EDG UI Ali. En SE The whole Grid (namely, a Resource Broker) is seen by the server as a single Ali. En CE, and the whole Grid storage is seen as a single, large Ali. En SE. = An “interface site” is thus an EDG User Interface machine which runs the Ali. En client suite Cluster. Monitor, CE and SE = grid 006. to. infn. it (EDG 1. 2. 3) Data Catalogue Data. TAG WP 4 Meeting CNAF Jan 14, 2003 = testbed 010. cern. ch (EDG 1. 4. 0) = grid 010. to. infn. it (EDG 1. 4. 2) Interfacing Ali. En and EDG 3/13 Stefano Bagnasco, INFN Torino

Job Submission 1 EDG RB Server Job submission = The interface Interface Site Ali. En CE EDG UI client “pulls” a job from the server; = The Resource Broker interface is implemented as a Local Queue object (like PBS, for example) Data. TAG WP 4 Meeting CNAF Jan 14, 2003 Ali. En SE =A new JDL file is generated, adding: - requirements for Ali. En runtime environment - requirement for outgoing connectivity - environment variables containing the Proc. ID/Job. Token pair = Special. Requirements Class. Ad attribute is used to pass requirements not meaningful to Ali. En = The job is submitted to the Resource Broker Interfacing Ali. En and EDG 4/13 Stefano Bagnasco, INFN Torino

Job Submission 2 EDG RB Server Job submission Interface Site EDG Site Ali. En CE EDG UI EDG CE EDG SE Ali. En SE Status report = A DB of EDG/Ali. En Job. IDs is kept by the WN interface CE to keep track of jobs that did not report yet to the server Ali. En M Problem tracking yet to come. . . Data. TAG WP 4 Meeting CNAF Jan 14, 2003 Interfacing Ali. En and EDG 5/13 Stefano Bagnasco, INFN Torino

Data catalogue registration 1 =An output file is Server generated by an Ali. EN job running on some EDG site = The Close. SE is determined by Ali. En code (running on the WN) from the. Broker. Info file = The file is stored in EDG Site EDG CE EDG SE PFN WN Ali. En the selected SE and registered in EDG Replica Catalogue = LFN uniqueness is enforced by Ali. En EDG RC Data Catalogue Data. TAG WP 4 Meeting CNAF Jan 14, 2003 Interfacing Ali. En and EDG 6/13 Stefano Bagnasco, INFN Torino LFN

Data catalogue registration 2 = A “intermediate” file Server EDG Site name is generated using the EDG LFN and the VO name (to allow form multiple VO/RC) EDG CE = The file is now EDG SE registered in Ali. En Data Catalogue using this “intermediate FN” as PFN WN Ali. En = The file is registered in both catalogues, thus ensuring accessibility from both worlds. Data Catalogue EDG RC EDG: //<VO>/<LFN> Data. TAG WP 4 Meeting CNAF Jan 14, 2003 Interfacing Ali. En and EDG 7/13 Stefano Bagnasco, INFN Torino

Data access - basic case = Ali. En Job running on EDG site accessing Ali. En-generated data stored in EDG resources Two-step process via the Ali. En Data Catalogue and the EDG Replica Catalogue, all file transfers are local to the site: M Input. Data requirements are not yet passed automatically to the RB via the JDL. As a temporary workaround, input file information has to be specified by hand using the Special. Requirements Class. Ad attribute in the Ali. En JDL. EDG Site EDG CE EDG SE WN Ali. En Data Catalogue Ali. En LFN EDG: //<VO>/<EDG LFN> Data. TAG WP 4 Meeting CNAF Jan 14, 2003 PFN LFN EDG RC Interfacing Ali. En and EDG 8/13 Stefano Bagnasco, INFN Torino

Data access - EDG case = Non-Ali. En job running on EDG accessing Ali. En-generated data on an EDG SE Files are registered in both catalogues with consistent LFNs. The job can use directly the EDG Replica Catalogue. EDG Site EDG CE EDG SE WN EDG RC Data Catalogue Data. TAG WP 4 Meeting CNAF Jan 14, 2003 Interfacing Ali. En and EDG 9/13 Stefano Bagnasco, INFN Torino

Data access - exotic cases =Ali. En job running on EDG accessing data on an Ali. En SE The requirement for Outgoing. IP ensures Ali. En Data Catalogue from the EDG WN. Ali. En Site Interface Site EDG Site Ali. En Client EDG CE Ali. En CE EDG UI EDG SE WN Ali. En CE WN Ali. En SE Data Catalogue Data. TAG WP 4 Meeting CNAF Jan 14, 2003 Ali. En LFN Ali. En PFN EDG RC Interfacing Ali. En and EDG 10/13 Stefano Bagnasco, INFN Torino

Data access - exotic cases =Job running on Ali. En site accessing Ali. En-generated data stored in EDG resources Two-step process via the Ali. En Data Catalogue and the interface SE (implementing an MSS object, like Castor, to interface to EDG): Ali. En Site Interface Site EDG Site Ali. En Client EDG CE Ali. En CE EDG UI EDG SE WN Ali. En CE Ali. En SE Data Catalogue Data. TAG WP 4 Meeting CNAF Jan 14, 2003 EDG RC Interfacing Ali. En and EDG 11/13 Stefano Bagnasco, INFN Torino

Open issues M Error and problem tracking not yet complete M Input. Data requirements are not yes passed automatically to the RB (because of the “intermediate” LFN) M The interface site may be a bottleneck for crossworld jobs (i. e. jobs on EDG needing data from Ali. En and vice-versa) M Much testing still to be done Data. TAG WP 4 Meeting CNAF Jan 14, 2003 Interfacing Ali. En and EDG 12/13 Stefano Bagnasco, INFN Torino

Conclusions System is in place, but. . . =Full functionality still to be tested - The work just started, until now only tested separated pieces M A couple more issues to address MMany small (even trivial) problems: minor bugs, EDG releases, different RC schemas, not all EDG tools correctly return error value, Ali. En installation in EDG sites. . . Data. TAG WP 4 Meeting CNAF Jan 14, 2003 Interfacing Ali. En and EDG 13/13 Stefano Bagnasco, INFN Torino