If there is an automated process to merge a test integration into a prodcution site, I’m unaware of it and would be interested, too.
In the mean time, I’ve created a checklist of manual steps that has evolved over many years.
The checklist has some specifics to MD Anderson but you may find it a useful start, but I will not be a part of explaining it because it is written for a person with a certain level of understanding so they don’t forget anything or get it out of order.
The document is not intended to hand it to an inexperienced person and have them make sense out of it.
The jest of what is in our migration checklist is that we make a new site that is a copy of the current prodcution site, for example
cd /sites/5.2.1P2/p_g_adt_out
mkdir v04_2006.12.06
tar _tar_dir v03_2006.11.17 v04_2006.12.06
#!/usr/bin/ksh
# Begin Module Header ==============================================================================
#
#——
# Name:
#——
#
# tar_tar_dir
#
#———
# Purpose:
#———
#
# Copy an entire directory tree with all files and links to another base directory
# using the tar command
#
# Notes:
#——-
#
# This script is nice because it pipes the output of one tar command to another,
# which requires a little bit of temporary memory.
#
# Example of normal usage:
#
# cd $HCIROOT
# tar_tar_dir ./test_picis /3.5.2P_picis
#
#———
# History:
#———
#
# 1999.10.29 Russ Ross
# – wrote initial version
#
# End of Module Header =============================================================================
(cd $1 && tar -cf – .) | (cd $2 && tar -xBf -)
cd $HCIROOT
ln -s /sites/5.2.1P2/p_g_adt_out/v04_2006.12.06 p_g_adt_out_new
Then we prep the new site, and take our time to modify it to our satisfaction.
Once satisfied we make the switch over by
– shuttidng down the current site
– pointing the link for the current production site to the new version
– start site back up
If we have problems and have to back out then we can do so quickly with 100% confidence by pointing the link back to the previous site version which has never been changed.
Using this method, the downtime is acceptable; my last switch over resulted in 16 minutes of downtime of the impacted prodcution interfaces.
By the way, having multiple sites with a limited number of threads in it will also reduce the impact of any changes.
As simple and safe as these basic overview steps are you will need a comprehensive checklist to make sure nothing is missed and everything is done in the proper order.
I’m sorry to say that I tried to upload my word document checklist that I use but finally gave up trying due to failure.
You did not provide an email address in your profile so I will not be sending you a copy.
Russ Ross
RussRoss318@gmail.com
.
