Einstein Status

From Nuclear Physics Group Documentation Pages
Revision as of 15:14, 9 June 2008 by Steve (talk | contribs)
Jump to navigationJump to search

Massive amount of deployment documentation for RHEL 5

  1. Check all services einstein currently provides. Locate as many custom scripts, etc. as is reasonable and label/copy them.
    1. Network interfaces.
    2. Iptables
    3. DNS - Done.
    4. LDAP
    5. Postfix
    6. AMaViS
    7. ClamAV
    8. SpamAssassin
    9. Dovecot
    10. /home
    11. Samba If anyone needs samba access, they need to find us and have us make them a samba account. No LDAP integration.
    12. Web?
    13. Fortran compilers and things like that? (Also needs compat libs)
  2. Switch einstein <-> tomato, and then upgrade what was originally einstein
  3. Look into making an einstein, tomato failsafe setup.

Current setup on einstein2

/ is /dev/md0, which is a 3-way mirror comprised of sda1, sdb2, and sdc1. /home is a 2-way mirror of sdb2 and sdc2. sda2 is the swap partition. The reason it is set up this way is that the system came installed on a 250gb, and Matt wanted redundancy and space for /home, since it's (one of) the most important things. Two 750gb's were added, root was expanded to take up most of the original drive, thus dictating the size of root on the two new drives. Home was then made using the remaining space, giving PLENTY for anyone here. Grub should currently be installed on all three drives, so that if any one (or two!) drives fails, the system can still boot and run. The RAID setup is standard software raid1 using 3 elements for root and 2 elements for home. This will allow us to put the drives in any other system if need be.