COMPASS Database Work in 2014/15

Transcription

1 COMPASS Database Work in 2014/15 Martin Bodlak Joined Czech Group, COMPASS Experiment at CERN 30 July 2015

2 COMPASS database servers in 888 PCCODB00 VIRTUAL ADDR PCCODB22 CLIENTS PCCODB21 PCCODB23 PCCODB20 MySQL PROXY

3 Summary of work in 2014/15 all database servers reinstalled to use SLC bit MySQL server software upgraded from to MySQL replication and backup system set up MySQL Proxy server migrated to a more powerful machine one additional MySQL server introduced master-master replication with one additional slave later changed to master 2 slaves after tests: master master/slave slave or a circular replication web based interfaces to work with MySQL databases developed (or improved)

4 DAQ configuration tool possibility to control DAQ settings run types management (physics run, DAQ test run, etc.) hardware management (define hardware registers for specified run type) define how ports are connected together in a specified run type process management (on which machine a process is running, which hardware it monitors, etc.) possiblity to create trigger mixtures

5 DAQ configuration tool

6 New COMPASS electronic logbook overview of runs, shifts, comments, and other functionalities still under development should contain all the functionalities of the old electronic logbook improved and more user-friendly filtering of runs, shifts, and comments strong ephasis on improving the user experience

7

8

9 Quattor to Puppet migration of COMPASS servers Quattor and Puppet: tool-kits to install, configure, and manage computers CERN IT division was using Quattor until 2014, the support for Quattor-managed machines stopped in October 2014 COMPASS had three instances managed by Quattor - compass02, compass03, and compass22 compass02 - COMPASS public web page (wwwcompass), MySQL database used by Coral to get calibration data during mdst production compass03 - filling event-building metadata to ORACLE database compass22 - a virtual machine, secondary MySQL server for mdst production

10 New machines managed by Puppet several virtual machines requested compassvm21, compassvm22, compassvm23 used as MySQL servers for mdst production more powerful than compass02 and compass22 compassvm02 and compassvm03 used as webservers plans to migrate COMPASS public web pages to centralized CERN services (web service and database on demand) however, compass02 is still being used, opening of ports on compassvm03 is not yet finished

11 Modern approach to applications development in the business world, development of web (and mobile) applications is on its rise why should high energy physics experiments be any different? current situation: lots of undocumented programs and scripts that are not maintained anymore, but are still necessary and needs to be recompiled sometimes when the system is updated all machines where the script or program needs to run need to have correct libraries installed

12 Web application scheme Client-side app INTERNET / INTRANET WEB SERVER(s) Server-side app DATABASE SERVER

13 Web applications web applications are running on dedicated server(s) (= web server) clients access the application through a network (internet / intranet) server side (runs on the web server and serves data to the client) usually written in an interpreted language (PHP, Python, Ruby) client side (runs in the client s browser) written in JavaScript every client connected to the correct network can use the application immediately

14 Web applications - better approach why to reinvent a wheel for every application? development of CGI scripts in Perl or C to serve data to the client is obsolete and inefficient development with PHP (server side) + JavaScript (client side) is easy, but highly inefficient lots of repetitive tasks needs to be programmed manually, especially in the JavaScript code (even when using libraries like jquery) dividing server and client part of the application REST API provider on the server side REST API consumer on the client side use of a better server side and client side frameworks AngularJS (client side, written in JavaScript) Django (server side, written in Python)

15 REST (REpresentational State Transfer) 1 consumer (client) sends a HTTP request to the provider (via GET, POST, PUT, DELETE methods) 2 provider (server) processes the request and sends HTTP response code and data in a standardized format (e.g. JSON, XML) 3 consumer parses the response and displays data in the web browser (or anywhere else) in a defined template multiple consumers can access the same provider (e.g. AngularJS in the web browser, Android or ios mobile app)

16 THANK YOU FOR YOUR ATTENTION