Preamble
- notify all stake holders before the release.
- eas commit id: 4844261f1f4d
config commit id: d738727199fe
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.
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:
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
then run the migration to 1.3.5...
cd C:\apps\eas_automation\automation\src python job.py --action EXECUTE --job migrate_to_1.3.5 --env SF_PROD
Schedule and enable the orphaned_address_report to run every ??????.
Use an existing scheduled item to crib from.
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 4844261f1f4d d738727199fe 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.5 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