[167] in iswork
Moving toward full production for IS Work
daemon@ATHENA.MIT.EDU (Tim McGovern)
Tue Nov 21 12:58:00 2000
Message-ID: <3A1AB783.9140AAE8@mit.edu>
Date: Tue, 21 Nov 2000 12:57:33 -0500
From: Tim McGovern <tjm@MIT.EDU>
Reply-To: tjm@MIT.EDU
MIME-Version: 1.0
To: kcunning@mit.edu, iswork@mit.edu
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Kevin,
Now that the IS Work database has been in a degree of service for a while, we
should talk about the cutover to formal production status.
I'd like to see this happen in a fairly deliberate and coordinated manner, so I
think it would be useful to sit down and talk about this _before_ it occurs.
In the process of moving the server from Kris' machine to the closet, there are
several outcomes that I want to ensure are met:
1) there should be minimal / no downtime for IS Work as we move to the
production site.
2) there should still be a test environment on Kris' machine that she can
use to continue development and testing feature that are requested by
the ITLT.
Related to the test/production databases, I want to talk about a process
for the migration of new features, etc. between the two.
3) there should be clear lines of authority and responsibility for who
can do what to the database. I particularly want to undertand what
the coverage is for those times when you are not available -- vacations,
business travel, etc.
Of course, there are other issues that might also need some discussion. What's
a good day for you next week?
Thanks,
Tim
