Relational DB for KM3NeT Cristiano Bozza – University of Salerno – Sept 5 th, 2012 Items that should have full documentation Identification of each PMT (S/N – barcode association) Datasheets of each PMT Results of test-bench for each PMT PMT Calibrations Electronic board certifications (electronic format) Deliveries – transport Log of sea operations (placement) Data a tower produces as soon as it’s in place Data from acoustic position sensors Sea properties

Relational DB for KM3NeT Cristiano Bozza – University of Salerno – Sept 5 th, 2012 Test bench data collectionExample of PMT data: Tension Current Temperature Delays Tasks to accomplish: Define data to be stored Define DB tables Set up the DB Build a GUI interface for easy operation Real-time documentation of construction and tests In the (hopefully remote) case of failures, documentation of construction tasks will be needed Mechanical structure Results of tests Check how many components fail to pass the tests and need fixing

Relational DB for KM3NeT Cristiano Bozza – University of Salerno – Sept 5 th, 2012 Hardware needed for Database of construction and test-bench Client #1 Client #2 Barcode reader Internet DB Mirror DB A mirror server would be useful but may be made with stock HW

Relational DB for KM3NeT Cristiano Bozza – University of Salerno – Sept 5 th, 2012 Hardware needed for Database of construction and test-bench 1× server with limited, redundant storage (< 100 GB) – 4 k€ 2× client machines to perform test-bench data insertion – 4 k€ (such machines will be displaced to the production firms) Placement of the construction DB: to be defined in accordance with the overall tender for construction

Relational DB for KM3NeT Cristiano Bozza – University of Salerno – Sept 5 th, 2012 R&D for Database of experiment data Tasks to accomplish: Implement efficient and safe data storage (including proper backup policy) Distribute data to consumers (mostly analysis centers) in a way that is suitable for the analysis software Work in 24  7 fashion, with redundant servers: maintenance tasks must be foreseen in advance, and the system must be able to work in downgraded mode for a limited amount of time

Relational DB for KM3NeT Cristiano Bozza – University of Salerno – Sept 5 th, 2012 Hardware needed for R&D on Database of experiment data 2× realistic storage devices (RAID array of HDD drives and SSD cache) – 13 k€ each 2× DB servers in a cluster arrangement with FiberChannel – 5 k€ each Duplication of tasks is an essential feature at this stage: real performances can only be assessed in RAC (cluster) configuration Need to simulate at least 10 reader jobs together with 1 or 2 writer jobs Understand possible bottlenecks and scalability with number of machines No backup is foreseen at this stage to save money

Relational DB for KM3NeT Cristiano Bozza – University of Salerno – Sept 5 th, 2012 Overview of financial requests for DB project 2× storage devices for data DB R&D – 26 k€ 2× DB servers for data DB R&D – 10 k€ 2× clients for test-bench data collection and documentation of construction/certification information – 4 k€ 1× DB server for test-bench and construction information – 4 k€ but The DB server for construction and test-bench data can be consolidated with the servers for data DB R&D, saving 4 k€ Grand total: 40 k€