Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 3
Next »
Personnel
- Programmer is Mike Wenk
- 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
- TODO
- 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