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 4 Next »

[Note, the fallback release if April 17, 2010]

Personnel:
•    Kirk Alexander
•    Sandra Stewart
•    UC Davis programming team
•    rSmart programming team
Communication
•    server: irc.freenode.net
•    channel: #ucdsakai
During Maintenance Window
Pre Implementation tasks

  1. (March 16, rSmart team) check out SAK-3163.patch for Gradebook 2 from our subversion patches director.
  2. (March 16, rSmart team) build Release Candidate 1 on smartsite-test.rsmart.com using the SAK-3163 patch.
  3.  (March 16, rSmart team) add -Psakai2.6 to the mvn command. This will tell gb2 to build using kernel but not edu-services.
  4. (March 16, UCDavis team) attach code for duplicate sections fix patch (sak-3144) to RSN: 3986-8306816 ticket.      
  5. (March 16, rSmart team) build patch for RSN: 3986-8306816 on smartsite-test.rsmart.com.
  6. (March 22, rSmart team) build Release Candidate 2, subversion tag 1.2.0-RC2 on smartsite-test.rsmart.com
  7. (March 29, rSmart team) build Final Release Candidate, subversion tag 1.2.0-RCn on smartsite-test.rsmart.com

[note: we may several gradebook release candidates prior to the production release on April 13.]

During the Implementation rollout
•    (5:00am to 5:05 am, rSmart) Place SmartSite into maintenance mode.
•    (5:05am to 5:20am, rSmart) rSmart will
o    Build Final Release Candidate  on smartsite-test.rsmart.com using the SAK-3163 patch.

Add -Psakai2.6 to the mvn command. This will tell gb2 to build using kernel but not edu-services.
o    Retrieve attachment from RSN: 3986-8306816 ticket and apply to SmartSite prod.
•    (5:21am to 5:25am, rSmart) rSmart will bring up one node, still in maintenance mode, for QA verification.

Content and Function Verification Testing
•    (5:21am to 6:00am, UCDavis) QA  will verify that the system has been successfully upgraded by doing the following:
o    [QA test plan tbd]
o   
•     ( 6:01am – 6:15am, rSmart and UCDavis) Team will decide go or roll back.
Vote on our readiness to bring the system back up
•    (6:16am – 6:17am rSmart and UCDavis) Team to vote on readiness to bring the system back up assuming we’re going forward.  See rollback section for retreating.

Release the system to public
•    (6:35am – 6:45am, rSmart) bring up all application servers.
•    (6:46 am – 6:47am, rSmart) will release application to public by reapplying normal mode.
•    (6:48 am – 6:50am, UCDavis)  QA/PM will send email notification to our SmartSite community to say the system is back up.  (6:50 am – 6:52am, UCDavis)   Project or Program Manager will change the MOTD.

Rollback
•    (6:32 am – 7:00 am)      To be determined by rSmart.
    (List the first step in rolling back)
•     (6:41 am – 6:50am, UCDavis)  QA will log in and verify that the fix has been removed by doing the following:
    (to be determined)
    (to be determined)
•     (6:51 am – 6:55 am, rSmart) will bring up the application
•    (6:56 am – 6:57am, rSmart)  will release application to public
•    (6:58 am – 7:00am, UCDavis)  QA/PM will send email notification to our SmartSite community to say the system is back up
•    (6:58 am – 7:00am, UCDavis)   Project or Program Manager will change the MOTD.

  • No labels