Sometimes in life, you get even bigger servers, with MOAR NICs then you can count on one hand.
At rAge we had 12 of the bad boys.

Here, we will use 5 in a server with 5 x 1 GbE on the Mobo, and an add in card with another 4 NICs.

We will only use 5 for now, as we dont wanna kill that switch so early in its lifetime!

This is what we are working with:

root@gamecache:/# networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback n/a n/a
2 ens7f0 ether n/a n/a
3 ens7f1 ether n/a n/a
4 ens4f0 ether n/a n/a
5 ens4f1 ether n/a n/a
6 ens5f0 ether n/a n/a
7 ens5f1 ether n/a n/a
8 enp12s0f0 ether n/a n/a
9 enp12s0f1 ether n/a n/a
10 enp16s0 ether n/a n/a

10 links listed.

That is 9 NICs, all 1GbE. So lets team up!

Here is what we would use in our interfaces file:

# The loopback network interface
auto lo
iface lo inet loopback

#Bond1
auto bond0
iface bond0 inet static
address 192.168.1.33
netmask 255.255.255.0
bond-slaves none
bond-mode 4
bond-miimon 100

#we will use port 1,2,3,4,A21 as we know they work

#Port 1
auto ens7f0
iface ens7f0 inet manual
bond-master bond0
bond-primary ens7f0 ens7f1 ens4f0 ens4f1 ens5f1

#Port 2
auto ens7f1
iface ens7f1 inet manual
bond-master bond0
bond-primary ens7f0 ens7f1 ens4f0 ens4f1 ens5f1
#Port 3
auto ens4f0
iface ens4f0 inet manual
bond-master bond0
bond-primary ens7f0 ens7f1 ens4f0 ens4f1 ens5f1

#Port 4
auto ens4f1
iface ens4f1 inet manual
bond-master bond0
bond-primary ens7f0 ens7f1 ens4f0 ens4f1 ens5f1

#Port 5
auto enp16s0
iface enp16s0 inet dhcp

#Add on 2 Port 1
auto ens5f1
iface ens5f1 inet manual
bond-master bond0
bond-primary ens7f0 ens7f1 ens4f0 ens4f1 ens5f1

#Add on 2 Port 2
#auto ens5f0
#iface ens5f0 inet dhcp
Quite a few NICs, and now we have 5Gbps at hand, with a total of 9 if we need in future.

Off to the DC we go!

Sometimes, we can use allll of the IPs, we don’t get the luxury of having an infinite amount available, and we need to make do with ONE IP.

Well, NGINX doesnt stress about that, we just need to set it up. Nginx will take a look at the Host Headers, and use those to determine what server the user is looking for.

So here is more-or-less how it works:

===
server {
listen www.domain1.com:80;
access_log /var/log/nginx/host.domain1.access.log main;
root /var/www/domain1;
server_name www.domain1.com;
xxx
}
}

server {
listen www.domain2.com:80;
access_log /var/log/nginx/host.domain2.access.log main;
root /var/www/domain2;
server_name www.domain2.com;
xxx
}
===

Now the important thing is the server_name.

Here, you put the redirected DNS hosts, and bob is your uncle… It works with the StreamCache setup perfectly.

So, stats from the SteamCache at rAge 2015

16.4TB was recieced through the internet IP, and 51.1TB was sent out by the cache’s Steam IP.
The highest peak of traffic to the cache from the LAN bond, was 10.07Gbps, on Friday morning.
The max tracked connections to the cache was 1400 connections per second.
The max System Load on the box was around 15
We hit 5000 Read/Writes per second as a max.

So, it is in motion!
The event is slowly being built up, and its quite impressive to see.

From the LAN side, we have put out the 12KM odd of LAN cable, and the associated power cables. Nothing is live quite yet, and we await the networking equipment, but this will come in time! The servers were setup and are now running, what beasts.
One issue I ran into was the Hardware VS Software RAID.. There was a RAID done on the server as is with its RAID Controller, then Ubuntu was trying to RAID itself with its Software raid. Which really confused me. But after stumbling around I found this out, removed the Ubuntu RAID, removed the Hardware RAID, and boom, we were able to raid ALL the drives for 1TB of SSD goodness.
I am still not sure if we should have left one drive out of the RAID for its boot drive, but eh. Time will tell.

For now, all 8 of the 120GB SSDs are in RAID 0 for around 1TB of space, I didn’t really want -1 drive for the OS, as we were a little low on space as is.
We have 128GB of RAM in this BEAST, and she will be our main Steam box.

I ran into the first issue quite quickly, I wasn’t able to get onto the net as we haven’t set ours up yet, and the Wifi inside the event wasn’t gonna work for a server that REALLY doesn’t have WiFi capabilities.

But thanks to this link: http://askubuntu.com/questions/359856/share-wireless-internet-connection-through-ethernet
we should be able to connect the server to my lappy, and share its connection from the WiFi or from my 3G hotspot to it. Boom. Then we can get the files and perhaps updates we need onto the server.

Then we are estimating that the internet from IS will get there on Thursday.

And here I leave you with some bad images of some of the setup

:

Yeah, I’ll be that guy and make a first post.
Yolo.

Here is where I will write about, you guessed it,
ALL THE THINGS.