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.
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 crontab -l $ sudo -u postgres ...
ETL
Deploy new code to ETL server. There are new deploy helper scripts that you can place in the top directory. Follow the pattern shown in the DEV env.
Execute the migrate_to_1.1.7 job...
> python job.py --action EXECUTE --job migrate_to_1.1.7 --env SF_PROD
Web Server
Log into SF PROD WEB and deploy the application as shown here.
# see warning at top regarding branch or trunk 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 regarding branch or trunk 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
- cross post to yammer
- send email to stake holders
- remove 1.1.7 from road map
Done!
0 Comments