[OpenAFS] Creating a partial sandbox of the production Cell & krb5 realm

Troy Benjegerdes hozer@hozed.org
Sun, 11 Nov 2012 18:18:41 -0600

> > I would appreciate any other tips that anyone has.
> > 
> > BTW, I proposed using a differently/named test cell/realm and was shot down.
> > 
> > Sincerely,
> > Jason


> Taking the other tack,
> I've never tried this, but think it might be interesting:
> set up a virtual environment where *everything* is the same
> as your production environment.  ip addresses, cell & realm names,
> file structure, everything.  The advantage of this is you can clone
> things from your production environment to testing - and to a lesser
> extent you could also go backwards.  The disadvantage of this is of
> course you're going to have to duplicate everything in a
> carefully confined piece of network space.

This sounds like a good way to blow away the production system by 
accidentally typing in the wrong window.

If this is going to be a sane test, I'd suggest one of the following:

1) a second entire mouse/keyboard/machine with a 'TEST SYSTEM' sticky
note plastered on the monitor, and an entire duplicate virtual isolated
network, with no wires connected to the production system


2) create instructions for whomever shot down the different named realm
idea, and have them test it, since it's obviously critical for them that
they need the same name, and you need to make sure it works *for them*.
The idea is to make it their problem if it blows up. Your mileage may 
vary on this scheme.