1.3.4

Owned by Robert Gaston (Unlicensed)
Last updated: Jan 07, 2019 by Samuel Valdez (Unlicensed)
1 min read

Preamble

  • notify all stake holders before the release.
  • eas commit id: 0c7d9265be4e

  • config commit id: 1573c4a261c1


  • execute all steps in the SF ENVs first and test the application.

  • if tests pass, then execute steps on SD ENVs.
  • In the unlikely event that things go very badly, we switch over to the old application in SD.

Web into MAINT Mode

put the web servers into maintenance mode (SF WEB, SD WEB)

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

Database Backup

Log onto the SF DB and back up the databases. The exact command line resides in the postgres user crontab.

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

Deploy App to Web (SF)

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

cd /var/www/html
sudo ./deploy_eas_init.sh 0c7d9265be4e 1573c4a261c1 rgaston

Test the application to make sure everything works.

Deploy to SD

If testing in SF passes, deploy the web app to SD PROD with steps parallel to SF PROD (WEB only).

Make sure the SD web application works.

You will not be able to log into the web application in SD if DB replication is running.

Put SD PROD WEB server into STANDBY mode

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

Release Notifications

  • remove 1.3.4 from road map
  • publish blog post
  • send email to stake holders using automation:
python job.py --action EXECUTE --job announce_new_release --env SF_PROD


Done!