Progress – details at C-RRB tomorrow

Computing MoUs TaskforceSecond Reportpresented to the LHC Resource Review Boards25th October 2004David JacobsTaskforce Chair DJ: Computing MoU Taskforce Report – 25 October 2004

Progress – details at C-RRB tomorrow • Advanced the body-text of the documents to the rather stable state now given to you for comment • The Annexes will be finalised over the winter • Important element will be Jan-Feb 2005 review of experiments’ needs (chair P. McBride – FNAL) • Presentation of complete documents ahead of April 2005 meetings with a view to approval at that time and launch of the described procedures • The timetable presented in April is thus being adhered to DJ: Computing MoU Taskforce Report – 25 October 2004

Overall Approach Adopted • Decomposed whole LHC experiment-related computing activity into 4 parts: • Main offline infrastructure & common software → LCG MoU (details at C-RRB tomorrow) • Small analysis facilities → left to the experiment concerned • Development of detector-specific and physics analysis s/w → research activities of the scientists in the experiments • The other aspects of experiment-specific Core Computing (mainly effort for development, maintenance and support) →Addenda to the four M&O MoUs DJ: Computing MoU Taskforce Report – 25 October 2004

Overall Approach Adopted Note softening of original boundary between Tier1 and Tier2 centres – reflects a move away from strictly hierarchical relationship in The computing model • Decomposed whole LHC experiment-related computing activity into 4 parts: • Main offline infrastructure & common software → LCG MoU • Small analysis facilities → left to the experiment concerned • Development of detector-specific and physics analysis s/w → research activities of the scientists in the experiments • The other aspects of experiment-specific Core Computing (mainly effort for development, maintenance and support) →Addenda to the four M&O MoUs DJ: Computing MoU Taskforce Report – 25 October 2004

Agreement amongst suppliers  Monitored by Computing RRB Overall Approach Adopted • Decomposed whole LHC experiment-related computing activity into 4 parts: • Main offline infrastructure & common software → LCG MoU • Small analysis facilities → left to the experiment concerned • Development of detector-specific and physics analysis s/w → research activities of the scientists in the experiments • The other aspects of experiment-specific Core Computing (mainly effort for development, maintenance and support) →Addenda to the four M&O MoUs DJ: Computing MoU Taskforce Report – 25 October 2004

Agreement amongst suppliers  Monitored by Computing RRB Additions to the existing M&O MoUs  Monitored by Experiment RRB’s Overall Approach Adopted • Decomposed whole LHC experiment-related computing activity into 4 parts: • Main offline infrastructure & common software → LCG MoU • Small analysis facilities → left to the experiment concerned • Development of detector-specific and physics analysis s/w → research activities of the scientists in the experiments • The other aspects of experiment-specific Core Computing (mainly effort for development, maintenance and support) →Addenda to the four M&O MoUs DJ: Computing MoU Taskforce Report – 25 October 2004

Must be clear... • The computing as now discussed comes on top of the subject matter of the Experiments’ Construction and M&O MoUs – the M&O MoUs make this clear in their Article 3.1 • Cannot therefore offset a computing contribution against what has already been pledged in these documents DJ: Computing MoU Taskforce Report – 25 October 2004

M&O MoU Addenda (MMA’s) • One for each Experiment • Light-weight text, since relies on parent agreement for basic material • E.g. Parties are the same – all of the institutes participating in the experiment • Body text should be same for all Expts: • Differences lie in the Appendices • Even there, Expts starting from similar templates DJ: Computing MoU Taskforce Report – 25 October 2004

MMA’s – Subject Material • Address Expts’ “Core Computing” e.g.: • Infrastructure for s/w development & deployment • Information & documentation systems • Computing model • Management of distributed environment • Links to Grid activities • Building, deploying and operating production systems • Designing, prototyping and operating filter farms • Local data storage and transfer to offline DJ: Computing MoU Taskforce Report – 25 October 2004

MMA’s – Subject Material (2) • Primarily a manpower activity • Naturally part of M&O: • Ongoing • Large operational content • Mainly Category “B” • Institutes take responsibility for parts of work • May be some Category “A” • Mainly related to support and operations tasks DJ: Computing MoU Taskforce Report – 25 October 2004

MMA’s – Approval & Oversight • Nothing new invented… • Since part of M&O, the RRB of each Experiment fulfills this role • Scrutiny and approval becomes part of the already established mechanism for other M&O activities • The RRB is advised on this along with the other M&O matters by the M&O Scrutiny Group • Same rolling procedure – #s presented in April ‘05 will launch the scrutiny procedure for 2006 DJ: Computing MoU Taskforce Report – 25 October 2004

MMA’s – IPR & Liability • IPR clause is for protection of the users • Protects against introduction of software the use of which could later be prohibited • Open Source license is considered the appropriate way to do this • Liability • Parties have no liability to each other with respect to the software • These clauses only have worth if binding DJ: Computing MoU Taskforce Report – 25 October 2004

Progress – details at C-RRB tomorrow