/
December 18, 2008 Sakai Deployment

December 18, 2008 Sakai Deployment

Dec 17, 2008

December 18, 2008 sakai deployment

December 18, 2008

  • 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

# OTHERS

  • (05:29 Sandra will set a database marker for a possible restore.

  • (05:30 Joncarlo) Initiate maintenance mode via root cron jobs on all 7 sakai app servers.

  • (05:30 Mike, Joncarlo or somebody) Shutdown all 7 sakai app servers.

  • (05:32 Prabhu) Back up production database so that it can be fully restored.

  • Parallel Tasks

    • (05:35 Joncarlo) Deploy SAK-2486

    • (05:35 Mike) Run svn update in ucd-help on sakaiprod1

  • (05:52 Prabhu) Confirm backup finished

  • (05:52 Prabhu) Run DB upgrade scripts on SAK-2451 and SAK-2439

  • (05:55 Mike) Deploy Prod Tag 009 (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)

  • TBD

DEV TEST PLAN

  • Simple functionality

    • Can I log in?

    • Time site-info on a large site

    • Validate tools on a site are accessible.