Deployment
-
Deployment Strategy
Phase 1 of Lecture Recording will see the Implementation of 114 rooms and the necessary associated service integrations in place for the start of the academic year 17/18.
This checklist relates to the integrations required for authentication and authorisation of users, allowing access to the system, plus appropriate service information and responsibilities.
The supplier chosen for Lecture Recording is Echo360. Echo360 is a cloud based provider.
Access to the lecture recording service in Phase 1 (academic year 17/18) will be via the two University VLEs only. Learn and Moodle.
Echo360 use an LTI integration as the link between Echo360’s Active Learning Platform (ALP) and our VLEs. Although we are using recording hardware in the 114 rooms, we are not hosting any servers relating to the lecture recording platform onsite. Once a lecture has been recorded by the device, it will send the file over the network to Ech0360’s ALP where it will be processed.
As the service is contained to access via the VLEs for Phase 1 it was determined that no feed of identities from the Identity Management Service was required. Instead the users will be fed across from the VLEs via the LTI link and will automatically be given the appropriate permissions within their relevant course space within Echo360.
Some users will be pre-populated in the service. Those are the Course Organisers/Course Secretaries. As a one-off process for Phase 1 this information has been gathered along with all course information from EUGEX, placed into a CSV file which will be uploaded to the Echo360 ALP.
This is required so that the initial link between VLE course and Echo360 ALP course can be made manually. Once that is done all other course users will be provisioned automatically as they click through via the LTI connection.
Echo360 relies on the email address of a user as their primary identifier. ITI have implemented the format uun@ed.ac.uk as a non-primary alias for all university users. We are adopting this as our primary identifier in the Echo360 system.
Doing this has the advantage of making sure all users will only ever have one consolidated account in Echo360.
To facilitate this, alterations have had to be made to the user feeds that maintain Learn and Moodle. Email fields in both of those services have been updated to the uun@ed.ac.uk format.
Staff Visitors can be provisioned through the Visitor Registration Service (VRS) for Lecture Recording. As we are restricting access to Lecture Recording to the VLEs, the lecture Recording button in the VRS will prime a user with Learn and Email.
Single Sign On (SSO) has been configured for the new service, but no curated direct login page will be advertised or support by the university.
SSO via Shibboleth can be used for access to the system only where an account already exists. No account creation will occur using direct SSO login.
Echo360 has been given the identity Media Hopper Replay and will be one of the family of Media Hopper services. The original Media Hopper (media.ed.ac.uk) remains and will be rebranded as Media Hopper Create.
The service pages for Media Hopper Replay care here:
https://www.wiki.ed.ac.uk/pages/viewpage.action?pageId=342907476
The deployment schedule can be found here:
https://www.wiki.ed.ac.uk/display/insite/Deployment+to+Live+Schedule
-
Dependencies
Access to lecture recording is dependent on access for a user to a course within a VLE that has been linked to a course space inside Media Hopper Replay (Echo360).
Media Hopper Replay (Echo360) uses the email of a user as their primary identifier. We are dependent on uun@ed.ac.uk being an active email address for all users at the university.
Linking a course in a VLE to a course space in Media Hopper Replay (Echo360) requires the course to be created in MH Replay and that course linked manually by the course owner through the VLE.
-
Communication
The lecture recording programme employs a Communication Officer to manage the wider communications to users for training, marketing and signposting the service pages to users.
The changes to the email field in Learn and Moodle has been communicated by the Digital Learning and Media (DLAM) and Education Design and Engagement (EDE) to the appropriate user groups.
Unidesk categories have been setup for the Media Hopper family of services.
The Service Priority for Media Hopper Replay has been set to ‘Medium’
-
Deployment Checklists
Application checklist
|
Component |
Success Criteria |
Project Stage Required (Agile) |
OK (Y/N) | Reviewed by (date) | Outdstanding Actions (Who) |
|---|---|---|---|---|---|
|
Implementation Plan |
Feedback from previous test implementations completed and successful full implementation undertaken for UAT |
DSOR (Release 1-n) |
Y |
Learn: MLE0033-1 Moodle: MLE0033-3 VRS: K:\ISAPPS\dsg\Projects\MLE003\Deployment HB 28/08/2017 |
|
|
Implementation Risk Assessment |
A risk assessment has been undertaken for the Implementation Plan and selected deployment dates. (e.g. roll back) |
ASOR (Release 1-n) |
Y | Moodle, Learn: Existing Feeds VRS: Bamboo deploy rollback. Remove DB entries HB 28/08/2017 | VRS: Database rollback to be scripted - DevTeam |
|
TAD/Operational Document |
Documentation complete Action: The Document must be copied to the Wiki |
ASOR (Release 1-n) |
Y | Learn, Moodle, VRS: No changes at TAD level. HB 28/08/2017 | |
|
System Design Specification (SDS) |
Document complete and accurate.
Action: The Document must be copied to the Wiki |
ASOR (Final Release / Handover) |
Y |
Cloud-hosted application. SDS N/A HB 280/08/2017 |
|
|
System Description Document |
Document complete and accurate.
Action: The Document must be copied to the Wiki |
ASOR (Final Release / Handover) |
Y | Cloud-hosted application. SDS N/A HB 280/08/2017 | |
|
Scalability/Load Testing |
Adequate load testing has taken place. The results have been recorded and analysed to ensure that the application will cope with the anticipated load. |
ASOR (Final Release / Handover) |
N/A | HB 28/08/2017 | |
|
Performance |
The application has been tested against stated performance criteria. Performance has been assured by user and support staff testing. |
ASOR (Final Release / Handover) |
N/A | LTI access tested. VRS Visitor assignment UAT completed. HB 28/08/2017 | |
|
Source Code
Source control must be checked out till go-live and checked-in after go live |
Source code has been secured with SVN or other source control tool. Action: ensure Production Branch created Where code is provided by a third party (e.g. supplier) it has been established who is responsible to maintain source code
|
DSOR (Final Release / Handover) |
N/A | HB 28/08/2017 | |
|
Configuration Management Database |
The relevant details regarding new or changed infrastructure components have been added to the CMDB in unidesk |
ASOR (Release 1-n) |
N/A | HB 28/08/2017 | |
|
Change Control(s) |
A Change & Release record has been created in unidesk for the LIVE implementation request. Action: record unidesk number |
ASOR / (Release 1-n) |
Y |
Link to deployment schedule and change references. https://www.wiki.ed.ac.uk/display/insite/Deployment+to+Live+Schedule/ |
Change required for VRS components. ProjServices |
|
Test Log Review |
A review of the test log (JIRA) has taken place to ensure all required actions have been completed. If this is not the case, then confirmation on criticality of outstanding issues and action plan for resolution is required. |
ASOR (Final Release / Handover) |
JIRA Review for MLE0034 pending | ||
|
Production Management Handover |
Handover to Applications Management and Technology Management is completed or arranged and the teams are in position to support the application post deployment. Action: record handover dates |
ASOR (Final Release / Handover) |
Y | Implemented via existing Learn, Moodle feeds. Handover not required. HB 28/08/2017 | |
|
Support Accounts |
Read access accounts or update current read access accounts have been set up for support staff(requires business owner approval) |
ASOR (Final Release / Handover) |
N/A | No accounts specific to Authentication Work package. | |
|
Password Manager (InfoKeep) |
InfoKeep has been updated with all relevant account details including external supplier accounts |
ASOR (Release 1-n) |
N/A | No accounts specific to Authentication Work package. | |
|
Environment comparison |
Database comparison between TEST and LIVE (might be required before and after go-live) |
ASOR (Final Release / Handover) |
N/A | Cloud-hosted application. HB 28/08/2017 | |
|
Client requirements |
Does the application have specific client requirements, such as JVM/JRE versions, JInitiator etc If so have these requirements been raised with Desktop services Wiki pages to be updated: [1] https://www.wiki.ed.ac.uk/display/insite/Corporate+applications+with+client+based+requirements [2] https://www.wiki.ed.ac.uk/display/insite/Client+side+requirements+for+co... |
ASOR (Release 1-n) |
N/A | Cloud-hosted application. SDS N/A HB 28/08/2017 | |
|
Technologies |
Is there any new software or technologies involved? (Y/N) If yes state any additional actions taken to ensure adequate handover to the production support team |
ASOR (Release 1-n) |
N | HB 28/08/2017 | |
|
Access outside University |
By default all web based applications are accessible outside University without use of VPN etc Wiki list If not accessible from outside University this needs to be approved by Production Management. |
ASOR (Release 1-n) |
Y | HB 28/08/2017 | |
|
Vendor Access Required |
Does vendor require db/app access (Y/N) If yes, ensure access details are in TAD |
ASOR (Final Release / Handover) |
N | Cloud-hosted application. HB 28/08/2017 | |
|
Certificates |
All changes to certificates or new certificates for this service have to be added to the certificate master list. The certificate master list is being managed by Applications Management This includes TEST and LIVE certificates and records type of certificate and expiry dates. |
ASOR (Final Release / Handover) |
N/A | Cloud-hosted application. HB 28/08/2017 | |
|
Deployment Date(s) |
Agreed date has been confirmed that allows adequate time for completion of Acceptance Sign Off Review. |
ASOR (Final Release / Handover) |
Y |
Deployment 04/09/2017 HB 28/08/2017 |
|
|
Deployment Resources |
IS and business area resources required for deployment, including those needed for post implementation checking and sign off have been secured. |
ASOR (Final Release / Handover) |
Y | Resource arranged. HB 28/08/2017 | |
|
Deployment Ownership |
Responsibilities for managing the go-live, including: comms with service owner and end users, ensuring go live timescales are met, managing issues arising and managing comms between all teams involved in go live. |
ASOR (Final Release / Handover) |
Y | Project Mgmt dealing HB 28/08/2017 | |
|
Service Announcement(s) |
A Service announcement has been raised with the agreed deployment date on the alert system:
http://reports.is.ed.ac.uk/alerts/
Service announcements should be raised by Project Manager 10 days before go live, but no later than 4 days. |
ASOR (Release 1-n) |
Y | Application is Cloug-hosted. Learn and Moodle feed updates occur in advance. |
Service Alert required for VRS. Change advisory required. |
|
Reporting and Analytics |
New BI Universes or substantial changes to Universes/report offerings need to be documented in the Information Portal managed by GaSP. https://www.wiki.ed.ac.uk/display/IP/Information+Portal+Home |
ASOR (Release 1-n) |
N/A | Cloud-hosted application. HB 28/08/2017 |
Infrastructure checklist
|
Component |
Success Criteria |
Project Stage Required (Agile) |
OK (Y/N) | Reviewed by (date) | Outdstanding Actions (Who) |
|---|---|---|---|---|---|
|
Technical Architecture/Operational Document(TAD) |
Documentation complete and accurately reflects the environment subjected to UAT.
|
ASOR (Release 1-n) |
Y |
Learn, Moodle, VRS: No changes at TAD level. HB 28/08/2017 SSO Config added to the Service Wiki from Dave Tech (Hannah) CF 29/08/2017 |
|
|
Security |
All security requirements, e.g. SSL encryption, IP based restrictions firewall requirements have been specified, tested and implemented in LIVE |
ASOR (Release 1-n) |
N/A | Cloud-hosted application. HB 28/08/2017 | |
|
User Accounts |
|||||
|
Patching |
Ensure that all applications have an agreed patching schedule and this schedule is agreed with service owners. Different technologies have different patching strategies: Oracle, Windows, Linux |
ASOR (Final Release / Handover) |
N/A | Cloud-hosted application. HB 28/08/2017 | |
|
Start/Stop scripts |
Are Server Start-up/Shutdown scripts in place? Including start-up procedure documented, enabled and tested |
ASOR (Release 1-n) |
N/A | Cloud-hosted application. HB 28/08/2017 | |
|
Ports |
Port allocation file been updated:
https://www.wiki.ed.ac.uk/display/insite/Port+Allocation+on+Unix+Servers |
ASOR (Release 1-n) |
N/A | Cloud-hosted application. HB 28/08/2017 | |
|
Backup and Recovery |
All backups as noted in the TAD need to be confirmed operational.
A test recovery of user data needs to be done to validate the integrity of the recovery mechanism and process. |
ASOR (Release 1-n) |
N/A | Cloud-hosted application. HB 28/08/2017 | |
|
DR Copy |
DR copy to SECONDARY DB configured and tested (unless existing database which is already setup). |
ASOR/Release1 |
N/A | Cloud-hosted application. HB 28/08/2017 | |
|
Logs |
For all logs the following is in place:
|
ASOR (Release 1-n) |
N/A | Cloud-hosted application. HB 28/08/2017 |
Support checklist
|
Component |
Success Criteria |
Project Stage Required (Agile) |
OK (Y/N) | Reviewed by (date) | Outdstanding Actions (Who) |
|---|---|---|---|---|---|
|
Support Agreement (including any charging arrangements) |
A support agreement OLA is in place for any new applications – including any hosting or support charges. Where external suppliers are involved an SLA should be in place as well.
Action: SLA moved to wiki:
https://www.wiki.ed.ac.uk/display/insite/SLA+repository+-+Applications+Management |
ASOR (Final Release / Handover) |
Y |
OLA added to: https://www.wiki.ed.ac.uk/pages/viewpage.action?pageId=342907476 HB 29/08/2017 |
|
|
Time Recording Code |
A Time Recording code for the application, if required, has been confirmed and set up (in ASTA) Action: Does application require a separate entry for business area in ASTA |
ASOR (Final Release / Handover) |
Y | Confirmed utilisation of existing Media Hopper ASTA code for authentication. Lecture capture application support is provided via LTW. HB 29/08/2017 | |
|
Disaster Recovery and Business Continuity |
Appropriate DR/BC provision is in place and has been fully tested. Application DR/BC details have been transferred to the DR Portfolio and DR level (1, 2 or 3) has been agreed |
ASOR (Release 1-n) |
N/A | Cloud-hosted application. HB 28/08/2017 | |
|
Test Environment |
An adequate TEST environment has been established for the application which may be used by support to test future changes prior to releasing these in the LIVE environment. |
ASOR (Release 1-n) |
Y |
Authentication Workpackage streams complete. HB 28/08/2017 |
|
|
Hardware and Software Licensing |
All required licensing is in place including maintenance/support arrangements with external suppliers. |
ASOR (Final Release / Handover) |
Y |
Link to the Service Wiki and OLA https://www.wiki.ed.ac.uk/pages/viewpage.action?pageId=342907476 CF 29/08/2017 |
|
|
Browser Compatibility |
Browser compatibility has been tested and compatibility information updated See for details |
ASOR (Final Release / Handover) |
N/A | Cloud-hosted application. HB 28/08/2017 | |
|
Portal Compatibility |
Portal compatibility, where required, has been confirmed the Portals Service Owner. |
ASOR (Final Release / Handover) |
N/A | HB 28/08/2017 | |
|
Help Desk |
The new application is recognised with the UniDesk (A business contact queue is defined where initial calls are raised with) |
ASOR (Final Release / Handover) |
Y |
Both Media Hopper Replay and the renamed Media Hopper Create (Kaltura) have been added to Unidesk. CF 29/08/2017 |
VRS Service Details communicatied to Visit approvers - ServiceMgmt or via Product release? |
|
User Guide Documentation |
Appropriate documentation has been produced for users of the new application. |
ASOR (Final Release / Handover) |
Y | Documentation at: http://www.ed.ac.uk/information-services/learning-technology/lecture-recording HB 29/08/2017 | Digital Skills have signed off the training docs. Will be published on the 5th of Sep. |
|
Training Material |
Training material, if required, has been produced and is of an appropriate standard. |
ASOR (Final Release / Handover) |
Y | http://www.ed.ac.uk/information-services/learning-technology/lecture-recording/training HB 28/08/2017 |
Courses on the use Media Hopper Replay have been running successfully since the 16th of August. CF 29/08/2017 |
|
Demonstration or Walkthrough |
Demonstration or walkthrough of the new application has taken place for other stakeholder. |
ASOR (Final Release / Handover) |
N/A | Cloud-hosted application. HB 28/08/2017 | |
|
Web Sites and Other Document Sources |
External and internal web sites have been reviewed to ensure that all application references are present, correct and up to date. |
ASOR (Final Release / Handover) |
Y | LTW Web page now includes links to Media Hopper Create and Replay. HB 28/08/2007 |