The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Difference between revisions of "Funtoo Compute Initiative"
Line 26: | Line 26: | ||
# {{c|net.eth0}} will be configured using [[Networking|Funtoo Networking]] as {{c|interface-noip}}, and will be connected to a WAN switch | # {{c|net.eth0}} will be configured using [[Networking|Funtoo Networking]] as {{c|interface-noip}}, and will be connected to a WAN switch | ||
# {{c|net.brwan}} will have {{c|net.eth0}} as slave, and will be configured with a routable IPv4 address. | # {{c|net.brwan}} will have {{c|net.eth0}} as slave, and will be configured with a routable IPv4 address. | ||
# {{c|net.eth1}} will be configured using [[Networking|Funtoo Networking]] as {{c|interface- | # {{c|net.eth1}} will be configured using [[Networking|Funtoo Networking]] as {{c|interface-noip}}, and will be connected to a fast private LAN switch. | ||
# {{c|net.brlan}} will have {{c|net.eth1}} as slave, and will be configured with a non-routable static IPv4 address. | # {{c|net.brlan}} will have {{c|net.eth1}} as slave, and will be configured with a non-routable static IPv4 address. | ||
The network and initial server configuration will be covered in more detail below. | The network and initial server configuration will be covered in more detail below. |
Revision as of 04:51, October 27, 2015
For many years, the Funtoo project has been using Funtoo Linux for its entire infrastructure. A few years ago, we began to allow Funtoo Linux users to use our OpenVZ-based infrastructure for hosting, development and other projects, which you can learn more about at Funtoo Hosting.
The 'Funtoo Compute Initiative is an effort to document how Funtoo sets up servers and its container infrastructure, including everything from ordering of bare metal, to deployment, operation and maintenance. In short, it's our effort to share all our tricks with you, so you can use Funtoo Linux to quickly and inexpensively deploy very powerful hosting and container-based compute solutions.
Reference Hardware
The hardware that the Funtoo Project has used for its last two server deployments are documented below:
- HP Proliant DL 160 Generation 6 (G6), with 48GB RAM and two 6-core Intel Xeon x5650 (2.66 GHz Westmere) processors (25 CPU threads total.) Cost: Approx $750 USD used (off-lease) on eBay (Other alternatives: DL 360 G7 -- search eBay for the best off-lease options.)
- Crucial MX200 1TB Solid State Disk. Cost: Approx $330. Also consider using a 256GB disk for the root filesystem and a second 1TB disk that is dedicated to OpenVZ containers.
- 1 tube of high-quality thermal grease
The above hardware allows you to build a 1U, 12-core, 24-thread, 48GB compute platform with 1TB of SSD storage for right around $1100. Once receiving the off-lease server, it's recommended that you remove the CPU heat sinks, clean them and the tops of the CPUs with alcohol cleaning pads, and re-apply high-quality thermal grease. Based on my experience, the thermal grease on off-lease servers is often in need of re-application.
Hardware Deployment and Initial Setup
Place the 1TB in drive bay 1 as a single ATA disk, and install the Intel64-westmere build of Funtoo Linux following our Install instructions, using the following recommended configuration:
Configuration overview:
- I typically allocate 1GB for the /boot filesystem
- It's a good idea to have 24-48GB for swap, for emergencies
- Use ext4 for the root filesystem. OpenVZ is optimized for ext4.
- Rather than using debian-sources, use the
openvz-rhel6-stable
kernel with thebinary
USE flag set. - Emerge
sys-cluster/vzctl
and add thevz
service to the default runlevel (this is covered below.) net.eth0
will be configured using Funtoo Networking asinterface-noip
, and will be connected to a WAN switchnet.brwan
will havenet.eth0
as slave, and will be configured with a routable IPv4 address.net.eth1
will be configured using Funtoo Networking asinterface-noip
, and will be connected to a fast private LAN switch.net.brlan
will havenet.eth1
as slave, and will be configured with a non-routable static IPv4 address.
The network and initial server configuration will be covered in more detail below.