1.1.7

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)

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

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

SFGIS ETL

Ensure the following SFGIS workspaces are of the latest version on the FME Server Production server (10.250.60.184).

Job #CategoryNameStart TimeFME Workspace
1Basemap_ParcelsGet AIA Assessor Data for Staging1800aia_import_etl_into_sfgis_sde_stg__setenv.fmw
2Basemap_StreetsGet Street Centerline Data from DPW for Staging1830 streets_source_to_sfgisStg_setenv.fmw
3Basemap_StreetsProcess Street Centerline Data on Staging1845streets_sfgisStg_to_sfgisStg_setenv.fmw
4Basemap_ParcelsGet Parcel Data from DPW for Staging1900parcels_source_to_sfgisStg__setenv.fmw
5Basemap_ParcelsProcess Parcel Data on Staging1930parcels_sfgisStg_to_sfgisStg__setenv.fmw


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!