From Nuclear Physics Group Documentation Pages
Revision as of 15:20, 12 January 2008 by Maurik (talk | contribs)
Jump to navigationJump to search


Pumpkin is our new 8 CPU 24 disk monster machine. It is really, really nice. Currently it is only tied to the "corn" ip address. Because of this, it seems like we're going to have Corn be the big physical machine, and pumpkin be the virtualized machine.

Basic Setup

  • We will run Xen on this so that it can have 2 personalies: Pumpkin, 64-bit, and Corn, 32-bit, RHEL5.
    • Xen documentation of questionable quality.
    • In order to do this right, Pumpkin should be the host, since you can't virtualize 64-bit under 32-bit, but you can do the other way around. See the bottom of [1].
    • These may come in handy: [2] and [3]
  • The RAID is currently split. This allows for much easier maintenance and in the future possible upgrades.
    • Disk 1 to 11 is in RAID Set 0, which holds the RAID Volumes: System (300GB, RAID6, SCSI:0.0.0), System1(300GB, RAID6, SCSI:0.0.1), Data1 (6833GB, RAID5, SCSI:0.0.2)
    • Disk 11 to 22 is RAID Set 1, which holds the RAID Volume: Data2 (7499GB, RAID5, SCSI:0.0.3)
    • Disk 23 and 24 are passthrough (single disks) at SCSI:0.0.6 and SCSI:0.0.7. These can be used as spares, as backup, or to expand the other RAID sets later on. Currently they are seen as /dev/sde* and /dev/sdf*. /dev/sdf1 and /dev/sdf2 hold the old RHEL4 install the system came with.
    • The RAID card can be monitored at login as "admin" with a password that is the same as the door combo.
    • To use this card with Linux you need a driver: arcmsr. This must be part of the initrd for the kernel, else you cannot boot from the RAID. You can also install from the CDs, if you have a driver floppy. It will then add the arcmsr driver into the initrd for you. You will still always need to have this driver!
      • The kernel module can be build from the sources located in /usr/src/kernels/Acera_RAID. Just run make.
  • There exists a temporary drive which holds a RHEL5 distro and the original RHEL4 distro from the manufacturer. It is currently disconnected from pumpkin.

To Do

  • Setup the other system with Xen on the System1 drive. Done. It just needs RHN-enabled, except that we're out of entitlements. Since we're getting a new benfranklin at some point, can we remove benfranklin's entitlement? The new one can be CentOS. Actually, not quit done yet. It needs a farm ethernet connection. Corn isn't currently working, after having changed the CPUs and memory as it was running.
  • Setup SNMP for cacti monitoring.
  • Add the new systems to the lentil backup script
  • There must be other things....
  • Setup sensors so that we can monitor the system. Will have to wait for a kernel that supports it


  • Setup ethernet.
  • Setup RAID volumes.
  • Setup partitions and create file systems.
  • Move the system to System drive and remove the current temp drive.
  • Setup mount points for the data drives.
  • Setup LDAP for users to log in.
  • Setup Exports, so other systems can see the drives. There were issues with firewall, so I modeled the firewall after taro's. Seems to be working, I can successfully ls /net/data/pumpkin1 and ls /net/data/pumpkin2 on einstein.
  • Setup autofs so that it can see other drives. What other drives? It's working for einstein:/home Other drives such as data drives
  • Setup smartd so we will know when a disk is going bad. This can be done inside the RAID card using a system to send SNMP and EMAIL. but it needs to be done. E-mail seems to be set up, let's see if we get any through npg-admins
  • Restrict access (/etc/security/access.conf)
  • Setup sudo on both pumpkin and corn.