| 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 |
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.
...
| Job # | Category | Name | Start Time | FME Workspace |
|---|---|---|---|---|
| 1 | Basemap_Parcels | Get AIA Assessor Data for Staging | 1800 | aia_import_etl_into_sfgis_sde_stg__setenv.fmw |
| 2 | Basemap_Streets | Get Street Centerline Data from DPW for Staging | 1830 | streets_source_to_sfgisStg_setenv.fmw |
| 3 | Basemap_Streets | Process Street Centerline Data on Staging | 1845 | streets_sfgisStg_to_sfgisStg_setenv.fmw |
| 4 | Basemap_Parcels | Get Parcel Data from DPW for Staging | 1900 | parcels_source_to_sfgisStg__setenv.fmw |
| 5 | Basemap_Parcels | Process Parcel Data on Staging | 1930 | parcels_sfgisStg_to_sfgisStg__setenv.fmw |
Web Server
Log into SF PROD WEB and deploy the application as shown here.
...
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 SD_STANDBY |
Release Notifications
- publish blog post
- cross post to yammer
- send email to stake holders
- remove 1.1.7 from road map
Done!
...