Page Comparison

...

• notify all stake holders before the release.
• eas commit id:  55cab733f98a

• config commit id: ba154b3a5042

• 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.

...

Add the bulkloader_etl job to the production etl task scheduler: The bulkloader_etl job should run every weekday at 11:45 PM.  This is a suitable time because it follows the COMMIT parcels at 10:15 PM and COMMIT streets at 11:15 PM, and based on the Task Scheduler history, COMMIT streets does not require more than a minute to complete.

run_job EXECUTE bulkloader_etl SF_PROD
Details for setting up the task in the Task Scheduler
Name         run_job EXECUTE bulkloader_etl SF_PROD
Program      "C:\apps\eas_automation\automation\bin\run_job.cmd"
Arguments    EXECUTE bulkloader_etl SF_PROD
start in     C:\apps\eas_automation\automation\bin\

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 [eas commit id] [config commit id] 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!