Implementation Plan July 17-18, 2009

Owned by James Renfro
Last updated: Jul 28, 2009 by Former user (Deleted)Version comment
2 min read

Personnel

  • Programmer is James Renfro
  • QC is Sandra

Preparation for production release

During maintenance window

  • (S + 0 min Programmer) Put all application servers into maintenance mode and shutdown Sakai on each one
  • (S + 2m Programmer) Deploy sakai release tag via setup-sakai-node.sh to sakaiprod1.
  • (S + 5m Programmer) Restart sakaiprod1 sakai instance
  • (S + 10m QC) Verification
    • Make sure that both Gradebook 2 and the Sakai Gradebook are still functional
    • Make sure Gradebook 2 still functions per my old AAS sites (can't submit grades here)
    • Make sure sample of Summer Session 1 pilot participants still have Gradebook 2 and it looks the same as it did before the upgrade.
    • James will check for any errors that may have been created during the roll out.
  • (S + 30m Programmer) Deploy release tag via setup-sakai-node.sh to sakaiprod2 . . . sakaiprod6, and sakaiprodmail1.
  • (S + 40m Programmer) Start Sakaiprod2 . . . sakaiprod6, and sakaiprodmail1.
  • (S + 50m Programmer) Take smartsite-prod out of maintenance mode 
  • (S + 55m Sandra) Send Release Management email

Fall-back Procedure (If needed) Time D is the decision time made to fallback

  • (D + 0m Programmer) Shutdown Sakai on smartsite-prod
  • (D + 2m Programmer) Remove sakai.properties from config-staging and rename sakai.properties.017 to sakai.properties
  • (D + 5m Programmer) Deploy previous tag on head node and all other app servers via setup-sakai-node.sh
  • (D + 15m Programmer) Restart sakai head node after verifying with DBA that restore is complete
  • (D + 20m ProjManmgt) check database marker
  • (D + 25m Programmer) Restart sakai on remaining nodes
  • (D + 30m Programmer) Take application servers out of maintenance mode