1.3.7

*** THIS IS A DRAFT AND IS NOT COMPLETE ***

Preamble

• eas changeset id: TBD
• sfeas_config changeset id: TBD

1. Send an email to DT-EAS-User-Group and CC-ed to DT-SFGIS-User-Group to let them know that the version release has begun.
2. Perform the steps below in the San Francisco production environment (SF PROD *) and then test the application in that environment.
3. If the application passes its tests, then perform the steps below in the disaster recovery production environment (DR PROD *) and then test the application in that environment.
4. In the unlikely event that things go very badly, we would switch over to the previous version of the application in the disaster recovery production environment (DR PROD *).

Web Application into Maintenance Mode

Place the Web servers into maintenance mode (SF PROD WEB, DR PROD WEB):

cd /var/www/html
sudo ./set_eas_mode.sh MAINT

Backup the Database

Log onto SF PROD DB and back up the databases:

sudo -u postgres -i
/home/dba/scripts/dbbackup.sh > /var/tmp/dbbackup.log

Deploy the Web Application (SF)

Log into SF PROD WEB and deploy the application as shown here:

cd /var/www/html
sudo ./deploy_eas_init.sh <eas-changeset-id> <sfeas_config-changeset-id> samuelvaldez

Test the application to make sure everything works.

Deploy the Web Application (Disaster Recovery)

If testing in the San Francisco production environment (SF PROD *) is successful, then deploy the Web application to the disaster recovery production environment (DR PROD *) with steps that parallel those that were used in the San Francisco production environment (* PROD WEB only).

Make sure that the disaster recovery production environment Web application works.

Place the disaster recovery Web server (DR PROD WEB) into standby mode:

cd /var/www/html
sudo ./set_eas_mode.sh STANDBY_SD

Release Notifications

• Remove 1.3.7 from the road map.
• Remove the entire DRAFT message that follows the table of contents above, and then publish this blog post.
• Log on to the automation machine (SF PROD AUTO) and run the following job to send the release announcement to stake holders:

python job.py --action EXECUTE --job announce_new_release --env SF_PROD

• When you receive the release announcement, then forward it by email to DT-EAS-New-Release-Announcement.  This is a temporary workaround to issue #234.  One example of this email was sent on 5/11/2018 8:44 PM.
  
• Return to Step 18 of the version checklist because you are all done here!