Preamble
- notify all stake holders before the release.
- eas commit id: 105b3579cb3d
config commit id: a192794562a3
execute all steps in the SF ENVs first and test the application.
- if tests pass, then execute steps on DR ENVs.
- In the unlikely event that things go very badly, we switch over to the old application in DR.
Web into MAINT Mode
put the web servers into maintenance mode (SF WEB, DR WEB)
cd /var/www/html sudo ./set_eas_mode.sh MAINT
Database Backup
Log onto the SF DB and back up the databases:
sudo -u postgres -i /home/dba/scripts/dbbackup.sh > /var/tmp/dbbackup.log
Deploy Automation Scripts
Deploy new code to automation server. Remove the following two directories:
c:\apps\eas_automation\automation c:\apps\eas_automation\database
Then run the deploy script like so:
cd C:\apps\ python eas_automation_deploy.py eas_automation
Keep your session open because you will use the automation scripts to send the release notification at the end.
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 105b3579cb3d a192794562a3 samuelvaldez
Test the application to make sure everything works.
Deploy to DR
If testing in SF passes, deploy the web app to DR PROD with steps parallel to SF PROD (WEB only).
Make sure the DR web application works.
You will not be able to log into the web application in DR if DB replication is running.
Put DR PROD WEB server into STANDBY mode
cd /var/www/html sudo ./set_eas_mode.sh STANDBY_DR
Release Notifications
- remove 1.3.6 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!
Add Comment