[187] in iswork
Moving toward "service" status...
daemon@ATHENA.MIT.EDU (Tim McGovern)
Fri Dec 1 10:58:50 2000
Message-ID: <3A27C914.65E3BEC5@mit.edu>
Date: Fri, 01 Dec 2000 10:51:48 -0500
From: Tim McGovern <tjm@MIT.EDU>
MIME-Version: 1.0
To: rferrara@mit.edu, iswork@mit.edu
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Bob,
Yesterday, Kevin, Kris and I met to discuss and plan the steps needed to
move IS Work into full production/service status. Here are the results
of that conversation.
We are moving ahead with the intention of announcing the move of IS Work
to full service status on Dec. 15, or earlier if at all possible.
The situation right now is that the Filemaker databases that support IS
Work already reside on train.mit.edu, which is the FM db server that is
maintained by Kevin. [Kevin is considering renaming train.mit.edu to
isdbs.mit.edu, to reflect the expansion of its role in our work.] The
IS Work web pages which point to those databases exist on Kris's desktop
fiji.mit.edu.
We will be taking the following steps between now and the 15th.
* Install Timbuktu remote access software on Kris' desktop(s) so that
she can access and modify HTML pages on train.mit.edu.
* Freeze the HTML pages on fiji.mit.edu, and transfer pages to
training.mit.edu.
[training.mit.edu is NOT the same as train.mit.edu. The former is the
home of web pages which undergird a variety of Support functions,
including training, product support sheets, etc. train.mit.edu is
configured as an FMPro Database Server.]
* Test access to IS Work via the HTML pages when located on
training.mit.edu.
* Document recovery procedures for IS Work in the event of system
failure.
* Redirect the cname iswork.mit.edu, which currently points to
fiji.mit.edu, to point to training.mit.edu
* Announce the change in phase into service to ITLT. The change should
be invisible, but notification is important should there be any hiccups
in the service. No general announcement is warranted at this time.
We talked about how service issues will be handled after the change. We
reached several conclusions.
* Kris is modifying the HTML pages now so that feedback or responses
from the IS Work pages themselves will be directed to the mailing list
is-home@mit.edu, the triage point for the entire collection of IS
related web pages. The team that handles is-home will ensure that any
iswork questions are forwarded to the iswork@mit.edu mailing list for
resolution.
* Kevin is the point person for a set of databases that exist on
machines in the N42 server closet. Tim Griffin of the Help Desk is also
a key person for the Casetracker databases that exist there. There are
a small number of individuals in N42 -- Kevin, Tim, Rob, and soon Kris
-- with "keys" to the closet. Together, they will be responsible for
handling system failures that relate to IS Work. System failures can be
reported to is-home or to iswork@mit.edu.
* The database machine in the N42 closet is already subscribed to ADSM,
and is backed up nightly.
* The machines in the closet are on UPS devices which should help in
temporary power loss situations, but there are no provisions for
redundancy on the server or database machines.
Please let us know as soon as possible if you have other questions about
this change, or if there are additional service entry requirements that
you feel need to be addressed.
Thanks,
Tim -- writing on behalf of Kris and Kevin
