This long weekend consisted of extensive work to ready eLMS on the System40 server. A working version of eLMS is now residing on that server.
We temporarily stopped eLMS services on Legacy in order to do a complete copy of the frozen database to Sys40. eLMS services have been restored on Legacy (see information about dual operation below).
Copied census and application JSON files generated by eLMS to Sys40.
Modified the cron jobs in Legacy, Sys40 and a relay server to accommodate dual operation. Under dual operation, both Legacy and Sys40 will simultaneously, but independently operate the eLMS service. Legacy is still necessary in order to accommodate myLPFM and FCCdata which continue to work on Legacy until they are transitioned.
We have been experiencing issues with and have been tweaking the configuration of the mySQL server on Sys40 in order to make it more optimal with our operation. The new server has presented some new challenges and we will continue to make adjustments that may result in some downtime or strange performance due to configuration changes, etc.
It may be necessary to make substantial modifications to some of the programs that interface with the database to better optimize database usage. We have been experiencing some very slow response times on queries. This is something that we are aware of and will work to try to improve.
Recoded, implemented and tested several daily update programs that are used to interface with eLMS and other databases during the morning run.
Stopped services to monitor IPAWS and NWS on Legacy. Copied the frozen CAP database from Legacy to Sys40. Repointed the Toybox CAP application from Legacy to Sys40. Reinstated services on Legacy and started services on Sys40 for the first time. We will run IPAWS and NWS in dual operation until after the myLPFM transition and we have verified that no other applications that may be using the CAP database are still pointed to Legacy.
FCC.today is now internally pointing to Sys40. (The source code was previously transitioned to Sys40 but was receiving its data from the Legacy mySQL server.)
To help address some performance issues, we have modified the CAP database to retain past weather alert messages to 7 days from the last time the alert was seen on NWS API. This date used to be 30 days back. IPAWS WEA and non-EAS alerts will still be retained for 30 days and EAS eligible alerts are still being retained indefinitely.
Weekend development is still in progress. This changelog may be updated based on other progress made. We have identified places where the database can be improved. This will involve recoding and database parameter modifications in order to improve the efficiency of the underlying Sys40 database.
