Deployment

API DEPLOYMENT CHECKLIST

 

 

Application checklist

 

Component

Success Criteria

OK (Y/N) Reviewed by (date) Outstanding Actions (Who)

Implementation Plan and Rollback plan

Implementation plan is documented including risk assessment and rollback process

Y AG 14/05/19  

Combined System Description/System Design wiki page

Document complete and accurate in the Wiki

see: https://www.wiki.ed.ac.uk/display/insite/eFin+to+myProject+Feed+System+Description+Document

Y AG 14/05/19  

Source Code

Source code has been secured in GIT and merged with Production branch

https://gitlab.is.ed.ac.uk/isapps-software/projectbalances-ms 

https://www.bamboo.is.ed.ac.uk/browse/MS-PROJ

Y AG 14/05/19  
Configuration Management Database

Urls are created and link to infrastructure in CMDB in Unidesk

Y AG 14/05/19 TO BE DONE

Change Control

Change  record  has been created in Unidesk for the LIVE implementation.

 Action: record unidesk number - C1904-108

Y AG 14/05/19 C1904-108

Jiras outstanding

A review of all outstanding Jiras has taken place to ensure all required actions have been completed.

Y AG 14/05/19 9 outstanding to be reviewed again

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

  AG 14/05/19 to be arranged

Deployment Date

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

Y AG 14/05/19 14th-22nd May 2019
Add new API to API registry

Check if new API has been added to API Registry otherwise check with Service Management

Y AG 14/05/19 Passed to Susan Cooke by AW 14/05/19
         
         
         
         
         
         
         
         
         
         
         
         
         
         
         
         
         
         

 

Infrastructure checklist

 

Component

Success Criteria

OK (Y/N) Reviewed by (date) Outdstanding Actions (Who)

Technical Architecture/Operational Document(TAD)

Documentation complete and accurately. Mico

Action: Uploaded to  sharepoint see:

https://uoe.sharepoint.com/sites/disasterrecoveryplans/Shared%20Documents/Forms/AllItems.aspx?FolderCTID=0x012000296452A078E6C54AB4AAFB4B08464F0F&id=%2Fsites%2Fdisasterrecoveryplans%2FShared%20Documents%2FSystem%20Documentation%2FInfrastructure%2FMicroservices

 

     

Stop/Start scripts

Application Start-up/Shutdown scripts are in place including start-up procedure documented, enabled and tested

     
Default Deny

Default deny has been enabled as outlined in the policy:

https://www.wiki.ed.ac.uk/display/insite/Default+Deny+Policy

Any exceptions must be noted in the TAD and signed off by Head of Production Services.

     

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)

     
         
       
         
         
         
         
         
       

 

Project Info

Project
Estates EPPM Implementation (EST103)
Code
EST103
Programme
Estates Capital System (EPPM)
Management Office
ISG PMO
Project Manager
Shirley Blyth
Project Sponsor
Jane Johnston
Current Stage
Execute
Status
In Progress
Project Classification
Transform
Start Date
13-Jun-2017
Planning Date
15-Nov-2018
Delivery Date
13-Jun-2019
Close Date
15-Nov-2019
Programme Priority
2
Overall Priority
Highest
Category
Discretionary