| Table of Contents |
|---|
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.
Down
web servers into MAINT mode
put both web servers into maintenance mode (SF WEB, SD WEB)
| Code Block |
|---|
cd /var/www/html sudo ./set_eas_mode.sh MAINT |
database backup
Log into PROD DB and back up the DB
| Code Block |
|---|
sudo -u postgres -i /home/dba/scripts/dbbackup.sh > /var/tmp/dbbackup.log |
Deploy
Database
Update the database version as described here: /wiki/spaces/DBA/pages/393226
ETL
Log into to the ETL server and do the following. Note that there is no ETL server in SD.
| Code Block |
|---|
REM see warning above cd "C:\Program Files\MAD\" del etl setup.bat |
Geoserver
Log into geoserver and deploy the configuration changes.
...
The should be no exceptions besides this one.
Web Server
Log into the web server and deploy the application as shown here.
| Code Block |
|---|
# see warning at top cd /var/www/html sudo ./deploy_eas_init.sh |
Test
Test the application to make sure everything works.
Deploy to SD Datacenter
If testing passes, repeat all steps on the SD VMs.
For the SD data center deploy, you can skip these steps
...
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.
Up
Make sure SF PROD WEB is in LIVE mode. If not, do this...
...
| Code Block |
|---|
cd /var/www/html sudo ./set_eas_mode.sh SD_STANDBY |
Done!