Maintenance will be performed on git.ligo.org, containers.ligo.org, and docs.ligo.org on Tuesday 25 March 2025 starting at approximately 8:30am PDT. It is expected to take around 30 minutes and there will be several periods of downtime throughout the maintenance. Please address any comments, concerns, or questions to the helpdesk.
This code is as ready as I can get it. Here's what still needs to be done:
Figure out issue with lvalert-overseer.
Check for possible issues on uploading hardware injections (see here. I haven't been able to test it, but it uses StringIO which is definitely a cause for concern in terms of Python 2/3 compatibility.
Tag a new version of lvalert-overseer, push it to PyPI, and update the requirements.txt file in this repository to use the new tag.
Suggested strategy for rolling it out
Test the deployment with the new puppet configuration on gracedb-dev2 or dev1 (more below)
Deploy on playground and see what happens
Test this image on gracedb-test
Tag it
Deploy on production
To test on UWM VMs
Delete /home/gracedb/djangoenv
As root, run puppet and immediately turn it off so it doesn't revert to the default configuration:
Once it seems stable on playground, test it on gracedb-test
If that seems good, merge the code into master and tag it
NOTE: gracedb-dev2 is currently set up for Python 3 both in terms of its Puppet configuration and its code base.
Puppet is currently turned off so that it doesn't revert to the "default" Puppet configuration with Python 2.
Once you're ready to "officially" deploy with Python 3, and the Puppet configuration is merged, just do puppet agent -t as root on this server to restart Puppet.
Final deployment in AWS
Should be easy - it's all in a Docker image!
Potential issues
The parts of the code that I expect the most issues to occur are:
VOEvent building (gracedb/annotations/voevent_utils.py) since it was completely rewritten
VOEvent ingestion for external events (gracedb/events/translator.py) since it was completely rewritten
