| Table of Contents |
|---|
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.
web into MAINT mode (SF_PROD_WEB)
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 |
EAS ETL
Deploy new code to ETL server and run the following commands in order.
...
When we run the streets STAGE job, note that DB replication will be on. This may result in a replication delay alert from NAGIOS but it should not overwhelm replication because its well under 100K records (with line geometry).
SFGIS ETL
initialize database feature classes (delete and recreate using ArcGIS)
...
Test the application to make sure everything works.
Deploy to SD Datacenter
If testing passes, deploy the web app to SD PROD WEB.
...
| Code Block |
|---|
cd /var/www/html sudo ./set_eas_mode.sh STANDBY_SD_STANDBY |
Release Notifications
- remove 1.1.8 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!
...