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 13
Next »
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
- I'll use site ENL 199 S03 / ENL 118 S01 / ENL 198 S02 SSS 2009 but without su'ing to MyUCDavis
- complete gradebook final grades using the override field
- submit final grades. Should get an error message from MyUCDavis and a refusal to redirect.
- James will review the afs gradefile to verify that only the lecture or only one lecture had grades applied.
- (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