Otaking 2.0

From otaking wiki

(Difference between revisions)

Current revision

Plans for otaking 2.0

1 Hardware
2 Software
- 2.1 Main Goal
- 2.2 Fallback
3 Concept
4 Virtual Machines
- 4.1 Additional services
- 4.2 Storage
5 VMware tweaks
6 VMware discussion forum
- 6.1 Interesting topics
7 Links
- 7.1 VMware
- 7.2 Tom's Hardware

Hardware

Hardware plans have changed yet again, and it's close to being final. This time the focus is on relatively low power consumption.

[edit]

Pre-existing hardware

I have a bunch of old drives that are starting to tap out. I have decided to put them out of their misery rather than trying to squeeze the last few months out of them.

[edit]

What I need

My main requirement for a new server is data redundancy. I'm tired of unreliable hard drives that fail with little or no prior indication. The new server's system drives will therefore be set up as a two disk raid 1 array. Most likely software raid.

Low purchase and running cost is also of concern.

This has been my most recent starting point when deciding what hardware I should buy.

[edit]

Planned purchases

Case

Chieftec Mesh Fulltower or Chieftec Mesh Miditower with a 400W PSU included.

I will require two 120mm fans and three to five 92mm fans as well as a fan controller with at least 4 channels to go with them. Maybe some filters as well.

Motherboard

Asus M2NBP-VM or M2NPV-VM (they seem to be fairly equal) with the AM2 socket and ECC memory support.

CPU

AMD Athlon X2 BE-2350.

RAM

I believe 2 GB of DDR2 ECC RAM of a decent brand will be enough.

Graphics card

I won't be needing one with the current choice of motherboard. It comes with integrated graphics.

Storage

2x 320 GB SATA HDDs (Western Digital RE, RE=Raid Edition with 5 year warranty and other goodies). These will be for my system drive in a software RAID 1 array.

Eventually I will consider getting the following as well:

4x 500 GB Western Digital RE2 for additional storage in a software RAID 5 array.

[edit]

Software

[edit]

Main Goal

Host OS: CentOS 5 (based on Red Hat Enterprise Linux)

VMware Server for Linux

I want to attempt this possible solution since this will give me more freedom. It will be much more dynamic to use VM machines than having just one main OS directly on top of the hardware. It allows for more experimentation, and easier backup.

[edit]

Fallback

Host OS: FreeBSD 6.x (or 7)

If the VMware solution isn't feasible I will fall back on having FreeBSD installed directly. If I have to go with this idea I will explore FreeBSD compatible virtual machine server software.

[edit]

Concept

Minimal host OS running multiple guest OSes with VMware Server.

[edit]

Virtual Machines

A short list of possible configurations of virtual machines. Each VM has some overhead in terms of RAM usage which limits the number of VMs I can run at one time. Possible overhead (up to 54 MB for a VM allocated up to 512 MB RAM) is not included in resource proposal per VM.

(This list was composed when I was aiming for 4 GB of RAM and more CPU power. It will be updated in time, but for now it stays.)

	Description	Guest OS	Service(s)	Resource proposal	Main storage	Comment
VM 1	Firewall/ router/ port forwarding	Free- or OpenBSD	ipfw with dummynets(?)	~128-256 MB RAM	Configuration saved within VMfs
VM 2	HTTP/FTP/radio/mail etc.	FreeBSD	Apache 2.x PureFTPd(?)	~256-512 MB RAM	Files accessed via NAS(?)
VM 3	DB/storage server	FreeBSD	MySQL 5.x, SVN, samba	~256-512 MB RAM	DB saved within VMware virtual disk Misc storage t.b.d.	Current database size ~120 MB
VM 4	minikai	Windows (2k?)	MSN, IRC, ICQ, Jabber, etc.	~512-768 MB RAM	Files saved within VMware virtual disk
VM 5	Misc Windows client	Windows (2k?)	DC/BT etc.	~512-768 MB RAM	Storage access to VM 3 via VM 1
Summary				~1.6-2.8 GB RAM / 4 GB

[edit]

Additional services

Some form of combined user database to connect mail, FTP and storage. LDAP?

[edit]

Storage

Different ways to manage VM/data storage. The easiest way to share access to data is to utilize the storage VM server.

One idea is to store the information in the same VMware virtual disk as the guest OS. This could work well enough when the required storage space is low.

A better idea is to store the data in a separate VMware virtual disk from the guest OS for easy backup. In the case of large storage requirements, like for the NAS server, this is a much better idea than the previous since it separates the OS from the data.

A third idea, mainly for the NAS server's more permanent storage of larger files, is to mount one or more partitions/devices raw. You wouldn't need to have data stored in VMware virtual disk files on such drives, which increases portability and access from outside of the VM if necessary.

[edit]

VMware tweaks

VMware clock drift (Linux guest)

This page recommends adding the following kernel options in your boot loader:

nosmp noapic nolapic clock=pit

Minimize clock drift in FreeBSD guest

Add this line to your /boot/loader.conf file:

hint.apic.0.disabled=1

General time options

Add these lines to your VM's .vmx config file:

tools.syncTime = "TRUE"

Additional .vmx file configuration parameters that may be useful if the above alone isn't working:

CONFIG_HZ_1000=y

[edit]

VMware discussion forum

VMware Server forum

My recently posted topic: VM and data storage (comments on my planned server upgrade is appreciated)

[edit]

Interesting topics

ram drive

Physical Disk Multiple VMservers

Multiple NICS in host machine

Shared Drive question..

VMDK Performance tweaks....how to obtain the best performance???

Vmware Server – Teaming / Bonding Multiple NICs in Linux

Add VMXNet and Heartbeat to Monowall!

VMware Server Tips’n’Tricks « Jayson Rowe’s Ramblings

[edit]

Otaking 2.0

From otaking wiki

Current revision

Contents

Hardware

Pre-existing hardware

What I need

Planned purchases

Software

Main Goal

Fallback

Concept

Virtual Machines

Additional services

Storage

VMware tweaks

VMware discussion forum

Interesting topics

Links

VMware

Tom's Hardware

Views

Personal tools

Navigation

Search

Toolbox

-=Plans for otaking 2.0=
+'''Plans for otaking 2.0'''
-==Hardware==
+=Hardware=
-New hardware will utilize most of my old gaming rig.
+Hardware plans have changed yet again, and it's close to being final. This time the focus is on relatively low power consumption.
-===Pre-existing hardware===
+==Pre-existing hardware==
-Case: Chieftec Dragon miditower with the insides covered with vibration and sound dampening sheets
+I have a bunch of old drives that are starting to tap out. I have decided to put them out of their misery rather than trying to squeeze the last few months out of them.
-Case fans: 5x Arctic Cooling 8cm fans running at 7 V (2 front, 2 rear, 1 psu)
+==What I need==
+My main requirement for a new server is data redundancy. I'm tired of unreliable hard drives that fail with little or no prior indication. The new server's system drives will therefore be set up as a two disk raid 1 array. Most likely software raid.
-CPU fan: Zalman 7000Cu
+Low purchase and running cost is also of concern.
-Motherboard: MSI Neo-FIS2R K8T800
+This has been my most recent starting point when deciding what hardware I should buy.
-CPU: AMD Athlon64 3000+ (2.0 GHz)
+==Planned purchases==
+'''Case'''
-RAM: 2 GB
+[http://www.chieftec.com/oka.html Chieftec Mesh Fulltower] or [http://www.chieftec.com/okx.html Chieftec Mesh Miditower] with a 400W PSU included.
-Graphics card: nVidia Geforce 6600GT (may be replaced by an ATI Rage Pro since any graphics performance is not required)
-===Planned purchases===
+I will require two 120mm fans and three to five 92mm fans as well as a fan controller with at least 4 channels to go with them. Maybe some filters as well.
-x 160-320 GB SATA HDDs; For use as system disks in a RAID 1 array.
-Fan controller for 3.5" drive bay to replace current 5.25" fan controller.
-Drive bay, 4 in 3 (four 3.5" internal bays in three 5.25" external slots, maybe the [http://www.komplett.se/k/ki.aspx?sku=306518 Cooler Master 4 in 3 module] at komplett.se). Hopefully this drive bay doesn't carry the vibrations too much to the chassi. I've grown to enjoy the silence achieved by not having hard drives directly in contact with the steel. Those vibrations can be really annoying.
+'''Motherboard'''
-==Software==
+Asus M2NBP-VM or M2NPV-VM (they seem to be fairly equal) with the AM2 socket and ECC memory support.
+'''CPU'''
+AMD Athlon X2 BE-2350.
+'''RAM'''
+I believe 2 GB of DDR2 ECC RAM of a decent brand will be enough.
+'''Graphics card'''
+I won't be needing one with the current choice of motherboard. It comes with integrated graphics.
+'''Storage'''
+x 320 GB SATA HDDs (Western Digital RE, RE=Raid Edition with 5 year warranty and other goodies).
+These will be for my system drive in a software RAID 1 array.
+Eventually I will consider getting the following as well:
+x 500 GB Western Digital RE2 for additional storage in a software RAID 5 array.
+=Software=
+==Main Goal==
 Host OS: CentOS 5 (based on Red Hat Enterprise Linux)
 VMware Server for Linux
+I want to attempt this possible solution since this will give me more freedom. It will be much more dynamic to use VM machines than having just one main OS directly on top of the hardware. It allows for more experimentation, and easier backup.
+==Fallback==
+Host OS: FreeBSD 6.x (or 7)
+If the VMware solution isn't feasible I will fall back on having FreeBSD installed directly. If I have to go with this idea I will explore FreeBSD compatible virtual machine server software.
-==Concept==
+=Concept=
 Minimal host OS running multiple guest OSes with VMware Server.
-==Virtual Machines==
+=Virtual Machines=
+A short list of possible configurations of virtual machines. Each VM has some overhead in terms of RAM usage which limits the number of VMs I can run at one time. Possible overhead (up to 54 MB for a VM allocated up to 512 MB RAM) is not included in resource proposal per VM.
+(This list was composed when I was aiming for 4 GB of RAM and more CPU power. It will be updated in time, but for now it stays.)
 {| border="1" cellpadding="4" cellspacing="1"
 !
 !Guest OS
 !Service(s)
-!Resources
+!Resource proposal
 !Main storage
 !Comment
 |VM 1
 |Firewall/
-port forward
+router/
-|FreeBSD
+port forwarding
-|(?)
+|Free- or OpenBSD
-|~64-192 MB RAM
+|ipfw with dummynets(?)
+|~128-256 MB RAM
 |Configuration saved within VMfs
 |
 |-valign="top"
 |VM 2
-|DB server
+|HTTP/FTP/radio/mail etc.
 |FreeBSD
-|MySQL 5.x
+|Apache 2.x
-|~192-256 MB RAM
+PureFTPd(?)
-|DB saved within VMfs
+|~256-512 MB RAM
-|Current database size ~100 MB
+|Files accessed via NAS(?)
+|
 |-valign="top"
 |VM 3
-|NAS
+|DB/storage server
 |FreeBSD
-|FreeNAS(?)
+|MySQL 5.x, SVN,
-|~128 MB RAM(?)
+samba
-|Files saved within VMfs(?)
+|~256-512 MB RAM
-|
+|DB saved within VMware virtual disk
+Misc storage t.b.d.
+|Current database size ~120 MB
 |-valign="top"
 |VM 4
-|HTTP server
+|minikai
-|FreeBSD
+|Windows (2k?)
-|Apache 2.x
+|MSN, IRC, ICQ, Jabber, etc.
-|~256 MB RAM
+|~512-768 MB RAM
-|Files accessed via NAS(?)
+|Files saved within VMware virtual disk
 |
 |-valign="top"
 |VM 5
-|Mail server
+|Misc Windows client
-|FreeBSD
+|Windows (2k?)
-|Courier-IMAP and Postfix
+|DC/BT etc.
-with SpamAssassin
+|~512-768 MB RAM
-|~128-256 MB RAM
+|Storage access to VM 3 via VM 1
-|Mailboxes accessed via NAS or local(?)
-|
-|-valign="top"
-|VM 6
-|FTP server
-|FreeBSD
-|PureFTPd(?)
-|~128-256 MB RAM
-|Files accessed via NAS(?)
 |
 |-valign="top"
 !
 !
-!~896-1344 MB RAM
+!~1.6-2.8 GB RAM
-/ 2048 MB
+/ 4 GB
 |}
-===More services===
-Some form of user database connection with mail, FTP and NAS. Candidates: LDAP?
+==Additional services==
+Some form of combined user database to connect mail, FTP and storage. LDAP?
+==Storage==
+Different ways to manage VM/data storage. The easiest way to share access to data is to utilize the storage VM server.
+One idea is to store the information in the same VMware virtual disk as the guest OS. This could work well enough when the required storage space is low.
+A better idea is to store the data in a separate VMware virtual disk from the guest OS for easy backup. In the case of large storage requirements, like for the NAS server, this is a much better idea than the previous since it separates the OS from the data.
+A third idea, mainly for the NAS server's more permanent storage of larger files, is to mount one or more partitions/devices raw. You wouldn't need to have data stored in VMware virtual disk files on such drives, which increases portability and access from outside of the VM if necessary.
+=VMware tweaks=
+[http://www.djax.co.uk/kb/linux/vmware_clock_drift.html VMware clock drift (Linux guest)]
+This page recommends adding the following kernel options in your boot loader:
+nosmp noapic nolapic clock=pit
+'''Minimize clock drift in FreeBSD guest'''
+Add this line to your /boot/loader.conf file:
+hint.apic.0.disabled=1
+'''General time options'''
+Add these lines to your VM's .vmx config file:
+tools.syncTime = "TRUE"
+Additional .vmx file configuration parameters that may be useful if the above alone isn't working:
+CONFIG_HZ_1000=y
+=VMware discussion forum=
+[http://www.vmware.com/community/forum.jspa?forumID=219 VMware Server forum]
+My recently posted topic: [http://www.vmware.com/community/thread.jspa?threadID=86721 VM and data storage (comments on my planned server upgrade is appreciated)]
+==Interesting topics==
+[http://www.vmware.com/community/thread.jspa?messageID=550980 ram drive]
+[http://www.vmware.com/community/thread.jspa?messageID=569943 Physical Disk Multiple VMservers]
+[http://www.vmware.com/community/thread.jspa?messageID=610886 Multiple NICS in host machine]
+[http://www.vmware.com/community/thread.jspa?messageID=569802 Shared Drive question..]
+[http://www.vmware.com/community/thread.jspa?messageID=550373 VMDK Performance tweaks....how to obtain the best performance???]
+[http://www.vmware.com/community/thread.jspa?messageID=521137 Vmware Server – Teaming / Bonding Multiple NICs in Linux]
+[http://communities.vmware.com/thread/35543 Add VMXNet and Heartbeat to Monowall!]
+[http://jaysonrowe.wordpress.com/2008/01/04/vmware-server-tipsntricks/ VMware Server Tips’n’Tricks « Jayson Rowe’s Ramblings]
+=Links=
+[http://www.anchorite.org/blog/2006/11/13/minimal-services-on-centos-44-mini-howto/ Minimal Services on CentOS 4.4 mini howto]
+[http://www.tuxyturvy.com/blog/index.php?/archives/37-Troubleshooting-VMware-ESX-network-performance.html Troubleshooting VMware ESX network performance]
+[http://www.thoughtpolice.co.uk/vmware/howto/centos-5-vmware-tools-install.html Installing VMware Tools in CentOS 5]
+[http://ezine.daemonnews.org/200702/fbsd_and_vmwsrvr.html Installing FreeBSD 6.x under VMware server]
+==VMware==
+[http://www.vmware.com/pdf/vmware_timekeeping.pdf VMware timekeeping]
+[http://www.vmware.com/pdf/WS6_Performance_Tuning_and_Benchmarking.pdf Performance Tuning and Benchmarking (pdf)]
+==Tom's Hardware==
+[http://www.tomshardware.com/2007/08/21/energy-efficient_computing_options/index.html Energy-Efficient Computing Options (21 august 2007)]
+[http://www.tomshardware.com/2007/08/16/ups_to_the_rescue/ UPSes To The Rescue (16 august 2007)]
+[http://www.tomshardware.com/2007/08/09/pc_power_supplies/ PC Power Supplies: More Important than You Think (9 august 2007)]
+[http://www.tomshardware.com/2007/06/01/the_power_saving_guide/ The Power Saving Guide, Part 2 (1 june 2007)]
+[http://www.tomshardware.com/2007/05/30/the_power_saving_guide/ The Power Saving Guide (30 may 2007)]