| Table of Contents |
|---|
Preamble
- notify all stake holders before the release.
- eas commit id: f37cbbdb3e77
- config commit id: 6448994241e1
- 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)
| Code Block |
|---|
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.
| Code Block |
|---|
sudo -u postgres -i crontab -l /home/dba/scripts/dbbackup.sh > /var/tmp/dbbackup.log |
Deploy Automation Scripts
Deploy new code to automation server. Remove the following two directories:
...
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.
...
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).
...
| Code Block |
|---|
cd /var/www/html sudo ./set_eas_mode.sh STANDBY_SD |
Release Notifications
- remove 1.3.1 from road map
- publish blog post
- send email to stake holders using automation:
| Code Block |
|---|
python job.py --action EXECUTE --job announce_new_release --env SF_PROD |
Done!