...
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:
...
- [QA test plan tbd]
...
- [ ]
...
- ( 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:
...
...
...
...
...
- #(6:51 am – 6:55 am, rSmart) will bring up the application
- #(6:51 am – 6:55 am, rSmart) will bring up the application
...
- #(6:56 am – 6:57am, rSmart) will release application to public
- #(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) 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.