p3s/DQM infrastructure issues
- two crashes of EOS public instance, the latest just recently today
- FUSE operations (which we use for routine scripting) may be less performant than usual at times
- p3s server rendered unresponsive for a few hours on Oct.8 due to automated software update on OpenStack, there is a recipe how to fix that was recently applied (Maxim)
- apart from these isolated instances, operation has been remarkably stable
- p3s/DQM will shift into maintenance mode with minimal new development. Example - time series plots pull a lot of data now from default which needs to be parsed, noticeable slowdown, need to make adjustments
- will move older input data into a holder directory in EOS, too many files
New payload integration - "protoReco" by George
- tested, will be included in the auto-generation of DQM jobs today
- see attached screenshots
Beam Instrumentation integration - a few issues, may not be optimal for DQM