Implementation Plan August 18, 2009
Personnel
- Programmer is Thomas Amsler
- QC is Sandra
Preparation for production release
During maintenance window
- (S - 10 min Sandra) Set DB markers.
- (S + 0 min Programmer) Put all application servers into maintenance mode and shutdown Sakai on each one
- (S + 2m Prabhu) Backup production DB
- (S + 30m Prabhu) Apply DB scripts
- (S + 35m Programmer) Deploy sakai release tag via setup-sakai-node.sh to sakaiprod1.
- (S + 40m Programmer) Restart sakaiprod1 sakai instance
- (S + 45m 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 2 pilot participants still have Gradebook 2 and it looks the same as it did before the upgrade.
- Programmer will check for any errors that may have been created during the roll out.
- (S + 55m Programmer) Deploy release tag via setup-sakai-node.sh to sakaiprod2 . . . sakaiprod6, and sakaiprodmail1.
- (S + 60m Programmer) Start Sakaiprod2 . . . sakaiprod6, and sakaiprodmail1.
- (S + 65m Programmer) Take smartsite-prod out of maintenance mode
- (S + 70m 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 Prabhu) Restore production DB
- (D + 2m Programmer) Remove sakai.properties from config-staging and rename sakai.properties.018 to sakai.properties
- (D + 5m Programmer) Deploy previous tag on head node and all other app servers via setup-sakai-node.sh
- (D + 50m Programmer) After DB has been restored, restart sakai head node after verifying with DBA that restore is complete
- (D + 55m ProjManmgt) check database marker
- (D + 60m Programmer) Restart sakai on remaining nodes
- (D + 65m Programmer) Take application servers out of maintenance mode
{"serverDuration": 20, "requestCorrelationId": "a0db5390ce9c4bfebc187d4e81052489"}