About mike.neir.org

I started this site when I was a freshman at Michigan State, in late 1997. It’s changed a whole lot from then to now. I used to think that I could make a page about me that would be really cool and that people would just visit, but that delusion faded quickly. Now mostly I just keep the site up to disseminate various news items to friends and family, and to make note of cool things I’ve done with technology. I’ve learned a lot of various web stuff from the whole process… Stuff like HTML and PHP coding, database/website interaction, and web server administration. I run the site from my own server setup. Information on it is included below.For those of you who are curious, I have coded everything on the site (for better or worse) except the following things…

The Servers

For what it does, my server setup is total overkill. In my defense, it does more than just host my site. It also hosts sites for a few friends and family members, stores backups of things I hold dear, and serves as a testbed for things I deem cool.

I’m a strong believer in virtualization, and my method of choice is Xen. I have two servers used as dedicated Xen nodes, with a third server providing filesystem storage for the Xen child instances (domUs). I export the filesystems off the storage server using ATA over Ethernet (AoE). Having the domU filesystems stored in a central location allows me to use one of the more impressive features of Xen – hot migration of domUs. In the event that I want to take down a Xen node, I can migrate the domUs running in that node to another node with only a few milliseconds of downtime and no loss of system state. Very cool.

I have domUs dedicated to the various roles my setup performs (HTTP, MySQL, mail, Jabber, DNS, Shoutcast, etc.) for better resource allocation and security. For instance, I give larger memory footprints to services like MySQL and Apache, but less resource intensive things like DNS and jabber servers get domUs with a much smaller memory footprint. I can also put the less CPU-intensive services on slower machines and/or allocate less CPU time to them, while the more intensive services can run on the better hardware. Segregating various services can also help keep an intrusion limited to a particular domU should one occur.

 

ariel
Role: Xen Node
Model: HP/Compaq DL580 G2
Processors: 4x Xeon 3.0Ghz with 512KB L2 cache and 4MB L3 Cache
Memory: 10GB PC-1600 ECC/REG
Storage: 2x18GB SCSI in RAID1
Onboard HP/Compaq SmartArray RAID controller
Network: 4x 100Mbit ethernet
1x 1000Mbit ethernet
Operating System: CentOS 5
umbriel
Role: Xen Node
Model: HP/Compaq DL580 G2
Processors: 4x Xeon 3.0Ghz with 512KB L2 cache and 4MB L3 cache
Memory: 10GB PC-1600 ECC/REG
Storage: 2x18GB SCSI in RAID1
Onboard HP/Compaq SmartArray RAID controller
Network: 4x 100Mbit ethernet
1x 1000Mbit ethernet
Operating System: CentOS 5
atlas
Role: Storage Server
Model: Compaq DL380
Processors: 2x Pentium III 1400Mhz with 512KB L2 cache
Memory: 1GB PC133 ECC/REG
Storage: 2x18GB SCSI in RAID1 (OS)
30x36GB SCSI in RAID6 + 2 hot spares (Data)
Compaq SmartArray 5304 RAID controller with 128MB battery backed cache
2x Compaq StorageWorks 4314R SCSI RAID cabinets
Network: 2x 100Mbit ethernet
2x 1000Mbit ethernet
Operating System: CentOS 5
atlas + RAID Cabinets -  December 10, 2007

Leave a Comment


NOTE - You can use these HTML tags and attributes:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>