/
Implementation Plan December 18-19, 2009 rSmart SmartSite

Implementation Plan December 18-19, 2009 rSmart SmartSite

Owned by Former user (Deleted)
Last updated: Dec 18, 2009 by Thomas AmslerVersion comment

Note:  For User Testing during maintenance mode, you can use the spreadsheet for content testing here  and one for functional testing  here.  OR you can update the Google Doc directly here .  Let me know if you don't have access to the Google Docs.  If you use the separate spreadsheets attachments, please update the Google Docs frequently so the group can keep track of progress. 

All times are in Pacific Standard Time. 

--For content and functional testing Dec 19, 2009, DO NOT change data in staff or instructor's project or course sites. 

--Do not create course sites for instructors without prior permission.

--In your project or course site, send email notifications to one of us only.

Personnel:

rSmart Team

UCDavis programmers, DBA, Project and Program Managers (Kirk and Sandra), UCDavis QA (David Woods, Vernon O'Connor, Pete Peterson).

Communication

  • server: irc.freenode.net
  • channel: #ucdsakai

All times are in Pacific Standard Time.

During Maintenance Window

Pre Implementation tasks

  • Transfer all mothra ID changes to Banner schema.
  • Undo the temporary fixes wrt for CAS not using the MothraID but was using the Kerberos ID.
  • Sakai local.properties changes : rSmart's local.properties
    • Guest Access properties 
      guest.registration.tool.url=https://smartsite.ucdavis.edu/portal/site/f8382610-2f5b-4cd9-9687-564ca6e26b9c/page/41483e8f-08ae-4d89-9145-e50cdbb12fad?toolstate-1ed95b3d-c019-407b-88c6-0e657264d639=
forgot.passwork.link=https://smartsite.ucdavis.edu/portal/site/f8382610-2f5b-4cd9-9687-564ca6e26b9c/page/41483e8f-08ae-4d89-9145-e50cdbb12fad?toolstate-1ed95b3d-c019-407b-88c6-0e657264d639=/register/pwreset
    • Gradbook 2 properties 
      final_grade_submission_url=https://classes.ucdavis.edu/CourseManagement/final_submit/fgs_direct_upload.cfm?sakai_id=
final_grade_submission_enterprise_service_url=https://classes.ucdavis.edu/CourseManagement/final_submit/fgs_ss_deliver.cfm

gb2.help.url=http://smartsite.ucdavis.edu:8000/smartsite/ucd-gateway/Gradebook2Documents.html
  • (warning) Make sure that rSmart configures their firewall to allow outgoing traffic to classes.ucdavis.edu
  • To make sure that the firewall is configured correctly, execute the following command: 
    • wget --no-check-certificate  https://classes.ucdavis.edu/CourseManagement/final_submit/fgs_ss_deliver.cfm

# This should return something like the following. The key is  to get the "400 Bad Request" and not a 403


Resolving classes.ucdavis.edu (classes.ucdavis.edu)... 128.120.33.73
Connecting to classes.ucdavis.edu (classes.ucdavis.edu)|128.120.33.73|:443... connected.
WARNING: cannot verify classes.ucdavis.edu￢ﾀﾙs certificate, issued by ￢ﾀﾜ/C=US/O=Equifax/OU=Equifax Secure Certificate Authority￢ﾀ�:
  Unable to locally verify the issuer￢ﾀﾙs authority.
HTTP request sent, awaiting response... 400 Bad Request
2009-12-16 14:44:03 ERROR 400: Bad Request.
    • CAS properties 
      login.url=https://smartsite.ucdavis.edu/xsl-portal/login
loggedOutUrl=https://cas.ucdavis.edu/cas/logout?service=https://smartsite.ucdavis.edu/xsl-portal
    • CAS code changes 
      Change all the "smartsite-test.rsmart.com" references to "smartsite.ucdavis.edu in:
https://svn.rsmart.com/svn/customizations/ucd/trunk/config/sakai-login-tool/rsmart.properties

We probably need to create a new tag after the code changes.
    • Gateway URL references in local.properties 
      References to "http://smartsite-test.ucdavis.edu:8000/" need to be replaced with "http://smartsite.ucdavis.edu/ucd-gateway"

During the Implementation rollout

  • (UCDavis SysAdmin, 12.17.2009, 5:00pm) Put the SmartSite Prod. and SmartSite-NG servers into maintenance in status monitoring.
  • (UC Davis Sysadmn, 12.17.2009, 5:05pm) Shut down Davis Smartsite Prod. and SmartSite-NG and put the application servers in maintenance mode.
  • (UCDavis SysAdmin/Operators,12.17.2009, 5:05pm) Change DNS to point SmartSite.ucdavis.edu to rSmart's IP address (72.44.195.46) and set this same IP as the MX record for the host.
  • (UCDavis SysAdmin, 12.17.2009, 5:10pm) Update UCD SMTP mailertable to point smartsite mail at rSmart's IP.
    • Change this: smartsite.ucdavis.edu esmtp:[sakaiprodmail1.ucdavis.edu]
    • To this: smartsite.ucdavis.edu esmtp:[smartsite.ucdavis.edu]
  • (rSmart, 12.17.2009, 5:00pm) Post our Scheduled Maintenance page  at 72.44.195.46 (smartsite.ucdavis.edu).
  • (UCDavis SysAdmin, 12.17.2009, 5:15pm) Setup a local url redirect to SmartSite hosted by rSmart.  Keep this in place while the full DNS propagation proceeds.
  • (UCDavis DBA12.17.2009, 5:30pm) Take a final snaphot of SmartSite-PROD internal database.
  • (UCDavis SysAdmin, 12.17.2009, 6:00pm) Transmit the DB snapshot to rSmart.
  • (UCDavis SysAdmin, 12.17.2009, 6:00pm) Perform the final rsync for AFS against the uncontaminated content store.  Stop the nightly cron job that runs on caje.
  • (UCDavis DBA, 12.17.2009, 6:30pm) apply final database snapshot to NG, internal database.
  • (UCDavis, DBA, before 12.18.2009) connect NG app server to Steele external database.
  • (rSmart) Load final database snapshot.
  • (rSmart) Perform database conversion.
  • (rSmart) Run configuration spreadsheet.
  • (rSmart) Bring up Smartsite.ucdavis.edu (new IP address) and inform UCDavis.
  • (rSmart/UCDavis) Complete manual configuration as per Kara's post installation document
  • (UCDavis, programmers, afternoon 12.18.2009 or 12.19.2009, 7:30am) Bring up NG.
  • (UCDavis, programmers,afternoon 12.18.2009 or12.19.2009, 7:35am) Grant QA su access in NG.
  • (UCDavis, afternoon 12.18.2009 or12.19.2009, 7:40 am) Begin user testing verification.  Remember to log into IRC.
  • (UCDavis, SysAdmin) Send littlejohn's IP address to Dave Thomson for rsycing back to our DC SAN.
  • (UCDavis/rSmart) After user testing and we open Smartsite to the public, make sure we're in normal mode, i.e., we can access the system from any IP address.

Content and Function Verification Testing (Identify 10 sites for roster and site info comparison prior to Dec 19). 

See attached spreadsheets  here  and here or Google docs here .  Remember to update the Google docs if you decided to work with spreadsheets offline.

  • Bring up the system in maintenance mode
  • Verify that creating a new account sets the right tools and permissions in MyWorkspace
  • Verify all critical tools are present and functional (open, basic function, close) for project and course sites.
    NOTE: For items below do most of the testing on existing sites as creating new sites will send out emails
    • Test and Quizzes -- create a quiz.  Make sure students can take it.  Make sure instructor can see results.
    • Gradebook 2 -- Just make sure it's populated.
    • Section Info -- Make sure it creates automatically when you create a course site.  Make sure you can assign TAs (doe this as an Instructor not as an admin.)  Make sure that newly created course sites DO NOT have the Open Campus and Wait Listed Roles.
    • Site Info -- Make sure you can create and populate ad hoc  groups.  Make sure Site Info loads in 3-4 seconds.
    • Rosters -- Make sure you can see the Open Campus students in Enrollment Status.
    • Assignments -- Create an assignment, make sure the student can submit it, make sure the instructor can see the students work.
    • Web Content -- make sure you can create a link.
    • rWiki -- add a page
    • Announcements -- create an announcement.  Make sure participants can see it.
    • Chat -- create chat entries.  Make sure participants can see entries and create more.
    • Syllabus --
    • Mailtool -- send email to one of us.  Make sure we receive it.
    • Email Archive -- make sure mailtool et al copies to email archive.
    • Home -- Make sure it's there
    • Page Order tool -- Make sure it orders tools, renames, drops, adds.
  • Verify that we can create sites, project and course.
  • Verify that existing course and project sites have their same tools
  • Verify all known critical and blocker bugs have been fixed
  • Verify that OSP is fixed or not available for users.
  • Verify Guest Access:
    • add a guest, and verify email goes out to a real gues (e.g. test with real gmail accounts)
    • register as a guest,
    • activate a guest,
    • use the forgot your password function.
  • Verify that my campus messages works and doesn't require a second login.
  • Verify that the Support and Training link is present
  • Verify that project sites have the site statistics tool
    • Can Lead TAs use it?
    • Can Instructors use it?
  • Verify that all our tools are present for project and course sites and the defaults are checked.
  • Make sure that ad hoc groups works in old project sites.
  • Verify final grade submission url is point toward My Prod. [How is this done - need specific instructions here]
  • Verify Davis database markers can be found; internal database converted correctly
  • Verify the PDA portal works
  • Verify that the performance is 3 sec or better by running a load test. [a scripted load test or just visit Site info on large class??]
  • Verify that that all our roles exist:
    • new course sites can add Lead TA; 
    •  new project sites can add Organizer and Participant.  
    • Auditor,
  • Verify that the names of each server appears including the tag
  • Verify the gateway is correct - Kirk to make edits here above before QA starts as the one coming from UCD will be incorrect.]
  • Verify that MOTD works correctly
  • Verify response time is good
  • Verify Phoenix hot spare is being updated
  • Verify table create scripts are running as scheduled
  • Confirm Melete files exist and we can export a converted module
  • Verify SU (Super User) functionality in order to conduct intensive QA testing.

Process for reporting problems during verification

       Shouldn't this all go into the rSmart Jira?

Vote on our readiness

Release the system to public