...
- Place the Web servers into maintenance mode (SF PROD WEB, DR PROD WEB):
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd /var/www/html sudo ./set_eas_mode.sh MAINT |
...
- Log onto SF PROD DB and back up the databases:
| Code Block | ||||
|---|---|---|---|---|
| ||||
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 * * WEB Server. If you stage the uncompressed repositories ahead of time, then you can use these commands to deploy the Web application:
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd /var/www/html sudo ./deploy_eas_init.sh 0485057b0593 b80a53e54e66 samuelvaldez |
...
5 - Deploy the Web Application (DR)
| Note | ||
|---|---|---|
| ||
You will not be able to log into the Web application in the disaster recovery production environment (DR PROD WEB) if database replication is running. |
- 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
...
- Place the disaster recovery Web server (DR PROD WEB) into standby mode:
| Code Block | ||||
|---|---|---|---|---|
| ||||
cd /var/www/html sudo ./set_eas_mode.sh STANDBY_SDDR |
6 - Release Notifications
- 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 | ||||
|---|---|---|---|---|
| ||||
cd C:\apps\eas_automation\automation\src python job.py --action EXECUTE --job announce_new_release --env SF_PROD |
- When you receive the release announcement, then forward it by email to DT-EAS-New-Release-Announcement. This is a temporary workaround to issue #234. One example of this email was sent on 5/11/2018 8:44 PM.
- This release announcement will also be sent to the Yammer All Company group, so check your email inbox for the request from Yammer to post the release announcement there.
- Return to Step 18 of the version release checklist because you are all done here!
...