Database services in KM3NeT

DATABASES
DB INTERFACE
GRAPHICAL INTERFACES
DATABASE SERVICES IN KM3NET
Cristiano Bozza – Università di Salerno – LNS, NOV 2014
DB System in KM3NeT
km3netdbweb.in2p3.fr
DB
KM3NET
CCIN2P3
km3netsrv01.na.infn.it
DB
KM3ITA
DB
KM3ITA
LNS
UNINA
km3netsrv01.na.infn.it:81
Cristiano Bozza – Università di Salerno – LNS, NOV 2014
DB NEMO
MySQL
DATABASES
2
DB System in KM3NeT
DB
KM3NET
Oracle Database Server
Enterprise Edition
RAC (3 servers in SCAN)
700 GB (extendable)
CCIN2P3
DB
KM3ITA
Oracle Database Server
Standard Edition
Expires July 2015
UNINA
Sized to host several TB’s/year
of Slow Control / DAQ Control data
Oracle Database Server
Enterprise Edition
Partitioning Option
100 NUPs Perpetual
12 TB already available
Oracle licenses purchased with special conditions
100 NUPs = 25 users × 8 cores × 0.5 (Intel core factor)
Cristiano Bozza – Università di Salerno – LNS, NOV 2014
DATABASES
3
State of DB’s
• CCIN2P3
• KM3NeT Collaboration management info (including
authentication)
• PBS
• Integration/cabling information
• Products
• Test/calibration results
• PPM-DOM and PPM-DU book-keeping
• KM3Ita
• Detector definitions
• Runsetups
• User accounts sync’ed with CCIN2P3
• Slow control / DAQ control data log
• Products
(in progress)
• In progress:
• Test/calibration results
• Paper authorship information
(in progress)
• QA/QC documents
• Under development:
Cristiano Bozza – Università di Salerno – LNS, NOV 2014
•
Runsetups
•
Slow control / DAQ control data log
DATABASES
4
KM3Ita
• Complete dataset of NEMO phase 2 Slow Control
• Copy from MySQL DB
• GUI interface to upload component documentation
and test/calibration data in Excel format or ASCII
format (PSS)
• A fraction of components is already documented,
more to come soon
Cristiano Bozza – Università di Salerno – LNS, NOV 2014
DATABASES
5
Functions of the DB Interface (by Arnauld Albert)
• Provide access to the DB
• HTTP protocol
• Optimized SQL (read) and DML (write)
• Local read/write cache managed and optimized
• Fault-tolerance with respect to network failures (works
even if the central DB is temporarily unreachable)
• Hides network latency
• Authentication services
• Unified login credentials provided by central DB
• Local encryption
Cristiano Bozza – Università di Salerno – LNS, NOV 2014
DB INTERFACE
6
DB Interface – DB access to support acquisition
Cristiano Bozza – Università di Salerno – LNS, NOV 2014
DB INTERFACE
7
Detector Manager Structure
Web Server
SAWI, GUI (HTML, JSON)
Control Core
Command
console
Control Thread
Async write
Notifications
from other
components
of the DU
CLB Control
Thread
Data Log
Virtual Dir
Monitoring
SRP
(IKVM.NET)
SRP threads
SRP to CLB
Cristiano Bozza – Università di Salerno – LNS, NOV 2014
Text log
DB INTERFACE
8
Structure of the DB Interface
Web Server
SAWI, GUI (HTML, JSON)
Control Core
Requests
from other
components
of the CU
Data to
other
components
of the CU
Command
Console
Async read
Data Log
DB
RS #2
RS #1
RS #3
Central DB
DB cache
(runsetups and more)
Cristiano Bozza – Università di Salerno – LNS, NOV 2014
DB INTERFACE
9
DB Interface working cycle
DB
Polling – new runsetups
for this detector?
New runsetups
defined locally
RS #2
RS #1
RS #3
DL #6
DL #4
DL #5
DL #3
Runsetup cache
«current»
Datalogs to be written
Cristiano Bozza – Università di Salerno – LNS, NOV 2014
«old»
Written Datalogs
DB INTERFACE
10
DB Interface in the towers: re-use SW from strings
Scheme discussed
with A. Rovelli and
T. Chiarusi
11
Cristiano Bozza – Università di Salerno – LNS, NOV 2014
DB INTERFACE
11
DB Interface in the towers: re-use SW from strings
• Runsetup set for Data Manager and TriDAS
• Format definition underway: Matteo Manzali
• Uploading TriDAS logs into DB (technology similar
to CU Datalogs)
Cristiano Bozza – Università di Salerno – LNS, NOV 2014
DB INTERFACE
12
Requirements for graphical interfaces
• Matteo Favaro volunteered
• Technology: HTML+Javascript+AJAX+JSON
• Ease of integration into web applications (central
webservers, DetectorManager, DBInterface, TriDAS
Manager)
• Building runsetup/detector descriptions by GUI
• Ease of use
• Completeness
• Importing-reusing runsetups from DB or local cache
Cristiano Bozza – Università di Salerno – LNS, NOV 2014
GRAPHICAL INTERFACES
13
Web server for graphical interfaces
• Same technology as central Web services and CU
• Access and management of runsetup will be
identical in central Web services and in shore
stations
• Local and remote handling of runsetups
• JSON protocol
• Functions to implement
• List
• Read
• Write
Cristiano Bozza – Università di Salerno – LNS, NOV 2014
GRAPHICAL INTERFACES
14