Вы находитесь на странице: 1из 7

Change/Release Details Form

4Vendor/Partner Change Requestor Vendor Approver Current Date ANB Systems ONCOR Raja Srinivasan 11-09-2011 Reference Name/Release Num. Status Date to be implemented Date Completed

EEPM11092011V2.15.91
To be Delivered in UAT 11-09-2011 11-09-2011

Required Information for change Fields Summary of change Business Impact - impact to the business, how this change effects the business, chgs to frontend or user interface etc Technical Impact - impact of systems, what is chging in the backend systems Hardware affected/associated- list of servers/machine names Software affected/associated such as specific database names and/or tables, applications effected Planned Implementer who is expected to perform chg Level of expertise for chg/implementation such as DBA, DB script, .net app chg, netwk chg, firewall chg, sharepoint chg: web parts Specific Instructions for applying change detailed step by step deployment instructions Change Verification Process details of how/what to verify, attach additional doc is necessary Change Reviewer/Verifier- Person that verified chg in test sys prior to prod imp, written client approval prior to prod chg Integrity of Systems will chg effect data directly or indirectly Identified Risks Mitigation of Risks Testing Methodology how chg was tested and results Testing performed by Backout Plan/Removal of Change detailed instructions on how to remove chg in the event of errors Development Contact if problem arises during deployment the chg implementer must be able to request additional information for the deployment and/or a new code package/patch/release Expected Outage any expected downtime expected in any systems or client outage Production Change Reviewer/Development team Verifier Business Owner Signoff Additional Details
Please review the release file attached Dev Team & Joe Nixon Details below .Net Code, DB Changes

Details Required
Please refer to the release file attached .Net Code, DB Changes

Code, DB Changes

ANB Team in QA, ECP in Production & UAT System admin with access to copying files from one environment to another. DBA for running DB scripts and for backing up and restoring databases. Deploy InfoPath forms

Details below

Please review the release file attached

Joe Nixon, ONCOR

Indirectly None

Raja Srinivasan, 610-952-8139

No outage is required. Raja Srinivasan, 610-952-8139

FILENAME: Change Request Release Form11092011V2 15 91 TEMPLATE VERSION 2.0

PAGE 2 OF 7 PRINTED ON: 11/11/2011 12:06 PM

Change/Release Details Form 1. Software Release Notes


Name of Releaser Release Version Mode of Delivery Release type (Change Request/Both) Amar Anne 2.15.91 File upload NA

Environment Information (QA-Staging, QA-Production, UAT-Staging, UAT-Production, Training, Production-Staging, Production-Test, Production) Change Management Folder

UAT 10.111.110.20/CYONAPU01 Production -10.111.110.140/CYONAPP01, 10.111.110.141/CYONAPP02

10.111.110.21 D:\change management

2. Environments to be released in Environment QA Staging QA Production UAT Staging UAT Production Training Staging Training Production Production Staging Production Test Production 3. CC Release Package Details Planned Release Date Completed Date

11-09-2011 11-09-2011

Change Request Release Form11092011V2 15 91.xls

4. Pre-Deployment Instruction Create the subfolder with the release number under the instance being updated, as per the instruction below in the folder setup instructions. (ANB Team will do this). 5. Maintenance Message QA Staging Training Staging Production In IIS Manager, go to the Production .Net server 10.111.110.140 and change the default content page to the maintenance.aspx page by selecting and moving it up in the list. Do the same in the second server 10.111.110.141. QA Production Training Production UAT Staging Production Staging UAT Production Production Test

FILENAME: Change Request Release Form11092011V2 15 91 TEMPLATE VERSION 2.0

PAGE 3 OF 7 PRINTED ON: 11/11/2011 12:06 PM

Change/Release Details Form

6. Backup Instructions QA Staging Training Staging Production Backup the database to the already setup folder related to the instance being updated. The database name and location are provided in the database matrix. The DB backups are about 15 GB. QA Production Training Production UAT Staging Production Staging UAT Production Production Test

QA Staging Training Staging Production

QA Production Training Production

UAT Staging Production Staging

UAT Production Production Test

Backup the code to the already setup folder related to the instance being updated. The code to be backed up and the location to obtain it from are provided below in the file location matrix. The code is about 90 MB. For production instances, there are 2 servers, 140 and 141 so the backup needs to be done for both servers.

FILENAME: Change Request Release Form11092011V2 15 91 TEMPLATE VERSION 2.0

PAGE 4 OF 7 PRINTED ON: 11/11/2011 12:06 PM

Change/Release Details Form 7. Database Synch Instructions QA Staging Training Staging Production Kindly run the SharePoint script after DB Synch QA Production Training Production UAT Staging Production Staging UAT Production Production Test

8. DB Sync Script: QA Staging Training Staging Production QA Production Training Production UAT Staging Production Staging UAT Production Production Test

9. .Net Code / File Deployment Instructions QA Staging Training Staging Production Copy over the .Net code from the change management folder to the instances code location. Refer to the file location section down below for location of the code in each of the instances. Replace all files. QA Production Training Production UAT Staging Production Staging UAT Production Production Test

10. Database Code Deployment Instructions QA Staging Training Staging Production Connect to the database being updated, the details are provided in the database matrix. Run the DB Scripts pertaining to the instance being upgraded, the script file will be present in the change management folder, under the release number folder for the instance being updated.
DBScript.sql

QA Production Training Production

UAT Staging Production Staging

UAT Production Production Test

11. Rollback Procedures QA Staging Training Staging Production QA Production Training Production UAT Staging Production Staging UAT Production Production Test

FILENAME: Change Request Release Form11092011V2 15 91 TEMPLATE VERSION 2.0

PAGE 5 OF 7 PRINTED ON: 11/11/2011 12:06 PM

Change/Release Details Form The code backup can be restored by copying the files over from the backup done in step 4 of this instruction.

12. Testing Procedures (the business analyst to provide this in the testing sheet of the excel workbook) QA Staging Training Staging Production QA Production Training Production UAT Staging Production Staging UAT Production Production Test

Please refer to the excel workbook for testing instructions. 13. Final Steps QA Staging Training Staging Production Move the maintenance page down and put the default page back. This is basically reversing the pre-deployment instruction. QA Production Training Production UAT Staging Production Staging UAT Production Production Test

FILENAME: Change Request Release Form11092011V2 15 91 TEMPLATE VERSION 2.0

PAGE 6 OF 7 PRINTED ON: 11/11/2011 12:06 PM

Change/Release Details Form

General Instructions

Folder Setup Instructions (one time setup are NOT bolded) Currently setup on 10.111.110.21
1. Create a change management folder in a common drive which is accessible to the change management lead from the development team and EC Power. 2. This folder should have a folder for each of the application instances. 3. Under each of these instances we should create a folder with the release number every time a release is being made. 4. The release number folder will have 2 folders one for the backup and one for the code being rolled out. 5. The change release document and the excel sheet should be placed in the root of the release folder. 6. We can have a DB backup folder and a Code backup folder under the backup folder. An archival strategy should be determined for this folder so we dont let this grow uncontrolled. Sample Folder Structure

Database Matrix
INSTANCE NAME QA STAGING QA PRODUCTION UAT STAGING UAT PRODUCTION TRAINING STAGING TRAINING PRODUCTION PRODUCTION STAGING PRODUCTION TEST PRODUCTION
FILENAME: Change Request Release Form11092011V2 15 91 TEMPLATE VERSION 2.0

IP ADDRESS 10.111.10.21 10.111.10.21 10.111.10.20 10.111.10.20 10.111.10.20 10.111.10.20 10.111.10.146 10.111.10.146 10.111.10.146

DATABASE NAME Staging_qa oncor_eepm_qa Staging_oncor_uat Oncor_uat straining_uat training_uat Staging_oncor_prod Staging_prod Oncor_prod

SQL login user used by app savant savant Oncor Oncor Oncor Oncor eepmprod eepmprod eepmprod
PAGE 7 OF 7 PRINTED ON: 11/11/2011 12:06 PM

Change/Release Details Form

File Location Matrix


INSTANCE NAME QA STAGING QA PRODUCTION UAT STAGING UAT PRODUCTION TRAINING STAGING TRAINING PRODUCTION PRODUCTION STAGING Server 1 PRODUCTION TEST Server 1 PRODUCTION Server 1 PRODUCTION STAGING Server 2 PRODUCTION TEST Server 2 PRODUCTION Server 2 IP ADDRESS 10.111.110.21 10.111.110.21 10.111.110.20 10.111.110.20 10.111.110.20 10.111.110.20 10.111.110.140 10.111.110.140 10.111.110.140 10.111.110.141 10.111.110.141 10.111.110.141 SOURCE FOLDER NAME C:\Inetpub\wwwroot\QA\Staging C:\Inetpub\wwwroot\QA\Production C:\Inetpub\wwwroot\UAT\Staging C:\Inetpub\wwwroot\UAT\Production C:\Inetpub\wwwroot\UAT_Training\Staging C:\Inetpub\wwwroot\UAT_Training\Production C:\Inetpub\wwwroot\ONOCR_EEPM\Staging C:\Inetpub\wwwroot\ONOCR_EEPM\Production_Test C:\Inetpub\wwwroot\ONOCR_EEPM\Production C:\Inetpub\wwwroot\ONOCR_EEPM\Staging C:\Inetpub\wwwroot\ONOCR_EEPM\Production_Test C:\Inetpub\wwwroot\ONOCR_EEPM\Production

FILENAME: Change Request Release Form11092011V2 15 91 TEMPLATE VERSION 2.0

PAGE 8 OF 7 PRINTED ON: 11/11/2011 12:06 PM

Вам также может понравиться