Content Comparison

...

cd /opt/rh/httpd24/root/var/www/html
sudo ./set_eas_mode.sh MAINT

•  SF PROD WEB is in maintenance mode: http://eas.sfgov.org/
  

cd /opt/rh/httpd24/root/var/www/html
sudo ./set_eas_mode.sh MAINT

•  DR PROD WEB is in maintenance mode: https http://easdrweb.sfgov.org/
  

3 - Backup the EAS

...

Log onto SF PROD DB and back up the EAS databases.  The database backup script simply creates an additional daily backup, which are periodically purged from the file system, so there is no need to be concerned about the accumulation of "forgotten" database backups.

sudo -u postgres -i
/home/dba/scripts/dbbackup.sh > /var/tmp/dbbackup.log

•  Database was backed up
  

# You should receive an email notifying you of the status of the backup.
# The database backup log file is another source of information about the
# outcome of the backups.  Note that an empty database backup log file
# indicates that the backups were successful.
ls -la /var/tmp/dbbackup.log
cat /var/tmp/dbbackup.log

# The existence of the database backups can also be confirmed directly
# from the command line:
ls -la /mnt/backup/pg/daily/easproddb.sfgov.org-*

•  Database backup was verified

...

Database

DT DBA staff should backup the EAS database prior to EAS upgrades.  See service request SER0377668 (Support the release of EAS 1.4.1) for more information.

•  Database backup was performed and verified

4 - Upgrade Geoserver (DR)

•  Edgar will fulfill service request SER0377256 (Upgrade GeoServer on DR PROD GEOX)

•  Configure GeoServer on DR PROD GEOX.  You can use these commands:

sudo curl -O https://bitbucket.org/sfgovdt/easx/raw/1.4.1/geoserver/deploy_geoserver_init.sh
sudo chmod 700 ./deploy_geoserver_init.sh
sudo ./deploy_geoserver_init.sh

•  Check that the DR PROD GEOX configurations deployed properly via geoserver web admin.

5 - Upgrade Geoserver (SF)

•  Edgar will fulfill service request SER0377256 (Upgrade GeoServer on SF PROD GEOX)

•  Configure GeoServer on SF PROD GEOX.  You can use these commands:

sudo curl -O https://bitbucket.org/sfgovdt/easx/raw/1.4.1/geoserver/deploy_geoserver_init.sh
sudo chmod 700 ./deploy_geoserver_init.sh
sudo ./deploy_geoserver_init.sh

•  Check that the SF PROD GEOX configurations deployed properly via geoserver web admin.

...

6 - Deploy the Web Application (SF)

•  Deploy the Web application to SF PROD WEB.  You can use these commands to deploy the Web application:

cd /opt/rh/httpd24/root/var/www/html
sudo ./deploy_eas_init.sh 85b4845 ca66c28 rgaston

•  Test the application to make sure everything works.

...

7 - Deploy the Web Application (DR)

•  If testing in the San Francisco production environment (SF PROD *) is successful, then deploy the Web application to the disaster recovery production environment (DR PROD *) with steps that parallel those that were performed in the San Francisco production environment (* PROD WEB only).
•  Make sure that the disaster recovery production environment Web application functions correctly.

•  Place the disaster recovery Web server (DR PROD WEB) into standby mode:

cd /opt/rh/httpd24/root/var/www/html
sudo ./set_eas_mode.sh STANDBY_DR

...

8 - Release Notifications

•  Remove 1.4.1 from the road map.
•  Publish the blog post for this release.  Ideally, this blog post would have already been drafted.  An example is Release 1.3.6.
•  Log on to the automation machine (SF PROD AUTO) and run the following job to send the release announcement to stake holders:

cd C:\apps\eas_automation\automation\src
C:\sfgis\program\python36\eas_venv\Scripts\python.exe job.py --action EXECUTE --job announce_new_release --env SF_PROD

...