aboutsummaryrefslogtreecommitdiff
path: root/content/post/framework-server-p2/index.md
diff options
context:
space:
mode:
authorKumar Damani <me@kumardamani.net>2024-08-12 18:01:11 +0000
committerKumar Damani <me@kumardamani.net>2024-08-12 18:01:11 +0000
commit3a2dd35f4b6b6414ec3ba4af4e0984598ff9aa35 (patch)
tree1dda0c3650d0629e364169a17e9cc85e53e57d27 /content/post/framework-server-p2/index.md
parent2ad56f29b3a5b37aaf3a0500cdd2c7955c4f62e2 (diff)
new post
Diffstat (limited to 'content/post/framework-server-p2/index.md')
-rw-r--r--content/post/framework-server-p2/index.md78
1 files changed, 45 insertions, 33 deletions
diff --git a/content/post/framework-server-p2/index.md b/content/post/framework-server-p2/index.md
index c30e2e3..85b7aff 100644
--- a/content/post/framework-server-p2/index.md
+++ b/content/post/framework-server-p2/index.md
@@ -1,94 +1,106 @@
---
-title: "Making my Framework 13 a laptop again"
+title: "Letting my Framework 13 be a laptop again"
date: 2024-06-03T13:43:05-04:00
-draft: true
-description: "Moving to a more conventional home-lab."
+draft: false
+description: "Graduating to a more conventional home-lab."
+author: "Kumar Damani"
---
My process of converting my Framework server back into a laptop.
<!--more-->
-My wife is in need of an upgrade from her 2015 Macbook Pro,
-but shelling out a cool $1600 + tax for one of the shiny new *M* Macbooks
+My wife needs an upgrade from her 2015 MacBook Pro,
+but shelling out a cool $1600 + tax for one of the shiny new *M* MacBooks
for the 16GB variant hardly seems an ideal proposition now that Apple
has relinquished consideration of its customers who
would prefer to amortize upgrades over the lifespan of a machine.
-It seems that leaving the Mac platform is our only consumer-friendly option
+It seems that leaving the Mac platform is our only consumer-friendly option,
which avoids fighting a losing battle with Apple w.r.t. upgradability.
> :wave: Framework has entered the chat.
-Meanwhile, Framework seems to have up-held its promise of providing a path
+Meanwhile, Framework seems to have upheld its promise of providing a path
to long-term upgradability for its products.
-The new Ryzen main-boards being compatible with my original Framework 13
+The new Ryzen mainboards being compatible with my original Framework 13
(2021) is an example of this.
So at this point, I'm far more inclined to commit to the Framework ecosystem
for my wife (and probably myself) than Apple.
Other than the initial non-trivial pain of migrating her from macOS to Windows,
-she should have a substantially better user-experience running all of her
+she should have a substantially better user-experience running all of the
Adobe crapware she wants on my old Framework.
-*The only problem is that my entire home-lab currently runs on my Framework.*
+**The only problem is that my entire home-lab currently [runs on my Framework](/post/framework-server) 😰.**
-Time to go shopping :shopping_cart:.
+:shopping_cart: time!
# The Pledge
-We'll be using second-hand equipment as much as possible. Afterall,
-the point of all this is to avoid spending the $1600 for a new laptop.
+We'll be using second-hand equipment as much as possible. After all,
+the point of all this is to avoid spending $1600 on a new laptop.
So we should be well under that to make it worthwhile.
+I picked these up from eBay:
+
+![server front](server-front.png)
+![ethernet adapter](ethernet.png)
+
| Part | Price (shipped) |
| -------------- | --------------- |
-| - HP Z240 Workstation Intel Xeon 3.4GHz 16G Ram 180G SSD Nvidia K620 | $150 |
-| - Mellanox ConnectX-2 PCIe x8 10Gbe SFP+ network card | $23 |
+| HP Z240 Workstation Intel Xeon 3.4GHz 16G RAM 180G SSD Nvidia K620 | $150 |
+| Mellanox ConnectX-2 PCIe x8 10Gbe SFP+ network card | $23 |
-> My Framework currently has 32GB memory, and while this is much less
-I would still be okay with my current utilization for my current workload.
+> My Framework currently has 32GB of memory, and while this is much less,
+it will still be okay with my current utilization for my current workload.
One nice thing about this case is that it would be possible to rack-mount this
-workstation side-ways on a standard rack shelf if I decide to go that
+workstation sideways on a standard rack shelf if I decided to go that
route in the future.
-Also, I don't presently have 10Gb networking equipment at my home to actually plug
+Also, I don't presently have 10Gb networking equipment at home to plug
anything into that network card, but I'm getting it now for future-proofing.
IPMI would have been nice-to-have, but I decided that for this price, and the
bonus of that Nvidia K620 was too good to pass up! This is an
-immediate upgrade from my current integrated Iris gpu in my Framework server.
+immediate upgrade from my current integrated Iris GPU on my Framework server.
+
+![server inside](server-inside.png)
All of my home-lab VMs, and LXC containers run within Proxmox.
-So I setup a fresh Promox here.
+So I set up a fresh Proxmox here.
Fortunately for me, `lspci` showed all the hardware on the first go.
-But in order to use (pass-through) the Nvidia GPU in my guests,
-I need to first setup the Proxmox host.
+But to use (pass-through) the Nvidia GPU in my guests,
+I need to first set up the Proxmox host.
See my git repo for what I did to make this work.
# The Turn
-In order to make the migration of our services *less painful*,
+To make the migration of our services *less painful*,
we utilize Proxmox's migration features.
We just need to make sure our nodes are part of a cluster.
**Create the cluster on the old node.**
-Then from the new node, **join** the existing cluster.
+Then, from the new node, we **join** the existing cluster.
> Proxmox 8 will not let a node with existing guests join a cluster.
# The Prestige
-Now it really is as easy as selecting a VM, or a LXC container and hitting
-the Migrate button, and watching your VM fly away to the new node!
-For VMs with large OS disks it takes a little longer to copy over
+Now it really is as easy as selecting a VM or an LXC container, hitting
+the Migrate button, and watching your guest fly away to the new node!
+For guests with large OS disks, it takes a little longer to copy over
since my network is slow.
-Eventually I will use Ceph backed VM storage to make this a zero-downtime op.
+Eventually, I will use Ceph-backed VM storage to make this a zero-downtime op.
-In a few mins, I was able to knock out all of my services.
-Refer to my github project to see how I handled the Nvidia K60 pass-through
+In a few minutes, I could knock out all of my services.
+Refer to my gitlab project to see how I handled the Nvidia K60 pass-through
to my Nextcloud AIO instance and Plex guests.
+Here's what my "rack" looks like now:
+
+![current lab](current-lab.jpg)
+
Once everything was back online, I powered down the old Framework server
-and re-installed it back into its laptop chassis, bought a W10 license, and
-proceeded to finish the rest of the install.
+and re-installed it back onto its laptop chassis, bought a W10 license, and
+finished the rest of the installation.