/
Implementation Plan June 14, 2009

Implementation Plan June 14, 2009

Jun 15, 2009

Personnel

  • Programmer is James Renfro

  • DBA is Prabhu Pilli

  • QC is Sandra

Preparation for second pre-production release (June 12, 2009)

  • (Programmer) Migrate SAK-2853.patch and SAK-2854.patch to production branch

  • (Programmer) Modify prod sakai.properties to include final grade submission urls

  • (Programmer) Cut gb2 prod release branch as:

  • (Programmer) Update svn scripts to include gradebook2 prod release branch

  • (Programmer) Create prod tag sakai_2-5-x-prod-017-RC3

  • (Programmer) Create sakai.properties prod tag: https://mware.ucdavis.edu/svn/ucd-sakai/sakai-properties/tags/sakai-properties-2-5-x-prod-017-RC3 from prod branch

  • (Programmer) Checkout Prod-Tag-2-5-x-RC-17-RC3 on mario and deploy to staging

  • (Programmer) Under config-staging, export sakai.properties as sakai.properties-prod-017-RC3 and make modifications by hand to sakai.properties

  •  

Preparation for final production release (June 14, 2009)

  • (Programmer) Copy over sakai and properties tags to non-release-candidate version

  • sakai.properties additions/changes

    • # GB2: Help URL gb2.help.url=http://smartsite.ucdavis.edu:8000/smartsite/ucd-gateway/Gradebook2Documents.html # GB2 : Final Grade Submission final_grade_submission_url=https://classes.ucdavis.edu/CourseManagement/final_submit/fgs_direct_upload.cfm?sakai_id= final_grade_submission_path=/afs/.ucdavis.edu/app/sakai/gradefiles/ # Stealth Tool List stealthTools@org.sakaiproject.tool.api.ActiveToolManager=sakai.discussion,sakai.presentation,sakai.metaobj,sakai.search,sakai.ucd.training.admin.tool,sakai.rutgers.linktool,sakai.rutgers.testlink,blogger,sakai.assignment,sakai.ucd.enterprise.data.tool,sakai.messagecenter,sakai.ucd.stats,sakai.reports,smartsite.guest.activate,smartsite.guest.register,sakai.gradebook.gwt.rpc

During maintenance window

  • (ProjManmgt) Set database marker.

  • (S + 0 min Programmer) Put all application servers into maintenance mode and shutdown Sakai on each one

  • (S + 10m DBA) Backup full database

  • (S + 35m DBA) Apply sql scripts at:

  • (S + 2m Programmer) Deploy sakai release tag via setup-sakai-node.sh to sakaiprod1.

  • (S + 35m Programmer) Restart sakaiprod1 sakai instance

  • (S + 40m Programmer) Add gb2 to the following sites:

    • Login to sakaiprod1 as an admin user

    • Go to Administration Workspace, Sites tool

    • Search for siteid 319258e7-c2ee-4eab-80c8-65365458c345 (AAS 070 001 W06) by pasting 19258e7-c2ee-4eab-80c8-65365458c345 into the box to the left of SiteId and then clicking on SiteId

    • Drill down via the SiteId to the site properties page and scroll down to and click on "Pages"

    • Choose New Page

    • Enter Page Title: Gradebook 2

    • Click on New Tool at the top of the new page

    • Click on the radio button next to Gradebook NG (sakai.gradebook.gwt.rpc)

    • Change the title in the box at the bottom from Gradebook NG to Gradebook 2

    • Click Save

    • Visit the site to verify that the tool is there and activates the new tool

  • (S + 45m QC) Verification for the following sites: (1) AAS 070 001 W06

    • Add gradebook2 to my sites

    • Verify that I can navigate to each UI panel.

    • Verify that same number of learners exist as before (screen shots).

    • Verify that I have the same number of categories and items as before (screen shots).

    • Verify that grades can be entered.

    • Verify that categories and items can be added.

  • (S + 60m Programmer) Deploy release tag via setup-sakai-node.sh to sakaiprod2 . . . sakaiprod6, and sakaiprodmail1.

  • (S + 70m Programmer) Start Sakaiprod2 . . . sakaiprod6, and sakaiprodmail1.

  • (S + 80m Programmer) Take smartsite-prod out of maintenance mode 

  • (S + 84m 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 DBA) Restore all database tables from backup

  • (D + 5m Programmer) Remove sakai.properties from config-staging and rename sakai.properties.016 to sakai.properties

  • (D + 15m Programmer) Deploy previous tag on head node and all other app servers via setup-sakai-node.sh

  • (D + 42m Programmer) Restart sakai head node after verifying with DBA that restore is complete

  • (D + 45m ProjManmgt) check database marker

  • (D + 50m Programmer) Restart sakai on remaining nodes

  • (D + 60m Programmer) Take application servers out of maintenance mode