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 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 + 5m Prabhu) Backup the following DB Tables:
    • GB_GRADEBOOK_T
    • GB_CATEGORY_T
  • (S + 10m Prabhu) Apply DB scripts (These are both alter table commands)
  • (S + 8m Programmer) Deploy sakai release tag via setup-sakai-node.sh to sakaiprod1.
  • (S + 10m Programmer) Restart sakaiprod1 sakai instance
  • (S + 15m QC) Verification
    • Log in as a guest user and check for the "forgot your password" link.
    • Programmer will check for any errors that may have been created during the roll out.
  • (S + 20m Programmer) Deploy release tag via setup-sakai-node.sh to sakaiprod2 . . . sakaiprod6, and sakaiprodmail1.
  • (S + 30m Programmer) Start Sakaiprod2 . . . sakaiprod6, and sakaiprodmail1.
  • (S + 35m Programmer) Take smartsite-prod out of maintenance mode 
  • (S + 40m 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 the following tables:
    • GB_GRADEBOOK_T
    • GB_CATEGORY_T
  • (D + 2m Programmer) Remove sakai.properties from config-staging and rename sakai.properties.020 to sakai.properties
  • (D + 4m Programmer) Run mvn sakai:deploy from previous tag directory
  • (D + 15m Programmer) Deploy previous tag on head node and all other app servers via setup-sakai-node.sh
  • (D + 20m Programmer) Restart sakai on remaining nodes
  • (D + 25m Programmer) Take application servers out of maintenance mode
  • No labels