Einstein Status

From Nuclear Physics Group Documentation Pages
Revision as of 17:24, 10 June 2008 by Minuti (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 - UNH: Done (VLAN)! Farm: Done!
    2. Iptables - Not working.
    3. DNS - Done!
    4. LDAP - Done!
    5. Postfix
    6. AMaViS
    7. ClamAV
    8. SpamAssassin
    9. Dovecot
    10. /home - Done!
    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? - This will be handled by roentgen.
    13. Fortran compilers and things like that? (Also needs compat libs) - Isn't this what pumpkin is for?
  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, sdb1, and sdc1. /var/spool/imap (can be changed to match our dovecot configuration) is /dev/md1, which is a 3-way mirror comprised of sda2, sdb2, and sdc2. /home is a 2-way mirror of sdb3 and sdc3. sda3 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 mail and /home, since they're (some of) the most important things. Two 750gb's were added, and RHEL5 was reinstalled without a hitch. 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/mail and 2 elements for home. This will allow us to put the drives in any other system if need be.