dave/site
1
0
Fork 0
mirror of https://github.com/davegallant/davegallant.github.io.git synced 2025-08-14 12:20:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: f36e0474838c4a5a009028c7d667143f1c9b1c3c

Browse Source
This commit is contained in:
davegallant
2022-01-03 06:09:55 +00:00
parent c754dc7ccd
commit 153181403e
40 changed files with 40 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
blog/2021/09/06/what-to-do-with-a-homelab/index.html
View File

@@ -166,7 +166,7 @@ Having multiple machines/nodes provides the advantage of increased redundancy, b
<h2 id=virtualization>Virtualization</h2>
<p>Virtualizing your hardware is an organized way of dividing up your machine&rsquo;s resources. This can be done with something such as a <em>Virtual Machine</em> or something lighter like a container using <em>LXC</em> or <em>runC</em>.
Containers have much less overhead in terms of boot time and storage allocation. This <a href=https://stackoverflow.com/questions/16047306/how-is-docker-different-from-a-virtual-machine>Stack Overflow answer</a> sums it up nicely.</p>
<p><img src=https://user-images.githubusercontent.com/4519234/132440142-3acd9c41-86e9-447d-b507-08b9a22b1cc6.png alt=image></p>
<p><img src=/images/proxmox.png alt=image></p>
<p>A hypervisor such as <a href=https://www.proxmox.com/en/proxmox-ve/get-started>Proxmox</a> can be installed in minutes on a new machine. It provides a web interface and a straight-forward way to spin up new VMs and containers. You&rsquo;ll want to ensure that VT-d and VT-X are enabled in the BIOS if you decide to install a hypervisor to manage your virtualization.</p>
<h2 id=services>Services</h2>
<p>So what are some useful services to deploy?</p>
@@ -179,7 +179,7 @@ Containers have much less overhead in terms of boot time and storage allocation.
<h2 id=vpn>VPN</h2>
<p>You could certainly setup and manage your own VPN by using something like <a href=https://openvpn.net/community-downloads/>OpenVPN</a>, but there is also something else you can try: <a href=https://tailscale.com/>tailscale</a>. It is a very quick way to create fully-encrypted connections between clients. And by using its <a href=https://tailscale.com/kb/1081/magicdns/>MagicDNS</a>, it is a truly magical solution. If one of your nodes has a hostname of <code>plex</code>, you can simply access it by referring to its hostname (i.e <code>ssh plex@plex</code>). This way you can create a secure tunnel to your homelab from anywhere.</p>
<h2 id=monitoring>Monitoring</h2>
<p><img src=https://user-images.githubusercontent.com/4519234/133014770-4b799051-e34f-4b29-86c0-fbb9480cd63f.png alt=dashboard></p>
<p><img src=/images/netdata.png alt=dashboard></p>
<p>Monitoring can become an important aspect of your homelab after it starts to become something that is relied upon. One of the simplest ways to setup some monitoring is using <a href=https://www.netdata.cloud/>netdata</a>. It can be installed on individual containers, VMs, and also a hypervisor (such as Proxmox). All of the monitoring works out of the box by detecting disks, memory, network interfaces, etc.</p>
<p>Additionally, agents installed on different machines can all be centrally viewed in netdata, and it can alert you when some of your infrastructure is down or in a degraded state. Adding additional nodes to netdata is as simple as a 1-line shell command.</p>
<p><a href=https://grafana.com/>Grafana</a> is another open source analytics and monitoring solution. If you are looking for ideas, check out <a href=https://www.wikimedia.org/>Wikimedia</a>&rsquo;s <a href=https://grafana.wikimedia.org/>public Grafana</a>.</p>
@@ -214,7 +214,7 @@ Previous</span>
</main>
<footer id=footer class=footer>
<div class="container sep-before"><div class=copyright>
<p> &copy; 2020-2021 Dave Gallant </p>
<p> &copy; 2020-2022 Dave Gallant </p>
</div>
</div>
</footer>