shawnhammer overhaul

[swh76]

shawnhammer has (embarrassingly) become the primary method for rebooting and configuring SMuRF systems. I vote we make the following improvements to make it more usable:

• Rename to something more legitimate sounding and move it and its associated script out of my scratch. I'm thinking we rename it smurf_startup and move it into a top level scripts directory in pysmurf.
• Instead of hard-coded configuration parameters directly in the script, and different pysmurf branches for every system, we should have a configuration file on each system that shawnhammer loads. This would have the benefit of getting everyone onto the same branch, which would make maintaining and synchronizing all of our systems simpler. I propose a directory /data/smurf_startup_cfg, and then each institution has a cfg file in cfg_files/ that they softlink to /data/smurf_startup_cfg/startup.cfg (or something).
• It'd be nice to have some command line options for shawnhammer to control whether or not it reboots/etc.
• joehammer (the inspiration for shawnhammer) had validation steps to check if the system passes some basic validation checks as it boots up and initializes. It'd be great to add that functionality into the proposed smurf_startup script.

[slacrherbst]

I think it should not be a script at all. A while back I had proposed a rogue instance to interface with the impi and other general shelf functions. The shamhammer functionality should be included as a routine in this rogue instance. This routine could then be initiated through an external command.

[jlashner]

Just for the record, here's my solution to this. jackhammer hammer implements everything that shawnhammer does in python, and brings up the OCS/smurf-streamer dockers. System and startup configuration info is stored in a yaml file "sys_config.yaml" located in the ocs-site-config directory. There are also other commands you can run such as jackhammer soft_reset which will just reset software without rebooting the smurf-slots, or jackhammer pysmurf <slot> which will place you in an ipython session with pysmurf instantiated. It would still be great to add validation steps to make sure the system has booted properly. lmk if you have any feedback, and if you think it's useful for non-simons experiments maybe we can move it to the pysmurf directory.

[slacrherbst]

Is there any chance we can attempt to overlap the configurarions on the jackhammer script and the core rogue/pysmurf system. This was we only have to set some variables in a single config file instead of two places?

[jlashner]

Sure, the sys_config.yaml file replaces the shawn_startup_config file and adds some additional info, like the location of the pysmurf config files. I'm hesitant to merge the sys_config and the pysmurf config files, since I'd like sys_config to be small and human readable and easy to compare, and I don't really want to put all of the rogue registers in there. What did you have in mind?

[slacrherbst]

We definitly could keep it a seeperate file and stie specific, but maybe change the structure a bit to match the equivelennt fields in th rogue/pysmurf configuration. And then we can just load that file as part of the rogue/pysmurf configuration process. I will take a closer look and suggest a format later today.