1 / 17

Configuration Database

Configuration Database. Antony Wilson MICE CM 29 15-18 February 2011 RAL. Overview. Handover Configuration Deployment Backups Software Move to WSDL Issues. Handover. David has provided a document as a mice note http://mice.iit.edu/micenotes/restricted/pdf/MICE0327/MICE0327.pdf

emiko
Download Presentation

Configuration Database

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. Configuration Database Antony Wilson MICE CM 29 15-18 February 2011 RAL

  2. Overview • Handover • Configuration • Deployment • Backups • Software • Move to WSDL • Issues

  3. Handover • David has provided a document as a mice note • http://mice.iit.edu/micenotes/restricted/pdf/MICE0327/MICE0327.pdf • Beam Line Settings • needs extending, discussed later • Calibrations • Electronic Channel Mapping and Cabling • Alarm Handler • newer version implemented with WSDL interface • Geometry • newer version implemented with WSDL interface

  4. configuration

  5. Deployment FIREWALL PPD configDB micewww postgres • All client access is via Tomcat • Off site access is read only via micewww • Access from MICENET is read write Configuration database Tomcat CDB readonly API read only db user read/write db user Tomcat CDB API continuous update MICENET online box new mouse box CDB client API postgres Configuration database read/write db user This is a manual failover controlled by a configuration file Tomcat CDB API

  6. Backups OS on mirrored array Database on mirrored array Transaction logs on mirrored array OS on mirrored array Database on mirrored array Transaction logs on mirrored array ConfigDB – on PPD SALVE Hourly off site backup Coming soon continuous update ConfigDB – on MICENET MASTER

  7. Recovery Procedure • Recovery procedure tested on one machine • http://micewww.pp.rl.ac.uk:8080/projects/configdb/wiki/Backups • Postgres 9 provides native support for master slave mechanism. N.B. slave is read only • ISSUE • The redmine database is on heplnm069

  8. Software

  9. Updating Config DB Code • Coding standards introduced for G4Mice group (C++) • Analogous standards being used for the Config DB (Java) • As code is updated • Fully documented with javadoc • Logging added using log4j • Unit tests with junit • JAX-WS used to generate WSDL interface

  10. Move to Web Service Definition Language (WSDL) • A WSDL interface describes how to communicate with the Config DB • The WSDL can be used to generate client APIs • All new/updated component will provide a WSDL interface • AlarmHandler • Geometry • Controls • API documentation is provided via javadoc • http://hepunx.rl.ac.uk/egee/mice/doc/

  11. WSDL Clients • Java clients • Generated using JAX-WS • Used for system testing • Python clients • Use suds from suds.client import Client url= 'http://micewww.pp.rl.ac.uk:8080/cdb/geometry?wsdl' cdbGeometyClient = Client(url) # client to talk to Config DB print cdbGeometyClient# list available methods on Config DB print cdbGeometyClient.service.getStatus() # call Config DB method

  12. WSDL Clients • C++ clients • Generate using gSoap • James has generated a C++ client for the AlarmHandler • Ivan has generated a C++ client for the Geometry • Controls is a work in progress

  13. Issues • Controls interface requires access to HV cabling data • Beam line settings – extra fields required

  14. Access to HV Cabling Data • Current Electronic Channel Mapping and Cabling API takes a file as input parameter • Config DB has no knowledge of the contents of the file • Config DB needs access to HV cabling data • Is HV cabling data embedded in these files? • Need to agree on common format for all HV cabling data and provide new Config DB API • What to do with the rest of the cabling data?

  15. Beam Line Settings • We already have a Boolean status flag • Need to add “run type” flag? • Use bit map • Cosmic test • Target not dipped • Normal mice run • Additional data quality information stored in the metadata database?

  16. Beam Line Settings DAQ Run 1 1 To Do • Add “run type” flag • Change Depth from mm to microns • These are in the ops room spreadsheet • Triggers per spills • Particle triggers • Proton absorber thickness (mm) • Momentum at target • Id[primary key] Trigger GateWidth Version RunNumber[primary key] Start End Notes MomentumD1 MomentumD2 Species PulseStart PulseEnd Step Status • DaqId [foreign key] • TargetId [foreign key] • ISISId [foreign key] ISIS 1 1 • Id[primary key] RepRate NominalBeamCurrent NominalBeamLoss TargetFrequency 1 Target 1 1 • Id[primary key] DriveVoltage Delay Depth 1..* Magnets • Id[primary key] MagnetName SetCurrent • RunNumber [foreign key]

  17. Summary • Recovery mechanism from transaction logs tested and documented • Alarm Handler WSDL interface in use • Geometry WSDL interface prototyped • Blocking issue on Controls WSDL interface • Require access to HV cabling data • Beam line settings WSDL conversion not started yet • Require agreement for new field(s)

More Related