Westerntechnologyandsovieteconomicdevelopment1930to1945 antony sutton
Configuration Database MICE Collaboration Meeting 28, Sofia David Forrest University of Glasgow...
-
Upload
primrose-mcgee -
Category
Documents
-
view
212 -
download
0
Transcript of Configuration Database MICE Collaboration Meeting 28, Sofia David Forrest University of Glasgow...
Configuration Database
MICE Collaboration Meeting 28, Sofia
David ForrestUniversity of Glasgow
Antony WilsonScience and Technology Facilities Council (RAL)
Overview
My (David’s) final talk on the configuration database and Antony’s first
Current state + handover Summary of work done
Handover
Antony Wilson is the new go-to guy for database stuff
My contribution is over a few days after this CM I have run a well attended database workshop
covering on call expert training, client code, database development
I have slides from this including solutions to the exercise, and audio recording if you are having trouble sleeping – should be online later today
In addition I am writing a note on the database which justifies the design, introduces client code development, troubleshooting, describes what you need to do to communicate back and forth with the system as it stands
This should be updated consistently
What’s done
Requirements capture, design Postgres installed, running, backed up Apache Tomcat running robustly Database API implemented for set values, tagged
set values, calibrations, alarm handler limits PHP User interfaces (freebies) Classes in G4MICE (Malcolm) for client code
development EPICS client (James) Performance testing New: Update set values of a run (password
protected functionality)
Updating Set Values
• This is controversial and James assures it will be password protected on the client side
• It is critical it is not used as a substitute for competent record keeping
• Writing bad information to the database is vandalism no matter who tells you to do it
• No plans to implement functionality to update a tagged run as this should have a permanently immutable meaning. If you want to change it make a new tag!
What’s done
Backup (of database and associated server side software)
Documentation In summary, at minimum we should be
using the database for beamline settings and automatic entry of settings such as magnet currents
Documentation – The D Word
There is a MICE Note nearing completion justifying the requirements and design
It also includes what to do in the event of a failure
The code is documented. No, really.
Cabling – The C Word
Better thought of as 'Electronic components and cabling'
We had a design for cabling specific to the detectors which took in the use cases but was too complex
Effort began to arrive at a more generic, simpler description
I will finish this but want to ensure I understand what people want as output
What’s not done
My thesis (W.I.P) Network modification Cabling Polarity (although I have stepped through how
to do it in the solution slides of the db workshop)
What else? Development/evolution is ongoing.
Into the Future
There has to be a flow of conversation between analysis, detector groups, online/sw groups and Antony
System needs to be championed as it sits on the interface with many other systems. It has minimal demands on those systems but there inertia with work required for integration.
The database is only as good as whats in it – constraints will have to be tightened, GUIs improved but there is a human element also
Handover
The new database guy is Antony Wilson, who you will see in a moment
Somehow despite only just joining he is now responsible for any bugs I may have produced
Also he is responsible for further development
The alternative is....
Thanks
Thanks to everyone who helped this project along.
Thanks for the chance to do it :) Perhaps leave questions til the end?
Initial Tasks
Bring code inline with new project coding standardsJavadoclog4j server side logging
Move testing into junit frameworkSwitch from Soap to Axis serverGenerate Java client APIPackaging
jar/aar file
DeploymentUse rpms where possible
Tomcat
Setup scriptSimple instructions
Intermediate Tasks
Review existing use cases
Gather new use cases
Produce proposal to address use cases
heplnm069
postgrespostgres
heplnm068
Apache/api/elog
/redmine
Apache/api/elog
/redmine
TomcatCDB APITomcat
CDB APIConfiguration
database
FIREWALL
80808080 44434443
MICENET
44434443
online box
CDB client API
CDB client API
heplnm068
Apache/api
/elog/redmine
Apache/api
/elog/redmine
TomcatCDB read only API
TomcatCDB read only API
FIREWALL
80808080 44434443
MICENET
heplnm069
postgrespostgres
Configuration database
TomcatCDB APITomcat
CDB API
new mouse box
postgrespostgres
Configuration database
TomcatCDB APITomcat
CDB API
online box
CDB client API
CDB client API
continuous backup
continuous backup
44434443
44434443
This is a manual failover controlled by a configuration file
This is a manual failover controlled by a configuration file