[Hosting] Fatalpha proposal

[Jon Carnes]

John speaks wisdom.  And it is quite easy to move an IP address to another
server so that services transfer to the new server all at once.

-----Original Message-----
From: hosting-admin@trilug.org [mailto:hosting-admin@trilug.org]On
Behalf Of John Beimler
Sent: Wednesday, August 07, 2002 7:04 PM
To: hosting@trilug.org
Subject: Re: [Hosting] Fatalpha proposal


I've been through quite a few OS upgrades and application migration
work, I'd suggest moving the services you plan on moving to the new
servers, get them stable, then start the work on fatalpha.  Since a lot
of stuff is moving around anyhow, move it now, I understand that
patching fatalpha seems like extra work (I volunteer to help) its better
than the downtime that will most likely occur from doing too much at
once.

Peace.

john

On Wed, 2002-08-07 at 17:49, Tanner Lovelace wrote:
> Hi folks,
>
> I've been thinking about the role of fatalpha now that we have the new
> machines.  Fatalpha is currently running redhat 6.2 which has worked
> great.  However, it would be much nicer if we could get it running
> a 7.x version of redhat instead. Many of the things we're doing
> (i.e. ldap, kerberos, logical volume management, etc...) apparently
> work right out of the box in 7.x and need a bit of fiddling with
> on 6.x.  So, what I'd like to propose is doing the following:
>
> 1. Temporarily copy all the home directories over to a partion
>    on dargo.  This can either be a directory on the large drive
>    array, or I can create a actual partition using the LVM tools.
> 2. Back up all the configuration information (i.e. dns stuff,
>    firewall settings, scripts, web settings, etc...
> 3. Move any mysql databases over to dargo.  I believe the only
>    one we have right now is the membership database.
> 4. Save anything else we need to save (what have I forgotten?)
> 5. Bring down fatalpha and install 7.x (whatever the latest
>    "x" is), wiping all the drives in the process.
> 6. Setup the disks that previously held the mirrors using
>    LVM and place /home there.
> 7. Copy the saved /home on dargo back to fatalpha.
> 8. Move mysql/web/etc... back to fatalpha.
>
> What do people think about that?  Looking over fatalpha,
> we could actually back up all of fatalpha on dargo (the
> largest thing on fatalpha is the mirrors and they've already
> been moved) so we make sure we don't lose anything.
>
> We would basically end up with fatalpha being
>
> 1. The shell server
> 2. The web server
> 3. The mysql server
> 4. The dns server
>
> Dargo would be the
>
> 1. Mirror server (ftp and http)
>
> And moya would be
>
> 1. kerberos/ldap server
> 2. e-mail server
> 3. mailing list server
> 4. imap server
>
> What services have I forgotten?  Is there any reason we shouldn't
> do this?  Note that I'm not envisioning doing this right now.
> I want to get moya and dargo up and running first.  The earliest
> I would consider doing this is sometime next week, and it would
> probably be after that.
>
> Thoughts?
>
> Thanks,
> Tanner
> --
> Tanner Lovelace | lovelace@opennms.org | http://www.opennms.org/
> --*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--
> GPG Fingerprint = AFD2 597F 4028 FFE2 B11A  4383 BE46 B4E1 26DC 03A3
> --*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--
> "What is this talk of "release?"  We do not make software "releases."
> Our software "escapes" leaving a bloody trail of designers and quality
> assurance people in its wake." - MoncriefJM@gvl.esys.com
>
> _______________________________________________
> Hosting mailing list
> Hosting@trilug.org
> http://www.trilug.org/mailman/listinfo/hosting

_______________________________________________
Hosting mailing list
Hosting@trilug.org
http://www.trilug.org/mailman/listinfo/hosting