Test new server sundial (eventual replacement for cronus)

[jameswilburlewis]

Our server cronus is nearing end-of-support, and its replacement has arrived. The new server is accessible as sundial.ssl.berkeley.edu.
It's running RHEL version 8.7, so a few things might be different from our other Linux servers (which are set up with Centos).

I've already asked for a few tweaks to the configuration:

1. Create /mydisks/home/thmsoc directory (Done)
2. Install svn, git, and mysql binaries (Done)
3. Install include files for C++ boost libraries (Done)

Once these changes are made, we can start testing cron jobs and looking for other potential issues. Some command line tools might have changed options, syntax, or default behavior. We may need to add sundial to the list of permitted hosts on our svn, mysql, or other servers, services, or firewall configurations.

The goal is for the new cronus to be able to run any cron job or workflow from the other Linux servers, not just the ones currently on cronus. It might be good, where practical, to try running the jobs interactively (switching to /bin/sh, setting the THMSOC variable, then calling the script on the command line) just in case any issues show up in the script outputs that might not necessarily make it into the log files.

Nick: PHP scripts, file inventories, GOES/POES summary plots, etc
Jim M: L1->L2 processing, THEMIS summary plots
Cindy: GMAG processing
Jim L: Telemetry, L0, L1 processing tools; logging to mysql and email notifications, SVN client compatibility

I have confirmed that SVN working copies created on our Centos machines need to be upgraded to be compatible with the svn client on sundial. But then they won't be usable on the other machines until we upgrade their svn clients.

[jameswilburlewis]

The IT folks say they'll do the switch after April 10, when Greg P is back from vacation. old cronus' hostname, IP address and SSH host ID will be transferred to new cronus, so that should fix the problems Cindy was seeing in the gmag scripts.
old cronus will be renamed to ophion and will remain online if we want to use if for large reprocessing jobs.

[nickssl]

If there are no objections, I will ask helpdesk to upgrade PHP to a current version on both the old and the new cronus.