CD FY09 Tactical Plan Review FY09 Tactical Plans for Scientific Database Applications Igor Mandrichenko Sept. 24, 2008

CD FY09 Tactical Plan Review 2 FY09 Tactical Plan for Database Services CD DocDB Document 2890-v Tactical Plan Scientific Database Applications Tactical Plan Leader: J.Trumbo Organizational Unit home: LSCS/DBI/DBA

CD FY09 Tactical Plan Review 3 FY09 Tactical Plan: Strategies and Goals Tactical Plan Strategies - Develop and maintain expertise in design, development and support. - Select minimal but sufficient set of software solutions. - Offer limited number of solutions for wide variety of scientific applications, focus on non commercial software products, freeware, public domain products and OS - First tier choices for databases are Oracle and PostrgeSQL. We will also support applications using MySQL and MSSQL. - Research new technologies as they become available, select & use them in developing new applications Tactical Plan Goals –Provide expertise, design, develop and support database applications for HEP and Astrophysics –Maintain & support an inventory of existing RunII applications

CD FY09 Tactical Plan Review 4 FY09 Tactical Plan: Objectives Tactical Plan Objectives Maintain the inventory of existing database applications used by RunII experiments developing a support strategy and prioritized plan, taking account resources. Support D0 Trigger DB application. Support db_server technology. Consult D0 and if necessary participate in revamping of D0 Luminosity DB application, move it into support/maintenance mode. Consult CDF and identify opportunities for CD to assume support roles for database applications. Participate in design and development of DES, NOvA, ILC & Project X.

CD FY09 Tactical Plan Review 5 Service Activity: Scientific Database Application Support Key Metrics 1.Timely efficient support 2.Development goals and milestones met Issues and Risks (specific to this activity, includes allocation impact) 1.Old applications approaching their scalability, performance limits 2.Desire of Run II experiments to collect as much as possible data before end of Tevatron era 3.Loss of experts by Run II experiment Support running experiments D0, CDF, ILC, NOvA, DES, Project X, SDSS at appropriate levels. Insure a stable, performant, and smooth running environment. Goals Related to this Activity [from Tactical Plan] –Keep applications secure and base line compliant. –Provide useful products optimizing software and maintenance costs.

CD FY09 Tactical Plan Review 6 FY09 Resource Request, Preliminary Allocation Level 0 Activity: Scientific Database Applications FY09 Tactical PlanActivity Level 1 FTE Request At Activity Level 1 M&S Request At Activity Level 1 FTE Allocation At Activity Level 1 M&S Allocation At Activity Level 1 Scientific Database Applications D0 CDF DES Nova Project X RF Cavitiies License Renewal Total 2.05$ $0

CD FY09 Tactical Plan Review 7 Impact of Preliminary Allocation

CD FY09 Tactical Plan Review 8 Template Guidance: (not part of the presentation) Activity = Activity Level 1 or lower explicitly listed in Tactical Plan Activities have been classified in Tactical Plans as either being more Project-like or Service-like Projects: finite defined lifetime, defined deliverable. Includes R&D work. A.k.a Upgrades, … Services: same operation or task repeatedly. A.k.a. Operations, Maintenance, Support, … Whether an activity is a project or service determines which format slide to use later. Terminology Obligation Budget: Allocated budget. This may differ from the budget request. YTD Obligations: Fully incurred expenses. Does not include RIPs, Req.s in CD, etc. Current FY08 Forecast: Estimate of all obligations to be incurred by the end of FY08. M&S: Equipment + Operating. Operating includes Travel, Material Purchases, Professional Services (contractors), Maintenance (licenses), and Other. RIP: Requisitions in Progress