Page Comparison

...

•  Place the Web servers into maintenance mode (SF PROD WEB, DR PROD WEB):

cd /var/www/html
sudo ./set_eas_mode.sh MAINT

...

•  Log onto SF PROD DB and back up the databases:

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

...

•  Deploy the Web application to SF PROD WEB per the Deployment Workaround for 2018 TLS 1.2 Compatibility Issue.  If you stage the uncompressed repositories ahead of time, then you can use these commands to deploy the Web application:

cd /var/www/html
sudo ./deploy_eas_init.sh 0485057b0593 b80a53e54e66 samuelvaldez

...

5 - 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 used in the San Francisco production environment (* PROD WEB only).
•  Make sure that the disaster recovery production environment Web application functions correctly.

...

...

title	Disable Database Replication?

• Testing the disaster recovery production environment

...

• Web application surfaced this issue:DR PROD WEB

...

• /GEO cannot connect to DR PROD DB
•  Place the disaster recovery Web server (DR PROD WEB) into standby mode:

Code Block
language bash linenumbers true
cd /var/www/html sudo ./set_eas_mode.sh STANDBY_DR

...

•  Remove 1.3.7 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:

Code Block
language bash linenumbers true
cd C:\apps\eas_automation\automation\src python job.py --action EXECUTE --job announce_new_release --env SF_PROD

...