Displaying report 1-1 of 1.
Reports until 23:28, Monday 17 February 2014
H1 SYS (IOO, ISC, SUS, SYS)
jameson.rollins@LIGO.ORG - posted 23:28, Monday 17 February 2014 (10128)
guardian upgrades

A bunch of guardian upgrades were done over the weekend:

guardian core was upgraded.  it's currently at r720, but it's still moving as bugs are identified and features added

cdsutils (ezca) was upgraded . currently r164, but again still working out some kinks.

The guardian supervision infrastructure was upgraded and moved to a new location on local disk on h1guardian0.  I'll report on the new infrastructure in a followup post.  This required killing the main process supervisor ("initctl stop guardian-runsvdir"), which shut down all the current guardian nodes.

The SUS base guardian code was upgraded.  The base SUS.py was copied over from LLO.  Some improvements have been made as well, which I'll report on later.  Once this was in place I brought up the SUS_SRM node for testing.  Was it seemed to be behaving well the SUS_MC{1,2,3} nodes were restarted.  The rest of the SUS nodes were left off for the moment, but will be restarted tomorrow.

The IMC autolocker code was upgraded.  The new code is based on the code that was developed at LLO.  Again, to be expounded later.  The IMC autolocker upgrad exposed some issues with the current guardian behavior that will need to be fixed tomorrow.

Displaying report 1-1 of 1.