Merge branch 'master' of vcs.enp.one:omni/omni-docs

This commit is contained in:
Ethan Paul 2019-08-31 20:47:42 -04:00
commit 38e323c072
7 changed files with 151 additions and 2 deletions

View File

@ -0,0 +1,29 @@
# Ubiquiti EdgeRouter Lite
**Quick Links:**
* [Official spec sheet](https://dl.ubnt.com/datasheets/edgemax/EdgeRouter_DS.pdf)
* [Software/firmware downloads](https://www.ui.com/download/edgemax/edgerouter-lite)
* ["Which EdgeRouter Should I Use?"](https://help.ubnt.com/hc/en-us/articles/219652227--EdgeRouter-Which-EdgeRouter-Should-I-Use-)
![EdgeRouter Lite](../img/erl.jpg)
Ubiquiti's EdgeMax platform is the closest thing you can get to an enterprise
grade router for less than $200. I bought my EdgeRouter Lite (ERL) for my first
apartment almost five years ago and I have never once regretted my decision.
The only time I've ever thought about giving it up was when I briefly thought
about buying a bigger EdgeRouter.
The EdgeMax/EdgeRouter operating system, creatively named EdgeOS, is a fork of
the open source [VyOS](https://vyos.io/) and is loaded with excellent features
and a killer web UI.
The ERL is fanless and sports three gigabit ethernet ports, as well as a
dedicated serial console port for when I inevitably lock myself out.
It's also rackmountable:
* [EdgeRouter Lite rackmount kit](http://www.ispsupplies.com/categories/Indoor-Enclosures/KAM-Fab-UB-RM1.html)
---
*Last updated `{{ git_revision_date }}`*

View File

@ -0,0 +1,72 @@
# Dell PowerEdge R410
**Quick links:**
* [Official Spec Sheet](https://www.dell.com/downloads/emea/products/R410_spec_sheet.pdf)
![Dell R410](../img/r410.jpg)
The PowerEdge R400 series is a full-depth dual-CPU server platform that usually
has a 4x3.5" drive arrangement, but did have a variant with 6x2.5" drives as
well. The R410 generation uses DDR3 ECC memory and supports the
[Gulftown](https://ark.intel.com/content/www/us/en/ark/products/codename/29886/gulftown.html) generation of Intel CPUs.
The backbone of my homelab is made up of two Dell R410's: `romulus` and
`remus`. Together the form the bulk of my system's compute power, storage
capacity, and hosting capabilities. Even with as much stuff as I have crammed
onto them I am still nowhere near to using their full potential.
| Hostname | Model | CPU | Memory | Storage | OS |
|----------|---|---|---|---|---|
| `remus` | 2010 PowerEdge R410 | Intel Xeon e5500 Series | 48GB DDR3 ECC | 4x WD Red 3TB, RAID 5 | CentOS 7.5 |
| `romulus`| 2011 PowerEdge R410 | Intel Xeon x5600 Series | 96GB DDR3 ECC | 4x HST Travelstar 146GB, RAID 5 | CentOS 7.5 |
## Romulus
Romulus is the newer of the two servers, coming from the 2011 series of the
R410. It has a standard 4x3.5" drive configuration and two Intel Xeon x5600
series CPUs. I've installed a Dell PERC h310 and four 146GB 10K SAS drives in
it, giving it considerably higher R/W throughput rates than its companion.
## Remus
Remus will always be special because it was my first server, literally pulled
out of a dumpster my sophomore year of college. Since then I've replaced the
motherboard, drives, backplane, CPUs, and memory (which admittedly does start to evoke the [Ship of Theseus](https://en.wikipedia.org/wiki/Ship_of_Theseus)).
Remus is older than Romulus, coming from the 2010 generation of the R410. Like
Romulus it also has the standard 4x3.5" drive configuration, however it houses
four 3TB Western Digital Red NAS drives which make up the bulk of the homelabs
data storage capacity. The Intel Xeon e5500 series processors also make it
slightly slower than Romulus, though it has more memory.
Remus also sacrificed its DVD drive to host a 256GB SSD boot drive which runs the host operating system.
## Configuration
My preferred server-side operating system is [CentOS](https://www.centos.org/),
and as such both Romulus and Remus are running CentOS 7.5 on bare metal.
Both are configured to run [KVM for virtualization](../virtualization/vms.md)
and Romulus is setup with an instance of the Open Virtualization Manager
(OVirt) to manage the virtual machines running on both hosts.
See the [configuration section](../config.md) for more information.
## Upgrades
These are planned upgrades that will eventually be made to these systems:
* Upgrade Remus from e5500 to x5600 processors. This will allow virtual
machines running on one server to be live-migrated to the other.
* Balance RAM distribution across the two servers, moving memory out of
Romulus and into Remus.
* Upgrade memory modules running at 1333MHz to modules running at 1600MHz.
This will allow virtual machines running on one server to be live-migrated to
the other
* Restructure shared and internal storage. See the ongoing
[redundancy improvement efforts](../roadmap/redundancy.md)
---
*Last updated `{{ git_revision_date }}`*

BIN
docs/img/erl.jpg Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 41 KiB

View File

Before

Width:  |  Height:  |  Size: 8.8 KiB

After

Width:  |  Height:  |  Size: 8.8 KiB

BIN
docs/img/r410.jpg Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 25 KiB

View File

@ -0,0 +1,49 @@
# Redundancy Efforts
Currently the Homelab suffers from a critical lack of data redundancy. Fixing
this will require improvements both to the hardware and software layout of the
homelab.
## Goals
1. Improve data storage redundancy to mitigate loss-risk associated with
physical failures
2. Improve failover capacity, allowing for certain systems to be taken offline
in a controlled manner without losing services
3. Institute a backup creation and management system to reduce risk of
data corruption
## Storage Redundancy
### Current State
All primary data is stored on a single 8TB drive array in hardware RAID 5. The
array is comprised of four Western Digital Red NAS drives, each with a 3TB
capacity. The array is fault tolerant, but not redundant. Secondary data is
stored in one of three places: the primary array, a secondary drive array, or
the 256GB boot drive of a single server.
The secondary array is 470GB aggregate, comprised of four HST Travelstar 10K
SAS drives, also in hardware RAID 5. The boot drive of the server is a consumer
grade SSD. None of these systems are backed up or redundant.
Primary data includes personal data including books, projects, documents,
documentation, photos, etc. Secondary data is application configuration
information and deployed hosting systems.
In addition to the primary and secondary data, there is the tertiary data of
a media collection (movies, TV, etc). Tertiary data is stored on the primary
drive array, only because there is nowhere else with enough capacity to store
it.
### Desired State
Data should be more efficiently segregated by priority tier. The two drive
arrays should be split up into two arrays each: a pair of 3TB arrays using the
WD Red's and a pair of 146GB array's using the Travelstars. Each pair of arrays
should be installed into the two [Dell R410's](../hardware/poweredge-r410.md).
Secondary data exists on the 146GB arrays on each server and is routinely
backed up to the 3TB arrays on the same server.
Primary data should be cloned on both of the 3TB arrays. Primary data should
be backed up externally to a third server.

View File

@ -5,7 +5,7 @@ theme:
palette: palette:
primary: black primary: black
accent: amber accent: amber
favicon: images/favicon.ico favicon: img/favicon.ico
logo: https://cdn.enp.one/img/logos/e-w-sm.png logo: https://cdn.enp.one/img/logos/e-w-sm.png
plugins: plugins:
- git-revision-date - git-revision-date
@ -40,4 +40,3 @@ nav:
- Dell PowerEdge R410: hardware/poweredge-r410.md - Dell PowerEdge R410: hardware/poweredge-r410.md
- EdgeRouter Lite: hardware/erl.md - EdgeRouter Lite: hardware/erl.md
- Workstations: hardware/workstations.md - Workstations: hardware/workstations.md