Difference between revisions of "Gourd/Einstein Migration Plan"

From Nuclear Physics Group Documentation Pages
Jump to navigationJump to search
m
m
Line 17: Line 17:
 
#System Setup
 
#System Setup
 
##NFS
 
##NFS
−
##*Set up NFS Shares for /home and /mail '''done - Currently /mail share only accessible by Tomato, need to change to Einstein at switchover'''
+
##*Set up NFS Shares for /home and /mail '''done - Currently /mail share accessible by Tomato, need to change to Einstein at switchover'''
−
##*Create npghome.unh.edu alias interfaces on Gourd
+
##*Create npghome.unh.edu alias interfaces on Gourd '''done'''
 
##**Add to DNS configs '''done - Assigned farm IP of 10.0.0.240'''
 
##**Add to DNS configs '''done - Assigned farm IP of 10.0.0.240'''
−
##**Needs to be added to Servers in LDAP for iptables to work
+
##**Needs to be added to Servers in LDAP for iptables to work '''done on Tomato'''
−
##Change Automount configuration in LDAP (possibly also on clients) to use npghome:/home instead of einstein for /net/home -- '''TEST''' and warn users before switchover
+
##Change Automount configuration in LDAP (possibly also on clients) to use npghome:/home instead of einstein for /net/home '''done on tomato'''
 +
##*Ran into some trouble with this setup on feynman, could login but apps wouldn't run and Gnome would eventually freeze. Tested several possibilities:
 +
##**Setting npghome to Einstein's IP address in hosts file worked
 +
##**Bringing up npghome alias interfaces on Einstein worked
 +
##**On a hunch tried bringing down the firewall on Gourd, and then I could login and mount /net/home to npghome with no issues. Fixed the firewall configuration (ports were set incorrectly, added eth0.2 as the unh interface instead of eth1, and had the iptables script going to tomato's ldap since it contains the entry for npghome which needed to be added to the firewall, and automount to npghome is now working on feynman, parity, gourd, and tomato without issue as of 01/16
 
##Backups
 
##Backups
 
##*Change rsync-backup.conf so that /mail and /home get backed up
 
##*Change rsync-backup.conf so that /mail and /home get backed up
Line 29: Line 33:
 
##**Corn '''done'''
 
##**Corn '''done'''
 
##**Roentgen
 
##**Roentgen
 +
 +
 +
=Einstein VM ( Currently Tomato )=
 +
 +
#VM Setup '''done'''
 +
##Create the Virtual Machine, Install / setup OS '''done'''
 +
##*Tomato is currently a CentOS 5.4 machine running on gourd
 +
##**Ran into issues with rhn since we don't seem to have a spare license to register tomato. We used CentOS so that we could install and update necessary packages and test out the new configuration, but we can set up Tomato with Einstein's license once that is free if needed, and then copy configs over from the current machine.
 +
##*Tomato virtual machine is setup to boot when Gourd boots. Tested this setup and gourd comes up successfully after a reboot. Initial login on gourd is a bit sluggish as you have to wait for tomato to finish booting, but works fine after a few seconds.
 +
#LDAP Configuration '''done'''
 +
##Copied LDAP configuration from Einstein. Have tested authentication with tomato's LDAP on feynman, gluon, parity, gourd, and tomato itself. Seems to work as well as Einstein.
 +
#Firewall setup '''done''' - used old Einstein's iptables-npg config. Probably need to clean up some of the old unused rules, from the old machine, though.
 +
#Mail Setup
 +
##Copy over configs for Dovecot, Postfix, Spamassassin, Mailman and Squirrelmail
 +
##*Need to setup Apache for Squirrelmail. Also /var/www from old einstein for automount. Should websites from Einstein run on the new VM, or move to Roentgen?

Revision as of 17:36, 16 January 2010

This page is for notes on the steps needed in order to fully migrate from the current Einstein system to the new Gourd hardware and Einstein System.

Gourd

Gourd will serve as the file server for home folders and mail, as well as the Virtualization host for Einstein and other Virtual Machines such as Roentgen and Corn

Migration Checklist for Gourd

  1. Drives and RAID
    1. Configure hard drives and RAID arrays as outlined here
      • Copy the 250GB system drive pass-thru disk to a 250GB RAID 1 volume on two 750GB disks (Slots 1 and 2) done
      • Remaining 500GB on each drive spanned to a 1TB RAID 0, mounted on /scratch done
      • Two 750GB disks as pass-thru, set up as software RAID (Slots 3 and 4) done
      • 500GB RAID 1 for home folders (/dev/md0) mounted on /home done
      • 100GB RAID 1 for Einstein's /var/spool/mail (/dev/md1) mounted on /mail done
      • 150GB RAID 1 for virtual machines (/dev/md2) mounted on /vmware and added as a local datastore in VMWare done
      • Two 750GB drives in Slots 7 and 8 as hot spares done
  2. System Setup
    1. NFS
      • Set up NFS Shares for /home and /mail done - Currently /mail share accessible by Tomato, need to change to Einstein at switchover
      • Create npghome.unh.edu alias interfaces on Gourd done
        • Add to DNS configs done - Assigned farm IP of 10.0.0.240
        • Needs to be added to Servers in LDAP for iptables to work done on Tomato
    2. Change Automount configuration in LDAP (possibly also on clients) to use npghome:/home instead of einstein for /net/home done on tomato
      • Ran into some trouble with this setup on feynman, could login but apps wouldn't run and Gnome would eventually freeze. Tested several possibilities:
        • Setting npghome to Einstein's IP address in hosts file worked
        • Bringing up npghome alias interfaces on Einstein worked
        • On a hunch tried bringing down the firewall on Gourd, and then I could login and mount /net/home to npghome with no issues. Fixed the firewall configuration (ports were set incorrectly, added eth0.2 as the unh interface instead of eth1, and had the iptables script going to tomato's ldap since it contains the entry for npghome which needed to be added to the firewall, and automount to npghome is now working on feynman, parity, gourd, and tomato without issue as of 01/16
    3. Backups
      • Change rsync-backup.conf so that /mail and /home get backed up
      • Create new LDAP group for backups so that gourd doesn't get backed up a second time as npghome - change backup script in Lentil to use new group
    4. Virtual Machines
      • Copy virtual machines from Taro to /vmware on gourd
        • Corn done
        • Roentgen


Einstein VM ( Currently Tomato )

  1. VM Setup done
    1. Create the Virtual Machine, Install / setup OS done
      • Tomato is currently a CentOS 5.4 machine running on gourd
        • Ran into issues with rhn since we don't seem to have a spare license to register tomato. We used CentOS so that we could install and update necessary packages and test out the new configuration, but we can set up Tomato with Einstein's license once that is free if needed, and then copy configs over from the current machine.
      • Tomato virtual machine is setup to boot when Gourd boots. Tested this setup and gourd comes up successfully after a reboot. Initial login on gourd is a bit sluggish as you have to wait for tomato to finish booting, but works fine after a few seconds.
  2. LDAP Configuration done
    1. Copied LDAP configuration from Einstein. Have tested authentication with tomato's LDAP on feynman, gluon, parity, gourd, and tomato itself. Seems to work as well as Einstein.
  3. Firewall setup done - used old Einstein's iptables-npg config. Probably need to clean up some of the old unused rules, from the old machine, though.
  4. Mail Setup
    1. Copy over configs for Dovecot, Postfix, Spamassassin, Mailman and Squirrelmail
      • Need to setup Apache for Squirrelmail. Also /var/www from old einstein for automount. Should websites from Einstein run on the new VM, or move to Roentgen?
Retrieved from "https://nuclear.unh.edu/wiki/index.php?title=Gourd/Einstein_Migration_Plan&oldid=4833"