1 / 5

Database Infrastructure

Database Infrastructure. Major Current Projects CDF Connection Metering, codegen rewrite, hep w/ TRGSim++ – Dennis CDF DB Client Monitor Server and MySQL Database – Yuyi CDF sow controls, ICICLE (test with 9i) - Margherita

clayr
Download Presentation

Database Infrastructure

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Database Infrastructure • Major Current Projects • CDF Connection Metering, codegen rewrite, hep w/ TRGSim++ – Dennis • CDF DB Client Monitor Server and MySQL Database – Yuyi • CDF sow controls, ICICLE (test with 9i) - Margherita • DAN Middle Tier DB Caching Server, and supporting tools – Steve, Margherita • Proposed Projects • Common Statistics Collecting, Archiving, Monitoring (Alarms, Query, Static Web Presentation) tools ( 6 week project, ~2 FTE’s) • In exploratory phase to find common areas between CDF and D0. – Yuyi, Steve, Eric, Jim, Margharita, John, Lee • Explore common design to handle information • Find common presentation tools • API development work for Run Conditions and Hardware databases ( 10 Week, ~ .5 FTE from DBS, ~2 FTE from CDF) • Goals: rewrite calls to tables from the above db applications to go through a definite API based on the existing DBManager, with extensions, and analogous to the present Calibration API. Text, OTL, ODBC back ends • This step is necessary as a precursor to further 3-tier or freeware development / deployment.

  2. Database Infrastructure • Monitoring (Yuyi) • The logging server design is done, server is working, based on Jims original design in document. • Deliverables for server are complete, pending approval by CDF • Web reporting layer is still being worked on. • Dedicated server machine (fcdfcaf054) for running production monitor provided by CDF. Work completed on the machine to make it useable. • Installed db monitor server and mysql db on this machine. • We cannot move everything away from whcdf03 until cdf has cut new release of client code, with new server address. • CDF client (Dennis) • Tested TRGSim++ from various CDF releases from 4.8.0int2 through 4.9.1pms in an attempt to 'vet' DBManager/DBObjects connection code that has been ready for 4 months into a production release. • Issues for cdf, version upgrades offline software are delayed, trigsim++, Eric is helping as DBS “advocate”.

  3. Freeware Database Infrastructure (1) • General – Dennis, Yuyi, Svetlana • Testing scripts and procedures to map and automate ORACLE to MySQL, MySQL to ORACLE, and MySQL to MySQL transfers. • Some testing of MySQL operation and performance • Minos • Still not completely sure of requirements. • Want remote site to be operational even when network down. • Need to have back up strategy. • Prefer some kind of freeware solution. • Plan to distribute database to university collaborators. • No big hurry, run in 2 years, but would like to establish solution much sooner. Will talk with them and understand needs. Dennis has been the contact so far.

  4. Database and Freeware DB Infrastructure January 28, 2002 Lee Lueking – CEPA/DBS

  5. Freeware Database Infrastructure (2) • CDF (Alan Sill) • Goals: Export at least some of the CDF database to remote institutions in a manner that will allow them to operate more or less independently from the CDF central servers if desired. • People: This was originally a bootleg project on the part of Richard Hughes and David Waters from the collaboration. Recently Svetlana Lebedeva has been working within Fermilab to understand and duplicate their efforts. • Note this has been a high priority on the part of the collaboration for some time, at least in reviews, but support from the CD and from other members of the collaboration has not always been coherent or successful. Note also that this work does not have to compete in principle with a 3-tiered or multi-tiered architecture, as their goals are different. • Status: Richard and others within the collaboration have been able to make access successfully to the calibration portion of the database through modifications to the existing API. This is a clear lesson to us, I think, in the value of having a coherent API.

More Related