HARDWARE ALLOCATION
– The server machine will be an Athlon64 x2 4000+ (socket AM2)
– The server machine will have 3gigs DDR2 ram
– It will have a RAID5 array (4 drives x250gig SATA)
—– The RAID5 array is a large XFS partition.
– It will have one OS drive (120gig, PATA)
—– The OS drive will be partitioned using LVM.
—– The LVM drive will be broken up into two ‘Volume Groups’
——— Volume Group one will be called “system” and will be dedicated to the dom0 OS files, a swap partition, and a /tmp. (7GB, 1GB, 5GB)
——— Volume Group two will be called “VM” and will be broken up into small partitions for the VMs being hosted.
——— The structure of the VM LVM partitioning: one LVM partition for swap (512MB), one for / (5-10gig) , and one for /tmp (3-5gig)
– It will have one external USB hard drive (250 gig) for external backup purposes
– There will be one Hauppauge WinTV tuner card which will be shared by dom0
– There will be one Hauppauge PVR250 tuner card which will be shared by dom0

DOM0 Setup
– Dom0 will get a 5gig partition on the LVM system for the /, 512MB for swap and 2gigs for /tmp
– Dom0 will get 384MB of ram.
—– All it has to do is serve NFS and Samba shares, and allow for management of virtual machines. A NXserver will be running to allow for a GUI into the machine.
– IP Address: 192.168.0.3 , server03
– It will pass-through the tuner cards for other domains to use.
– Will have only a bare (console only) OpenSuSE 10.3 install.
– On that will be installed NXServer, blackbox WM, and a bare minimum X server
– dom0 FOLDER STRUCTURE
—– The RAID5 array will be called /data, and the downloads partition will be /downloads
– dom 0 will be an NFS and Samba server
—– NFS will be serving the /data and /downloads folders
—– Samba will be serving /downloads, /multimedia, /work

– Run CronJobs to backup specific parts of the RAID5 array (as it’s currently done)
– Add to cronjobs a weekly backup of the VM machines.
– Run Webmin to manage certain things remotely, and setup email updates if there are problems.

VIRTUAL MACHINES
MythTV backend (Running all the time)
– Running OpenSuSE 10.3
– One CPU. Try to scale back the amount of CPU used, since not much performance is needed.
– 384MB of ram? should be enough
– VNCserver should suffice for connection.
– IP Address: 192.168.0.21 , mythtv-backend01 (undecided)

Application server (Running all the time)
– Running OpenSuse 10.3 (to replace the desktop workstation and allow laptop to run beefy applications to run)
– Two CPUs. Try to allocate as much CPU power as possible, since some power hungry apps will be running here.
– 1.25 gigs ram should be plenty
– Run NX server for connection. Tested opengl applications and they ran very well.
– It will be nice to run applications on the same hardware as where the files are residing, eliminating the bottleneck of file transfer.
– IP Address: 192.168.0.4 app-server (undecided)

WinXP installation (Running only when something win related is required)
– To run 3D CAD, or other win specific apps that wine can’t run in linux. This has been tested, and even OpenGL apps run acceptably fast over RDP.
– One CPU? should be enough? 3D Cad will be limited by the speed of RDP display export.
– 1 gig ram
– Display will be exported through RDP for main use. (install VNC for management, when RDP fails?)
– RDP data will be exported out of the actual server physical machine by NXserver running on dom0. This should theoretically improve the speed of the RDP connection (or so the nxmachine site claims)
– IP Address: 192.168.0.xxx (undecided)

Web Services Server (Running all the time
– Running OpenSuse 10.3 with only text console)
– One CPU, with minimal usage.
– 384MB of ram? should be enough
– Run a LAMP server with SSL capabilities (https)
– FTP server, HTTP server, and other web services
– IP Address: 192.168.0.10