[1615] in SIPB-AFS-requests
Re: Cutover plans
daemon@ATHENA.MIT.EDU (Derek Atkins)
Wed Nov 16 01:58:30 1994
To: yandros@MIT.EDU
Cc: warlord@MIT.EDU, ghudson@MIT.EDU, mhbraun@MIT.EDU, sipb-afsreq@MIT.EDU
In-Reply-To: Your message of "Tue, 15 Nov 1994 22:45:52 +0500."
<9411160345.AA14523@infocalypse.MIT.EDU>
Date: Wed, 16 Nov 1994 01:55:31 EST
From: Derek Atkins <warlord@MIT.EDU>
> The vldb keeps entries by IP address. When ronald-ann moves from
> 18.70 to 18.181 it will require us to rebuild the vldb, and coordinate
> with IS to get the CellServDB.
>
> If we bring up one of the `extra' machines as basselope, make it an
> AFS server in the SIPB cell, and move all the volumes there, why do we
> need to rebuild the VLDB? Doesn't the VLDB get updated automatically
> when I `vos move project.outland rosebud a basselope a -cell sipb -verbose'?
Chad -- re-read what I said. I said "when ronald-ann is moved from
18.70 to 18.181 (which will just entail unplugging it from one delni
and plugging it into another), the vldb will need to be rebuilt".
There are three migrations that need to happen. The first is moving
rosebud to a decstation, the second is moving the decstation-rosebud
to 18.181, and the third is moving ronald-ann to 18.181. I am saying
that we can do the first two steps together, but the third will
require a vldb rebuild.
My proposal is to do steps one and two ASAP, since it requires no
syncing with anyone in IS. Step three is when we will need to get
help from IS to coordinate name changes and CelServDB updates, but
that can wait.
As for when this happens, it can happen in real time at any time,
since there is no downtime for any server. This migration could be
done in the middle of the day! I assume that the 4gb disk is the one
that is means for AFS space? If so, then we probably do want to wait
for that to arrive, since the rosebud migration is really the only one
that will require moving volumes around.
-derek
