[CITL] FW: vhost Service: User Acceptance Testing
Azra Ayers
azra.ayers at ucr.edu
Fri Apr 30 15:34:27 PDT 2021
Dear CITL Members,
This information is for awareness purposes. The email below was sent earlier today to the Campus Web Advisory Group to kick off the UAT phase of the vhost Service Migration as it relates to Project Genesis. I have attached the linked documents below in case there are access limitations. Please review the information, forward it to your colleagues as you see fit, and let me know if you have any questions.
The recipients of the email below were sent BCC, so I have included them here for your reference:
Agam Patel, Alexandra Chrystal, Bill Manes, Cherysa Cortez, Crystal Brailsford, Eddie Greer, Ilse Ungeheuer, James Lin, Jeff Girod, Jennifer Yturralde, Joann Young, Joel Valdez, Johnny Lam, Jorge Sanchez, Joseph Bradfield, Julie Porter, Kelly McGrail, Kelvin Mac, Loretta Vandivier, Luis Bravo, Luis Sanz, Mark Manalang, Melanie Ramiro, Paul Simon, Puja Pannu, Shanon Langlie, Shanshan Liao, Stan Fletcher, Tom Windeknecht, Travis Gutierrez, Ross French.
Thank you,
Azra Ayers
From: Michelle C Tabula <Michelle.Tabula at ucr.edu>
Sent: Friday, April 30, 2021 3:12 PM
Cc: Azra Ayers <azra.ayers at ucr.edu>
Subject: vhost Service: User Acceptance Testing
Dear Web Advisory Group,
Why am I receiving this email?
We are writing to inform you that we are now in the “User Acceptance Test Phase” (UAT) of the vhost service migration for Project Genesis. You are receiving this email because you have been identified as a functional partner for this service and we require your assistance to conduct UAT in the new Staging environment. If you believe you have been identified in error, please let us know as soon as possible. Additionally, please forward this notice to all applicable Site Factory Managers (SFM) and vhost Site Owners.
What is required of me?
The UAT phase requires your support as it involves functional testing to confirm your website(s) is working as expected in the new Amazon Web Services (AWS) environment. Testing will include ensuring that you can connect to the service’s staging environment (staging aliases can be found at vhostsites.ucr.edu), that it is working as expected, that features, and functionality of the website(s) are available, and that the data is accurate. As you conduct testing, should any issues/errors arise we ask that you fill out the UAT Issue Tracking Document (linked below) and provide your findings as soon as possible so that ITS may address any reported issues. Additionally, the service’s Planned Technical Changes (linked below) details recommended areas to focus testing as they relate to your specific website(s). Functional owner testing feedback is required by June 1, 2021, in order to proceed with next steps towards the scheduled production move later this Summer 2021.
What does the UAT Issue Tracking Document<https://o365ucr.sharepoint.com/:x:/t/DrupalWebAdvisoryGroup/ER31UR3K7aJAsKaiqSMSm_oBMiEFnHFQcuWhTN3odK_AxA?e=dKeGHm> entail?
The linked UAT Issue Tracking Document contains the following sections:
• Ref #: ITS will populate this section if a ServiceNow ticket is opened on your behalf to address the reported issue
• URL*: URL of the website impacted by the reported issue
• Tester Name*: Name of the Site Owner or SFM conducting the testing and encountering the issue
• Test Case Description*: Short description of the issue being encountered
• Expected Result*: Explain the expected results when navigating to this specific feature of the site
• Actual Result*: Detailed description of what the tester is experiencing during testing
• Comments*: Include any additional information or supporting solutions
• Status: ITS will populate this section to keep track of the issue’s progress
* Site Owner/Tester will complete these sections.
Key Dates:
04/30/2021
Communication to SFMs and Site Owners to begin UAT
05/01/2021 – 06/01/2021
Review technical changes; Perform testing; Report any issues via UAT Issue Document
06/01/2021
Deadline to report any issues/errors
06/01/2021 – 07/31/2021
ITS to remediate reported issues/errors; Work with site owners as needed on issues and testing; Continue vhost service migration preparation
08/TBD/2021
Move Event: Staging environment to cutover to production in new hosting location (AWS)
What does the Planned Technical Changes Document<https://o365ucr.sharepoint.com/:b:/t/DrupalWebAdvisoryGroup/EReC12lig3FBtNITvvs-03wBDrBXcxa1rEa1Vdt4PdgKng?e=2Lm1PT> entail?
The linked Planned Technical Changes Document provides an overview of the new AWS environment of the vhost service. The document contains the new baseline software versions and architectural layout, possible Site Owner required remediation and refactoring (site dependent), as well as recommended areas to focus on during UAT to ensure the website(s) are functioning as expected.
What is the next step after testing?
Upon completion of UAT, the vhost service’s Production Move Event (ME) schedule will be confirmed. Production MEs take place over the course of a weekend, beginning Friday night and concluding sometime on Sunday. Please note that the impacted service will be intermittently unavailable during the production move.
What else should I know in preparation for my application’s production move event?
In preparation for production cut-over here are a few items to note:
* Websites will continue to be accessed via VPN/Campus IP through SFTP or SSH.
* Current AWS staging URLs will be cutover to production URLs during the Go-Live weekend, therefore staging environment UAT and validation is integral.
* All on-prem hardware and software supporting the service will be decommissioned.
* Any existing software or custom code uploaded/created by Site Owners will need to be maintained and upgraded by Site Owners for individual websites.
* Sites that are no longer needed should be requested for decommissioning/shutdown by submitting a Systems Service Request<https://ucrsupport.service-now.com/ucr_portal/?id=sc_cat_item&sys_id=1ee50eb10f5a0300138942bce1050e5f>.
How can I get help or additional information?
If you would like to discuss the documents and testing expectations, please reach out to Michelle.Tabula at ucr.edu<mailto:Michelle.Tabula at ucr.edu> who will coordinate support with the technical team as needed.
For more information on Project Genesis, please visit https://genesis.ucr.edu<https://genesis.ucr.edu/>.
Thank you for your continued partnership,
Michelle Tabula
Web Analyst
Information Technology Solutions
University of California, Riverside
Azra Ayers
Project Manager
Information Technology Solutions
University of California, Riverside
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ucr.edu/pipermail/citl/attachments/20210430/3017f8eb/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vhost Service Migration to AWS - Planned Technical Changes.pdf
Type: application/pdf
Size: 191816 bytes
Desc: vhost Service Migration to AWS - Planned Technical Changes.pdf
URL: <https://lists.ucr.edu/pipermail/citl/attachments/20210430/3017f8eb/attachment-0001.pdf>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vhost Service - UAT Issue Tracking.xlsx
Type: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
Size: 37008 bytes
Desc: vhost Service - UAT Issue Tracking.xlsx
URL: <https://lists.ucr.edu/pipermail/citl/attachments/20210430/3017f8eb/attachment-0001.xlsx>
More information about the CITL
mailing list