Deployment - Provisioner

Implementation Plan

Feedback from previous test implementations completed and

successful full implementation undertaken for UAT

DSOR (Release 1-n)

N

Adam

19-Sept-14

Implementation Plan successfully followed for Live deployment.

For future reference it would be good to include a section in this document to cover the deployment of the revised email lookup tool as soon as this is understood. COM008-73 (Dev/Tech)

Latest version of this document was uploaded to the wiki without the above changes on 19th-Sept-2014.

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

Adam

12-May-14

New service has been deployed.

System Design Specification (SDS)

Document complete and accurate.

Action: The Document must be copied to the Wiki

ASOR (Final Release  / Handover)

N

Adam

19-Sept-14

Ross may want to make a few alterations to this after the code handover that we had w/c 19th-May (Ross)

Latest version of this document was uploaded to the wiki without the above changes on 19th-Sept-2014.

System Description Document

Document complete and accurate.

Action: The Document must be copied to the Wiki

ASOR (Final Release  / Handover)

N

Adam

12-May-14

SDS for the C# section of the Provisioner is good. However no content explaining the PowerShell section, just a note that there is a dependency on a PowerSheel script and that this isn't documented in the SDS at present. There needs to be a section to explain the PowerShell functions. (Neil)

No latest version of this doc is attached to the projects website. (Morna)

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)

Y

Adam

19-Sept-14

There are currently IDM time out issues. COM008-125 (Ross/Neil)

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

Adam

19-Sept-14

There are still memory issues under high load conditions. COM008-124 (Ross/Neil)

Source Code

Source control must be checked out till go-live and checked-in after go live

Source code has been secured with VSS or other source control tool.

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

Adam

12-May-14

It looks like all source code is included in Source Control. There is no production branch, however code changes are continuing to be made to resolve outstanding high priority JIRAs. As soon as all JIRAs are closed I would expect a production branch in SVN. (Ross)

Configuration Management Database

The relevant details regarding new or changed infrastructure components

have been added to the configuration management database

(This is currently maintained in the Change Control System)

ASOR (Release 1-n)

N

Adam

12-May-14

PROVISKB1 is still present in change control as it has not been decomissioned and the new provisioning server has yet to be added. (Adam)

Change Control(s)

A change control entry has been created for the LIVE

implementation request.

ASOR / (Release 1-n)

Y

Adam

02-May-14

Change control: 90727

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)

Y

Adam

02-May-14

It was agreed that the provisioner could be put LIVE subject to the signing iff of the remaining high priority JIRA issues. This was achieved on the same day as the deployment.

https://www.projects.ed.ac.uk/project/com008/milestones/acceptance-review-provisioning

Production Management Handover

Handover to Production Management is completed and the team are in are in position to support the application post deployment.

ASOR (Final Release  / Handover)

Y

Adam

02-May-14

Time has been scheduled for handover to support. (Morna)

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)

Y

Adam

02-May-14

JIRA-108 has been closed.

Password Manager (InfoKeep)

InfoKeep has been updated with all relevant account details including external supplier  accounts

ASOR (Release 1-n)

Y

Adam

02-May-14

General users for database access are defined in InfoKeep. Direct RDP access is via Windows login and restricted to Tech Mgmt and Apps Mgmt team members.

Environment comparison

Database comparison between TEST and LIVE (might be required before and after go-live)

ASOR (Final Release  / Handover)

n/a

Adam

19-Mar-14

There is no test environment.

Client requirements

Does the application have specific client requirements, such as JVM/JRE versions, JInitiator?

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+corporate+applications

ASOR (Release 1-n)

Y

Adam

02-May-14

There are no client requirements for the Exchange Provisioner.

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)

Y

Adam

19-Mar-14

Upgraded to Powershell 3, and MS SQL Server 2008. Not significantly different from existing implementation, so no further action required.

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

Adam

19-Mar-14

The Exchange Provisioner is intentionally inaccessible outside Production Management, with the exception of remote database access for Service Management to view the provisioning logs and to update the org-unit : mail service relation.

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)

Y

Adam

21-Mar-14

The proviso365kb1.is.ed.ac.uk certificate is self-signed and not user facing, therefore does not need to be tracked.

Technical Architecture Document(TAD)

Documentation complete and accurately reflects the environment subjected to UAT.

Action: TAD needs to be copied to Wiki

ASOR (Release 1-n)

N

Adam

13-May-14

Sections of TAD relating to provisioner must be completed and agreed. (DevTech)

Operational Document

Describes fully operational tasks and ongoing maintenance.This document should be fully populated and any missing sections or issues should be highlighted.

Action: TAD needs to be copied to Wiki

ASOR (Release 1-n)

N

Adam

13-May-14

Sections of Operational Doc relating to provisioner must be completed. (ServiceMgmt)

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

Adam

13-May-14

Tech Mgmt to confirm if this is the case for the new Exchange Provisioning server. (TechMgmt)

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

Adam

13-May-14

Tech Mgmt to decide what is best to do here for the new server. (TechMgmt)

Infrastructure diagrams

All infrastructure diagrams are updated with newest server and infrastructure detail:

https://www.wiki.ed.ac.uk/display/insite/Server+Layout+%28Unix%29

and

https://www.wiki.ed.ac.uk/display/insite/Server+Layout+%28Windows%29

ASOR (Release 1-n)

N

Adam

13-May-14

Not sure if this is still relevant. Tech Mgmt to confim. (TechMgmt)

Start/Stop scripts

Are Server Start-up/Shutdown scripts in place?

Including start-up procedure documented, enabled and tested.

ASOR (Release 1-n)

N

Adam

13-May-14

Tech Mgmt to confirm. (TechMgmt)

Ports

Port allocation file been updated:

https://www.wiki.ed.ac.uk/display/insite/Port+Allocation+on+Unix+Servers

ASOR (Release 1-n)

N

Adam

13-May-14

Tech Mgmt to confirm. (TechMgmt)

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

Adam

13-May-14

Tech Mgmt to confirm. (TechMgmt)

DR Copy

DR copy to Edzell configured and tested(unless existing database which is already setup).

ASOR/Release1

N

Adam

13-May-14

Tech Mgmt to confirm. (TechMgmt)

Logs

For all logs the following is in place:

• Logs are rotated and old logs are archived or deleted to ensure server space is not reached
• In production only minimal levels of logging is switched on (debug may be adequate on DEV, but not on Production)

ASOR (Release 1-n)

Y

Adam

28-May-14

Log roation has been confirmed as working din Live - Deletion of successful changes over 7 days old.

Support Agreement (including any charging arrangements)

A support agreement (SLA or OLA) is in place for any new applications – including any hosting or support charges.

Action: SLA moved to wiki:

https://www.wiki.ed.ac.uk/display/insite/SLA+repository+-+Applications+Management

ASOR (Final Release  / Handover)

N

Adam

13-May-14

OLA still to be updated and agreed. (Morna)

Time Recording Code

A Time Recording code for the application, if required, has been confirmed and set up.

ASOR (Final Release  / Handover)

Y

Adam

19-Mar-14

No change to exisiting code.

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

Adam

13-May-14

Tech Mgmt to confirm. (TechMgmt)

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)

N

Adam

19-Mar-14

There is no test envioronment. Can it be confirmed if the project will deliver a test environment before closure? (Morna)

Hardware and Software Licensing

All required licensing is in place including maintenance/support arrangements with external suppliers.

ASOR (Final Release  / Handover)

Y

Adam

19-Mar-14

Assumption: A documented procedure is in place for raising support calls with Microsoft.

Browser Compatibility

Browser compatibility has been tested and compatibility information updated

See

http://www.ed.ac.uk/schools-departments/information-services/services/computing/application-development/application-support/supported-web-browsers/browser-application

 for details

ASOR (Final Release  / Handover)

Y

Adam

19-Mar-14

Not a web application.

Portal Compatibility

Portal compatibility, where required, has been confirmed the Portals Service Owner.

ASOR (Final Release  / Handover)

Y

Adam

19-Mar-14

Not a portal application.

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

Adam

19-Mar-14

Use existing procedure.

User Guide Documentation

Appropriate documentation has been produced for users of the new application.

ASOR (Final Release  / Handover)

Y

Adam

19-Mar-14

There are no end-users for this application.

Training Material

Training material, if required, has been produced and is of an appropriate standard.

ASOR (Final Release  / Handover)

Y

Adam

19-Mar-14

There are no end-users for this application.

Demonstration or Walkthrough

Demonstration or walkthrough of the new application has taken place for other stakeholder.

ASOR (Final Release  / Handover)

Y

Adam

19-Mar-14

There are no end-users for this application.

Deployment Date(s)

Agreed date has been confirmed that allows adequate time for completion of Acceptance Sign Off Review.

ASOR (Final Release  / Handover)

Y

Adam

02-May-14

Deployment date was confirmed as Wednesday 30th April 2014.

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

Adam

02-May-14

Was confirmed before 30th-Apr-14.

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

Adam

02-May-14

Was confirmed before 30th-Apr-14.

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

Adam

02-May-14

http://reports.is.ed.ac.uk/alerts/index.cfm?fuseaction=view_alert&alert_id=3954 was published on 24-Apr-2014.

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)

N

Adam

13-May-14

Service mangement to confirm if this has been completed for web pages, and on the internal wiki. Old policies relating to the previous ExchProv will need to be reviewed. (Stephen)