1.1.6

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

Preamble

  • notify all stake holders before the release.
  • for this deploy we are pulling from svn trunk
  • 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.

ETL

Log into to the old PROD ETL server and DISABLE all of the jobs.

Log into to the new PROD ETL server and ENABLE all of the jobs.

To confirm things are working test the export_flat_file_to_ftp job in the new PROD ETL env.

Web Server

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

# see warning at top
cd /var/www/html
sudo ./deploy_eas_init.sh

Test the application to make sure everything works.

Deploy to SD Datacenter

If testing passes, deploy the web app to SD PROD WEB.

# see warning at top
cd /var/www/html
sudo ./deploy_eas_init.sh

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 SD_STANDBY

Release Notifications

  • publish blog post
  • x post to yammer
  • send email to stake holders
  • remove 1.1.6 from road map
  • provide copy of updated runbook to support providers
    • DT DBAs
    • PGX
    • FARGEO

Done!