- Confirm maintenance mode
- We need to allow access from dedicated IPs for possible pre-upgrade work
- Adjust iptables on production nodes to allow JMX access to port 9000 for specified IPs
- PORT 8443:
# 169.237.11.246 (thomas)
# 69.12.224.247 (thomas)
# 169.237.97.91 (zoidberg: vpn, terminal server)
# 169.237.97.133 (kirk)
# 169.237.11.220 (james)
# 169.237.11.130 (sandra)
# 169.237.11.6 (jon)
# 169.237.11.242 (mike)
# 169.237.11.37 (Pete Peterson)
# 169.237.205.242 (Nancy Wilkison)
# OTHERS
- PORT 9000:
# 169.237.11.246
Steps
Work Aheads:
- (Jan 30, 2009) Kirk, Create the template for guest type with an altered workspace to prevent membership, resources, worksite set up and ???
- (Jan 30, 2009) Kirk, Create the Guest Activation site
- (Jan 30, 2009) Kirk, Configure the Guest Activation site to the pageID of ?????
During rollout morning:
- (04:30 Sandra) Set database markers
- (04:35 Michael) Shutdown all 7 sakai app servers.
- (04:40 Prabhu) Back up production database so that it can be fully restored. (Are we making database changes that require a back up?)
- Parallel Tasks
- (04:40 Joncarlo) Deploy SAK-2586 switch
- (04:40 Mike) Run svn update in ucd-help on sakaiprod1
- (05:05 Prabhu) Confirm backup finished
- (05:05 Prabhu) Run DB upgrade scripts on SAK-??
- (05:15 Mike) Deploy Prod Tag 00 (This deploys JIRAs SAK-2238 and SAK-1515) on sakaiprod1
- (06:05 Mike) Start sakaiprod1
- (06:06 Mike) Test simple functions
- (06:10 Mike) If simple test is OK, then start deploying sakaiprod2-6 and sakaiprodmail1
- (06:20 Mike) Start all other app servers(sakaiprod2-6 and sakaiprodmail1)
- (06:22 Mike) Remove maintenance mode for sakaiprod1-6 and sakaiprodmail1
- (06:25 Mike) Validate all app servers are not in maintenance mode
Fall-back Procedure (If needed)
- (06:00 Prabhu) Run the restore
- (06:00 Michael) roll back the executable for all upgrade changes
- (06:40 Michael) bring up prod1
- (06:43 Sandra and Kirk) QA SmartSite to make sure it's back in its correct state. Check for database markers
- (