Personnel:
rSmart Team
UCDavis programmers, DBA, Project and Program Managers (Kirk and Sandra), UCDavis QA (David Woods, Vernon O'Connor, Pete Peterson).
During Maintenance Window
- (UCDavis programmers) Shut down Davis Smartsite Prod.
- (UCDavis DBA) Send rSmart a final snaphot of SmartSite-PROD internal database.
- (UCDavis SysAdmin) Perform the final rsynch for AFS against the uncontaminated content store.
- (rSmart) Load final database snapshot.
- (rSmart) Perform database conversion.
- (rSmart) Run configuration spreadsheet.
- (rSmart/UCDavis) Complete manual configuration.
User Verification Testing
- Bring up the system in maintenance mode
- Verify content was migrated
- Verify all critical tools are present and functional (open, basic function, close) for project and course sites.
- Verify that we can create sites.
- Verify that existing course and project sites have their same tools (identify 20 (5 each) of these to verify)
- Verify all known critical and blocker bugs have been fixed
- Verify final grade submission url is point toward My Prod.
- 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.
- Verify that the names of each server appears including the tag
- Verify the gateway is correct
- 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
Vote on our readiness
Release the system to public