...
*** THIS IS A DRAFT AND IS NOT COMPLETE ***
Preamble
- notify all stake holders before the release.
- eas commit eas changeset id: TBD
- sfeas_config commit changeset id: TBD
execute all steps in the SF ENVs first and test the application.
- if tests pass, then execute steps on SD ENVs
- Send an email to DT-EAS-User-Group and CC-ed to DT-SFGIS-User-Group to let them know that the version release has begun.
- Perform the steps below in the San Francisco production environment (SF PROD *) and then test the application in that environment.
- If the application passes its tests, then perform the steps below in the disaster recovery production environment (DR PROD *) and then test the application in that environment.
- In the unlikely event that things go very badly, we would switch over to the
...
- previous version of the application in
...
- the disaster recovery production environment (DR PROD *).
Web Application into
...
Maintenance Mode
put Place the web Web servers into maintenance mode (SF PROD WEB, SD DR PROD WEB):
| Code Block |
|---|
cd /var/www/html sudo ./set_eas_mode.sh MAINT |
Backup the Database
...
Log onto the SF PROD DB and back up the databases:
| Code Block |
|---|
sudo -u postgres -i /home/dba/scripts/dbbackup.sh > /var/tmp/dbbackup.log |
...
Deploy
...
c:\apps\eas_automation\automation
c:\apps\eas_automation\database...
the
...
| Code Block |
|---|
cd C:\apps\
python eas_automation_deploy.py eas_automation |
then run the migration to 1.3.5...
| Code Block |
|---|
cd C:\apps\eas_automation\automation\src
python job.py --action EXECUTE --job migrate_to_1.3.5 --env SF_PROD |
Schedule and enable the orphaned_address_report to run every Monday morning.
Use an existing scheduled item to crib from.
Keep your session open because you will use the automation scripts to send the release notification at the end.
...
Web Application (SF)
Log into SF PROD WEB and deploy the application as shown here. :
| Code Block |
|---|
cd /var/www/html sudo ./deploy_eas_init.sh 4844261f1f4d d738727199fe rgaston<eas-changeset-id> <sfeas_config-changeset-id> samuelvaldez |
Test the application to make sure everything works.
Deploy
...
the Web Application (Disaster Recovery)
If testing in SF passes, deploy the web app to SD PROD with steps parallel to SF PROD (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 the SD web that the disaster recovery production environment Web application works.
| 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. |
Put SD Place the disaster recovery Web server (DR PROD WEB server ) into STANDBY standby mode:
| Code Block |
|---|
cd /var/www/html sudo ./set_eas_mode.sh STANDBY_SD |
Release Notifications
- remove Remove 1.3.5 7 from the road map.
- Remove the entire DRAFT message that follows the table of contents above, and then publish this blog post.
- send email Log on to the automation machine (SF PROD AUTO) and run the following job to send the release announcement to stake holders using automation:
| Code Block |
|---|
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.
- Return to Step 18 of the version checklist because you are all done here!